May 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1633) Provide configuration of ws-security ad policy assertion

by Stefano Maestri (JIRA)

Provide configuration of ws-security ad policy assertion -------------------------------------------------------- Key: JBWS-1633 URL: http://jira.jboss.com/jira/browse/JBWS-1633 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxws Reporter: Stefano Maestri Assigned To: Stefano Maestri Fix For: jbossws-2.1.0 The goal is to provide a policy assertion implementation using jboss-ws-security_1_0.xsd schema. The policy will be equivalent to actual external file. -- 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 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1395) Add a Standard All Client Configuration to standard-jbossws-client-config.xml

by John Gilbert (JIRA)

Add a Standard All Client Configuration to standard-jbossws-client-config.xml ----------------------------------------------------------------------------- Key: JBWS-1395 URL: http://jira.jboss.com/jira/browse/JBWS-1395 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxws Reporter: John Gilbert Priority: Trivial It would be nice to have this in addition to Standard Client, Standard Secure Client, and Standard Addressing Client, so that all clients don't have to create their config file. <client-config> <config-name>Standard All Client</config-name> <post-handler-chain> <handler-chain-name>PostHandlerChain</handler-chain-name> <handler> <j2ee:handler-name>WSSecurityHandlerOutbound</j2ee:handler-name> <j2ee:handler-class>org.jboss.ws.wsse.WSSecurityHandlerOutbound</j2ee:handler-class> </handler> <handler> <j2ee:handler-name>SOAPClientHandler</j2ee:handler-name> <j2ee:handler-class>org.jboss.ws.addressing.soap.SOAPClientHandler</j2ee:handler-class> </handler> </post-handler-chain> </client-config> -- 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 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1471) Remove unwated tomcat excludes

by Thomas Diesler (JIRA)

Remove unwated tomcat excludes ------------------------------ Key: JBWS-1471 URL: http://jira.jboss.com/jira/browse/JBWS-1471 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-2.0.0 # TODO: Why are these excluded org/jboss/test/ws/jaxws/samples/wseventing/** org/jboss/test/ws/jaxrpc/samples/wssecurity/StorePassEncryptTestCase.* -- 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 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1412) WS-Eventing clustering capabilities

by Heiko Braun (JIRA)

WS-Eventing clustering capabilities ----------------------------------- Key: JBWS-1412 URL: http://jira.jboss.com/jira/browse/JBWS-1412 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-eventing 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1461) Migrate our addressing impl to JAXB

by Heiko Braun (JIRA)

Migrate our addressing impl to JAXB ----------------------------------- Key: JBWS-1461 URL: http://jira.jboss.com/jira/browse/JBWS-1461 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Fix For: jbossws-2.0.0 When the addressing custom types (epr, etc) will be marshalled by JAXB, they could be easily be reused to represent addressing elements inside the soap body. -- 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 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1314) Precursor to streaming optimizations, elimination of xmlFragment

by Thomas Diesler (JIRA)

Precursor to streaming optimizations, elimination of xmlFragment ---------------------------------------------------------------- Key: JBWS-1314 URL: http://jira.jboss.com/jira/browse/JBWS-1314 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxws Reporter: Thomas Diesler Fix For: jbossws-2.0.1 At some point, we should remove the xml string fragment processing phase. It's not needed in our long term streaming optimization plan, and it adds unneeded performance overhead in the current design. Instead we could pass the corresponding DOM chunk directly to the marshalling layer. JAXB supports this using javax.xml.transform.Source, and it wouldn't be difficult to enhance JBossXB to do the same. This would also be more robust because it would eliminate the xml escape processing that we duplicate from a standard XML parser (see [JBWS-1240] for an example). -- 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 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-1670) SunRI client does not throw UserException

by Thomas Diesler (JIRA)

SunRI client does not throw UserException ----------------------------------------- Key: JBWS-1670 URL: http://jira.jboss.com/jira/browse/JBWS-1670 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: integration-sunri Reporter: Thomas Diesler Fix For: jbossws-2.1.0 [tdiesler@tddell sunri]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.exception.ExceptionTestCase one-test one-test: [junit] Running org.jboss.test.ws.jaxws.samples.exception.ExceptionTestCase [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 5.974 sec [junit] Test org.jboss.test.ws.jaxws.samples.exception.ExceptionTestCase FAILED -- 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 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-1669) Fix WebServiceContext.getMessageContext()

by Thomas Diesler (JIRA)

Fix WebServiceContext.getMessageContext() ----------------------------------------- Key: JBWS-1669 URL: http://jira.jboss.com/jira/browse/JBWS-1669 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-sunri Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.1.0 tests-run-internal: [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase [junit] Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 7.163 sec [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3.312 sec BUILD SUCCESSFUL Total time: 15 seconds [tdiesler@tddell sunri]$ cat output-tests/reports/TEST-org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase.txt Testsuite: org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 7.163 sec Testcase: testGetWebContext took 1.919 sec FAILED expected:<pass> but was:<fail> junit.framework.ComparisonFailure: expected:<pass> but was:<fail> at org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase.testGetWebContext(WebServiceContextEJBTestCase.java:71) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- 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 months

1
6
0 / 0

[JBoss JIRA] Created: (JBWS-1667) Implement WSContractProvider for Sun-RI integration

by Heiko Braun (JIRA)

Implement WSContractProvider for Sun-RI integration --------------------------------------------------- Key: JBWS-1667 URL: http://jira.jboss.com/jira/browse/JBWS-1667 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: integration-sunri Affects Versions: jbossws-2.1.0 Reporter: Heiko Braun Assigned To: 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1656) XFire does not default to the correct namespace

by Thomas Diesler (JIRA)

XFire does not default to the correct namespace ----------------------------------------------- Key: JBWS-1656 URL: http://jira.jboss.com/jira/browse/JBWS-1656 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-xfire Affects Versions: xfire-1.2.6 Reporter: Thomas Diesler Unexpected response element {http://eardeployment.jaxws.ws.test.jboss.org}echoResponse expected: {http://eardeployment.jaxws.ws.test.jboss.org/}echoResponse Note, the trailing slash -- 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 months

1
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues May 2007