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

17 years, 10 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

17 years, 10 months

2
1
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

17 years, 11 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

17 years, 11 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

17 years, 11 months

1
3
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

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1911) Support for JMS transport bindings in Jbossws-2.0.1 and further

by Gopi Chand Uppala (JIRA)

Support for JMS transport bindings in Jbossws-2.0.1 and further --------------------------------------------------------------- Key: JBWS-1911 URL: http://jira.jboss.com/jira/browse/JBWS-1911 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-2.0.1 Environment: All Mid Range platforms ( AIX, Linux etc) Reporter: Gopi Chand Uppala AT&T is in a process of developing a web services framework for the Enterprise usage . The Requirements for this framework includes the support of JMS transport bindings with JAX-WS . JBoss EAP 4.3 (Jbossws 2.0.1) is being considered as one of the target containers for this framework and the inability to support the JMS transport with JAX-WS would eliminate JBoss as one of the three target Application Servers for web services usage in AT&T. This is very critical feature for AT&T and we would like Jboss to support it. -- 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, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (JBWS-1502) wsdl-java in wstools-config.xml: location should be relative to config file

by David Robison (JIRA)

wsdl-java in wstools-config.xml: location should be relative to config file --------------------------------------------------------------------------- Key: JBWS-1502 URL: http://jira.jboss.com/jira/browse/JBWS-1502 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Reporter: David Robison Priority: Minor The wsdl location specified in the wstools-config.xml file should be relative to that file. This helps when building with ant. If I build with ant from the subproject, it builds well. If I build from the parent directory, it cannot find the location. I use "dir/file.wsdl" but that relative path does not work from the parent directory -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1887) Basic Eclipse configuration for user WS-enabled projects

by Alessio Soldano (JIRA)

Basic Eclipse configuration for user WS-enabled projects -------------------------------------------------------- Key: JBWS-1887 URL: http://jira.jboss.com/jira/browse/JBWS-1887 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

17 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-1880) WS-Addressing with endpoints using soap 1.2

by Alessio Soldano (JIRA)

WS-Addressing with endpoints using soap 1.2 ------------------------------------------- Key: JBWS-1880 URL: http://jira.jboss.com/jira/browse/JBWS-1880 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.1 Reporter: Alessio Soldano Assigned To: Alessio Soldano Our current WS-Addressing implementation actually works with endpoints using soap 1.1. We should provide standard endpoint and client configurations using soap 1.2 protocol binding. This should also allow us to run the full W3C Web Services Addressing 1.0 Test Suite. -- 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, 11 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2007