January 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-299) Tools: "NoDataBinding" option for doc/literal Web Services

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-299?page=all ] Darran Lofthouse updated JBWS-299: ---------------------------------- Fix Version/s: jbossws-2.0.1 (was: jbossws-2.0.0) > Tools: "NoDataBinding" option for doc/literal Web Services > ---------------------------------------------------------- > > Key: JBWS-299 > URL: http://jira.jboss.com/jira/browse/JBWS-299 > Project: JBoss Web Services > Issue Type: Feature Request > Components: wstools > Reporter: Anil Saldhana > Assigned To: Darran Lofthouse > Priority: Optional > Fix For: jbossws-2.0.1 > > > wscompile has an option "-f:nodatabinding" that turns off data binding in the input parameters and return types for doc/lit web services. More information is available in the feature matrix. That info is copy/pasted here: > > wscompile uses this option to turn off data binding for literal encoding. This is a very important option when dealing with doc/literal wsdl files. Let us take an example of a web service that returns employee data. > > The SEI generated by wscompile will look as follows: > public interface EmployeeQuery extends Remote { > public double getSalary() throws RemoteException; > public String getManagerName(int level) throws RemoteException; > } > Now if the -f:nodatabinding option is used, the generated SEI will not have any typed arguments or return types, but they will all be mapped to javax.xml.soap.SOAPElement (xsd:any equivalent). > public interface EmployeeQuery extends Remote { > public javax.xml.soap.SOAPElement getSalary() throws RemoteException; > public javax.xml.soap.SOAPElement getManagerName(javax.xml.soap.SOAPElement level) throws RemoteException; > } > Supported by jbossws with the "nodatabinding" attribute in the <wsdltojava> element. > A point to be noted is the user will have to use SAAJ to construc messages to invoke the webservice and has to decode the return message (if any) using SAAJ. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1133) Unpacked JSR-181 POJO deployment fails for subsquent deployment.

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1133?page=all ] Darran Lofthouse updated JBWS-1133: ----------------------------------- Fix Version/s: jbossws-2.0.1 (was: jbossws-2.0.0) > Unpacked JSR-181 POJO deployment fails for subsquent deployment. > ---------------------------------------------------------------- > > Key: JBWS-1133 > URL: http://jira.jboss.com/jira/browse/JBWS-1133 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxws > Affects Versions: jbossws-1.0.1 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-2.0.1 > > > Unpacked JSR-181 POJO deployments are not deployed correctly for subsequent server starts. > This is because when this is first deployed the web.xml which is part of the deployment is modified so that the JBossServiceEndpointServlet servlet is used. > On subsequent deployments the web.xml is parsed but because all of the servlet classes have been replaced with the JBossServiceEndpointServlet it is JBossServiceEndpointServlet that is checked for annotations instead of the endpoint class. -- 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, 10 months

1
0
0 / 0

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

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-844?page=all ] Darran Lofthouse updated JBWS-844: ---------------------------------- Fix Version/s: jbossws-2.0.1 (was: jbossws-2.0.0) > 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: jaxrpc > Reporter: Jason T. Greene > Assigned To: Darran Lofthouse > Fix For: jbossws-2.0.1 > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1136) Allow username to be specified in the requires list

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1136?page=all ] Darran Lofthouse updated JBWS-1136: ----------------------------------- Fix Version/s: jbossws-2.0.1 (was: jbossws-2.0.0) > Allow username to be specified in the requires list > --------------------------------------------------- > > Key: JBWS-1136 > URL: http://jira.jboss.com/jira/browse/JBWS-1136 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-1.0.1 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-2.0.1 > > > Allow username to be specified in the requires list for endpoints so that messages without the username can be rejected. > At the moment for EJB endpoints they can be configured using standard J2EE security so if there is no authenticated user the request is rejected, however this can't be done for the POJO 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1452) WSDL To Java - Unwrapping wrapped arrays.

by Darran Lofthouse (JIRA)

WSDL To Java - Unwrapping wrapped arrays. ----------------------------------------- Key: JBWS-1452 URL: http://jira.jboss.com/jira/browse/JBWS-1452 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: wstools Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.2.1 I suspect there are some problems unwrapping wrapped arrays with wstools WSDL to Java, this Jira issue is so I can have a Jira number to use to create some test cases to investigate this. -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBWS-1093) Deploying a war that also contains normal servlets the web.xml is modified as if they are all endpoints

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1093?page=all ] Darran Lofthouse updated JBWS-1093: ----------------------------------- Fix Version/s: jbossws-1.0.4 > Deploying a war that also contains normal servlets the web.xml is modified as if they are all endpoints > ------------------------------------------------------------------------------------------------------- > > Key: JBWS-1093 > URL: http://jira.jboss.com/jira/browse/JBWS-1093 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.1 > Environment: Deploying to JBoss 4.0.4.GA > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-2.0.0, jbossws-1.0.4 > > > When deploying a war that contains web services the servlet definitions for the endpoints need to be modified so that they reference a JBossWS servlet instead of the endpoint implementation, this JBossWS implementation then delegates to the endpoint. > For JBossWS 1.0.0 servlet entries were only modified if they were identified as endpoints based on the deployment of the webservices.xml > For JBossWS 1.0.1 as part of removing the dependencies on JBossAS this was refactored and now the non web services servlets are identified if their name ends 'Servlet'. The original logic from JBossWS 1.0.0 needs to be reimplemented but we also need to take into acount the different deployment scenarios. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1133) Unpacked JSR-181 POJO deployment fails for subsquent deployment.

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1133?page=all ] Darran Lofthouse updated JBWS-1133: ----------------------------------- Fix Version/s: jbossws-2.0.0 (was: jbossws-1.2.1) > Unpacked JSR-181 POJO deployment fails for subsquent deployment. > ---------------------------------------------------------------- > > Key: JBWS-1133 > URL: http://jira.jboss.com/jira/browse/JBWS-1133 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxws > Affects Versions: jbossws-1.0.1 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-2.0.0 > > > Unpacked JSR-181 POJO deployments are not deployed correctly for subsequent server starts. > This is because when this is first deployed the web.xml which is part of the deployment is modified so that the JBossServiceEndpointServlet servlet is used. > On subsequent deployments the web.xml is parsed but because all of the servlet classes have been replaced with the JBossServiceEndpointServlet it is JBossServiceEndpointServlet that is checked for annotations instead of the endpoint class. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1136) Allow username to be specified in the requires list

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1136?page=all ] Darran Lofthouse updated JBWS-1136: ----------------------------------- Fix Version/s: (was: jbossws-1.2.1) jbossws-2.0.0 > Allow username to be specified in the requires list > --------------------------------------------------- > > Key: JBWS-1136 > URL: http://jira.jboss.com/jira/browse/JBWS-1136 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-1.0.1 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-2.0.0 > > > Allow username to be specified in the requires list for endpoints so that messages without the username can be rejected. > At the moment for EJB endpoints they can be configured using standard J2EE security so if there is no authenticated user the request is rejected, however this can't be done for the POJO 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1078) WSDL11ToJavaTestCase - Should verify the SEIs that are generated.

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1078?page=all ] Darran Lofthouse updated JBWS-1078: ----------------------------------- Fix Version/s: jbossws-2.0.0 (was: jbossws-1.2.1) > WSDL11ToJavaTestCase - Should verify the SEIs that are generated. > ----------------------------------------------------------------- > > Key: JBWS-1078 > URL: http://jira.jboss.com/jira/browse/JBWS-1078 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.1 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-2.0.0 > > > WSDL11ToJavaTestCase - Should verify the SEIs that are generated. > Also this test case should be expanded to incude all of the available WSDLs under 'src\test\resources\wsdlfixture'. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1093) Deploying a war that also contains normal servlets the web.xml is modified as if they are all endpoints

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1093?page=all ] Darran Lofthouse updated JBWS-1093: ----------------------------------- Fix Version/s: jbossws-2.0.0 (was: jbossws-1.0.4) (was: jbossws-1.2.1) > Deploying a war that also contains normal servlets the web.xml is modified as if they are all endpoints > ------------------------------------------------------------------------------------------------------- > > Key: JBWS-1093 > URL: http://jira.jboss.com/jira/browse/JBWS-1093 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.1 > Environment: Deploying to JBoss 4.0.4.GA > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-2.0.0 > > > When deploying a war that contains web services the servlet definitions for the endpoints need to be modified so that they reference a JBossWS servlet instead of the endpoint implementation, this JBossWS implementation then delegates to the endpoint. > For JBossWS 1.0.0 servlet entries were only modified if they were identified as endpoints based on the deployment of the webservices.xml > For JBossWS 1.0.1 as part of removing the dependencies on JBossAS this was refactored and now the non web services servlets are identified if their name ends 'Servlet'. The original logic from JBossWS 1.0.0 needs to be reimplemented but we also need to take into acount the different deployment scenarios. -- 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, 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 2007