[JBoss JIRA] (JBWS-3589) Set custom CXF compiler instance to be used in WSDLToJava
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3589:
-------------------------------------
Summary: Set custom CXF compiler instance to be used in WSDLToJava
Key: JBWS-3589
URL: https://issues.jboss.org/browse/JBWS-3589
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jbossws-cxf, tools-jaxws
Reporter: Alessio Soldano
Fix For: jbossws-cxf-4.2
We need to set a custom CXF compiler instance to be used in WSDLToJava; that allows us to provide a custom JavaFileManager to control JAXWS and JAXB api resolution without the need of "setting java.endorsed.dirs" sys prop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (JBWS-3453) JBossWSBusFactory check on Spring availability relies on TCCL only
by Steve Andrews (JIRA)
[ https://issues.jboss.org/browse/JBWS-3453?page=com.atlassian.jira.plugin.... ]
Steve Andrews commented on JBWS-3453:
-------------------------------------
On our project, we experienced this issue, but only intermittently. Is there something about the nature of this issue that would cause it to only manifest after some period of time? In other words, we have the requisite Spring classes in our WAR and calling a remote web service via CXF works fine for awhile. At some point, we end up getting the NoClassDefFoundError described in https://issues.jboss.org/browse/JBPAPP6-492
> JBossWSBusFactory check on Spring availability relies on TCCL only
> ------------------------------------------------------------------
>
> Key: JBWS-3453
> URL: https://issues.jboss.org/browse/JBWS-3453
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-4.1.0.Beta1
>
>
> JBossWSBusFactory has a check on Spring availability to decide the type of CXF BusFactory to build (Spring or not). The check is on TCCL being able to load Spring classes, but that's not enough in a JBoss Modules environment. As a matter of fact, that check needs to be extended to the defining classloader of the JBossWSBusFactory (which is the classloader for the org.jboss.ws.jaxws-client module), to be sure the factory can actually be loaded (it's going to be loaded using the defining classloader and of course the CXFBusFactory imports Spring classes)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (JBWS-3588) CXF "Unable to create JAXBContext for generated packages" error on Windows when classpath is empty
by Jim Ma (JIRA)
[ https://issues.jboss.org/browse/JBWS-3588?page=com.atlassian.jira.plugin.... ]
Jim Ma reopened JBWS-3588:
--------------------------
> CXF "Unable to create JAXBContext for generated packages" error on Windows when classpath is empty
> --------------------------------------------------------------------------------------------------
>
> Key: JBWS-3588
> URL: https://issues.jboss.org/browse/JBWS-3588
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: david.boeren
> Assignee: Jim Ma
> Attachments: jms_topic.zip
>
>
> 15:26:06,691 INFO [DynamicClientFactory] Created classes:
> net.webservicex.ChangeLengthUnit, net.webservicex.ChangeLengthUnitResponse,
> net.webservicex.Lengths, net.webservicex.ObjectFactory
> 15:26:08,316 INFO [STDOUT] javac: invalid flag:
> C:/Temp/org.apache.cxf.endpoint.dynamic.DynamicClientFactory@19b0120-1355516766691-classes
> Usage: javac <options> <source files>
> use -help for a list of possible options
> 15:26:08,348 SEVERE [DynamicClientFactory] Could not compile java files for
> http://www.webservicex.net/length.asmx?WSDL.
> 15:26:08,410 ERROR [TargetServiceAction] java.lang.IllegalStateException:
> Unable to create JAXBContext for generated packages: "net.webservicex"
> doesnt contain ObjectFactory.class or jaxb.index
> Run attached jms_topic.zip to reproduce the error. This only happens on Windows, not on OSX or Linux.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (JBWS-3588) CXF "Unable to create JAXBContext for generated packages" error on Windows when classpath is empty
by david.boeren (JIRA)
[ https://issues.jboss.org/browse/JBWS-3588?page=com.atlassian.jira.plugin.... ]
david.boeren updated JBWS-3588:
-------------------------------
Attachment: jms_topic.zip
> CXF "Unable to create JAXBContext for generated packages" error on Windows when classpath is empty
> --------------------------------------------------------------------------------------------------
>
> Key: JBWS-3588
> URL: https://issues.jboss.org/browse/JBWS-3588
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: david.boeren
> Assignee: Jim Ma
> Attachments: jms_topic.zip
>
>
> 15:26:06,691 INFO [DynamicClientFactory] Created classes:
> net.webservicex.ChangeLengthUnit, net.webservicex.ChangeLengthUnitResponse,
> net.webservicex.Lengths, net.webservicex.ObjectFactory
> 15:26:08,316 INFO [STDOUT] javac: invalid flag:
> C:/Temp/org.apache.cxf.endpoint.dynamic.DynamicClientFactory@19b0120-1355516766691-classes
> Usage: javac <options> <source files>
> use -help for a list of possible options
> 15:26:08,348 SEVERE [DynamicClientFactory] Could not compile java files for
> http://www.webservicex.net/length.asmx?WSDL.
> 15:26:08,410 ERROR [TargetServiceAction] java.lang.IllegalStateException:
> Unable to create JAXBContext for generated packages: "net.webservicex"
> doesnt contain ObjectFactory.class or jaxb.index
> Run attached jms_topic.zip to reproduce the error. This only happens on Windows, not on OSX or Linux.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (JBWS-3588) CXF "Unable to create JAXBContext for generated packages" error on Windows when classpath is empty
by david.boeren (JIRA)
david.boeren created JBWS-3588:
----------------------------------
Summary: CXF "Unable to create JAXBContext for generated packages" error on Windows when classpath is empty
Key: JBWS-3588
URL: https://issues.jboss.org/browse/JBWS-3588
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Reporter: david.boeren
Assignee: Jim Ma
15:26:06,691 INFO [DynamicClientFactory] Created classes:
net.webservicex.ChangeLengthUnit, net.webservicex.ChangeLengthUnitResponse,
net.webservicex.Lengths, net.webservicex.ObjectFactory
15:26:08,316 INFO [STDOUT] javac: invalid flag:
C:/Temp/org.apache.cxf.endpoint.dynamic.DynamicClientFactory@19b0120-1355516766691-classes
Usage: javac <options> <source files>
use -help for a list of possible options
15:26:08,348 SEVERE [DynamicClientFactory] Could not compile java files for
http://www.webservicex.net/length.asmx?WSDL.
15:26:08,410 ERROR [TargetServiceAction] java.lang.IllegalStateException:
Unable to create JAXBContext for generated packages: "net.webservicex"
doesnt contain ObjectFactory.class or jaxb.index
Run attached jms_topic.zip to reproduce the error. This only happens on Windows, not on OSX or Linux.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (JBWS-3396) Evaluate partial generation of jbossws-cxf.xml descriptor
by Jim Ma (JIRA)
[ https://issues.jboss.org/browse/JBWS-3396?page=com.atlassian.jira.plugin.... ]
Jim Ma commented on JBWS-3396:
------------------------------
OK,Alessio. I'll sum up this change in the doc. I looked at merge the duplicates endpoint from jbossws-cxf.xml and DD by purely processing the spring xml configuration, but it looks not the ideal and too many manual work. I believe we can make it simple. We can look at/discuss this again later, one of my thoughts is enable the cxf's servlet way to handle this complex case ? We can look at if this doable in our integration layer.
> Evaluate partial generation of jbossws-cxf.xml descriptor
> ---------------------------------------------------------
>
> Key: JBWS-3396
> URL: https://issues.jboss.org/browse/JBWS-3396
> Project: JBoss Web Services
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: Alessio Soldano
> Assignee: Jim Ma
> Fix For: jbossws-cxf-4.2
>
>
> See http://community.jboss.org/message/640779#640779 . Basically the issue with the need for user to specify every endpoint in the jbossws-cxf.xml, while in some case the info might come from the metadata created from the web.xml / annotations. At least we could have defaults.
> The same applies to defaults for the address attribute in jaxws:endpoint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months