May 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3632) Overwrite the webservice annotation using XML file

by kiran varanasi (JIRA)

[ https://issues.jboss.org/browse/JBWS-3632?page=com.atlassian.jira.plugin.... ] kiran varanasi updated JBWS-3632: --------------------------------- Description: We are using Jboss 4.2.3 GA ,which support JAXWS webservices. Webservice also as Stateless EJB. The deployment path of jar file is under webservices.war->webserviceEJB.jar. Using @webContext annotation the webservice is running on SSL. To avoid code change any XML configuration file is required which can define the @WebContext values for tranport-guarantee attribute.All the websevices has @WebContext with auth-method =BASIC and transport-guarantee =NONE. We need to overwrite the annontation using XML file. The idea of using configuration files is Webservices need to be configured in jboss either on http or https. Please reply that jboss 4.2.3GA support @WebContext values in configuration file for SSL and the required dependancy jars. was: We are using Jboss 4.2.3 GA ,which support JAXWS webservices. Webservice also as Stateless EJB. The deployment path of jar file is under webservices.war->webserviceEJB.jar. Using @webContext annotation the webservice is running on SSL. To avoid code change any XML configuration file is required which can define the @WebContext values for tranport-guarantee attribute.All the websevices has @WebContext with auth-method =BASIC and transport-guarantee =NONE. We need to overwrite the annontation using XML file. The idea of using configuration files is Webservices need to be configured in jboss either on http or https. Please reply that jboss 4.2.3GA support @WebContext values in configuration file for SSL and dependancy jars. > Overwrite the webservice annotation using XML file > -------------------------------------------------- > > Key: JBWS-3632 > URL: https://issues.jboss.org/browse/JBWS-3632 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: kiran varanasi > > We are using Jboss 4.2.3 GA ,which support JAXWS webservices. Webservice also as Stateless EJB. The deployment path of jar file is under webservices.war->webserviceEJB.jar. Using @webContext annotation the webservice is running on SSL. To avoid code change any XML configuration file is required which can define the @WebContext values for tranport-guarantee attribute.All the websevices has @WebContext with auth-method =BASIC and transport-guarantee =NONE. We need to overwrite the annontation using XML file. > The idea of using configuration files is Webservices need to be configured in jboss either on http or https. Please reply that jboss 4.2.3GA support @WebContext values in configuration file for SSL and the required dependancy jars. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3632) Overwrite the webservice annotation using XML file

by kiran varanasi (JIRA)

[ https://issues.jboss.org/browse/JBWS-3632?page=com.atlassian.jira.plugin.... ] kiran varanasi updated JBWS-3632: --------------------------------- Summary: Overwrite the webservice annotation using XML file (was: Overwrite the webservice annontation using XML file) > Overwrite the webservice annotation using XML file > -------------------------------------------------- > > Key: JBWS-3632 > URL: https://issues.jboss.org/browse/JBWS-3632 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: kiran varanasi > > We are using Jboss 4.2.3 GA ,which support JAXWS webservices. Webservice also as Stateless EJB. The deployment path of jar file is under webservices.war->webserviceEJB.jar. Using @webContext annotation the webservice is running on SSL. To avoid code change any XML configuration file is required which can define the @WebContext values for tranport-guarantee attribute.All the websevices has @WebContext with auth-method =BASIC and transport-guarantee =NONE. We need to overwrite the annontation using XML file. > The idea of using configuration files is Webservices need to be configured in jboss either on http or https. Please reply that jboss 4.2.3GA support @WebContext values in configuration file for SSL and dependancy jars. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3632) Overwrite the webservice annontation using XML file

by kiran varanasi (JIRA)

kiran varanasi created JBWS-3632: ------------------------------------ Summary: Overwrite the webservice annontation using XML file Key: JBWS-3632 URL: https://issues.jboss.org/browse/JBWS-3632 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: kiran varanasi We are using Jboss 4.2.3 GA ,which support JAXWS webservices. Webservice also as Stateless EJB. The deployment path of jar file is under webservices.war->webserviceEJB.jar. Using @webContext annotation the webservice is running on SSL. To avoid code change any XML configuration file is required which can define the @WebContext values for tranport-guarantee attribute.All the websevices has @WebContext with auth-method =BASIC and transport-guarantee =NONE. We need to overwrite the annontation using XML file. The idea of using configuration files is Webservices need to be configured in jboss either on http or https. Please reply that jboss 4.2.3GA support @WebContext values in configuration file for SSL and dependancy jars. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3607) Missing import/export of CXF schemas in AS modules

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3607?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3607: ---------------------------------- Issue Type: Bug (was: Feature Request) > Missing import/export of CXF schemas in AS modules > -------------------------------------------------- > > Key: JBWS-3607 > URL: https://issues.jboss.org/browse/JBWS-3607 > 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.2 > > > The AS modules that currently set dependencies on cxf module (and on jbossws-cxf-transports-httpserver) are using explicit imports elements for including META-INF and META-INF/cxf. We might need to also include schemas/** too (to be verified if that's already covered by default or not) -- 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

10 years, 11 months

1
0
0 / 0

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

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3606?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3606: ---------------------------------- Issue Type: Task (was: Feature Request) > 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: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.1.3 > Reporter: Jim Ma > Assignee: 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3602) Missing javax.servlet.api dependency in org.jboss.ws.jaxws-client AS module

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3602?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3602: ---------------------------------- Issue Type: Bug (was: Feature Request) > Missing javax.servlet.api dependency in org.jboss.ws.jaxws-client AS module > --------------------------------------------------------------------------- > > Key: JBWS-3602 > URL: https://issues.jboss.org/browse/JBWS-3602 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-4.2 > > > The org.jboss.ws.jaxws-client module is missing a dependency on the javax.servlet.api module. That is causing a NCDFE on ServletException when the endpoint destination cannot be matched with the context + url pattern specified in the request. > This is only reproducible using the jbossws-cxf integration w/ spring and having an endpoint whose address declaration in jbossws-cxf.xml is different from the computed address (context + url pattern) -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-1537) Add support for XML property files to override/augment JSR-181 webservice annotations

by kiran varanasi (JIRA)

[ https://issues.jboss.org/browse/JBWS-1537?page=com.atlassian.jira.plugin.... ] kiran varanasi commented on JBWS-1537: -------------------------------------- Please suggest whether this issue is resolved with Jboss 4.2.3GA > Add support for XML property files to override/augment JSR-181 webservice annotations > ------------------------------------------------------------------------------------- > > Key: JBWS-1537 > URL: https://issues.jboss.org/browse/JBWS-1537 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-1.0.4 > Reporter: david.boeren > Priority: Minor > Fix For: jbossws-2.0.0.CR5 > > > This is a request for an enhancement to JBossWS so that all webservice related annotations can be overridden/augmented by settings specified in an XML deployment descriptor. This feature already existing in other projects such as the ejb-jar.xml file overriding basic EJB3 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3596) Provide support for WS-Discovery

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3596?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3596: ---------------------------------- Issue Type: Feature Request (was: Task) > Provide support for WS-Discovery > -------------------------------- > > Key: JBWS-3596 > URL: https://issues.jboss.org/browse/JBWS-3596 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > This is about including the cxf-services-ws-discovery-api component in the application server and verifying endpoints are properly registered for WS-Discovery probing during deployment. > We need an alternative approach for enabling WS-Discovery for a user deployment (as the classpath based approach [1] does not fit the AS server side), e.g. a property to be specified in jboss-webservices.xml descriptor. > [1] http://cxf.apache.org/docs/ws-discovery.html -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3596) Provide support for WS-Discovery

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3596?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3596: ---------------------------------- Description: This is about including the cxf-services-ws-discovery-api component in the application server and verifying endpoints are properly registered for WS-Discovery probing during deployment. We need an alternative approach for enabling WS-Discovery for a user deployment (as the classpath based approach [1] does not fit the AS server side), e.g. a property to be specified in jboss-webservices.xml descriptor. [1] http://cxf.apache.org/docs/ws-discovery.html was:This is about verifying WS-Discovery client functionalities when running with cxf integrated in jbossws. > Provide support for WS-Discovery > -------------------------------- > > Key: JBWS-3596 > URL: https://issues.jboss.org/browse/JBWS-3596 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > This is about including the cxf-services-ws-discovery-api component in the application server and verifying endpoints are properly registered for WS-Discovery probing during deployment. > We need an alternative approach for enabling WS-Discovery for a user deployment (as the classpath based approach [1] does not fit the AS server side), e.g. a property to be specified in jboss-webservices.xml descriptor. > [1] http://cxf.apache.org/docs/ws-discovery.html -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3596) Provide testcase for WS-Discovery functionalities

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3596?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3596: ---------------------------------- Assignee: Alessio Soldano > Provide testcase for WS-Discovery functionalities > ------------------------------------------------- > > Key: JBWS-3596 > URL: https://issues.jboss.org/browse/JBWS-3596 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > This is about verifying WS-Discovery client functionalities when running with cxf integrated in jbossws. -- 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

10 years, 11 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 May 2013