February 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1892) Link tests build file to the Eclipse configuration

by Alessio Soldano (JIRA)

Link tests build file to the Eclipse configuration -------------------------------------------------- Key: JBWS-1892 URL: http://jira.jboss.com/jira/browse/JBWS-1892 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano The Eclipse project configuration for JBossWS tests should come with an Ant build file too. They have to be linked. May be the current test build file (actually shipped in the binary release) is fine, perhaps it could be simplified a bit for this (still to be evaluated) -- 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, 2 months

2
1
0 / 0

[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, 2 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, 2 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-1997) Update doc about supported application server versions

by Alessio Soldano (JIRA)

Update doc about supported application server versions ------------------------------------------------------ Key: JBWS-1997 URL: http://jira.jboss.com/jira/browse/JBWS-1997 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Fix For: jbossws-native-2.0.4 The documentation has to be updated before next release since support for AS 4.0 has been removed. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1995) Fix cxf build issues

by Thomas Diesler (JIRA)

Fix cxf build issues -------------------- Key: JBWS-1995 URL: http://jira.jboss.com/jira/browse/JBWS-1995 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Richard Opalka Fix For: jbossws-metro-1.0.1 The build fails when invoked with Ant. If this is intensional, we should have proper error messages [tdiesler@tddell trunk]$ ant main build.metro: [exec] Buildfile: metro-build-adapter.xml [exec] BUILD FAILED [exec] Target `WSIT.main' does not exist in this project. It is used from target `-metro.runtime.jar'. [exec] Total time: 1 second BUILD FAILED /home/tdiesler/svn/jbossws/stack/metro/trunk/ant-import/build-metro.xml:78: The following error occurred while executing this line: /home/tdiesler/svn/jbossws/stack/metro/trunk/ant-import/build-metro.xml:23: exec returned: 1 -- 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, 2 months

1
1
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, 2 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, 2 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, 3 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, 3 months

1
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