-
1. Re: JBossWS with Axis 1.2 Client (Flawed architecture?)
ranaaich Feb 16, 2005 4:58 PM (in response to ranaaich)Here is a clue:
I replaced the axis.jar by axis-ws4ee.jar (jboss4.0.0) in %JBOSS_HOME%\server\defualt\deploy\lib and started the JBoss.
My webserice started up well, But the web-application for storeX while querying StoreY has returned an exception:
------------------------------------------------------------------------
Caused by: java.lang.NoSuchMethodError: org.apache.axis.description.TypeDesc.(Ljava/lang/Class;Z)V
at qs.QueryDataRequestType.(QueryDataRequestType.java:162)
at com.nri.storeX.ui.InventoryQueryDispatchAction.queryOtherStores(InventoryQueryDispatchAction.java:179)
... 43 more
-------------------------------------------------------------------------
It seems org.apache.axis.description.TypeDesc class in axis.jar(in axis-1_2RC2 distrubution) and axis-ws4ee.jar for JBOSS 4.0.0 has some differences - namely, method init is not present in the later. -
2. Re: JBossWS with Axis 1.2 Client (Flawed architecture?)
anil.saldhana Feb 16, 2005 5:00 PM (in response to ranaaich)http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866172#3866172
Vishal from Australia documented the steps he followed to integrate custom axis jars (Axis 1.1 and 1.2) -
3. Re: JBossWS with Axis 1.2 Client (Flawed architecture?)
thomas.diesler Feb 16, 2005 5:09 PM (in response to ranaaich)You cannot use JBossWS and the apache axis libraries at the same time in jboss. Starting from jboss-4.0.2 we will move the axis package required by ws4ee to a org.jboss package to avoid these types of classloading issues.
What is your reason not to use ws4ee clients on storeX/Y? -
4. Re: JBossWS with Axis 1.2 Client (Flawed architecture?)
ranaaich Feb 16, 2005 6:48 PM (in response to ranaaich)Ideally there would be say 50 retail store chain.
So from each store query will go to other 49 stores. Each webservice is designed to query the local Store Database and return the inventory status for a particular item.
In that case I have to write ws4ee clients for all 49 stores.
I agree that using apache axis clients I also run WSDL2Java 49 times. But I figured out if only the ***ServiceLocator.class(genearted by WSDL2Java) is seperated out are kept in Store Specfic directory then it is mush more easier to maintain. (As all the stores wil have have the same wsdl and xsd thus only the *ServiceLocator.class will be differ from store to store).
Thus the directory structure would be as below:
- queryService
- StoreY
- StoreX
- StoreZ
- Store49
etc. The queryService directory will have same *RequestType, *ResponseType, *SoapBindingStub.class *Service.class for all the 49 stores. All I have to do is to compile this and put the jar file in the %JBoss%\server\default\lib directory.
This schema is working for the command line environment. But when I go for JBoss environment - I get this error. -
5. Re: JBossWS with Axis 1.2 Client (Flawed architecture?)
ranaaich Feb 17, 2005 12:18 PM (in response to ranaaich)Hello Thomas, Anil
Thanks for keeping this thread alive! Can you give us a tentative timeframe when the jboss-4.0.2 version will be released?
Regards,
Rana Aich -
6. Re: JBossWS with Axis 1.2 Client (Flawed architecture?)
thomas.diesler Feb 23, 2005 8:33 AM (in response to ranaaich)You could have a look at the road map
http://jira.jboss.com/jira/browse/JBWS?report=com.atlassian.jira.plugin.system.project:roadmap-panel