April 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1449) Generate extra XML schema file for SOAP message in document style web service

by qi liu (JIRA)

Generate extra XML schema file for SOAP message in document style web service ----------------------------------------------------------------------------- Key: JBWS-1449 URL: http://jira.jboss.com/jira/browse/JBWS-1449 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: qi liu The schema is currently inlined in the wsdl. An extra schema file is needed. -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Updated: (JBWS-844) Add support for a fully defined schema with a message endpoint

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-844?page=all ] Thomas Diesler updated JBWS-844: -------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-native-2.0.5) > Add support for a fully defined schema with a message endpoint > -------------------------------------------------------------- > > Key: JBWS-844 > URL: http://jira.jboss.com/jira/browse/JBWS-844 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Jason T. Greene > Fix For: jbossws-3.x > > > Currently a SOAPElement can only be mapped to a xsd:any type. We should add support for mapping SOAPElement to a message that has been fully specified. This would allow for the WSDL to represent a fully defined contract, and yet still allow the endpoint to have flexible parsing. > -Jason -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1544) SAML support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1544?page=all ] Thomas Diesler updated JBWS-1544: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-native-2.0.5) > SAML support > ------------ > > Key: JBWS-1544 > URL: http://jira.jboss.com/jira/browse/JBWS-1544 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: William DeCoste > Fix For: jbossws-3.x > > > Intuit request. Notes: > Support of single sign-on using Liberty, SAML and WS-Federation. > Support of SAML profile. -- 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, 1 month

1
0
0 / 0

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

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1615?page=all ] Thomas Diesler updated JBWS-1615: --------------------------------- Issue Type: Bug (was: Patch) Fix Version/s: jbossws-3.0.2 (was: community contributions) > wsprovide.sh is missing required libraries > ------------------------------------------ > > Key: JBWS-1615 > URL: http://jira.jboss.com/jira/browse/JBWS-1615 > Project: JBoss Web Services > Issue Type: Bug > 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 > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2093) update JBossWSSpecStatus doc for JBossWS1.2.x

by William DeCoste (JIRA)

update JBossWSSpecStatus doc for JBossWS1.2.x --------------------------------------------- Key: JBWS-2093 URL: http://jira.jboss.com/jira/browse/JBWS-2093 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: William DeCoste http://jbws.dyndns.org/mediawiki/index.php?title=JBossWSSpecStatus only spec versions for 1.0.x and 2.0.x -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2085) EJB3 components implement new API

by Heiko Braun (JIRA)

EJB3 components implement new API --------------------------------- Key: JBWS-2085 URL: http://jira.jboss.com/jira/browse/JBWS-2085 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assigned To: 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, 1 month

2
1
0 / 0

[JBoss JIRA] Commented: (JBWS-925) Provide initial support for FastInfoset

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-925?page=comments#action_12406091 ] Thomas Diesler commented on JBWS-925: ------------------------------------- You can have a look at the accociated test case + documentation > Provide initial support for FastInfoset > --------------------------------------- > > Key: JBWS-925 > URL: http://jira.jboss.com/jira/browse/JBWS-925 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-native-2.0.4 > > > A standard way of doing binary WS is FastInfoset > http://java.sun.com/developer/technicalArticles/xml/fastinfoset/ > The Fast Infoset standard draft (currently being developed as joint work by ISO/IEC JTC 1 and ITU-T) specifies a binary format for XML infosets that is an efficient alternative to XML. An instance of this binary format is called a fast infoset document. Fast infoset documents are analogous to XML documents. Each has a physical form and an XML infoset. Fast infoset documents are, given the results presented, faster to serialize and parse, and smaller in size, than the equivalent XML documents. Thus, fast infoset documents may be used whenever the size and processing time of XML documents is an issue. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1707) Resolved support patches should not appear as open issues

by Thomas Diesler (JIRA)

Resolved support patches should not appear as open issues --------------------------------------------------------- Key: JBWS-1707 URL: http://jira.jboss.com/jira/browse/JBWS-1707 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler JIRA project home contains a lot of noise from resolved support patches -- 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, 1 month

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2008