November 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1188) Relax requirement for wsu:id for UsernameToken

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1188?page=all ] Thomas Diesler updated JBWS-1188: --------------------------------- 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. > Relax requirement for wsu:id for UsernameToken > ---------------------------------------------- > > Key: JBWS-1188 > URL: http://jira.jboss.com/jira/browse/JBWS-1188 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-1.0.3 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-1.0.6 > > > The JBossWS UsernameToken implementation is mandating that the wsu:id attribute is present on incomming requests. > Some thirdparty web services stacks being used as clients to JBossWS do not send the ID so we are rejecting the request. Additionally we do not actually use the id anywhere anyway. > The requirement for the id should be relaxed. -- 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] Created: (JBWS-1318) JSR-181 array issue

by Jason T. Greene (JIRA)

JSR-181 array issue ------------------- Key: JBWS-1318 URL: http://jira.jboss.com/jira/browse/JBWS-1318 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Jason T. Greene Fix For: jbossws-1.0.5 junit] java.rmi.RemoteException: Call invocation failed: Java type 'class com.siemens.ivon.soap.client.ServiceWSArray' is not assignable from: [Lcom.siemens.ivon.soap.client.ServiceWS;; nested exception is: [junit] org.jboss.ws.WSException: Java type 'class com.siemens.ivon.soap.client.ServiceWSArray' is not assignable from: [Lcom.siemens.ivon.soap.client.ServiceWS; [junit] at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:719) [junit] at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:398) [junit] at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:164) [junit] at $Proxy1.getServiceInfos(Unknown Source) [junit] at com.siemens.ivon.facade.soap.TestServiceSOAP.testGetServiceInfos(TestServiceSOAP.java:336) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:585) [junit] at junit.framework.TestCase.runTest(TestCase.java:164) [junit] at junit.framework.TestCase.runBare(TestCase.java:130) [junit] at junit.framework.TestResult$1.protect(TestResult.java:110) [junit] at junit.framework.TestResult.runProtected(TestResult.java:128) [junit] at junit.framework.TestResult.run(TestResult.java:113) [junit] at junit.framework.TestCase.run(TestCase.java:120) [junit] at junit.framework.TestSuite.runTest(TestSuite.java:228) [junit] at junit.framework.TestSuite.run(TestSuite.java:223) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:289) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:656) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:558) [junit] Caused by: org.jboss.ws.WSException: Java type 'class com.siemens.ivon.soap.client.ServiceWSArray' is not assignable from: [Lcom.siemens.ivon.soap.client.ServiceWS; [junit] at org.jboss.ws.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:299) [junit] at org.jboss.ws.binding.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:233) [junit] at org.jboss.ws.binding.EndpointInvocation.getReturnValue(EndpointInvocation.java:182) [junit] at org.jboss.ws.jaxrpc.CallImpl.syncOutputParams(CallImpl.java:871) [junit] at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:706) [junit] ... 19 more public class ServiceWS { private Long id; private String name; public Long getId(){ return this.id;} public void setId(Long id) {this.id = id;} public String getName(){return this.name;}; public void setName(String name){this.name=name;} } Then there is the ServiceWSArray class public class ServiceWSArray { private ServiceWS[] value; public ServiceWSArray() { } public ServiceWS[] getValue() { return this.value; } public void setValue(ServiceWS[] value) { this.value = value; } } And finally there is my webservice endpoint @Stateless @WebService(serviceName="MyWebService") @SOAPBinding(style=Style.RPC,use=Use.LITERAL) public class FacadeWS { @WebMethod public ServiceWSArray getServiceInfos() throws UnknownServiceProviderException { if (this.logger.isTraceEnabled()) this.logger.trace("SOAP:getServiceInfos"); ServiceWS[] services = new ServiceWS[10]; for (int i=0;i<10;i++) services = new ServiceWS.fromService(); ServiceWSArray result = new ServiceWSArray(); result.setValue(services); return result; } } On the junit client I create the port to this service and just call this this.getPort().getServiceInfos(); -- 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

2
2
0 / 0

[JBoss JIRA] Updated: (JBWS-1079) Incorrect WSDL to Java mapping for anonymous struct.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1079?page=all ] Thomas Diesler updated JBWS-1079: --------------------------------- 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. > Incorrect WSDL to Java mapping for anonymous struct. > ---------------------------------------------------- > > Key: JBWS-1079 > URL: http://jira.jboss.com/jira/browse/JBWS-1079 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.1, jbossws-1.0.0 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-1.0.6 > > > When running wsdl to java for a wsdl that contains a complex type that contains an anonymous struct the class generated for the anonymous struct is incorrect. > <xsd:complexType name="Person"> > <xsd:sequence> > <xsd:element name="Address"> > <xsd:complexType> > <xsd:sequence> > <xsd:element name="Address1" /> > </xsd:sequence> > </xsd:complexType> > </xsd:element> > </xsd:sequence> > </xsd:complexType> > The above example would generate an class with the name 'PersonAddress'. > From the jax-rpc specification (section 4.2.3) : - > " An XML struct maps to a JavaBeans class with the same name as the type of the XML struct. If the struct is anonymous, then the name of the nearest enclosing xsd:element, xsd:complexType or xsd:simpleType is used instead." > So the name of the generated type should be Address. > The generation of the jaxrpc-mapping actually does assume the generated class was generated with the name 'Address' so the code generation and jaxrpc-mapping generation are out of synch. -- 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-1243) ComplexDataTypesRpcList_Service - null structures result in members with null values

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1243?page=all ] Thomas Diesler updated JBWS-1243: --------------------------------- 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. > ComplexDataTypesRpcList_Service - null structures result in members with null values > ------------------------------------------------------------------------------------ > > Key: JBWS-1243 > URL: http://jira.jboss.com/jira/browse/JBWS-1243 > 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 > > > A null structure, like the following:: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Header> </s:Header> <s:Body> <RetStructS1 xmlns="http://tempuri.org/"> <inStructS1 xmlns:d4p1="http://schemas.datacontract.org/2004/07/XwsInterop.SoapWsdl.ComplexDataTy..." i:nil="true" xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="" /> </RetStructS1> </s:Body> </s:Envelope> > results in a member being set to null instead of the structure itself: > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Body> <ns1:RetStructS1Response xmlns:ns1="http://tempuri.org/"> <RetStructS1Result xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ns_name:name xmlns:ns_name="http://schemas.datacontract.org/2004/07/XwsInterop.SoapWsdl.ComplexDataTy..." xsi:nil="1"> </ns_name:name> </RetStructS1Result> </ns1:RetStructS1Response> </env:Body> </env:Envelope> -- 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-270) JBossWS Tools should not overwrite preexisting classes that were generated previously

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-270?page=all ] Thomas Diesler updated JBWS-270: -------------------------------- 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. > JBossWS Tools should not overwrite preexisting classes that were generated previously > ------------------------------------------------------------------------------------- > > Key: JBWS-270 > URL: http://jira.jboss.com/jira/browse/JBWS-270 > Project: JBoss Web Services > Issue Type: Task > Components: wstools > Reporter: Anil Saldhana > Fix For: jbossws-1.0.6 > > > If the user provides the global option "override" as false in the xml configuration file for tools, JBossWS tools should not overwrite pre-existing generated files. > <?xml version="1.0"?> >  > <configuration> > <global override="false"> > </configuration/> -- 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-1133) Unpacked JSR-181 POJO deployment fails for subsquent deployment.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1133?page=all ] Thomas Diesler updated JBWS-1133: --------------------------------- 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. > Unpacked JSR-181 POJO deployment fails for subsquent deployment. > ---------------------------------------------------------------- > > Key: JBWS-1133 > URL: http://jira.jboss.com/jira/browse/JBWS-1133 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxws > Affects Versions: jbossws-1.0.1 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-1.0.6 > > > Unpacked JSR-181 POJO deployments are not deployed correctly for subsequent server starts. > This is because when this is first deployed the web.xml which is part of the deployment is modified so that the JBossServiceEndpointServlet servlet is used. > On subsequent deployments the web.xml is parsed but because all of the servlet classes have been replaced with the JBossServiceEndpointServlet it is JBossServiceEndpointServlet that is checked for annotations instead of the endpoint class. -- 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] Created: (JBWS-1346) wsa:ReplyTo alwayt null

by Thomas Diesler (JIRA)

wsa:ReplyTo alwayt null ----------------------- Key: JBWS-1346 URL: http://jira.jboss.com/jira/browse/JBWS-1346 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.0.6 I have statefull JBoss WS and .NET client, but ws doen't read properly soap header for me! my client sent: <soap:Header> <wsa:Action></wsa:Action> <wsa:MessageID>urn:uuid:1fa5a31f-bbe7-4ad5-8b92-d765f4a32dc9</wsa:MessageID> <wsa:ReplyTo> <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address> <wsa:ReferenceParameters> <ns1:clientid xmlns:ns1="http://somens">clientid-1</ns1:clientid> </wsa:ReferenceParameters> </wsa:ReplyTo> <wsa:To>http://mycomp:8080/testws</wsa:To> <wsse:Security> <wsu:Timestamp wsu:Id="Timestamp-fca171ac-95a4-41e5-b0bf-b46438247a3d"> <wsu:Created>2006-11-01T15:06:15Z</wsu:Created> <wsu:Expires>2006-11-01T15:11:15Z</wsu:Expires> </wsu:Timestamp> </wsse:Security> </soap:Header> When i get addressing with: AddressingProperties addrProps = (AddressingProperties)messageContext.getProperty(JAXWSAConstants.SERVER_ADDRESSING_PROPERTIES_INBOUND); header information like "ReplyTo" is always null. I don't understand why? Some ideas and suggestions?! -- 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] Commented: (JBWS-1273) Release jbossws-1.0.5.GA binary

by Prabhat Jha (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1273?page=comments#action_12346635 ] Prabhat Jha commented on JBWS-1273: ----------------------------------- I have fired the tests run against 4.0.4.GA with jdk1.4, Branch4.0 with 1.5. > Release jbossws-1.0.5.GA binary > ------------------------------- > > Key: JBWS-1273 > URL: http://jira.jboss.com/jira/browse/JBWS-1273 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-1.0.5 > > > The release criteria for jbossws-1.1.0.GA are: > * pass all internal jbossws tests > * pass all portable j2ee-1.4 tests from the jboss testsuite > * pass all tests in module jaxr,jaxrpc,saaj,webservice from the Sun compatiblity testsuite > * generate all test artifacts with wstools -- 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] Commented: (JBWS-1294) Add support for mapping async methods

by Jason T. Greene (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1294?page=comments#action_12346615 ] Jason T. Greene commented on JBWS-1294: --------------------------------------- This is referring to the code generation rules, not the interpretation that the proxy must apply. "In the absence of customizations" means that the code generator can produce a method with a different name. So with the existing implementation, a customization would break the proxy. > Add support for mapping async methods > ------------------------------------- > > Key: JBWS-1294 > URL: http://jira.jboss.com/jira/browse/JBWS-1294 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxws > Reporter: Jason T. Greene > Assigned To: Jason T. Greene > Fix For: jbossws-2.0.0.CR2 > > > JSR181MetaDataBuilder, the UnifiedMetaDataModel, and ClientProxy need to be refactored. -- 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] Commented: (JBWS-1294) Add support for mapping async methods

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1294?page=comments#action_12346614 ] Heiko Braun commented on JBWS-1294: ----------------------------------- This is taken from the JAX-WS spec 2.1 MR - Oct 20 2006 "Conformance (Asynchronous method naming): In the absence of customizations, the name of the polling and callback methods MUST be the value of the name attribute of the wsdl:operation suffixed with "Async" mapped according to the rules described in sections 2.8 and 2.8.1." Looks like the Async suffix is perfectly valid... > Add support for mapping async methods > ------------------------------------- > > Key: JBWS-1294 > URL: http://jira.jboss.com/jira/browse/JBWS-1294 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxws > Reporter: Jason T. Greene > Assigned To: Jason T. Greene > Fix For: jbossws-2.0.0.CR2 > > > JSR181MetaDataBuilder, the UnifiedMetaDataModel, and ClientProxy need to be refactored. -- 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