June 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1644) Process wsdl extensibility elements

by Alessio Soldano (JIRA)

Process wsdl extensibility elements ----------------------------------- Key: JBWS-1644 URL: http://jira.jboss.com/jira/browse/JBWS-1644 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assigned To: Alessio Soldano Fix For: jbossws-2.0.1 Wsdl extensibility elements/attributes have to be dealt in both marshalling and unmarshalling of wsdl to the unified wsdl structure. This is required to collect eventual policy attachment in wsdl or wsdl fragments. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1645) Modify WSDLGenerator to deal with policies

by Alessio Soldano (JIRA)

Modify WSDLGenerator to deal with policies ------------------------------------------ Key: JBWS-1645 URL: http://jira.jboss.com/jira/browse/JBWS-1645 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-policy Reporter: Alessio Soldano Fix For: jbossws-2.0.1 Given the unified metadata model containing the supported policies, the WSDLGenerator has to be modified to deal with them and produce the corresponding extensibility elements in the unified wsdl structure. Endpoint policy subjects only will be supported for now. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1704) The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All Requests

by Darran Lofthouse (JIRA)

The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All Requests ---------------------------------------------------------------------------------------- Key: JBWS-1704 URL: http://jira.jboss.com/jira/browse/JBWS-1704 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Reporter: Darran Lofthouse Fix For: jbossws-2.1.0 The use of JBoss Remoting causes a datatype parameter to be sent with all outgoing requests, this parameter is not required by the server and can cause problems as some loadbalancers reject the message. The reason for this is because of a workaround required in JBoss Remoting 1.4.5 to register the marshaller. See the createRemotingClient method: - http://anonsvn.jboss.org/repos/jbossws/tags/jbossws-1.2.1.GA/jbossws-core... It is possible to check the Remoting version using the following method: - public static int getDefaultVersion() >From 'org.jboss.remoting.Version', a possible solution will be to check the version to decide if we need to register the marshaller in this way. -- 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, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-1330) Fix jaxrpc wsse tests for jbossws-5.0

by Thomas Diesler (JIRA)

Fix jaxrpc wsse tests for jbossws-5.0 ------------------------------------- Key: JBWS-1330 URL: http://jira.jboss.com/jira/browse/JBWS-1330 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-2.0.0.CR2 [tdiesler@tdvaio test]$ ant -Dtest=jaxrpc/wsse test tests-main: [junit] Running org.jboss.test.ws.jaxrpc.wsse.MicrosoftInteropTestCase [junit] FIXME: [JBWS-1130] Consolidate namespace declarations [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.863 sec [junit] Running org.jboss.test.ws.jaxrpc.wsse.NotEncodedTestCase [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 3.536 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.NotEncodedTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.RoundTripTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3.289 sec [junit] Running org.jboss.test.ws.jaxrpc.wsse.RpcTestCase [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 6.722 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.RpcTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.SignEncryptFaultTestCase [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 7.19 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.SignEncryptFaultTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.SignFaultTestCase [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 5.947 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.SignFaultTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.SimpleSignEncryptTestCase [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 6.581 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.SimpleSignEncryptTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.StorePassEncryptTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 5.452 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.StorePassEncryptTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.SunInteropTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.382 sec [junit] Running org.jboss.test.ws.jaxrpc.wsse.UsernameTestCase [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 0.431 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.UsernameTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.WebClientTestCase [junit] [JBAS-3824] Fix ENC for EJB2.1 and Servlets [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.524 sec [junit] Running org.jboss.test.ws.jaxrpc.wsse.signup.AccountSignupTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 4.64 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.signup.AccountSignupTestCase 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, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-1694) SOAP header not being set as request param

by Heiko Braun (JIRA)

SOAP header not being set as request param ------------------------------------------ Key: JBWS-1694 URL: http://jira.jboss.com/jira/browse/JBWS-1694 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-1453) WSDl To Java - Invalid name for generated class if complex type name contains a period.

by Darran Lofthouse (JIRA)

WSDl To Java - Invalid name for generated class if complex type name contains a period. --------------------------------------------------------------------------------------- Key: JBWS-1453 URL: http://jira.jboss.com/jira/browse/JBWS-1453 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: wstools Affects Versions: jbossws-1.2.0.CR2 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.2.1 The following compex type: - <complexType name='String.Array'> <sequence> <element maxOccurs='unbounded' minOccurs='0' name='value' nillable='true' type='string'/> </sequence> </complexType> Causes the following class to be generated: - package org.jboss.support.phonebook; public class String.Array { protected java.lang.String[] value; public String.Array(){} public String.Array(java.lang.String[] value){ this.value=value; } public java.lang.String[] getValue() { return value ;} public void setValue(java.lang.String[] value){ this.value=value; } } This class name is invalid and the period needs to be replaced. -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1307) JAXWS user guide and sampes

by Thomas Diesler (JIRA)

JAXWS user guide and sampes --------------------------- Key: JBWS-1307 URL: http://jira.jboss.com/jira/browse/JBWS-1307 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: documentation Reporter: Thomas Diesler Fix For: jbossws-2.0.0 The user guide should cover all aspects of the JAXWS specification. Every chapter should be associated with code samples. It should be possible to take the userguide + samples and have instant working code as a easy entry point to JAXWS -- 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

17 years

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-1661) Update to jaxb-ri-2.1

by Heiko Braun (JIRA)

Update to jaxb-ri-2.1 ---------------------- Key: JBWS-1661 URL: http://jira.jboss.com/jira/browse/JBWS-1661 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.1.0 This is a container issue for dependent issues that require a JAXB update -- 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

17 years

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1722) Multiple context root not supported EJB2.1

by Giovanni Anastalo (JIRA)

Multiple context root not supported EJB2.1 ------------------------------------------ Key: JBWS-1722 URL: http://jira.jboss.com/jira/browse/JBWS-1722 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-jaxrpc Affects Versions: jbossws-1.2.1 Environment: OS:linux; application server:jboss-4.0.2.CR2 Reporter: Giovanni Anastalo I'm using ejb 2.1 17:09:10,157 INFO [EARDeployer] Init J2EE application: file:/home/jops/Programmi/jboss/jboss-4.2.0.CR2/server/default/deploy/progMW.ear 17:09:10,692 INFO [EjbModule] Deploying AutoriEntity 17:09:10,703 INFO [EjbModule] Deploying DocumentoEntity 17:09:10,712 INFO [EjbModule] Deploying IdEntityBean 17:09:10,787 INFO [EjbModule] Deploying DocumentoOldEntity 17:09:10,814 INFO [EjbModule] Deploying LoginWs 17:09:10,832 INFO [EjbModule] Deploying AteneoWs 17:09:10,851 INFO [EjbModule] Deploying DipartimentoWs 17:09:11,540 ERROR [ServiceEndpointPublisher] Cannot obtain waURL for: progMW.ear/progMW.jar 17:09:11,541 ERROR [MainDeployer] Could not create deployment: file:/home/jops/Programmi/jboss/jboss-4.2.0.CR2/server/default/tmp/deploy/tmp8223progMW.ear-contents/progMW.jar org.jboss.deployment.DeploymentException: Cannot create service endpoint; - nested throwable: (org.jboss.ws.WSException: Multiple context root not supported) at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53) at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:83) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy32.create(Unknown Source) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: org.jboss.ws.WSException: Multiple context root not supported at org.jboss.ws.integration.jboss42.ServiceEndpointGeneratorEJB.createJBossWebAppDescriptor(ServiceEndpointGeneratorEJB.java:258) at org.jboss.ws.integration.jboss42.ServiceEndpointGeneratorEJB.generatWebDeployment(ServiceEndpointGeneratorEJB.java:71) at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB21.generateWebDeployment(DeployerInterceptorEJB21.java:114) at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB.createServiceEndpoint(DeployerInterceptorEJB.java:49) at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:78) ... 29 more Is there an equivalent solution with ejb 2.1 to @WebContext(contextRoot="/beans") in ejb 3? thanks -- 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

17 years

2
3
0 / 0

[JBoss JIRA] Updated: (JBWS-624) Tools: testsuite/src/resources/webservice/jbws381

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-624?page=all ] Thomas Diesler updated JBWS-624: -------------------------------- Comment: was deleted > Tools: testsuite/src/resources/webservice/jbws381 > ------------------------------------------------- > > Key: JBWS-624 > URL: http://jira.jboss.com/jira/browse/JBWS-624 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tools-jaxrpc > Reporter: Jason T. Greene > Assigned To: Jason T. Greene > Fix For: jbossws-1.0.0.CR4 > > > [wstools] at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:88) > [wstools] at org.jboss.ws.tools.WSDLToJava.generateJavaSource(WSDLToJava.java:491) > [wstools] at org.jboss.ws.tools.WSDLToJava.getReturnType(WSDLToJava.java:377) > [wstools] at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:219) > [wstools] at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:320) > [wstools] at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:342) > [wstools] at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:173) > [wstools] at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:190) > [wstools] at org.jboss.ws.tools.jbossws.process(jbossws.java:101) > [wstools] at org.jboss.ws.tools.jbossws.generate(jbossws.java:84) > [wstools] at org.jboss.ws.tools.ant.wstools.execute(wstools.java:103) > [wstools] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) > [wstools] at org.apache.tools.ant.Task.perform(Task.java:364) > [wstools] at org.apache.tools.ant.Target.execute(Target.java:341) > [wstools] at org.apache.tools.ant.Target.performTasks(Target.java:369) > [wstools] at org.apache.tools.ant.Project.executeTarget(Project.java:1214) > [wstools] at org.apache.tools.ant.Project.executeTargets(Project.java:1062) > [wstools] at org.apache.tools.ant.Main.runBuild(Main.java:673) > [wstools] at org.apache.tools.ant.Main.startAnt(Main.java:188) > [wstools] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:196) > [wstools] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:55) -- 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

17 years, 1 month

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 June 2007