March 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3479) Implement @org.jboss.ws.api.annotation.WebContext support for POJO endpoints

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3479?page=com.atlassian.jira.plugin.... ] Jim Ma commented on JBWS-3479: ------------------------------ Ok. Alessio, Let's evaluate how much effort shall we pay for this feature and decide the next step. > Implement @org.jboss.ws.api.annotation.WebContext support for POJO endpoints > ---------------------------------------------------------------------------- > > Key: JBWS-3479 > URL: https://issues.jboss.org/browse/JBWS-3479 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-integration > Reporter: Richard Opalka > > We support @WebContext on EJB endpoints now. > Since Servlet 3.0 spec allows web deployments > without web.xml it is worth to support this annotation > also on POJO WS endpoints. > There are however two restrictions that must be ensured. > If there are multiple WS endpoints in web archive > all annotated with @WebContext annotation then the following > restriction must apply: > - contextRoot value must be the same for all @WebContext annotated endpoints > - virtualHost value must be the same for all @WebContext annotated endpoints > - if there's provided jboss-web.xml or jboss-webservices.xml with context root in deployment > this DD driven context root will have higher priority than context root specified in annotations. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3606) Add proper way to identify the cxf and native stack

by Jim Ma (JIRA)

Jim Ma created JBWS-3606: ---------------------------- Summary: Add proper way to identify the cxf and native stack Key: JBWS-3606 URL: https://issues.jboss.org/browse/JBWS-3606 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.1.3 Reporter: Jim Ma Fix For: jbossws-cxf-4.2 We now use the META-INF implementation vendor to identify the cxf or native stack. In the production process, this info could be changed. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3479) Implement @org.jboss.ws.api.annotation.WebContext support for POJO endpoints

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3479?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3479: --------------------------------------- Hi Jim, well, my point of view is that this would a) simplify the api from a user point of view (you could use this annotation regardless of the type of ws endpoint, pojo or ejb3), b) allow fully configuring pojo endpoints without web.xml, again something users might like. The context-root, btw, is not set in the web.xml, but in the jboss-web.xml, which is still not portable, so to me allowing using the @WebContext annotation here would not really affect portability. This said, I agree supporting this adds a bit of complexity when computing the actual context-root, virtual-host etc., but I still believe it's worth exploring the feasibility of this feature req issue. > Implement @org.jboss.ws.api.annotation.WebContext support for POJO endpoints > ---------------------------------------------------------------------------- > > Key: JBWS-3479 > URL: https://issues.jboss.org/browse/JBWS-3479 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-integration > Reporter: Richard Opalka > > We support @WebContext on EJB endpoints now. > Since Servlet 3.0 spec allows web deployments > without web.xml it is worth to support this annotation > also on POJO WS endpoints. > There are however two restrictions that must be ensured. > If there are multiple WS endpoints in web archive > all annotated with @WebContext annotation then the following > restriction must apply: > - contextRoot value must be the same for all @WebContext annotated endpoints > - virtualHost value must be the same for all @WebContext annotated endpoints > - if there's provided jboss-web.xml or jboss-webservices.xml with context root in deployment > this DD driven context root will have higher priority than context root specified in annotations. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3479) Implement @org.jboss.ws.api.annotation.WebContext support for POJO endpoints

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3479?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-3479: ------------------------- Fix Version/s: (was: jbossws-cxf-4.2) > Implement @org.jboss.ws.api.annotation.WebContext support for POJO endpoints > ---------------------------------------------------------------------------- > > Key: JBWS-3479 > URL: https://issues.jboss.org/browse/JBWS-3479 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-integration > Reporter: Richard Opalka > > We support @WebContext on EJB endpoints now. > Since Servlet 3.0 spec allows web deployments > without web.xml it is worth to support this annotation > also on POJO WS endpoints. > There are however two restrictions that must be ensured. > If there are multiple WS endpoints in web archive > all annotated with @WebContext annotation then the following > restriction must apply: > - contextRoot value must be the same for all @WebContext annotated endpoints > - virtualHost value must be the same for all @WebContext annotated endpoints > - if there's provided jboss-web.xml or jboss-webservices.xml with context root in deployment > this DD driven context root will have higher priority than context root specified in annotations. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3479) Implement @org.jboss.ws.api.annotation.WebContext support for POJO endpoints

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3479?page=com.atlassian.jira.plugin.... ] Jim Ma commented on JBWS-3479: ------------------------------ I'd prefer to not support this. We introduce the @WebContext for the ejb ws endpoint, partly because there is no descriptor in ejb archive to specify the contextRoot, urlPattern, virtualHost etc. Given there is web.xml which can specify all these things in @WebContext, we can ask user to configure in web.xml instead of annotation. It will be more portable and less complex to check various above restriction. Your opinion ? > Implement @org.jboss.ws.api.annotation.WebContext support for POJO endpoints > ---------------------------------------------------------------------------- > > Key: JBWS-3479 > URL: https://issues.jboss.org/browse/JBWS-3479 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-integration > Reporter: Richard Opalka > Fix For: jbossws-cxf-4.2 > > > We support @WebContext on EJB endpoints now. > Since Servlet 3.0 spec allows web deployments > without web.xml it is worth to support this annotation > also on POJO WS endpoints. > There are however two restrictions that must be ensured. > If there are multiple WS endpoints in web archive > all annotated with @WebContext annotation then the following > restriction must apply: > - contextRoot value must be the same for all @WebContext annotated endpoints > - virtualHost value must be the same for all @WebContext annotated endpoints > - if there's provided jboss-web.xml or jboss-webservices.xml with context root in deployment > this DD driven context root will have higher priority than context root specified in annotations. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3166) Review the code which enable the mtom threshold configuration from DDEndpoint in both spring and without spring stack

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3166?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3166: ---------------------------------- Fix Version/s: (was: jbossws-cxf-4.2) > Review the code which enable the mtom threshold configuration from DDEndpoint in both spring and without spring stack > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBWS-3166 > URL: https://issues.jboss.org/browse/JBWS-3166 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-native-3.4.0.CR1 > Reporter: Jim Ma > Assignee: Jim Ma > > We can probably add some more convenient APIs in cxf to configure the MTOMFeature easily. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3571) SOAPAddressWSDLParser does not process wsdl imports

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3571?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3571: ----------------------------------------------- Mustafa Musaji <mmusaji(a)redhat.com> made a comment on [bug 916944|https://bugzilla.redhat.com/show_bug.cgi?id=916944] Deleted unnecessary patch branch https://svn.jboss.org/repos/jbossws/thirdparty/cxf/branches/cxf-2.4.9.jbo... [mmusaji@mmusaji jbossws-common-2.0.4.GA_BZ-916944]$ svn ci -m "[BZ916944] Added changes from JBWS-3570" Authentication realm: <https://svn.jboss.org:443> JBoss Labs SVN Repository Password for 'mmusaji': Sending src/main/java/org/jboss/ws/common/deployment/Message.properties Sending src/main/java/org/jboss/ws/common/deployment/SOAPAddressWSDLParser.java Transmitting file data .. Committed revision 17384. [mmusaji@mmusaji jbossws-cxf-4.0.6.GA_BZ-916944]$ svn ci -m "[BZ916944] Merged changes from JBWS-3571" Authentication realm: <https://svn.jboss.org:443> JBoss Labs SVN Repository Password for 'mmusaji': Sending modules/server/src/main/java/org/jboss/wsf/stack/cxf/RequestHandlerImpl.java Sending modules/server/src/main/java/org/jboss/wsf/stack/cxf/configuration/BusHolder.java Sending modules/server/src/main/java/org/jboss/wsf/stack/cxf/configuration/NonSpringBusHolder.java Sending modules/server/src/main/java/org/jboss/wsf/stack/cxf/configuration/SpringBusHolder.java Sending modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/BusDeploymentAspect.java Sending modules/server/src/main/java/org/jboss/wsf/stack/cxf/metadata/MetadataBuilder.java Sending modules/server/src/main/java/org/jboss/wsf/stack/cxf/metadata/services/DDEndpoint.java Sending modules/server/src/main/java/org/jboss/wsf/stack/cxf/transport/AddressRewritingEndpointInfo.java Sending modules/server/src/main/java/org/jboss/wsf/stack/cxf/transport/SoapTransportFactoryExt.java Sending modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/jbws3098/BusHolderLifeCycleTestCase.java Transmitting file data .......... Committed revision 17385. > SOAPAddressWSDLParser does not process wsdl imports > --------------------------------------------------- > > Key: JBWS-3571 > URL: https://issues.jboss.org/browse/JBWS-3571 > 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.1 > > > The SOAPAddressWSDLParser currently does not process wsdl imports, so it basically misses soap:address entries corresponding to bindings living in imported wsdl docs. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3571) SOAPAddressWSDLParser does not process wsdl imports

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3571?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3571: ----------------------------------------------- Mustafa Musaji <mmusaji(a)redhat.com> made a comment on [bug 916944|https://bugzilla.redhat.com/show_bug.cgi?id=916944] I'm attaching a test patch > SOAPAddressWSDLParser does not process wsdl imports > --------------------------------------------------- > > Key: JBWS-3571 > URL: https://issues.jboss.org/browse/JBWS-3571 > 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.1 > > > The SOAPAddressWSDLParser currently does not process wsdl imports, so it basically misses soap:address entries corresponding to bindings living in imported wsdl docs. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3138) Better support for local WSDL deployment configurations (e.g., wsimport -clientjar)

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3138?page=com.atlassian.jira.plugin.... ] Jim Ma commented on JBWS-3138: ------------------------------ The -clientjar flag is already added in CXF: https://issues.apache.org/jira/browse/CXF-4871. After move to the next cxf release, we can add this in wsimport. > Better support for local WSDL deployment configurations (e.g., wsimport -clientjar) > ----------------------------------------------------------------------------------- > > Key: JBWS-3138 > URL: https://issues.jboss.org/browse/JBWS-3138 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-native, productivity, tools-jaxws > Affects Versions: jbossws-cxf-3.3.1, jbossws-native-3.3.1, jbossws-native-3.4.0.CR1 > Reporter: Ray Cardillo > Assignee: Jim Ma > Labels: jax-ws-catalog, local_wsdl, wsconsume, wsimport, wsimport_-clientjar, wsimport_clientjar, xml_catalog > Fix For: jbossws-cxf-4.2 > > > Developers who must deploy to disconnected or closed network environments often have challenges creating local WSDL deployment configurations. This is especially true when they want to create a shared library or use a shared configuration that several projects must all use. For example, if there are several J2EE web applications and web services that are all clients of a particular web service, most developers end up copying all of the required WSDL content to the WEB-INF/wsdl folder of each project and then using the wsdlLocation attribute to specify the local WSDL files. This type of strategy is difficult to maintain, and the only other option is to create a shared OASIS XML catalog library. However, using a shared OASIS XML catalog library can be very challenging because of the details involved... putting a properly compiled schema catalog JAR (with a properly configured jax-ws-catalog.xml file) in the WEB-INF/lib and having the container use that JAR to resolve references by configuring the service endpoint with a reference that will be resolved by the JAR. For more information about that, see the last reference provided below, but the details are tricky to say the least, and some containers actually have problems with this type of deployment configuration. > To help with this requirement, JAX-WS 2.2.2 RI has added a "-clientjar" option to the "wsimport" tool. This feature is extremely important to anyone facing these challenges, and offers a huge productivity boost, from several perspectives. For developers who know how to navigate the complexity of doing this, it helps by doing all of the labor intensive steps automatically (downloading the WSDL, creating correct resource references, compiling the JAR properly, annotating the binding properly, etc). For developers who do not know about these details, it is even more valuable because this option is not very well known, yet is something that should be a primary use case (supporting people on isolated networks). The requirement is often overlooked by the web services frameworks because they assume everyone will always have network access, but isolated networks are very common in certain communities. > See the following for more references: > http://www.java.net/print/476434 > http://wikis.sun.com/display/GlassFish/3.1Metro#3.1Metro-wsimport%5Cclien... > http://forums.java.net/jive/message.jspa?messageID=480624#480624 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3571) SOAPAddressWSDLParser does not process wsdl imports

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3571?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3571: ----------------------------------------------- Mustafa Musaji <mmusaji(a)redhat.com> made a comment on [bug 916944|https://bugzilla.redhat.com/show_bug.cgi?id=916944] Created one off branch for jbossws-common: https://svn.jboss.org/repos/jbossws/common/branches/jbossws-common-2.0.4.... > SOAPAddressWSDLParser does not process wsdl imports > --------------------------------------------------- > > Key: JBWS-3571 > URL: https://issues.jboss.org/browse/JBWS-3571 > 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.1 > > > The SOAPAddressWSDLParser currently does not process wsdl imports, so it basically misses soap:address entries corresponding to bindings living in imported wsdl docs. -- 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, 9 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 March 2013