January 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1891) Eclipse project configuration for JBossWS samples and tests

by Alessio Soldano (JIRA)

Eclipse project configuration for JBossWS samples and tests ----------------------------------------------------------- Key: JBWS-1891 URL: http://jira.jboss.com/jira/browse/JBWS-1891 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano -- 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
1
0 / 0

[JBoss JIRA] Created: (JBWS-1912) DispatcherDelegate - Bypass RMIAdaptor when used locally

by Magesh Kumar B (JIRA)

DispatcherDelegate - Bypass RMIAdaptor when used locally -------------------------------------------------------- Key: JBWS-1912 URL: http://jira.jboss.com/jira/browse/JBWS-1912 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-eventing Affects Versions: jbossws-2.0.1.SP2 Reporter: Magesh Kumar B When we dispatch an event from within the same JVM (through an ejb, jms component), an RMIAdaptor lookup is performed and then the SubscriptionManagerMBean is called to dispatch and this leads to the following error message if the jmx-console is secured: Exception in IncidentNotificationBean.wseNotify() : java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97) 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.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) 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.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.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118) at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:209) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:195) at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100) at $Proxy42.invoke(Unknown Source) at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201) at $Proxy542.dispatch(Unknown Source) at org.jboss.ws.extensions.eventing.mgmt.DispatcherDelegate.dispatch(DispatcherDelegate.java:42) -- 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
1
0 / 0

[JBoss JIRA] Created: (JBWS-1969) Cannot publish wsdl with imported schema files, using bottom up approach

by Maarten Moens (JIRA)

Cannot publish wsdl with imported schema files, using bottom up approach ------------------------------------------------------------------------ Key: JBWS-1969 URL: http://jira.jboss.com/jira/browse/JBWS-1969 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-2.0.2 Reporter: Maarten Moens When you create a Bottom up webservice and you normally want the existing wsdl to be used by the deployed service. On JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) combined withjbossws-native-2.0.1.GA or jbossws-native-2.0.2.GA the deploy of a EJB webservice endpoint with an wsdlLocation fails with the following error: org.jboss.ws.WSException: Cannot publish wsdl to: C:\<masked>\jbossxxx-node1\data\wsdl\echo.ear\echo-service.jar\echo\EchoService.wsdl ... Caused by: java.io.IOException: Cannot get URL for: META-INF/wsdl//echo/EchoService.xsd at org.jboss.wsf.common.URLLoaderAdapter.findChild(URLLoaderAdapter.java:106) at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99) If you don't use the hand written wsdl and let jboss generate it everything works just fine. The META-INF directory contains the following files: META-INF/ wsdl/echo/ EchoService.wsdl EchoService.xsd When you place the Wsdl and xsd directly in the wsdl directory everything works fine. However this is not an option because the real usecase is much more complicated with lots of other schema files to import. Sample code will be 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

16 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-1955) Use stable Metro CVS tag/version

by Thomas Diesler (JIRA)

Use stable Metro CVS tag/version -------------------------------- Key: JBWS-1955 URL: http://jira.jboss.com/jira/browse/JBWS-1955 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: jbossws-metro-1.0.0 Currently this is using a branch # metro cvs cvs.tag=WSIT-1_0-BRANCH and only works for # # Metro CVS access # cvs.user=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

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-1886) Provide basic configuration for WS-enabled user projects

by Alessio Soldano (JIRA)

Provide basic configuration for WS-enabled user projects -------------------------------------------------------- Key: JBWS-1886 URL: http://jira.jboss.com/jira/browse/JBWS-1886 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano Provide basic project configuration that users might use as a starting point for each of their ws-enabled projects. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBWS-1893) Provide meaningful advanced samples

by Alessio Soldano (JIRA)

Provide meaningful advanced samples ----------------------------------- Key: JBWS-1893 URL: http://jira.jboss.com/jira/browse/JBWS-1893 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano These should support tutorials in the documentation on advanced topics like security, attachments, addressing, etc. We should describe some scenarios, the possible technology solutions with their advantages and disadvantages, propose implementations and let users understand how to deal with some advanced real world issues. -- 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-1896) Create trailblazer or sample exercise, etc for each scenario

by Alessio Soldano (JIRA)

Create trailblazer or sample exercise, etc for each scenario ------------------------------------------------------------ Key: JBWS-1896 URL: http://jira.jboss.com/jira/browse/JBWS-1896 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano We should provide something to describe the scenario while letting the user play with it. She should be allowed to try different implementations, see the logs and request/response, etc. while following the description/explanation in the documentation. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBWS-1970) wsrunclient doesn't work with args

by Alessio Soldano (JIRA)

wsrunclient doesn't work with args ---------------------------------- Key: JBWS-1970 URL: http://jira.jboss.com/jira/browse/JBWS-1970 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productization Affects Versions: jbossws-2.0.2 Reporter: Alessio Soldano Assigned To: Alessio Soldano Priority: Minor Fix For: jbossws-native-2.0.4 Running something like this: ./wsrunclient.sh -classpath jaxws-samples-news-step1-agency.jar org.jboss.test.ws.jaxws.samples.news.Agency arg_one arg_two causes this: Exception in thread "main" java.lang.NoClassDefFoundError: arg_two The shell script need to be fixed since it overwrites the $args variable with the last argument specified. -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1894) Define scenarios and describe them

by Alessio Soldano (JIRA)

Define scenarios and describe them ---------------------------------- Key: JBWS-1894 URL: http://jira.jboss.com/jira/browse/JBWS-1894 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1977) Make client RM API optional

by Richard Opalka (JIRA)

Make client RM API optional --------------------------- Key: JBWS-1977 URL: http://jira.jboss.com/jira/browse/JBWS-1977 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.4 Users have to call RMProvider.createSequence() method to start RM message exchange now. This should be config driven and optional. -- 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

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