January 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1975) Activate WS-RM 1.0 in our initial implementation

by Richard Opalka (JIRA)

Activate WS-RM 1.0 in our initial implementation ------------------------------------------------ Key: JBWS-1975 URL: http://jira.jboss.com/jira/browse/JBWS-1975 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 Nowadays we support WS-RM 1.1 only but WS-RM 1.0 should be supported as well -- 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-1972) ANT installer creates unnecessary $JBOSS_HOME/default/deploy/jbossws.sar

by Juergen Zimmermann (JIRA)

ANT installer creates unnecessary $JBOSS_HOME/default/deploy/jbossws.sar ------------------------------------------------------------------------ Key: JBWS-1972 URL: http://jira.jboss.com/jira/browse/JBWS-1972 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-2.0.3 Environment: JDK 6u4, JBossAS 4.2.2 Reporter: Juergen Zimmermann When running "ant deploy-jboss422" $JBOSS_HOME/server/default/deploy/jbossws.sar is updated correctly. However, there is also a new and unnecessary directory created: $JBOSS_HOME/default/deploy/jbossws.sar Notice: without "server" in the middle -- 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
0
0 / 0

[JBoss JIRA] Created: (JBWS-1971) Missing clone on MemoryBufferRecorder

by Alessio Soldano (JIRA)

Missing clone on MemoryBufferRecorder ------------------------------------- Key: JBWS-1971 URL: http://jira.jboss.com/jira/browse/JBWS-1971 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productivity Affects Versions: jbossws-native-2.0.3 Reporter: Alessio Soldano Assigned To: Alessio Soldano Fix For: jbossws-native-2.0.4 When making the RecordProcessor cloneable we forgot the clone() method on the MemoryBufferRecorder; this causes the collected records to be shared between different endpoints. -- 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
0
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

16 years, 3 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

16 years, 4 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBWS-1615) wsprovide.sh is missing required libraries

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1615?page=all ] Darran Lofthouse updated JBWS-1615: ----------------------------------- Component/s: tools-jaxws (was: tools-jaxrpc) > wsprovide.sh is missing required libraries > ------------------------------------------ > > Key: JBWS-1615 > URL: http://jira.jboss.com/jira/browse/JBWS-1615 > Project: JBoss Web Services > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: tools-jaxws > Affects Versions: jbossws-1.2.1 > Environment: Linux amd64, JDK 6, although irrelevant for this issue. > Reporter: Panagiotis Astithas > Fix For: community contributions > > > wsprovide.sh fails to generate the WSDL file for the example specified here: > http://jbws.dyndns.org/mediawiki/index.php/JAX-WS_User_Guide#Bottom-Up_.2... > the error message is: > Generating WSDL: > Error: Could not generate. (use --show-traces to see full traces) > java.lang.NoClassDefFoundError: javax/ejb/Stateless > at org.jboss.ws.tools.jaxws.impl.WSContractProviderImpl.createUDI(WSContractProviderImpl.java:75) > at org.jboss.ws.tools.jaxws.impl.WSContractProviderImpl.provide(WSContractProviderImpl.java:117) > at org.jboss.ws.tools.jaxws.impl.WSContractProviderImpl.provide(WSContractProviderImpl.java:134) > at org.jboss.ws.tools.jaxws.command.wsprovide.generate(wsprovide.java:167) > at org.jboss.ws.tools.jaxws.command.wsprovide.main(wsprovide.java:76) > This patch fixes it for me: > ---------- > --- wsprovide.sh.bak 2007-04-19 17:14:48.000000000 +0300 > +++ wsprovide.sh 2007-04-19 17:16:11.000000000 +0300 > @@ -55,11 +55,13 @@ > WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jaxb-impl.jar" > WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jbossall-client.jar" > WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jbossws-client.jar" > +WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jboss-ejb3x.jar" > WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jboss-jaxws.jar" > WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jboss-jaxrpc.jar" > WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jboss-saaj.jar" > WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/log4j.jar" > WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/mail.jar" > +WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/wsdl4j.jar" > > # For Cygwin, switch paths to Windows format before running java > if $cygwin; then > ---------- -- 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
0
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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-1963) WSDL To Java - Various Fixes

by Darran Lofthouse (JIRA)

WSDL To Java - Various Fixes ---------------------------- Key: JBWS-1963 URL: http://jira.jboss.com/jira/browse/JBWS-1963 Project: JBoss Web Services Issue Type: Support Patch Security Level: Public (Everyone can see) Components: tools-jaxrpc Affects Versions: jbossws-2.0.1.SP2 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse -- 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
0
0 / 0

[JBoss JIRA] Created: (JBWS-1961) Patch wiki2xml anchor link support

by Alessio Soldano (JIRA)

Patch wiki2xml anchor link support ---------------------------------- Key: JBWS-1961 URL: http://jira.jboss.com/jira/browse/JBWS-1961 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Assigned To: Alessio Soldano When exporting mediawiki pages to docbook xml, links using anchors (i.e. stuff like [[Records_management#Use_cases|use cases]] ) are skipped. We have a lot of those links spread everywhere in the doc, thus we should fix the wiki2xml plug-in so that it processes them too. -- 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
0
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

16 years, 4 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 January 2008