January 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3203) Webservice deployment and namespace containing # character

by Aurélien Lansmanne (JIRA)

Webservice deployment and namespace containing # character ---------------------------------------------------------- Key: JBWS-3203 URL: https://issues.jboss.org/browse/JBWS-3203 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: Windows XP Reporter: Aurélien Lansmanne While developping a webservise with JBossWS, I've encountered the following problem. One of the namespace in the WSDL contains a '#'. Let's call it http://mynamespace.com/# . As I'm not the author of the WSDL, I can't really change these namespaces. When JBoss try to deploy my Webservice, an error occurs because Jboss is looking for a file called .../server/default/tmp/jbossws/mynamespace.com#.xsd ... but this is not even a valid file system name (even if the file exists). I think this is related to http://lists.jboss.org/pipermail/jbossws-users/2008-April/005280.html If i look inside org/jboss/ws/metadata/wsdl/xsd/SchemaUtils.java/ on http://grepcode.com/file/repository.jboss.com/maven2/org.jboss.ws.native/..., there is actually a fix that replace all '?', ':' and '/', but nothing about '#'. I'm using JBoss 4.2.2 and this is quite annoying. Is there any fix or workaround (I just can't modify the wsdl, so at the end, these elements should be belonging to the http://mynamespace.com/# namespave, and not http://mynamespace.com/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3181) Add support for symlinked bin/*.sh files

by Emmanuel Bernard (JIRA)

Add support for symlinked bin/*.sh files ---------------------------------------- Key: JBWS-3181 URL: https://jira.jboss.org/browse/JBWS-3181 Project: JBoss Web Services Issue Type: Patch Security Level: Public (Everyone can see) Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Related to JBAS-8670 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-3197) Update to Apache CXF 2.3.2

by Jim Ma (JIRA)

Update to Apache CXF 2.3.2 --------------------------- Key: JBWS-3197 URL: https://issues.jboss.org/browse/JBWS-3197 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3196) FastInfoSet leaving sockets in CLOSE_WAIT state

by Mustafa Musaji (JIRA)

FastInfoSet leaving sockets in CLOSE_WAIT state ----------------------------------------------- Key: JBWS-3196 URL: https://issues.jboss.org/browse/JBWS-3196 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Environment: JBoss EAP 5.1.0, Sun JDK 1.6.0_22, RHEL6 Reporter: Mustafa Musaji Assignee: Alessio Soldano Attachments: fixProject.zip When sending multiple requests from a ws client and using fastinfoset we see the number of sockets in a CLOSE_WAIT state increase and not get shut down properly. Removing fastinfoset from the code fixed this issue and increasing the verbosity of the logging of the soap message also removes this issue. I am attaching the following files for both scenarios (one with and one without Projects.zip - These are the JBDS projects that created the WAR and JAR above so that you can see the source code - This uses FastInfoSet and will reproduce the issue. fixedProject.zip - These are the JBDS projects that created the WAR and JAR above so that you can see the source code - This DOES NOT uses FastInfoSet and will not reproduce the issue -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
3
0 / 0

[JBoss JIRA] Updated: (JBWS-3196) FastInfoSet leaving sockets in CLOSE_WAIT state

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBWS-3196?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBWS-3196: --------------------------------- Attachment: fixProject.zip The source and deployables that do not contain fastinfoset and do not cause sockets to remain in CLOSE_WAIT state > FastInfoSet leaving sockets in CLOSE_WAIT state > ----------------------------------------------- > > Key: JBWS-3196 > URL: https://issues.jboss.org/browse/JBWS-3196 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-native-3.1.2 > Environment: JBoss EAP 5.1.0, Sun JDK 1.6.0_22, RHEL6 > Reporter: Mustafa Musaji > Assignee: Alessio Soldano > Labels: jbossws_native > Attachments: fixProject.zip > > > When sending multiple requests from a ws client and using fastinfoset we see the number of sockets in a CLOSE_WAIT state increase and not get shut down properly. Removing fastinfoset from the code fixed this issue and increasing the verbosity of the logging of the soap message also removes this issue. > I am attaching the following files for both scenarios (one with and one without > Projects.zip > - These are the JBDS projects that created the WAR and JAR above so that you can see the source code - This uses FastInfoSet and will reproduce the issue. > fixedProject.zip > - These are the JBDS projects that created the WAR and JAR above so that you can see the source code - This DOES NOT uses FastInfoSet and will not reproduce the issue -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3195) @Resource and @EJB injection in jaxws endpoints and handlers

by Malcolm Wong Ho (JIRA)

@Resource and @EJB injection in jaxws endpoints and handlers ------------------------------------------------------------ Key: JBWS-3195 URL: https://issues.jboss.org/browse/JBWS-3195 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.1 Environment: Operating system :Ubuntu 9.10 Java version :1.6.0_22 Jboss version :jboss-6.0.0.Final Reporter: Malcolm Wong Ho Priority: Minor The @Resource and @EJB injection in jaxws endpoints and handlers was working on jboss-5.1.0.GA with jbossws-cxf-3.4.0.GA, then upgraded to jboss-6.0.0.Final with jbossws-cxf-3.4.1.GA and injection into jaxws endpoint stopped working -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 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 2011