Elia Bolg

I was under the impression that when you extend the abstract class, you provide the type T (Config as in my example) so in turn the entityClass would be : private Config entityClass; I'm not getting the Class<T> in this case.

the following code was auto generated by Netbeans 7.3:

the abstract class:
public abstract class AbstractFacade<T> { private Class<T> entityClass; // notice the Class<T> public AbstractFacade(Class<T> entityClass) { this.entityClass = entityClass; } protected abstract EntityManager getEntityManager(); public void create(T entity) { getEntityManager().persist(entity); } . . . }


extending the absrtact class:
@Stateless public class ConfigFacade extends AbstractFacade<Config> { @PersistenceContext(unitName = "MyPU") private EntityManager em; @Override protected EntityManager getEntityManager() { return em; } public ConfigFacade() { super(Config.class); } }

why the following is not equivalent?:

my modified abstract class:
public abstract class AbstractFacade<T> { private T entityClass; // I simply used T here public AbstractFacade(T entityClass) { // and here this.entityClass = entityClass; } protected abstract EntityManager getEntityManager(); public void create(T entity) { getEntityManager().persist(entity); } . . . }

we had the following requirement for an SAP WebDynpro for java application:

system administrator must be able to design screen/forms at runtime based on the users requirements and assign the screen/form to the said user.
so i wrote a limited but very capable screen builder in webdynpro for java WYSIWYG style. you had the supported UI controles in one panel (Label, InputField, Groupbox, Transparent Container) , a tree-view of the layout of the screen being built in another panel, another panel shows the different properties for a selected UI components which the user can tweak (like font size for a label for example or information source tag for Inputfield) and finally you had a panel which shows you what your screen looks like after each UI teak or after addition of new UI component.

while the administrator build the screen, an XML representation of the screen's layout and UI components and their various properties is generated at the back and kept in sync. the XML then will be saved in the database. when the screen is called by the system user(s), we load the XML extract the information source tags and fill the values of those tags and then regenerate the screen for the user the way it was built.

all is good,

but because of the lack of dragAndDrop in WebDynpro, the administrator has to work with the tree-view of the layout that represent the screen. he has to find the node that represent a certain UI component and place the next UI component below or above. this process is tiresome and slow when you are building complex screen
with nested elements.

we are doing phase two of this project and I though maybe we can use an Java Applet for the screen builder. I'm looking for a tool I can customize for this purpose. it has to support drag and drop and can easily generate XML afterwards. is should be something like Netbeans Matisse but simpler (like UML diagramming tools).

so, could anyone please recommend a library or a tool I can use to achieve this? or do you have another thought? ..... I'm open for new Ideas.

right now i'm testing with WSDL2Java tool. i regenerated the web service starting from the WSDL . probably i'll finish it today and i'll update this thread.

Thank you for your reply, i'll try out some of what you pointed out.

i'm using the same version of Axis2 which is 1.2 on both servers.

one thing though, i'm not packing Axis2 in my war file, i simply deployed Axis2.war as a web application on glassfish. my web service is nothing more than a simple java class that contains my business logic in public methods (no WS API what so ever, just pure business logic and DB code). i package my classes in a jar then rename it as .aar and deploy it using the Axis2.war deployed on glassfish, it automatically generate the WSDL,XS etc. that is why i was surprised the responses looked a bit different from axis2 on webshpere.

i'm welling to drop Axis2 as long as i can find a way to keep the same wsdl/ response structure of my legacy web service since i can't touch the client code for any adjustments( i'm quite novice when it comes to WS )

i'm not using any ws api for this web service. it is just a POJO deployed to axis2.war which generates the WSDL and takes care of the rest. i want to know where is this difference in the response coming from as those responses are serialized by axis2.war on both websphere and glassfish? is there any way i can keep the web service the same and make axis2 produce the same response it produces when it was deployed on websphere.

as for the client, it was generated by MSVS2003 by adding a "Web Reference" to the C# project. changing the client code is out of the question as it has been deployed in many locations including remote areas.



here is the wsdl (it is the same autogenerated wsdl of the serivce on both app servers).
<wsdl:definitions targetNamespace="http://myService"> <wsdl:documentation>myService4QA</wsdl:documentation> <wsdl:types> <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://sql.java/xsd"> <xs:element name="SQLException" type="ax21:SQLException"/> <xs:complexType name="SQLException"> <xs:complexContent> <xs:extension base="xs:Exception"> <xs:sequence> <xs:element name="errorCode" type="xs:int"/> <xs:element name="nextException" nillable="true" type="ax21:SQLException"/> <xs:element name="sQLState" nillable="true" type="xs:string"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:schema> <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://myService/xsd"> <xs:element name="getActualQTY"> <xs:complexType> <xs:sequence> <xs:element name="bookingRef" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="getActualQTYResponse"> <xs:complexType> <xs:sequence> <xs:element name="return" nillable="true" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="SQLExceptionFault"> <xs:complexType> <xs:sequence> <xs:element name="SQLException" nillable="true" type="ns0:SQLException"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="createPrintJob"> <xs:complexType> <xs:sequence> <xs:element name="booking" nillable="true" type="xs:string"/> <xs:element name="printerName" nillable="true" type="xs:string"/> <xs:element name="du_type" nillable="true" type="xs:string"/> <xs:element name="actualQTY" nillable="true" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="createPrintJobResponse"> <xs:complexType> <xs:sequence> <xs:element name="return" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="ping"> <xs:complexType> <xs:sequence> <xs:element name="message" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="pingResponse"> <xs:complexType> <xs:sequence> <xs:element name="return" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="print"> <xs:complexType> <xs:sequence> <xs:element name="bookingRef" nillable="true" type="xs:string"/> <xs:element name="printer" nillable="true" type="xs:string"/> <xs:element name="du_type" nillable="true" type="xs:string"/> <xs:element name="qty" nillable="true" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="printResponse"> <xs:complexType> <xs:sequence> <xs:element name="return" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="printJob"> <xs:complexType> <xs:sequence> <xs:element name="jobID" nillable="true" type="xs:int"/> <xs:element name="page" nillable="true" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="printJobResponse"> <xs:complexType> <xs:sequence> <xs:element name="return" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="printLocal"> <xs:complexType> <xs:sequence> <xs:element name="bookingRf" nillable="true" type="xs:string"/> <xs:element name="du_type" nillable="true" type="xs:string"/> <xs:element name="actualQuantity" nillable="true" type="xs:int"/> <xs:element name="count" nillable="true" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="printLocalResponse"> <xs:complexType> <xs:sequence> <xs:element name="return" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="printWithArray"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" name="par" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="printWithArrayResponse"> <xs:complexType> <xs:sequence> <xs:element name="return" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="getPrintJob"> <xs:complexType> <xs:sequence> <xs:element name="printerName" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="getPrintJobResponse"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" name="return" nillable="true" type="ns:PrintJob"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="PrintJob" type="ns:PrintJob"/> <xs:complexType name="PrintJob"> <xs:sequence> <xs:element name="bookingRef" nillable="true" type="xs:string"/> <xs:element name="jobID" type="xs:int"/> <xs:element name="printerName" nillable="true" type="xs:string"/> <xs:element name="qty" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:schema> </wsdl:types> <wsdl:message name="printLocalMessage"> <wsdl:part name="part1" element="ns1:printLocal"/> </wsdl:message> <wsdl:message name="printLocalResponse"> <wsdl:part name="part1" element="ns1:printLocalResponse"/> </wsdl:message> <wsdl:message name="createPrintJobMessage"> <wsdl:part name="part1" element="ns1:createPrintJob"/> </wsdl:message> <wsdl:message name="createPrintJobResponse"> <wsdl:part name="part1" element="ns1:createPrintJobResponse"/> </wsdl:message> <wsdl:message name="createPrintJobFault"> <wsdl:part name="part1" element="ns1:SQLExceptionFault"/> </wsdl:message> <wsdl:message name="printJobMessage"> <wsdl:part name="part1" element="ns1:printJob"/> </wsdl:message> <wsdl:message name="printJobResponse"> <wsdl:part name="part1" element="ns1:printJobResponse"/> </wsdl:message> <wsdl:message name="getActualQTYMessage"> <wsdl:part name="part1" element="ns1:getActualQTY"/> </wsdl:message> <wsdl:message name="getActualQTYResponse"> <wsdl:part name="part1" element="ns1:getActualQTYResponse"/> </wsdl:message> <wsdl:message name="printWithArrayMessage"> <wsdl:part name="part1" element="ns1:printWithArray"/> </wsdl:message> <wsdl:message name="printWithArrayResponse"> <wsdl:part name="part1" element="ns1:printWithArrayResponse"/> </wsdl:message> <wsdl:message name="printMessage"> <wsdl:part name="part1" element="ns1:print"/> </wsdl:message> <wsdl:message name="printResponse"> <wsdl:part name="part1" element="ns1:printResponse"/> </wsdl:message> <wsdl:message name="pingMessage"> <wsdl:part name="part1" element="ns1:ping"/> </wsdl:message> <wsdl:message name="pingResponse"> <wsdl:part name="part1" element="ns1:pingResponse"/> </wsdl:message> <wsdl:message name="getPrintJobMessage"> <wsdl:part name="part1" element="ns1:getPrintJob"/> </wsdl:message> <wsdl:message name="getPrintJobResponse"> <wsdl:part name="part1" element="ns1:getPrintJobResponse"/> </wsdl:message> <wsdl:portType name="myService4QAPortType"> <wsdl:operation name="printLocal"> <wsdl:input message="axis2:printLocalMessage" wsaw:Action="urn:printLocal"/> <wsdl:output message="axis2:printLocalResponse"/> </wsdl:operation> <wsdl:operation name="createPrintJob"> <wsdl:input message="axis2:createPrintJobMessage" wsaw:Action="urn:createPrintJob"/> <wsdl:output message="axis2:createPrintJobResponse"/> <wsdl:fault message="axis2:createPrintJobFault" name="createPrintJobFault"/> </wsdl:operation> <wsdl:operation name="printJob"> <wsdl:input message="axis2:printJobMessage" wsaw:Action="urn:printJob"/> <wsdl:output message="axis2:printJobResponse"/> </wsdl:operation> <wsdl:operation name="getActualQTY"> <wsdl:input message="axis2:getActualQTYMessage" wsaw:Action="urn:getActualQTY"/> <wsdl:output message="axis2:getActualQTYResponse"/> </wsdl:operation> <wsdl:operation name="printWithArray"> <wsdl:input message="axis2:printWithArrayMessage" wsaw:Action="urn:printWithArray"/> <wsdl:output message="axis2:printWithArrayResponse"/> </wsdl:operation> <wsdl:operation name="print"> <wsdl:input message="axis2:printMessage" wsaw:Action="urn:print"/> <wsdl:output message="axis2:printResponse"/> </wsdl:operation> <wsdl:operation name="ping"> <wsdl:input message="axis2:pingMessage" wsaw:Action="urn:ping"/> <wsdl:output message="axis2:pingResponse"/> </wsdl:operation> <wsdl:operation name="getPrintJob"> <wsdl:input message="axis2:getPrintJobMessage" wsaw:Action="urn:getPrintJob"/> <wsdl:output message="axis2:getPrintJobResponse"/> </wsdl:operation> </wsdl:portType> <wsdl:binding name="myService4QASOAP11Binding" type="axis2:myService4QAPortType"> <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/> <wsdl:operation name="printLocal"> <soap:operation soapAction="urn:printLocal" style="document"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="createPrintJob"> <soap:operation soapAction="urn:createPrintJob" style="document"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> <wsdl:fault name="createPrintJobFault"> <soap12:fault use="literal" name="createPrintJobFault"/> </wsdl:fault> </wsdl:operation> <wsdl:operation name="printJob"> <soap:operation soapAction="urn:printJob" style="document"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="getActualQTY"> <soap:operation soapAction="urn:getActualQTY" style="document"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="printWithArray"> <soap:operation soapAction="urn:printWithArray" style="document"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="print"> <soap:operation soapAction="urn:print" style="document"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="ping"> <soap:operation soapAction="urn:ping" style="document"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="getPrintJob"> <soap:operation soapAction="urn:getPrintJob" style="document"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:binding name="myService4QASOAP12Binding" type="axis2:myService4QAPortType"> <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/> <wsdl:operation name="printLocal"> <soap12:operation soapAction="urn:printLocal" style="document"/> <wsdl:input> <soap12:body use="literal"/> </wsdl:input> <wsdl:output> <soap12:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="createPrintJob"> <soap12:operation soapAction="urn:createPrintJob" style="document"/> <wsdl:input> <soap12:body use="literal"/> </wsdl:input> <wsdl:output> <soap12:body use="literal"/> </wsdl:output> <wsdl:fault name="createPrintJobFault"> <soap12:fault use="literal" name="createPrintJobFault"/> </wsdl:fault> </wsdl:operation> <wsdl:operation name="printJob"> <soap12:operation soapAction="urn:printJob" style="document"/> <wsdl:input> <soap12:body use="literal"/> </wsdl:input> <wsdl:output> <soap12:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="getActualQTY"> <soap12:operation soapAction="urn:getActualQTY" style="document"/> <wsdl:input> <soap12:body use="literal"/> </wsdl:input> <wsdl:output> <soap12:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="printWithArray"> <soap12:operation soapAction="urn:printWithArray" style="document"/> <wsdl:input> <soap12:body use="literal"/> </wsdl:input> <wsdl:output> <soap12:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="print"> <soap12:operation soapAction="urn:print" style="document"/> <wsdl:input> <soap12:body use="literal"/> </wsdl:input> <wsdl:output> <soap12:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="ping"> <soap12:operation soapAction="urn:ping" style="document"/> <wsdl:input> <soap12:body use="literal"/> </wsdl:input> <wsdl:output> <soap12:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="getPrintJob"> <soap12:operation soapAction="urn:getPrintJob" style="document"/> <wsdl:input> <soap12:body use="literal"/> </wsdl:input> <wsdl:output> <soap12:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:binding name="myService4QAHttpBinding" type="axis2:myService4QAPortType"> <http:binding verb="POST"/> <wsdl:operation name="hello"> <http:operation location="hello"/> <wsdl:input> <mime:content type="text/xml"/> </wsdl:input> <wsdl:output> <mime:content type="text/xml"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="printLocal"> <http:operation location="printLocal"/> <wsdl:input> <mime:content type="text/xml"/> </wsdl:input> <wsdl:output> <mime:content type="text/xml"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="createPrintJob"> <http:operation location="createPrintJob"/> <wsdl:input> <mime:content type="text/xml"/> </wsdl:input> <wsdl:output> <mime:content type="text/xml"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="printJob"> <http:operation location="printJob"/> <wsdl:input> <mime:content type="text/xml"/> </wsdl:input> <wsdl:output> <mime:content type="text/xml"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="getActualQTY"> <http:operation location="getActualQTY"/> <wsdl:input> <mime:content type="text/xml"/> </wsdl:input> <wsdl:output> <mime:content type="text/xml"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="printWithArray"> <http:operation location="printWithArray"/> <wsdl:input> <mime:content type="text/xml"/> </wsdl:input> <wsdl:output> <mime:content type="text/xml"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="print"> <http:operation location="print"/> <wsdl:input> <mime:content type="text/xml"/> </wsdl:input> <wsdl:output> <mime:content type="text/xml"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="ping"> <http:operation location="ping"/> <wsdl:input> <mime:content type="text/xml"/> </wsdl:input> <wsdl:output> <mime:content type="text/xml"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="getPrintJob"> <http:operation location="getPrintJob"/> <wsdl:input> <mime:content type="text/xml"/> </wsdl:input> <wsdl:output> <mime:content type="text/xml"/> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:service name="myService4QA"> <wsdl:port name="myService4QASOAP11port_http" binding="axis2:myService4QASOAP11Binding"> <soap:address location="XXX"/> </wsdl:port> <wsdl:port name="myService4QASOAP12port_http" binding="axis2:myService4QASOAP12Binding"> <soap12:address location="XXX"/> </wsdl:port> <wsdl:port name="myService4QAHttpport" binding="axis2:myService4QAHttpBinding"> <http:address location="XXX"/> </wsdl:port> </wsdl:service> </wsdl:definitions>

i have a web service deployed to axis2 on websphere and the same web service deployed to axis2 on glassfish v2.

the client is a desktop application generated and written in C# using VS2003.

the client works well with the service on websphere which it was originally designed for. but not with the service on glassfish.
the WSDL generated for both services is exactly the same. the only difference i could find is in the response messages.

this is the response message from the service on websphere:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <ns:getPrintJobResponse xmlns:ns="http://myService/xsd"> <ns:return> <bookingRef xmlns="http://myService/xsd">XXXXXX7730000010001</bookingRef> <jobID xmlns="http://myService/xsd">209572</jobID> <printerName xmlns="http://myService/xsd">NAME</printerName> <qty xmlns="http://myService/xsd">3</qty> </ns:return> </ns:getPrintJobResponse> </soapenv:Body> </soapenv:Envelope>
notice that xmlns value appears in all the properties (bookingRef, jobID, printerName, qty).

and here is the same response from glassfish
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <ns:getPrintJobResponse xmlns:ns="http://myService/xsd"> <ns:return> <bookingRef xmlns="http://myService/xsd">XXXXXX7730000010001</bookingRef> <jobID>209552</jobID> <printerName>NAME</printerName> <qty>15</qty> </ns:return> </ns:getPrintJobResponse> </soapenv:Body> </soapenv:Envelope>
notice that only the bookingRef has the xmlns


my service is a POJO without any annotations. it is wrapped as .aar


my questions...

A. why is this happening although i'm deploying to a common denominator on both app. servers which is the axis2.war ?
B. how do i make the response from glassfish matches the one from webshpere? where do i have to change and what?

i just wanted to add that i can recreate the problem simply by changing the status of a job manualy form "SQL Developer" for example from "Done" to "pending" and the job will keep beibg sent and will never be set to "Done" again....
[ July 09, 2008: Message edited by: Ali Bohlaiqh ]

Hello everyone,

i'm runing a printing queue web service on glassfish v2, the clients ask for thier printing jobs and the server send it to them. After each successful print the client invoke a web service method to flag that certain job as being "done" so that the client will not have it sent to him again the next round when it askes for available printg jobs...

it hapens many times that the new status "done" will not persist to the data base which leads to the pritnig job being sent over and over again.

i tried container managed transactions and bean managed transaction with the same result. i even tried em.flush(), but no luck.....

i'm using oracle toplink..

here is how the code looks like .....

. . . private void persist(Object obj){ try{ //ut.begin(); //em.merge(obj); em.persist(obj); //ut.commet(); }catch(Exception ex){ ... } } @webmethod public boolean markJobAsDone(long jobID){ try{ PrintingJob aJob = em.find(PrintingJob.class,jobID); aJob.setStatus("done"); persist(aJob); }catch(Exception ex){ return false; } return true; }
also the clients are asking for jobs every 30 seconds
another question, is there any other aproach to these queues and jobs?


please help