January 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-981) Virtual host configuration for EJB endpoints

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-981?page=all ] Thomas Diesler updated JBWS-981: -------------------------------- Fix Version/s: jbossws-native-2.0.4 (was: jbossws-3.0.1) > Virtual host configuration for EJB endpoints > -------------------------------------------- > > Key: JBWS-981 > URL: http://jira.jboss.com/jira/browse/JBWS-981 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Darran Lofthouse > Fix For: jbossws-native-2.0.4 > > > I use JBoss 4.0.4 GA and want to deploy a EJB3 (JSR-181) webserivce. Nearly everything is fine. The problem is that the generated servlet of the webservice is deployed on the default virtual host, but I want to change this to another. How is this possible? I tried to add an jboss-web.xml in META-INF directory of the jar-file containing the webservice bean and interface, but with no success. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1165) Support JSON data binding

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1165?page=all ] Thomas Diesler updated JBWS-1165: --------------------------------- Fix Version/s: jbossws-native-2.0.4 (was: jbossws-3.0.1) > Support JSON data binding > ------------------------- > > Key: JBWS-1165 > URL: http://jira.jboss.com/jira/browse/JBWS-1165 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-native-2.0.4 > > > Does anyone know how I could make a web service that had the option to return json instead of xml? Yahoo is doing just that. It would streamline a few client side things I have. > http://en.wikipedia.org/wiki/JSON -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1211) Add support for @WebFault

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1211?page=all ] Thomas Diesler updated JBWS-1211: --------------------------------- Fix Version/s: jbossws-native-2.0.4 (was: jbossws-3.0.1) > Add support for @WebFault > ------------------------- > > Key: JBWS-1211 > URL: http://jira.jboss.com/jira/browse/JBWS-1211 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-native-2.0.4 > > -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-939) Allow setting of SSL and authentication properties for retrieving remote WSDL files

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-939?page=all ] Thomas Diesler updated JBWS-939: -------------------------------- Fix Version/s: jbossws-native-2.0.4 (was: jbossws-3.0.1) > Allow setting of SSL and authentication properties for retrieving remote WSDL files > ----------------------------------------------------------------------------------- > > Key: JBWS-939 > URL: http://jira.jboss.com/jira/browse/JBWS-939 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Jason T. Greene > Fix For: jbossws-native-2.0.4 > > > Currently only system properties can be used. A possible solution is to enhance our proprietary service factory API. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1172) Support schema validation for incoming messages

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1172?page=all ] Thomas Diesler updated JBWS-1172: --------------------------------- Fix Version/s: jbossws-native-2.0.4 (was: jbossws-3.0.1) > Support schema validation for incoming messages > ----------------------------------------------- > > Key: JBWS-1172 > URL: http://jira.jboss.com/jira/browse/JBWS-1172 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-native-2.0.4 > > > I am trying to use JBOSSWS 1.0.2. and JBOSSAS-4.0.4GA > I am starting with a WSDL file that contains a schema. I used WSTOOLS to generate the appropriate artifacts > I would like to use DOCUMENT/LITERAL wrapped style and I would like to turn on schema validation of my XML instances against a schema defined in the WSDL (on receipt of the message the server does the validation ?). > Looking through the sources, I see that JAXBDeserializer (jbossws-core.jar) calls JAXBUnmarshallerImpl which calls UnmarshallerImpl (jboss-xml-binding.jar) which does the parsing of the XML. > I do not see any call to UnmarshallerImpl.setSchemaValidation in this call graph. Should this be called to turn on to do Schema Validation ? If so how and where ? > Is Schema Validation for Document/Literal something that JBOSSWS 1.0.2 supports ? > How does one turn on XML Schema validation in JBOSSWS ? -- 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

1
0
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-native-2.0.4 (was: jbossws-3.0.1) > 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 > Assigned To: Darran Lofthouse > Fix For: jbossws-native-2.0.4 > > > 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

17 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1161) Interop endpoints for MTOM

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1161?page=all ] Thomas Diesler updated JBWS-1161: --------------------------------- Fix Version/s: jbossws-native-2.0.4 (was: jbossws-3.0.1) > Interop endpoints for MTOM > -------------------------- > > Key: JBWS-1161 > URL: http://jira.jboss.com/jira/browse/JBWS-1161 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-native-2.0.4 > > > http://131.107.72.15/ilab/Messaging/WCFInteropPlugFest_Messaging.doc -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1251) 10.22SSL session support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1251?page=all ] Thomas Diesler updated JBWS-1251: --------------------------------- Fix Version/s: jbossws-native-2.0.4 (was: jbossws-3.0.1) > 10.22SSL session support > ------------------------- > > Key: JBWS-1251 > URL: http://jira.jboss.com/jira/browse/JBWS-1251 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-native-2.0.4 > > -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-925) Add support for FastInfoset

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-925?page=all ] Thomas Diesler updated JBWS-925: -------------------------------- Fix Version/s: jbossws-native-2.0.4 (was: jbossws-3.0.1) > Add 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 > 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

17 years

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-native-2.0.4 (was: jbossws-3.0.1) > 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-native-2.0.4 > > > 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

17 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2008