January 2013 - jbossws-issues - Jboss List Archives

[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

1
0
0 / 0

[JBoss JIRA] (JBWS-3569) WSDL produced for a multi-port service contains invalid port addresses in clustered configuration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3569: ----------------------------------------------- Michal Vanco <mvanco(a)redhat.com> made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] Hi Chris, I was just checking the same scenario which is already described here with JPP 6.0.0 ER05 (which also includes the patch JBPAPP-10497) and it seems like issue is still present. Again I have 2 producer nodes + loadbalancer + another jpp instance as consumer. I registered consumer against loadbanacer WSDL, added remote portlet and failover active producer node. Unfortunately portlet isn't displayed and it's not possible to refresh consumer. I'm getting: java.net.ConnectException: ConnectException invoking http://perf15.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/ServiceDesc...: Connection refused (perf15 was active producer node which was stopped). There is a change at loadbalancer, host:port/wsrp-producer/v2/MarkupService?wsdl - before it showed different node for each refresh - right now it points to active node only. But... the content is: <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:bind="urn:oasis:names:tc:wsrp:v2:bind" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:oasis:names:tc:wsrp:v2:wsdl"> <import location="http://perf13.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/MarkupServi..." namespace="urn:oasis:names:tc:wsrp:v2:bind"></import> <service name="WSRPService"> <port binding="bind:WSRP_v2_ServiceDescription_Binding_SOAP" name="WSRPServiceDescriptionService"> <soap:address location="http://perf11.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/ServiceDesc..."/> </port> <port binding="bind:WSRP_v2_PortletManagement_Binding_SOAP" name="WSRPPortletManagementService"> <soap:address location="http://perf11.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/PortletMana..."/> </port> <port binding="bind:WSRP_v2_Markup_Binding_SOAP" name="WSRPMarkupService"> <soap:address location="http://perf11.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/MarkupService"/> </port> <port binding="bind:WSRP_v2_Registration_Binding_SOAP" name="WSRPRegistrationService"> <soap:address location="http://perf11.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/Registratio..."/> </port> </service> </definitions> I expected perf13...(loadbalancer) will be used at all wsdl links (that's what patch was about), but it's not. This also means that current docs test at BZ doesn't reflect current portal behavior. Thanks for any updates!!! > WSDL produced for a multi-port service contains invalid port addresses in clustered configuration > ------------------------------------------------------------------------------------------------- > > Key: JBWS-3569 > URL: https://issues.jboss.org/browse/JBWS-3569 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Chris Laprun > Assignee: Alessio Soldano > Priority: Critical > Fix For: jbossws-cxf-4.1.1 > > > Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in ports containing the node URLs instead of the loadbalancer's. > I've tried using the dynamic WSDL rewriting as described in https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster node port) that haven't been used to access the WSDL, the port used to access the WSDL has the proper address though. -- 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

1
0
0 / 0

[JBoss JIRA] (JBWS-3569) WSDL produced for a multi-port service contains invalid port addresses in clustered configuration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3569: ----------------------------------------------- Michal Vanco <mvanco(a)redhat.com> changed the Status of [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] from ON_QA to ASSIGNED > WSDL produced for a multi-port service contains invalid port addresses in clustered configuration > ------------------------------------------------------------------------------------------------- > > Key: JBWS-3569 > URL: https://issues.jboss.org/browse/JBWS-3569 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Chris Laprun > Assignee: Alessio Soldano > Priority: Critical > Fix For: jbossws-cxf-4.1.1 > > > Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in ports containing the node URLs instead of the loadbalancer's. > I've tried using the dynamic WSDL rewriting as described in https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster node port) that haven't been used to access the WSDL, the port used to access the WSDL has the proper address though. -- 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

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (JBWS-3569) WSDL produced for a multi-port service contains invalid port addresses in clustered configuration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3569: ----------------------------------------------- Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] from ASSIGNED to ON_QA > WSDL produced for a multi-port service contains invalid port addresses in clustered configuration > ------------------------------------------------------------------------------------------------- > > Key: JBWS-3569 > URL: https://issues.jboss.org/browse/JBWS-3569 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Chris Laprun > Assignee: Alessio Soldano > Priority: Critical > Fix For: jbossws-cxf-4.1.1 > > > Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in ports containing the node URLs instead of the loadbalancer's. > I've tried using the dynamic WSDL rewriting as described in https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster node port) that haven't been used to access the WSDL, the port used to access the WSDL has the proper address though. -- 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

1
0
0 / 0

[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: ------------------------------ Doc is updated : https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration > 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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2013