-
1. Re: Porting from Weblogic to Jboss
jonlee Jun 16, 2003 10:30 AM (in response to jboss_user_1)The best place to start on JBoss.NET is with this tutorial. http://www.csd.abdn.ac.uk/%7Ebscharla/teaching/mtp_software/jboss/jboss-net-EJB-example.shtml (You will also find more inforation links from here to the JBoss test examples which are also a good source of information).
It also would not hurt to look at the operation of Axis to have a look at the underlying architecture - JBoss merely borrows Axis and manages service bootstrap and deployment for Axis. http://xml.apache.org/axis
These two will provide you with the basics of deploying Web services in JBoss (and the expected packaging necessary). Essentially, you will need to take your WebLogic deployment package and bundle it into a WSR for JBoss.NET. -
2. Re: Porting from Weblogic to Jboss
jboss_user_1 Jun 17, 2003 8:23 AM (in response to jboss_user_1)Hi,
Thanks for the reply..
I am able to deploy it but when I try to access the service through WSDL2 generated stub I face this exception
org.xml.sax.SAXException: Deserializing parameter 'pLocateAttributes': could no
t find deserializer for type {http://dataholder.util.gass.gsl.ml.com}LocateAvail
abilityAttributes
org.xml.sax.SAXException: Deserializing parameter 'pLocateAttributes': could no
t find deserializer for type {http://dataholder.util.gass.gsl.ml.com}LocateAvail
abilityAttributes
at org.apache.axis.message.RPCHandler.onStartChild(RPCHandler.java:276)
I have mentioned the serializer and deserializers like this in my wsdd file
<typeMapping
xmlns:ns="http://dataholder.util.gass.gsl.ml.com"
qname="ns:locateAvailabilityAttributes"
type="java:com.ml.gsl.gass.util.dataholder.LocateAvailabilityAttributes"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
Can any one help me how to handle this case?
Thanks
Shishir -
3. Re: Porting from Weblogic to Jboss
jonlee Jun 18, 2003 5:39 AM (in response to jboss_user_1)It's not clear from your description on which side you are encountering the problem but I assume that since these are return values that your client is unable to deserialize the data.
Have you included the Axis client libraries in your client? Also have you tried using tcpmon in-line with your transmission so you can monitor the client message and the server response (view the SOAP messages)? It will allow you to get a view window into the actual Web service transaction. IBM uses this tool as an integrated service in their WSAD editor. Look at the Axis documents for more about the tcpmon utility.
Hope it helps.