April 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2091) We should provide JBossWS console for Metro and CXF integration too

by Richard Opalka (JIRA)

We should provide JBossWS console for Metro and CXF integration too ------------------------------------------------------------------- Key: JBWS-2091 URL: http://jira.jboss.com/jira/browse/JBWS-2091 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro Affects Versions: jbossws-cxf-1.0.1, jbossws-metro-1.0.1 Reporter: Richard Opalka Fix For: jbossws-metro-1.0.2, jbossws-cxf-1.0.2 At the moment we provide JBossWS console for native only. We should include Metro and CXF to provide this console too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
5
0 / 0

[JBoss JIRA] Updated: (JBWS-555) wstools ant task has classloading problems

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-555?page=all ] Thomas Diesler updated JBWS-555: -------------------------------- Fix Version/s: (was: community contributions) Resolve outdated issues > wstools ant task has classloading problems > ------------------------------------------ > > Key: JBWS-555 > URL: http://jira.jboss.com/jira/browse/JBWS-555 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tools-jaxrpc > Reporter: Jason T. Greene > > Something is wrong with classloader handling in the wstools ant task. It will only work if log4j.jar is in the original ANT_CLASSPATH. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-565) Tools is missing the abiilty to change the xmlType for a parameter

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-565?page=all ] Thomas Diesler updated JBWS-565: -------------------------------- Fix Version/s: (was: community contributions) Resolve outdated issues > Tools is missing the abiilty to change the xmlType for a parameter > ------------------------------------------------------------------ > > Key: JBWS-565 > URL: http://jira.jboss.com/jira/browse/JBWS-565 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tools-jaxrpc > Reporter: Jason T. Greene > > The wsdl for the marshall tests can not be generated because there is no ability to customize an xmlType.Some Java types can be mapped to multiple xmlTypes. For example byte[] can be mapped to: > xsd:base64Binary > -or- > xsd:hexBinary > -or- > <complexType name="byteArray"/> > <sequence> > <element name="byte" minOccurs="0" maxOccurs="unbounded"/> > </sequence> > </complexType> > -Jason -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2101) Tomcat module needs to refer to SPI 1.0.2

by Heiko Braun (JIRA)

Tomcat module needs to refer to SPI 1.0.2 ----------------------------------------- Key: JBWS-2101 URL: http://jira.jboss.com/jira/browse/JBWS-2101 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Heiko Braun -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1930) Remove dependency on stax-api.jar

by Heiko Braun (JIRA)

Remove dependency on stax-api.jar --------------------------------- Key: JBWS-1930 URL: http://jira.jboss.com/jira/browse/JBWS-1930 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.2 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.1.0 JBossWS should rely on jboss-javaee.jar instead -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
7
0 / 0

[JBoss JIRA] Commented: (JBWS-679) Initial implementation of SSO/Security context propogation support

by Andrei Iltchenko (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-679?page=comments#action_12406554 ] Andrei Iltchenko commented on JBWS-679: --------------------------------------- Jason, Thomas, Prompted by your setting this request to "Out of Date" I wonder how does solves the problem of SSO for WS communication now? Thanks, Andrei. > Initial implementation of SSO/Security context propogation support > ------------------------------------------------------------------ > > Key: JBWS-679 > URL: http://jira.jboss.com/jira/browse/JBWS-679 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Jason T. Greene > > We should offer the ability to issue and propogate security tokens within web service requests. This would allow for a service endpoint to propogate the callers identity to any internal or external web service that it invokes. This should be done in a portable way, since a destination service can be running on any platform on any location on the internet. > There are a number of specifications that could achieve this functionality: > WS-Trust > SAML > WS-Security Kerberos Token Profile > WS-Security SAML Token Profile > Alot of this will depend on the new security framework being developerd. > The first release of such functionality could be focused on a pure JBoss environment. > -Jason -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2092) MetaData projet needs to refer to SPI 1.0.2

by Heiko Braun (JIRA)

MetaData projet needs to refer to SPI 1.0.2 ------------------------------------------- Key: JBWS-2092 URL: http://jira.jboss.com/jira/browse/JBWS-2092 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Heiko Braun -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
3
0 / 0

[JBoss JIRA] Updated: (JBWS-1526) Automated testing and availablity checks of public endpoints (interop)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1526?page=all ] Thomas Diesler updated JBWS-1526: --------------------------------- Fix Version/s: jbossws-3.0.2 (was: jbossws-3.x) Description: Is this a duplicate? > Automated testing and availablity checks of public endpoints (interop) > ---------------------------------------------------------------------- > > Key: JBWS-1526 > URL: http://jira.jboss.com/jira/browse/JBWS-1526 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-3.0.2 > > > Is this a duplicate? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1462) JMSTransportSupport should set JMSCorrelationID on response message if it is was set on the incomming request.

by Darran Lofthouse (JIRA)

JMSTransportSupport should set JMSCorrelationID on response message if it is was set on the incomming request. -------------------------------------------------------------------------------------------------------------- Key: JBWS-1462 URL: http://jira.jboss.com/jira/browse/JBWS-1462 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxrpc Affects Versions: jbossws-1.0.3 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.2.1 If an incomming request has the JMSCorrelationID set it should be set on the outgoing response message as this is a mechanism that can be used to track which responses correspond to which requests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-1652) ServiceEndpoint requirements for JBossESB

by Tom Fennelly (JIRA)

ServiceEndpoint requirements for JBossESB ----------------------------------------- Key: JBWS-1652 URL: http://jira.jboss.com/jira/browse/JBWS-1652 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Fennelly JBossESB implements what it calls a "JBossWSAdapter" (http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/core/listeners/...). This class allows the ESB to expose JBossWS endpoints through the ESB i.e. over all transport protocols supported by the ESB. In order to do this, JBossWSAdapter currently relies on a number of non-public JBossWS classes (tested against jbossws-1.0.3.SP1 only). After talking with Thomas (at JavaOne), we established that JBossWS will have a public API that will fit our requirements. This JIRA is just to track the ESB requirements in this area. So the ESB needs the following: 1. The ability to "lookup" a JBossWS ServiceEndpoint (or its equivalent in the new API). We currently use the ServiceEndpointManagerFactory to do this. 2. The ability to invoke the ServiceEndpoint to process a SOAP payload (ala the "ServiceEndpoint.handleRequest" method in jbossws-1.0.3.SP1). 3. The ability to register/deploy endpoint implementations. Thomas showed me how this can be done, but I forget the exact code now without having the code in front of me :-) 4. The ability to get the endpoint WSDL from the ServiceEndpoint instance (ala the ServiceEndpoint.handleWSDLRequest method in jbossws-1.0.3.SP1). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2008