[jira] Resolved: (CXF-3176) Update to latest Jetty version 7.2.1 from 7.2.0
[ https://issues.apache.org/jira/browse/CXF-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CXF-3176. --- Resolution: Fixed > Update to latest Jetty version 7.2.1 from 7.2.0 > --- > > Key: CXF-3176 > URL: https://issues.apache.org/jira/browse/CXF-3176 > Project: CXF > Issue Type: Improvement >Affects Versions: 2.3.1 >Reporter: Gary Gregory >Assignee: Willem Jiang > Fix For: 2.3.2 > > > Update to latest Jetty version 7.2.1 from 7.2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Issues with Attachments: week of 2010-12-13
CXF - Monday, December 13, 2010 7 Issues with Attachments (sorted oldest to newest) [CXF-2810] Wrong namespaces in WSDL - 2.2.6 OK, 2.2.7 and 2.2.8 BROKEN - Created: 2010-05-13 - Updated: 2010-12-09 - Type: Bug - Fix Versions: [] - Reporter: Jara Cesnek - Assigned: Unassigned - Attachments: [CXF-2810-testcase.zip] - https://issues.apache.org:443/jira/browse/CXF-2810 [CXF-3113] Meaningful Exception for HTTP Exceptions - Created: 2010-11-08 - Updated: 2010-11-15 - Type: Improvement - Fix Versions: [] - Reporter: Sébastien - Assigned: Unassigned - Attachments: [com.bsb.sf.sample.service.math.ws.HelloWorldWebServiceTestIt.txt] - https://issues.apache.org:443/jira/browse/CXF-3113 [CXF-3129] wsdl2java: place @Generated annotation on generated code - Created: 2010-11-16 - Updated: 2010-12-09 - Type: New Feature - Fix Versions: [] - Reporter: Andrew Spencer - Assigned: Unassigned - Attachments: [Patch+for+CXF+3129.txt] - https://issues.apache.org:443/jira/browse/CXF-3129 [CXF-3145] Refactor toSQL method as visitor pattern - Created: 2010-11-21 - Updated: 2010-11-24 - Type: Improvement - Fix Versions: [] - Reporter: Brian Topping - Assigned: Unassigned - Attachments: [cxf3145.patch] - https://issues.apache.org:443/jira/browse/CXF-3145 [CXF-3156] Have web service client cache SAML tokens used in SOAP calls - Created: 2010-11-29 - Updated: 2010-12-01 - Type: Wish - Fix Versions: [] - Reporter: Glen Mazza - Assigned: Unassigned - Attachments: [20101129DoubleItMetroWSTrust.zip] - https://issues.apache.org:443/jira/browse/CXF-3156 [CXF-3160] Reduce Code duplication between http transport variants - Created: 2010-12-01 - Updated: 2010-12-08 - Type: Improvement - Fix Versions: [] - Reporter: Christian Schneider - Assigned: Christian Schneider - Attachments: [CXF-3160-1.patch, CXF-3160-2.patch, CXF-3160-3.patch] - https://issues.apache.org:443/jira/browse/CXF-3160 [CXF-3161] Marshalling object fails with JAXB and CXF, throws nullpointerexception - Created: 2010-12-02 - Updated: 2010-12-02 - Type: Bug - Fix Versions: [] - Reporter: Paul Jutten - Assigned: Unassigned - Attachments: [JaxBProject.zip] - https://issues.apache.org:443/jira/browse/CXF-3161
[jira] Commented: (CXF-3179) ServerPersistenceTest fail intermittently
[ https://issues.apache.org/jira/browse/CXF-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970747#action_12970747 ] Freeman Fang commented on CXF-3179: --- this is actually caused by awaitMessages in ServerPersistenceTest.verifyRetransmissionQueue() is incomplete. Server should wait for SequenceAcknowledgement from client side. If client side send SequenceAcknowledgement just at the same time when bus shutdown, we will see test failure. Fix is coming soon. > ServerPersistenceTest fail intermittently > - > > Key: CXF-3179 > URL: https://issues.apache.org/jira/browse/CXF-3179 > Project: CXF > Issue Type: Test >Reporter: Freeman Fang >Assignee: Freeman Fang > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-3179) ServerPersistenceTest fail intermittently
[ https://issues.apache.org/jira/browse/CXF-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-3179. --- Resolution: Fixed Fix Version/s: 2.4 2.3.2 commit fix http://svn.apache.org/viewvc?rev=1045031&view=rev for trunk http://svn.apache.org/viewvc?rev=1045051&view=rev for 2.3 branch http://svn.apache.org/viewvc?rev=1045066&view=rev for 2.2 branch > ServerPersistenceTest fail intermittently > - > > Key: CXF-3179 > URL: https://issues.apache.org/jira/browse/CXF-3179 > Project: CXF > Issue Type: Test >Reporter: Freeman Fang >Assignee: Freeman Fang > Fix For: 2.3.2, 2.4 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DOSGI-69) CXF-DOSGi requires internet access when reading XML
[ https://issues.apache.org/jira/browse/DOSGI-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970813#action_12970813 ] David Bosschaert commented on DOSGI-69: --- Hi Julien, It looks good, but the Single-Bundle system tests fail with an exception [1]. So there's probably some additional changes needed. You can reproduce this by running: $ .../systests2/single-bundle> mvn install Thanks, David [1] java.lang.NoClassDefFoundError: org/springframework/asm/ClassVisitor at org.springframework.context.support.GenericApplicationContext.( GenericApplicationContext.java:103) at org.springframework.context.support.GenericXmlApplicationContext.(GenericXmlApplicationContext.java:47) at org.apache.cxf.dosgi.dsw.OsgiUtils.readIntentMap(OsgiUtils.java:409) at org.apache.cxf.dosgi.dsw.OsgiUtils.getIntentMap(OsgiUtils.java:382) at org.apache.cxf.dosgi.dsw.handlers.AbstractPojoConfigurationTypeHandle r.getIntentMap(AbstractPojoConfigurationTypeHandler.java:182) at org.apache.cxf.dosgi.dsw.handlers.AbstractPojoConfigurationTypeHandle r.mergeWithMaster(AbstractPojoConfigurationTypeHandler.java:210) at org.apache.cxf.dosgi.dsw.handlers.AbstractPojoConfigurationTypeHandle r.applyIntents(AbstractPojoConfigurationTypeHandler.java:98) at org.apache.cxf.dosgi.dsw.handlers.PojoConfigurationTypeHandler.create Server(PojoConfigurationTypeHandler.java:119) at org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminCore.exportService (RemoteServiceAdminCore.java:244) at org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminInstance$1.run(Rem oteServiceAdminInstance.java:78) at org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminInstance$1.run(Rem oteServiceAdminInstance.java:71) at java.security.AccessController.doPrivileged(Native Method) at org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminInstance.exportSer vice(RemoteServiceAdminInstance.java:71) at org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminInstance.exportSer vice(RemoteServiceAdminInstance.java:40) at org.apache.cxf.dosgi.topologymanager.TopologyManager$2.run(TopologyMa nager.java:254) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: org.springframework.asm.ClassVisito r at org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation (ModuleImpl.java:738) at org.apache.felix.framework.ModuleImpl.access$100(ModuleImpl.java:60) at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(Mod uleImpl.java:1650) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) ... 18 more > CXF-DOSGi requires internet access when reading XML > --- > > Key: DOSGI-69 > URL: https://issues.apache.org/jira/browse/DOSGI-69 > Project: CXF Distributed OSGi > Issue Type: Bug > Components: DSW >Affects Versions: 1.1 >Reporter: David Bosschaert >Assignee: David Bosschaert > Attachments: dosgi69-withoutEmbeddedDependencies.patch, dosgi69.patch > > > When the DOSGi system parses XML (such as an intent map or > remote-services.xml file) it tries to resolve the used XML schema's from the > internet, even though they are part of the distribution. This shouldn't be > happening. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-3184) SOAPBindingUtil.getProxy can't load right class in OSGi
SOAPBindingUtil.getProxy can't load right class in OSGi
---
Key: CXF-3184
URL: https://issues.apache.org/jira/browse/CXF-3184
Project: CXF
Issue Type: Bug
Affects Versions: 2.3.1, 2.2.12
Reporter: Willem Jiang
Assignee: Willem Jiang
Fix For: 2.3.2, 2.4
As a fix for CXF-3143 SOAPBindingUtil.getProxy uses now thread context
classloader.
This causes the following problem:
{code}
Caused by: java.lang.IllegalArgumentException: interface
org.apache.cxf.tools.common.extensions.soap.SoapBinding is not visible from
class loader
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:353)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
at
org.apache.cxf.tools.util.SOAPBindingUtil.getProxy(SOAPBindingUtil.java:87)
at
org.apache.cxf.tools.util.SOAPBindingUtil.getSoapBinding(SOAPBindingUtil.java:274)
at
org.apache.cxf.tools.util.SOAPBindingUtil.createSoapBinding(SOAPBindingUtil.java:426)
at
org.apache.cxf.binding.soap.SoapBindingFactory.createSoapBinding(SoapBindingFactory.java:190)
at
org.apache.cxf.binding.soap.SoapBindingFactory.createBindingInfo(SoapBindingFactory.java:175)
at
org.apache.cxf.binding.AbstractBindingFactory.createBindingInfo(AbstractBindingFactory.java:80)
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createBindingInfo(AbstractWSDLBasedEndpointFactory.java:360)
at
org.apache.cxf.jaxws.JaxWsServerFactoryBean.createBindingInfo(JaxWsServerFactoryBean.java:160)
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpointInfo(AbstractWSDLBasedEndpointFactory.java:257)
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:145)
at
org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:105)
at
org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:177)
at
com.sabre.gateway.g2g.G2GInConnector.(G2GInConnector.java:105)
at
com.sabre.gateway.g2g.G2GInConnector.(G2GInConnector.java:76)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126)
{code}
To avoid it we would to set context classloader to CXF bundle one before
calling CXF code that causes this exception or import the cxf packages in our
bundle and set context classloader to our bundle's one.
Both solutions look like workarounds.
We need to make the SOAPBindingUtil.getProxy more smart to load the class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-3185) CXF client NTLM Authentication Issue
CXF client NTLM Authentication Issue
-
Key: CXF-3185
URL: https://issues.apache.org/jira/browse/CXF-3185
Project: CXF
Issue Type: Bug
Affects Versions: 2.2.10
Environment: Java 6, CXF 2.2.10
Reporter: Amol Deshpande
Hi,
I have generated a cxf client using wsdl2java tool. This client is built to
consume the sharepoint webservice which requires NTLM authentication.
I was initially
On the link :
http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html ,
under the NTLM authentication section, it is stated that - "On Java 6, NTLM
authentication is built into the Java runtime and you don't need to do anything
special" .
As such I just turned off chunking and try to connect to the webservice,
However I get a Server redirected too many times issue.
The code and the error are as given below:
Code
*
SiteData ss = new SiteData(wsdlURL, SERVICE_NAME);
SiteDataSoap port = ss.getSiteDataSoap();
//Turn off chunking so that NTLM can occur
Client client = org.apache.cxf.frontend.ClientProxy.getClient(port);
HTTPConduit http = (HTTPConduit) client.getConduit();
HTTPClientPolicy httpClientPolicy = new HTTPClientPolicy();
httpClientPolicy.setConnectionTimeout(36000);
httpClientPolicy.setAllowChunking(false);
http.setClient(httpClientPolicy);
System.out.println("Invoking getSite...");
javax.xml.ws.Holder _getSite_getSiteResult = new
javax.xml.ws.Holder();
javax.xml.ws.Holder
_getSite_sSiteMetadata = new
javax.xml.ws.Holder();
javax.xml.ws.Holder
_getSite_vWebs = new
javax.xml.ws.Holder();
javax.xml.ws.Holder _getSite_strUsers = new
javax.xml.ws.Holder();
javax.xml.ws.Holder _getSite_strGroups = new
javax.xml.ws.Holder();
javax.xml.ws.Holder
_getSite_vGroups = new
javax.xml.ws.Holder();
//Webservice call
port.getSite(_getSite_getSiteResult, _getSite_sSiteMetadata,
_getSite_vWebs, _getSite_strUsers, _getSite_strGroups, _getSite_vGroups);
**
Error Message
***
The error I get is as follows :
Dec 13, 2010 1:30:05 PM org.apache.cxf.phase.PhaseInterceptorChain
doDefaultLogging
WARNING: Interceptor for
{http://schemas.microsoft.com/sharepoint/soap/}SiteData#{http://schemas.microsoft.com/sharepoint/soap/}GetSite
has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Could not send Message.
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:244)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
at $Proxy39.getSite(Unknown Source)
at
com.microsoft.schemas.sharepoint.soap.SiteDataSoap_SiteDataSoap_Client.main(SiteDataSoap_SiteDataSoap_Client.java:190)
Caused by: java.net.ProtocolException: ProtocolException invoking
http://corp.abc.com/_vti_bin/SiteData.asmx: Server redirected too many times
(20)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:2058)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:2043)
at
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:639)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSende
[jira] Created: (CXF-3186) Update to latest JAXB version 2.2.3 from 2.2.2
Update to latest JAXB version 2.2.3 from 2.2.2 -- Key: CXF-3186 URL: https://issues.apache.org/jira/browse/CXF-3186 Project: CXF Issue Type: Improvement Affects Versions: 2.3.1 Reporter: Gary Gregory Fix For: 2.3.2 Update to latest JAXB version 2.2.3 from 2.2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-3187) Update to latest Jetty version 7.2.2 from 7.2.1
Update to latest Jetty version 7.2.2 from 7.2.1 --- Key: CXF-3187 URL: https://issues.apache.org/jira/browse/CXF-3187 Project: CXF Issue Type: Improvement Affects Versions: 2.3.1 Reporter: Gary Gregory Fix For: 2.3.2 Update to latest Jetty version 7.2.2 from 7.2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (CXF-3177) Update to latest JAXB version 2.2.2 from 2.2.1
[ https://issues.apache.org/jira/browse/CXF-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reopened CXF-3177: --- This upgrade introduced a test failure of CodeGenBugTest[1], I had to rollback it. Will revisit later. [1]https://hudson.apache.org/hudson/job/CXF-2.3.x/org.apache.cxf$cxf-tools-wsdlto-test/81/testReport/junit/org.apache.cxf.tools.wsdlto.jaxws/CodeGenBugTest/testReuseJaxbBindingFile1/ > Update to latest JAXB version 2.2.2 from 2.2.1 > -- > > Key: CXF-3177 > URL: https://issues.apache.org/jira/browse/CXF-3177 > Project: CXF > Issue Type: Improvement >Affects Versions: 2.3.1 >Reporter: Gary Gregory >Assignee: Willem Jiang > Fix For: 2.3.2 > > Attachments: jaxb-api-2.2.2-bundle.jar > > > Update to latest JAXB version 2.2.2 from 2.2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-3188) The response code 500 and soapFault are produced for an one way operation when the soap understand headers can not be processed
The response code 500 and soapFault are produced for an one way operation when
the soap understand headers can not be processed
---
Key: CXF-3188
URL: https://issues.apache.org/jira/browse/CXF-3188
Project: CXF
Issue Type: Bug
Components: Core
Affects Versions: 2.3.1
Reporter: jimma
Assignee: jimma
Fix For: 2.3.2, 2.4
If there are must understand headers can not be processed/understood , server
responds with 500 response code and soap fault message . This doesn't conform
to WSI profile section 5.6.10.
Below is the request message to reproduce this issue:
Encoding: UTF-8
Content-Type: text/xml; charset=UTF-8
Headers: {content-type=[text/xml; charset=UTF-8], connection=[keep-alive],
Host=[localhost:9000], Content-Length=[256], SOAPAction=[""],
User-Agent=[Apache CXF 2.3.2-SNAPSHOT], Content-Type=[text/xml; charset=UTF-8],
Accept=[*/*], Pragma=[no-cache], Cache-Control=[no-cache]}
Payload: http://schemas.xmlsoap.org/soap/envelope/";>http://cxf.apache.org/mu";
soap:mustUnderstand="1"/>http://apache.org/handler_test/types"/>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-3184) SOAPBindingUtil.getProxy can't load right class in OSGi
[
https://issues.apache.org/jira/browse/CXF-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CXF-3184.
---
Resolution: Fixed
Fix Version/s: 2.2.13
Now the SOAPBindingUtil.getProxy will use the classloader of cls when it can't
create the proxy with the thread context classloader.
> SOAPBindingUtil.getProxy can't load right class in OSGi
> ---
>
> Key: CXF-3184
> URL: https://issues.apache.org/jira/browse/CXF-3184
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.2.12, 2.3.1
>Reporter: Willem Jiang
>Assignee: Willem Jiang
> Fix For: 2.3.2, 2.2.13, 2.4
>
>
> As a fix for CXF-3143 SOAPBindingUtil.getProxy uses now thread context
> classloader.
> This causes the following problem:
> {code}
> Caused by: java.lang.IllegalArgumentException: interface
> org.apache.cxf.tools.common.extensions.soap.SoapBinding is not visible from
> class loader
> at java.lang.reflect.Proxy.getProxyClass(Proxy.java:353)
> at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
> at
> org.apache.cxf.tools.util.SOAPBindingUtil.getProxy(SOAPBindingUtil.java:87)
> at
> org.apache.cxf.tools.util.SOAPBindingUtil.getSoapBinding(SOAPBindingUtil.java:274)
> at
> org.apache.cxf.tools.util.SOAPBindingUtil.createSoapBinding(SOAPBindingUtil.java:426)
> at
> org.apache.cxf.binding.soap.SoapBindingFactory.createSoapBinding(SoapBindingFactory.java:190)
> at
> org.apache.cxf.binding.soap.SoapBindingFactory.createBindingInfo(SoapBindingFactory.java:175)
> at
> org.apache.cxf.binding.AbstractBindingFactory.createBindingInfo(AbstractBindingFactory.java:80)
> at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createBindingInfo(AbstractWSDLBasedEndpointFactory.java:360)
> at
> org.apache.cxf.jaxws.JaxWsServerFactoryBean.createBindingInfo(JaxWsServerFactoryBean.java:160)
> at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpointInfo(AbstractWSDLBasedEndpointFactory.java:257)
> at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:145)
> at
> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:105)
> at
> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:177)
> at
> com.sabre.gateway.g2g.G2GInConnector.(G2GInConnector.java:105)
> at
> com.sabre.gateway.g2g.G2GInConnector.(G2GInConnector.java:76)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126)
> {code}
> To avoid it we would to set context classloader to CXF bundle one before
> calling CXF code that causes this exception or import the cxf packages in our
> bundle and set context classloader to our bundle's one.
> Both solutions look like workarounds.
> We need to make the SOAPBindingUtil.getProxy more smart to load the class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
