[Microcontainer] - Re: Class loading conflict
by objectiser
No, still no luck - just to check, the jboss-classloading.xml in esb.deployer is:
<classloading domain="jboss.esb:service=EsbDeployer,extension=LoaderRepository" xmlns="urn:jboss:classloading:1.0" name="EsbDeployer"
import-all="true" export-all="NON_EMPTY" version="0.0.0"
j2seClassLoadingCompliance="false" parentDomain="DefaultDomain" >
and it causes exceptions like:
15:34:00,679 ERROR [AbstractKernelController] Error installing to Instantiated: name=jboss.esb:service=PropertyService state=Described mode=Manual requiredState=Configured
java.lang.ClassNotFoundException: org.jboss.soa.esb.common.JBossESBPropertyService from BaseClassLoader@127d5a0{VFSClassLoaderPolicy@3a0533{name=vfsfile:/.......
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249437#4249437
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249437
16 years, 10 months
[EJB 3.0] - setProperty must be overridden by allsubclasses of SOAPMessa
by JBOSSFREEBEE
I am trying to run a standalone java client which will invoke a webservice. My webservice is a session bean implementation and is running and tested with SOAP UI. My client code looks like the following :
1 URL url = new URL ("wsdlURL");
2 QName qname = ("ServiceURI", "ServiceName")
3 ServiceFactory factory = Service.Factory.newInstance();
4 Service service = factory.createService(url, qname);
5 BeanName bean = (BeanName) remote.getPort(BeanName.class);
6 System.out.println( bean.method( String input));
On running this I am getting the following error on line no.6
Exception in thread "main" java.lang.reflect.UndeclaredThrowableException at bean.method(Unknown Source) .....................................
Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by allsubclasses of SOAPMessage ........................
After reading some postings on this issue i added the following jars to endorsed dir
activation.jar
jaxb-api.jar
stax-api.jar
in addition to serializer, xalan and xerces, this did not help.
I am using jdk 1.6, JBOSS AS 4.3, Eclipse 3.4.2.
This issue has been discussed in many places in web, but i could not figure out what will actually make it work. Any help will be appreciated.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249435#4249435
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249435
16 years, 10 months
[Microcontainer] - Re: Class loading conflict
by objectiser
Hi,
Tried that approach, but now I have a problem in that the ESB is complaining about classes not being found. The jboss-classloading.xml is placed in the esb.deployer, so I assume that isolation is now causing the jbossesb.sar to not resolve classes that it previously referenced from the esb.deployer.
So I assume to overcome this, I would need a jboss-classloading.xml in the jbossesb.sar?
The jbossesb.sar has a deployment.xml but it does not have a dependency on the deployer - if it did, would this overcome the problem? or do all deployment units that depend upon the ESB need to have its own jboss-classloading.xml? i.e. any .esb distribution?
The other problem with this approach is that it requires me to modify the ESB distribution. Is there no mechanism to just enable my sar to indicate that it wants to have only its own libs, and the jboss AS libs on its classpath?
Regards
Gary
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249415#4249415
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249415
16 years, 10 months