February 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1993) Test remoting 2.4.0.CR1

by Heiko Braun (JIRA)

Test remoting 2.4.0.CR1 ------------------------ Key: JBWS-1993 URL: http://jira.jboss.com/jira/browse/JBWS-1993 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-native-2.0.4 Should be included in AS 5 CR1, but it needs to be verified first -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1968) Documentation support for WSDL->Java

by Magesh Kumar B (JIRA)

Documentation support for WSDL->Java ------------------------------------ Key: JBWS-1968 URL: http://jira.jboss.com/jira/browse/JBWS-1968 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: tools-jaxws Reporter: Magesh Kumar B Priority: Minor Alessio Soldano says in JBWS-1850: "Doc support for WSDL->Java would require changes to the wsconsume tool and will thus be covered in another issue. " --> Opened this JIRA to cover that -- 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-1965) subscribe method on subscription manager - NullPointerException

by Antonio Souza (JIRA)

subscribe method on subscription manager - NullPointerException --------------------------------------------------------------- Key: JBWS-1965 URL: http://jira.jboss.com/jira/browse/JBWS-1965 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-eventing Affects Versions: jbossws-2.0.1.SP2 Environment: JBoss 4.2.2 / JDK 1.5_14 / Windows XP MCE / JBossWS 2.0.1-SP2 Reporter: Antonio Souza The subscribe method raises NullPointerException when trying to subscribe to an event source with the state of 'CREATED'. This happens because there's no SubscriptionManager endpoint declared. The event source never goes 'STARTED'. In the subscribe method when trying to get where managerAddress, it returns null raising NullPointerException. It should have an assertion on the EventSource object, verifying whether or not it is 'STARTED' as below: org.jboss.ws.extensions.eventing.mgmt.SubscriptionManager 303: if (null == eventSource) 304: throw new SubscriptionError(EventingConstants.CODE_UNABLE_TO_PROCESS, "EventSource '" + eventSourceNS + "' not registered"); Assertion snippet after 304: if (eventSource.getState() != STARTED) throw new SubscriptionError(EventingConstants.CODE_UNABLE_TO_PROCESS, "EventSource '" + eventSourceNS + "' not started"); or something like that. The exception happens here: 341: attrURI.setValue(eventSource.getManagerAddress().toString()); eventSource.getManagerAddress returns null raising NullPointerException. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBWS-2009) Get FileNotFoundException for nested included xsd files

by Franz Willer (JIRA)

Get FileNotFoundException for nested included xsd files ------------------------------------------------------- Key: JBWS-2009 URL: http://jira.jboss.com/jira/browse/JBWS-2009 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-2.0.1.SP2 Environment: JBoss-4.2.2.GA Reporter: Franz Willer I have following (simplified) structure: WEB-INF/wsdl/test.wsdl WEB-INF/schema/test/test.xsd WEB-INF/schema/ebRS/rs.xsd In test.wsdl is test.xsd imported (../schema/test/test.xsd) In test.xsd is rs.xsd imported (../ebRS/rs.xsd) Deployment failed with a FileNotFound Exception ( ..../wsdl/schema/ebRS/rs.xsd vs. i would expect: .../schema/ebRS/rs.xsd) I tracked the problem down to WSDLFilePublisher.publishSchemaImports: the resourcePath contains two slashes ( WEB-INF/wsdl//..schema/test/../ebRS/rs.xsd) before getting the resourceURL. I think this caused the getMetaDataFileURL method to treat the '..' part after wsdl wrong. (when i correct the resourcePath value it works fine) -- 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
4
0 / 0

[JBoss JIRA] Created: (JBWS-1966) No Handler execution for inbound response when using Dispatch

by Ciro Cavani (JIRA)

No Handler execution for inbound response when using Dispatch ------------------------------------------------------------- Key: JBWS-1966 URL: http://jira.jboss.com/jira/browse/JBWS-1966 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native, ws-security Affects Versions: jbossws-2.0.2 Environment: Java5 (1.5.0_13) Ubuntu 7.10 Reporter: Ciro Cavani It seems that DispatchImpl don't change message direction before executing handlers over response message. (this affects WS-Security implementation) -- 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
4
0 / 0

[JBoss JIRA] Commented: (JBWS-1211) Add support for @WebFault

by Alessio Soldano (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1211?page=comments#action_12400174 ] Alessio Soldano commented on JBWS-1211: --------------------------------------- In the mean time other tests were written using WebFault, first of all the exception test case in the framework testsuite. Thus I've added a test case to cover just the last missing thing, i.e. the fault element name/namespace dependence on the @WebFault annotation. > Add support for @WebFault > ------------------------- > > Key: JBWS-1211 > URL: http://jira.jboss.com/jira/browse/JBWS-1211 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Alessio Soldano > Fix For: jbossws-native-2.0.4 > > -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1776) Verify isolated classloading with WSProvide

by Heiko Braun (JIRA)

Verify isolated classloading with WSProvide ------------------------------------------- Key: JBWS-1776 URL: http://jira.jboss.com/jira/browse/JBWS-1776 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: tools-jaxws 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, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-1980) Inlining multiple XML Schema with same targetNamespace

by Dietmar Scheidl (JIRA)

Inlining multiple XML Schema with same targetNamespace ------------------------------------------------------ Key: JBWS-1980 URL: http://jira.jboss.com/jira/browse/JBWS-1980 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.1.SP2 Reporter: Dietmar Scheidl According to WSDL-2.0 Specification it is possible to have multiple schemas for the same targetNamespace. -- 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-1998) Bindings Package Customization and case sensitivity

by Magesh Kumar B (JIRA)

Bindings Package Customization and case sensitivity --------------------------------------------------- Key: JBWS-1998 URL: http://jira.jboss.com/jira/browse/JBWS-1998 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: tools-jaxws Affects Versions: jbossws-2.0.1.SP2 Reporter: Magesh Kumar B Priority: Trivial When we customize the package through the bindings tag inside the wsdl and using wsconsume the Exception wrapper is generated with the same name and causes "duplicate class" error while compiling. Consider the following wsdl: <definitions name='TestEndpointService' targetNamespace='http://org.jboss.ws/jaxws/asynchronous' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://org.jboss.ws/jaxws/asynchronous' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:jaxws="http://java.sun.com/xml/ns/jaxws" xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"> <jaxws:bindings> <jaxws:package name="ws.jboss.org.jaXWS.asynchronous"/> </jaxws:bindings> <types> <xsd:schema targetNamespace="http://org.jboss.ws/jaxws/asynchronous" xmlns:tns="http://org.jboss.ws/jaxws/asynchronous"> <xsd:element name="Exception" type="tns:Exception"/> <xsd:element name="echo" type="tns:echo"/> <xsd:element name="echoResponse" type="tns:echoResponse"/> <xsd:complexType name="echo"> <xsd:sequence> <xsd:element minOccurs="0" name="String_1" type="xsd:string"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="echoResponse"> <xsd:sequence> <xsd:element minOccurs="0" name="result" type="xsd:string"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="Exception"> <xsd:sequence> <xsd:element minOccurs="0" name="message" type="xsd:string"/> </xsd:sequence> </xsd:complexType> </xsd:schema> </types> <message name='TestEndpoint_echoResponse'> <part name='echoResponse' element='tns:echoResponse'/> </message> <message name='TestEndpoint_echo'> <part name='echo' element='tns:echo'/> </message> <message name="Exception"> <part name="Exception" element='tns:Exception'/> </message> <portType name='TestEndpoint'> <operation name='echo' parameterOrder='echo'> <input message='tns:TestEndpoint_echo'/> <output message='tns:TestEndpoint_echoResponse'/> <fault name="Exception" message="tns:Exception"/> </operation> </portType> <binding name='TestEndpointBinding' type='tns:TestEndpoint'> <soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/> <operation name='echo'> <soap:operation soapAction=''/> <input> <soap:body use='literal'/> </input> <output> <soap:body use='literal'/> </output> <fault name="Exception"> <soap:fault name="Exception" use="literal"/> </fault> </operation> </binding> <service name='TestEndpointService'> <port binding='tns:TestEndpointBinding' name='TestEndpointPort'> <soap:address location='http://tdvaio:8080/jaxws-samples-asynchronous/TestEndpoint'/> </port> </service> </definitions> The generation happens like below: parsing WSDL... generating code... ws\jboss\org\jaxws\asynchronous\Echo.java ws\jboss\org\jaxws\asynchronous\EchoResponse.java ws\jboss\org\jaxws\asynchronous\Exception.java ws\jboss\org\jaxws\asynchronous\ObjectFactory.java ws\jboss\org\jaxws\asynchronous\package-info.java ws\jboss\org\jaXWS\asynchronous\Exception.java ws\jboss\org\jaXWS\asynchronous\TestEndpoint.java ws\jboss\org\jaXWS\asynchronous\TestEndpointService.java I:\dev\IssueTracker\cases\161559\out4\ws\jboss\org\jaXWS\asynchronous\Exception.java:14: duplicate class: ws.jboss.org.jaXWS.asynchronous.Exception public class Exception ^ This is purely because of the package name containing the UPPER case characters "jaXWS". This is very trivial but neverthless it works with the same package name from the command line switch "-p". %JBOSS_HOME%\bin\wsconsume -k -p ws.jboss.org.jaXWS.asynchronous -o out4 TestService.wsdl parsing WSDL... generating code... ws\jboss\org\jaXWS\asynchronous\Echo.java ws\jboss\org\jaXWS\asynchronous\EchoResponse.java ws\jboss\org\jaXWS\asynchronous\Exception.java ws\jboss\org\jaXWS\asynchronous\Exception_Exception.java ws\jboss\org\jaXWS\asynchronous\ObjectFactory.java ws\jboss\org\jaXWS\asynchronous\TestEndpoint.java ws\jboss\org\jaXWS\asynchronous\TestEndpointService.java ws\jboss\org\jaXWS\asynchronous\package-info.java The generator is strict on case sensitivity on one side and ignores the case on other side hence the error perhaps. The code for generation should be re-used rather than having different path for different methods. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBWS-1872) EJB3 WebService implementation must have @Remote (instead of @Local) Business interface

by Michael McKibben (JIRA)

EJB3 WebService implementation must have @Remote (instead of @Local) Business interface --------------------------------------------------------------------------------------- Key: JBWS-1872 URL: http://jira.jboss.com/jira/browse/JBWS-1872 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.1 Environment: JBossAS 4.2.2.GA Reporter: Michael McKibben When my EJB has a @Local annotation I get the following error: 2007-10-24 17:55:04,811 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/home/mike/Applications/jboss-4.2.2.GA/server/all/deploy/admanager-ws.jar java.lang.NullPointerException at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderEJB3.buildMetaData(JAXWSMetaDataBuilderEJB3.java:69) at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:71) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115) at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97) at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) 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 $Proxy34.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor25.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:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.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.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.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.server.Invocation.invoke(Invocation.java:86) 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 $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 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 $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) Replacing @Local annotation with @Remote, my EJB endpoint deploys cleanly -- 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
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues February 2008