December 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1897) Enable/disable logging on every endpoint

by Alessio Soldano (JIRA)

Enable/disable logging on every endpoint ---------------------------------------- Key: JBWS-1897 URL: http://jira.jboss.com/jira/browse/JBWS-1897 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano We should provide something (let's say in the jmx-console) to enable/disable logging on every endpoint. See forum ref for details. -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1942) jUDDI tables are dropped at ESB shutdown

by Trevor Kirby (JIRA)

jUDDI tables are dropped at ESB shutdown ---------------------------------------- Key: JBWS-1942 URL: http://jira.jboss.com/jira/browse/JBWS-1942 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Trevor Kirby Priority: Blocker jaxr project needs updating to avoid juddi.sar and jbossesb.sar deploying a juddi config see http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4104506#4104506 -- 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, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-1505) Methods defined in an interface superclass don't appear in WSDL.

by Iaacov Rosenberg (JIRA)

Methods defined in an interface superclass don't appear in WSDL. ---------------------------------------------------------------- Key: JBWS-1505 URL: http://jira.jboss.com/jira/browse/JBWS-1505 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Environment: JBoss 4.0.5 GA, JRE 1.5.0_10, WinXP Reporter: Iaacov Rosenberg Given the following scenario: public interface Intf1 { public int getMember1(); public void setMember1(int member1); } public interface Intf2 extends Intf1 { public int getMember2(); public void setMember2(int member2); } Whenever JBossWS uses reflection, either when generating the WSDL file or when returning values that implement Intf2, only members defined in Intf2 (i.e. Member2) are processed, while ignoring inherited members. This only happens with interfaces. Inherited classes are processed correctly. -- 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, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBWS-1939) URL port information of soap:address is different from import schemaLocation URL

by Suresh Srinivas (JIRA)

URL port information of soap:address is different from import schemaLocation URL -------------------------------------------------------------------------------- Key: JBWS-1939 URL: http://jira.jboss.com/jira/browse/JBWS-1939 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-2.0.0 Environment: SunOS serrano 5.8 Generic_108528-18 sun4u sparc SUNW,Ultra-60 Reporter: Suresh Srinivas Setup info 1: The setup has in deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml the following lines commented: <property name="webServiceHost">${jboss.bind.address}</property> <property name="webServicePort">8080</property> This should result in the protocol, port and the host being picked up from requesters URL. Setup info 2: I have JBoss server setup behind apache server. Apache web server forwards request to the JBoss Server using mod_jk. The host ip for the apache server is 38.187.114.136. The host ip for the JBoss server is 38.187.114.238. The JBoss web services are bound to port 8180. Observer behavior: When I access the WSDL using http:/38.187.114.136/application/SessionService?wsdl the WSDL I received has the following information: <definitions name="InitMethod" targetNamespace="http://com.foo.service/callcontrol"> <types> <xsd:schema> <xsd:import namespace="http://com.foo.service/callcontrol/types" schemaLocation="http://38.187.114.136/service/SessionService?wsdl&resource=Session.xsd"/> </xsd:schema> ..... ..... ..... <port binding="ns2:SessionServiceBinding" name="SessionServicePort"> <soap:address location="http://38.187.114.136:8180/service/SessionService"/> </port> </service> </definitions> Problem description: - schemaLocation is right where it does not indicate port "http://38.187.114.136/service/SessionService?wsdl&resource=Session.xsd" - soap:address location does not match and it gives the port where the service is running - "http://38.187.114.136:8180/service/SessionService" -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1762) web.xml modified to web.xml.org - Subsequent runs fail

by Heiko Braun (JIRA)

web.xml modified to web.xml.org - Subsequent runs fail ------------------------------------------------------ Key: JBWS-1762 URL: http://jira.jboss.com/jira/browse/JBWS-1762 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun Assigned To: Thomas Diesler Fix For: jbossws-2.1.0 -- 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, 4 months

3
23
0 / 0

[JBoss JIRA] Created: (JBWS-1940) Cannot rename web.xml to web.xml.ejb.org

by Carsten Wolters (JIRA)

Cannot rename web.xml to web.xml.ejb.org ---------------------------------------- Key: JBWS-1940 URL: http://jira.jboss.com/jira/browse/JBWS-1940 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.2 Environment: WindowsXP Reporter: Carsten Wolters Priority: Blocker I cannot deploy a webservice and subsequent, the complete ear is not deployed. The exception I get is: 14:42:51,859 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/E:/Projekte/pvs/jboss/server/wsdeploy/ws.ear/ws-server.jar/ org.jboss.wsf.spi.deployment.WSFDeploymentException: javax.xml.ws.WebServiceException: Cannot rename web.xml: E:\Projekte\pvs\jboss\server\bardtke\tmp\deploy\ws.ear-ws-server.jar49792... at org.jboss.wsf.spi.deployment.WSFDeploymentException.rethrow(WSFDeploymentException.java:54) at org.jboss.wsf.container.jboss40.WebAppDeploymentAspect.create(WebAppDeploymentAspect.java:82) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115) at org.jboss.wsf.container.jboss40.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97) at org.jboss.wsf.container.jboss40.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 $Proxy36.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) 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.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 $Proxy6.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) Caused by: javax.xml.ws.WebServiceException: Cannot rename web.xml: E:\Projekte\pvs\jboss\server\bardtke\tmp\deploy\maxtrading.ear-maxtrading... at org.jboss.wsf.container.jboss40.WebXMLRewriterImpl.rewriteWebXml(WebXMLRewriterImpl.java:91) at org.jboss.wsf.container.jboss40.WebAppDeploymentAspect.create(WebAppDeploymentAspect.java:69) ... 30 more ----------------------- I found a description of the same problem with a solution here: http://lists.jboss.org/pipermail/jbossws-dev/2007-November/001075.html The problem seems to be connected to a deployment on windows filesystems. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1858) Generate WSDL after all relevant metadata is available

by Thomas Diesler (JIRA)

Generate WSDL after all relevant metadata is available ------------------------------------------------------ Key: JBWS-1858 URL: http://jira.jboss.com/jira/browse/JBWS-1858 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-2.0.3 This is related to [JBWS-1797] -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1937) Document/Literal addressing endpoint fails when retreiving Outbound Action

by Magesh Kumar B (JIRA)

Document/Literal addressing endpoint fails when retreiving Outbound Action -------------------------------------------------------------------------- Key: JBWS-1937 URL: http://jira.jboss.com/jira/browse/JBWS-1937 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc, jbossws-jaxws, ws-addressing Affects Versions: jbossws-1.2.1 Reporter: Magesh Kumar B Assigned To: Magesh Kumar B -- 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, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-1324) JMS Endpoint - Message delivery starts before endpoint is ready.

by Darran Lofthouse (JIRA)

JMS Endpoint - Message delivery starts before endpoint is ready. ---------------------------------------------------------------- Key: JBWS-1324 URL: http://jira.jboss.com/jira/browse/JBWS-1324 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxrpc Affects Versions: jbossws-1.0.3 Reporter: Darran Lofthouse Fix For: jbossws-1.0.6 For most endpoints we need the EJB to be initialised before we initialise the web service, this way we know the session bean will be ready to process requests before the first request from a client is received. For message driven beans we need the web service to be initialised before the first message is processed by the MDB, however the same logic is used as is used for session beans so it is possible that the first message will be received while the web service is still being initialised. -- 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, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBWS-1904) There should be a way to explicitly set the namespace of a WebFault in the generated WSDL schema

by Vesselin Kirov (JIRA)

There should be a way to explicitly set the namespace of a WebFault in the generated WSDL schema ------------------------------------------------------------------------------------------------ Key: JBWS-1904 URL: http://jira.jboss.com/jira/browse/JBWS-1904 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-2.0.1.SP2 Reporter: Vesselin Kirov At the moment the code in org.jboss.metadata.builder.jaxws.JAXWSMetaDataBuilder.addFault does not use the namespace information from @WebFault (if present) for the xml type in the WSDL schema that is generated. It is easy to change the code to do this, however I'm not sure if this would break some other use cases. The other approach would be to use the XmlType annotation (not used at all at the moment). -- 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, 4 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 December 2007