November 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1136) Allow username to be specified in the requires list

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1136?page=all ] Thomas Diesler updated JBWS-1136: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > Allow username to be specified in the requires list > --------------------------------------------------- > > Key: JBWS-1136 > URL: http://jira.jboss.com/jira/browse/JBWS-1136 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-1.0.1 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-1.0.6 > > > Allow username to be specified in the requires list for endpoints so that messages without the username can be rejected. > At the moment for EJB endpoints they can be configured using standard J2EE security so if there is no authenticated user the request is rejected, however this can't be done for the POJO endpoints. -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-805) Fault code is always 'Client'

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-805?page=all ] Thomas Diesler updated JBWS-805: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > Fault code is always 'Client' > ----------------------------- > > Key: JBWS-805 > URL: http://jira.jboss.com/jira/browse/JBWS-805 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.0.CR4 > Environment: JBoss-4.0.4RC2 > Reporter: Dave Head-Rapson > Assigned To: Thomas Diesler > Priority: Minor > Fix For: jbossws-1.0.6 > > > The faultCode on exceptions is always Client. Even for java.rmi.ServerError types. > As I understand it, the faultCode should be Server if there's nothing wrong with the message sent to the web service. > to replicate: > * Deploy a web service that is missing a dependent class i.e. will throw a NoClassDefFoundError on execution. > * Invoke the web service > * If the log4j level is set to DEBUG, you'll see the exception, which will have fault code Client. -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1217) WSDLtoJava Namespace to package mapping does not support multiple namespaces

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1217?page=all ] Thomas Diesler updated JBWS-1217: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > WSDLtoJava Namespace to package mapping does not support multiple namespaces > ---------------------------------------------------------------------------- > > Key: JBWS-1217 > URL: http://jira.jboss.com/jira/browse/JBWS-1217 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.3 > Reporter: Magesh Kumar B > Priority: Minor > Fix For: jbossws-1.0.6 > > > Consider the following WSDL: > <?xml version="1.0" encoding="UTF-8"?> > <definitions name='MySEIService' targetNamespace='http://javatype.mycompany.com' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:ns1='http://other.com' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://javatype.mycompany.com' xmlns:xsd='http://www.w3.org/2001/XMLSchema'> > <types> > <schema targetNamespace='http://other.com' xmlns='http://www.w3.org/2001/XMLSchema' xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' xmlns:tns='http://other.com' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'> > <complexType name='TestException'> > <sequence/> > </complexType> > <element name='TestException' type='tns:TestException'/> > </schema> > </types> > <message name='MySEI_testException'/> > <message name='MySEI_testExceptionResponse'/> > <message name='TestException'> > <part element='ns1:TestException' name='TestException'/> > </message> > <portType name='MySEI'> > <operation name='testException'> > <input message='tns:MySEI_testException'/> > <output message='tns:MySEI_testExceptionResponse'/> > <fault message='tns:TestException' name='TestException'/> > </operation> > </portType> > <binding name='MySEIBinding' type='tns:MySEI'> > <soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/> > <operation name='testException'> > <soap:operation soapAction=''/> > <input> > <soap:body namespace='http://javatype.mycompany.com' use='literal'/> > </input> > <output> > <soap:body namespace='http://javatype.mycompany.com' use='literal'/> > </output> > <fault name='TestException'> > <soap:fault name='TestException' use='literal'/> > </fault> > </operation> > </binding> > <service name='MySEIService'> > <port binding='tns:MySEIBinding' name='MySEIPort'> > <soap:address location='REPLACE_WITH_ACTUAL_URL'/> > </port> > </service> > </definitions> > Using the following wstools config: > <configuration xmlns="http://www.jboss.org/jbossws-tools"> > <global> > <package-namespace package="com.other" namespace="http://other.com"/> > <package-namespace package="com.mycompany.javatype" namespace="http://javatype.mycompany.com"/> > </global> > <wsdl-java file="MySEIService.wsdl"> > <mapping file="jaxrpc-mapping.xml" /> > </wsdl-java> > </configuration> > The TestException class is not generated in the com.other package. -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-985) Array property type generated twice

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-985?page=all ] Thomas Diesler updated JBWS-985: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > Array property type generated twice > ----------------------------------- > > Key: JBWS-985 > URL: http://jira.jboss.com/jira/browse/JBWS-985 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.1 > Reporter: Thomas Diesler > Fix For: jbossws-1.0.6 > > > @WebMethod > public RUCASConnectResponse RUCASConnect( > AppInfo appInfo, > LoginMethod[] loginMethods, > CryptMethod[] cryptMethods > ) > { > return null; > } > > Code: > <definitions name='SessionManagementService' targetNamespace='http://com.roshka.services/myapplicatio > n/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:ns1='http://security.beans.rucas.set.gov.py/jaws' > xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://com.roshka.services/myapplicat > ion/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'> > <types> > <schema elementFormDefault='qualified' targetNamespace='http://com.roshka.services/myapplication/' xm > lns='http://www.w3.org/2001/XMLSchema' xmlns:ns2='http://www.w3.org/2001/XMLSchema' xmlns:ns3='http: > //security.beans.rucas.set.gov.py/jaws' xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' > xmlns:tns='http://com.roshka.services/myapplication/' xmlns:xsi='http://www.w3.org/2001/XMLSchema-i > nstance'> > <import namespace='http://security.beans.rucas.set.gov.py/jaws'/> > <import namespace='http://www.w3.org/2001/XMLSchema'/> > <complexType name='AppInfo'> > <sequence> > <element name='language' nillable='true' type='string'/> > <element name='name' nillable='true' type='string'/> > <element name='uuid' nillable='true' type='string'/> > <element name='version' nillable='true' type='string'/> > </sequence> > </complexType> > <complexType name='ClientSystem'> > <sequence> > <element name='id' nillable='true' type='int'/> > <element name='name' nillable='true' type='string'/> > <element name='password' nillable='true' type='base64Binary'/> > </sequence> > </complexType> > <complexType name='CryptMethod'> > <sequence> > <element name='code' nillable='true' type='string'/> > <element name='name' nillable='true' type='string'/> > <element name='version' nillable='true' type='string'/> > </sequence> > </complexType> > <complexType name='CryptMethod.Array'> > <sequence> > <element maxOccurs='unbounded' minOccurs='0' name='value' nillable='true' type='ns3:CryptMethod'/> > </sequence> > </complexType> > <complexType name='LoginMethod'> > <sequence> > <element name='code' nillable='true' type='string'/> > <element name='name' nillable='true' type='string'/> > <element name='version' nillable='true' type='string'/> > </sequence> > </complexType> > <complexType name='LoginMethod.Array'> > <sequence> > <element maxOccurs='unbounded' minOccurs='0' name='value' nillable='true' type='ns3:LoginMethod'/> > </sequence> > </complexType> > <complexType name='RUCASConnectResponse'> > <sequence> > <element name='cryptMethod' nillable='true' type='ns3:CryptMethod'/> > <element name='loginMethod' nillable='true' type='ns3:LoginMethod'/> > <element name='temporarySessionId' nillable='true' type='string'/> > </sequence> > </complexType> > <complexType name='RUCASLoginResponse'> > <sequence> > <element name='permanentSessionId' nillable='true' type='string'/> > <element name='success' nillable='true' type='boolean'/> > </sequence> > </complexType> > </schema> > <schema elementFormDefault='qualified' targetNamespace='http://security.beans.rucas.set.gov.py/jaws' > xmlns='http://www.w3.org/2001/XMLSchema' xmlns:ns1='http://com.roshka.services/myapplication/' xmlns > :ns2='http://www.w3.org/2001/XMLSchema' xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' > xmlns:tns='http://security.beans.rucas.set.gov.py/jaws' xmlns:xsi='http://www.w3.org/2001/XMLSchema > -instance'> > <import namespace='http://com.roshka.services/myapplication/'/> > <import namespace='http://www.w3.org/2001/XMLSchema'/> > <complexType name='CryptMethod'> > <sequence> > <element name='code' nillable='true' type='string'/> > <element name='name' nillable='true' type='string'/> > <element name='version' nillable='true' type='string'/> > </sequence> > </complexType> > <complexType name='LoginMethod'> > <sequence> > <element name='code' nillable='true' type='string'/> > <element name='name' nillable='true' type='string'/> > <element name='version' nillable='true' type='string'/> > </sequence> > </complexType> > </schema> > </types> -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-844) Add support for a fully defined schema with a message endpoint

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-844?page=all ] Thomas Diesler updated JBWS-844: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > Add support for a fully defined schema with a message endpoint > -------------------------------------------------------------- > > Key: JBWS-844 > URL: http://jira.jboss.com/jira/browse/JBWS-844 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Jason T. Greene > Assigned To: Darran Lofthouse > Fix For: jbossws-1.0.6 > > > Currently a SOAPElement can only be mapped to a xsd:any type. We should add support for mapping SOAPElement to a message that has been fully specified. This would allow for the WSDL to represent a fully defined contract, and yet still allow the endpoint to have flexible parsing. > -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

18 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-751) Multiple schema imports with the same namespace

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-751?page=all ] Thomas Diesler updated JBWS-751: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > Multiple schema imports with the same namespace > ----------------------------------------------- > > Key: JBWS-751 > URL: http://jira.jboss.com/jira/browse/JBWS-751 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wstools > Reporter: Thomas Diesler > Fix For: jbossws-1.0.6 > > > <types> > <xs:schema> > <xs:import namespace="uri:tranHistory" schemaLocation="TransactionHistoryRq.xsd"/> > <xs:import namespace="uri:tranHistory" schemaLocation="TransactionHistoryRs.xsd"/> > <xs:import namespace="uri:tranHistory" schemaLocation="StatusRs.xsd"/> > </xs:schema> > </types> > Current handling of schema imports is incorrect, since it does not allow for multiple imports with the same namespace. > private void handleSchemaImports(Element schemaEl, URL wsdlLoc) throws MalformedURLException > { > if (wsdlLoc == null) > throw new IllegalArgumentException("Cannot process import, parent location not set"); > > Iterator it = DOMUtils.getChildElements(schemaEl, new QName(Constants.NS_SCHEMA_XSD, "import")); > while (it.hasNext()) > { > Element includeEl = (Element)it.next(); > String schemaLocation = includeEl.getAttribute("schemaLocation"); > String namespace = includeEl.getAttribute("namespace"); > > log.trace("handleSchemaImport: [namespace=" + namespace + ",schemaLocation=" + schemaLocation + "]"); > > // Skip, let the entity resolver resolve these > if (namespace.length() > 0 && schemaLocation.length() > 0) > { > URL currLoc = this.getLocationURL(wsdlLoc, schemaLocation); > schemaLocationsMap.put(namespace, currLoc); > } > else > { > log.warn("Skip invalid schema import: [namespace=" + namespace + ",schemaLocation=" + schemaLocation + "]"); > } > } > } -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-777) TransportOptionsTestCase does not fail wihout keystore

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-777?page=all ] Thomas Diesler updated JBWS-777: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > TransportOptionsTestCase does not fail wihout keystore > ------------------------------------------------------ > > Key: JBWS-777 > URL: http://jira.jboss.com/jira/browse/JBWS-777 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-1.0.6 > > > Testcase: testWithoutKeystore took 0.1 sec > FAILED > Expected security exception > junit.framework.AssertionFailedError: Expected security exception > at org.jboss.test.webservice.secure.noenv.TransportOptionsTestCase.testWithoutKeystore(TransportOptionsTestCase.java:116) > 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

18 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1241) BaseDataTypesRpcLit_Service - RetString - CR and CRLF handling

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1241?page=all ] Thomas Diesler updated JBWS-1241: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > BaseDataTypesRpcLit_Service - RetString - CR and CRLF handling > --------------------------------------------------------------- > > Key: JBWS-1241 > URL: http://jira.jboss.com/jira/browse/JBWS-1241 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: binding > Affects Versions: jbossws-2.0.0.Beta > Reporter: Jason T. Greene > Fix For: jbossws-1.0.6 > > > CR Fails: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><RetString xmlns="http://tempuri.org/"><inString xmlns="">HelloWorld</inString></RetString></s:Body></s:Envelope> > CRLF fails: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><RetString xmlns="http://tempuri.org/"><inString xmlns="">Hello > World</inString></RetString></s:Body></s:Envelope> > The returned value for both is LF only, which is incorrect. -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1283) Soap attachments were dropped on server responses. Attachment is added on a handler's handleResponse method; however it mysteriously disappeared on the outgoing soap message.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1283?page=all ] Thomas Diesler updated JBWS-1283: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > Soap attachments were dropped on server responses. Attachment is added on a handler's handleResponse method; however it mysteriously disappeared on the outgoing soap message. > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBWS-1283 > URL: http://jira.jboss.com/jira/browse/JBWS-1283 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.2 > Environment: windows, linux, jdk1.5 > Reporter: George Gan > Fix For: jbossws-1.0.6 > > Attachments: ServiceEndpointInvoker.java, ServiceEndpointInvokerEJB21.java > > > Soap attachments were dropped on server responses. Attachment can be added on a handler's handleResponse method; however it mysteriously disappeared on the outgoing soap message. > The problem was in the ServiceEndpointInvoker. It overwrote the SOAPMessage in the MessageContext. In this class, the method invokeServiceEndpoint was overwritten by ServiceEndpointInvokerEJB21, which invokes the EJB via the ServiceEndpointInterceptor. This ServiceEndpointInterceptor invokes the EJB and also the handlers; it creates the correct SOAPMessage and sets it in the ContextContext. Unfortunately, it was overwritten later by the ServiceEndpointInvoker. > Fixes are attached. -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-801) Chunked transfer of large attachments

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-801?page=all ] Thomas Diesler updated JBWS-801: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > Chunked transfer of large attachments > ------------------------------------- > > Key: JBWS-801 > URL: http://jira.jboss.com/jira/browse/JBWS-801 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Heiko Braun > Fix For: jbossws-1.0.6 > > > We are using SAAJ to send soap messages to IRS and v r trying a send a file of 600Mb. V r willing to send the file with "chunked" transfer-encoding method. I know that this is a Http Header but where should it be set, i mean does it go to the SOAPMessage or SOAPPart or AttachmentPart.. > I am using saaj and have taken the same approach as specified in jbossws guide (http://labs.jboss.com/portal/jbossws/user-guide/en/html/attachments.html#.... regarding the log all i get is OutOfMemoryException -- 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

18 years

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 November 2006