January 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-976) Enforce wsdl:part element(s) that have been defined using the type attribute.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-976?page=all ] Thomas Diesler updated JBWS-976: -------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Enforce wsdl:part element(s) that have been defined using the type attribute. > ----------------------------------------------------------------------------- > > Key: JBWS-976 > URL: http://jira.jboss.com/jira/browse/JBWS-976 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-3.x > > > From BP 1.1: > R2203 An rpc-literal binding in a DESCRIPTION MUST refer, in its soapbind:body element(s), only to wsdl:part element(s) that have been defined using the type attribute. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-798) Complete EventingTestCase

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-798?page=all ] Thomas Diesler updated JBWS-798: -------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Complete EventingTestCase > ------------------------- > > Key: JBWS-798 > URL: http://jira.jboss.com/jira/browse/JBWS-798 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-eventing > Reporter: Thomas Diesler > Fix For: jbossws-3.x > > > // > // "http://schemas.xmlsoap.org/ws/2004/08/eventing/DeliveryFailure" > // This value MUST be used if the event source terminated the subscription > // because of problems delivering notifications. > // > public void testSubscriptionEndMessage() > { > System.out.println("FIXME: testSubscriptionEnd"); > } > // > // "http://schemas.xmlsoap.org/ws/2004/08/eventing/SourceShuttingDown" > // This value MUST be used if the event source terminated the subscription > // because the source is being shut down in a controlled manner; > // that is, if the event source is being shut down but has the opportunity > // to send a SubscriptionEnd message before it exits. > // > public void testShutdownMessage() > { > System.out.println("FIXME: testShutdownMessage"); > } > // > // "http://schemas.xmlsoap.org/ws/2004/08/eventing/SourceCanceling" > // This value MUST be used if the event source terminated the subscription > // for some other reason before it expired. > // > public void testCancelMessage() > { > System.out.println("FIXME: testCancelMessage"); > } -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1069) Add security-constraint in generated web.xml for Endpoint API

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1069?page=all ] Thomas Diesler updated JBWS-1069: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Add security-constraint in generated web.xml for Endpoint API > ------------------------------------------------------------- > > Key: JBWS-1069 > URL: http://jira.jboss.com/jira/browse/JBWS-1069 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-3.x > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-759) Refactor DOMUtils

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-759?page=all ] Thomas Diesler updated JBWS-759: -------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Refactor DOMUtils > ----------------- > > Key: JBWS-759 > URL: http://jira.jboss.com/jira/browse/JBWS-759 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Heiko Braun > Fix For: jbossws-3.x > > > DOMUtils is not a stateless helper. It maintains state per thread (i.d. DOM Document, DocumentBuilder) > Threads can potentially be longliving objects (i.e from the tomcat worker pool) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-804) Provide an OASIS catalog wiki

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-804?page=all ] Thomas Diesler updated JBWS-804: -------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Provide an OASIS catalog wiki > ----------------------------- > > Key: JBWS-804 > URL: http://jira.jboss.com/jira/browse/JBWS-804 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-3.x > > > http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossOASISCatalog -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1105) SOAPMessageContext.getHeaders should return unmarshalled objects

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1105?page=all ] Thomas Diesler updated JBWS-1105: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > SOAPMessageContext.getHeaders should return unmarshalled objects > ---------------------------------------------------------------- > > Key: JBWS-1105 > URL: http://jira.jboss.com/jira/browse/JBWS-1105 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-3.x > > > Current impl return SOAPHeaderElement objects -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1531) Support to create custom SOAP Fault from EJB3 Web Service

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1531?page=all ] Thomas Diesler updated JBWS-1531: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Support to create custom SOAP Fault from EJB3 Web Service > --------------------------------------------------------- > > Key: JBWS-1531 > URL: http://jira.jboss.com/jira/browse/JBWS-1531 > Project: JBoss Web Services > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: jbossws-native > Environment: not specific > Reporter: Vinay Kumar > Fix For: jbossws-3.x > > > At this moment, we cannot create custom SOAP fault from a EJB3 Web Service. > This exception handling logic is coded inside org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper class. If you read the method "exceptionToFaultMessage(Exception reqEx)", then you find that it is throwing the same SOAPFaultException if it is receiving one. But, with EJB3 web service, every exception is bundled inside EJBException & then thrown to container. As a result this module only gets EJBException. So, that condition is not relevant to this scenario. > One way to this solution could be that you check if the argument is instanceof EJBException then take the cause. And, if that cause is the custom SOAPFaultException; then it becomes a small easy solution. > But, this is not sufficient. As you have exposed your SLSB as Web Service & we can also access that bean through RMI. > And, SOAPFaultException cannot be raised through RMI; it raises some problem while serlializing XML elements. > As a result, the last proposal also fades away. > Practically, we need something that checks if it is RMI raise the same exception & if it is SOAP then create custom SOAPFault from the same. > Looking forward to your advice. > regards -- 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, 4 months

1
0
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.x (was: jbossws-3.0.1) > 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.x > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1582) Externalize parser properties

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1582?page=all ] Thomas Diesler updated JBWS-1582: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Externalize parser properties > ----------------------------- > > Key: JBWS-1582 > URL: http://jira.jboss.com/jira/browse/JBWS-1582 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Priority: Critical > Fix For: jbossws-3.x > > > A question has come up around the dtd entity parsing denial of service issue raised here: > http://www-128.ibm.com/developerworks/xml/library/x-tipcfsx.html > http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150... > Are we allowing for the use of the parser.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true) to limit the defaults? > What about disabling doctypes via the http://apache.org/xml/features/disallow-doctype-decl feature: > http://xerces.apache.org/xerces2-j/features.html -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-788) Non-blocking one way invocations

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-788?page=all ] Thomas Diesler updated JBWS-788: -------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Non-blocking one way invocations > -------------------------------- > > Key: JBWS-788 > URL: http://jira.jboss.com/jira/browse/JBWS-788 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Ivan Neto > Assigned To: Thomas Diesler > Fix For: jbossws-3.x > > > Asynchronous calls (CallImpl.invokeOneWay()) block the client thread until the remote invocation completes on the server side. There's room for improvement, since the client thread could be unblocked as soon as the server validated the request. -- 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, 4 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 2008