October 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1084) Cleanup shared schema references

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1084?page=all ] Heiko Braun updated JBWS-1084: ------------------------------ Fix Version/s: jbossws-1.0.5 (was: jbossws-1.0.4) > Cleanup shared schema references > -------------------------------- > > Key: JBWS-1084 > URL: http://jira.jboss.com/jira/browse/JBWS-1084 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-1.0.5 > > > In particular the addressing and eventing schema usage needs to be cleaned up. The primary reference schould be delivered through the EntityResolver. -- 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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-895) Provide support for policy attachments

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-895?page=all ] Heiko Braun updated JBWS-895: ----------------------------- Fix Version/s: jbossws-1.0.5 (was: jbossws-1.0.4) > Provide support for policy attachments > -------------------------------------- > > Key: JBWS-895 > URL: http://jira.jboss.com/jira/browse/JBWS-895 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-policy > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-1.0.5 > > > Web Services Policy Attachment (WS-PolicyAttachment), > defines two general-purpose mechanisms for associating policies with the subjects to > which they apply; the policies may be defined as part of existing metadata about the > subject or the policies may be defined independently and associated through an external > binding to the subject. > Relevant to JBossWS are the following questions: > - How to reference policies from WSDL definitions. > - How to associate policies with deployed Web service 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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1303) Unmarshall issue with xsi:type specified bean property

by Thomas Diesler (JIRA)

Unmarshall issue with xsi:type specified bean property ------------------------------------------------------ Key: JBWS-1303 URL: http://jira.jboss.com/jira/browse/JBWS-1303 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxrpc Affects Versions: jbossws-1.0.3.SP1 Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.0.4 2006-10-12 09:08:18,539 ERROR [org.jboss.ws.jaxrpc.CallImpl] Call invocation failed with unkown Exception javax.xml.rpc.JAXRPCException: org.jboss.ws.binding.BindingException: org.jboss.ws.jaxb.UnmarshalException: Failed to parse source: Type binding not found for type string specified with xsi:type for element {http://netid.msu.edu:8080/lastmod.pl}TimeChanged at org.jboss.ws.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:303) at org.jboss.ws.binding.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:233) at org.jboss.ws.binding.EndpointInvocation.getReturnValue(EndpointInvocation.java:182) at org.jboss.ws.jaxrpc.CallImpl.syncOutputParams(CallImpl.java:873) at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:704) at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:404) at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:148) -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1306) Fix testsuite on standalone tomcat

by Thomas Diesler (JIRA)

Fix testsuite on standalone tomcat ---------------------------------- Key: JBWS-1306 URL: http://jira.jboss.com/jira/browse/JBWS-1306 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.0.5 -- 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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1289) Fail to find the imported xsd files in the wsdl

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1289?page=comments#action_12345353 ] Thomas Diesler commented on JBWS-1289: -------------------------------------- There are quite a number of tests in our testsuite and the Sun CTS that test this xsd imports. Please provide source and sample deployment that allows me to reproduce what you are seeing. > Fail to find the imported xsd files in the wsdl > ------------------------------------------------ > > Key: JBWS-1289 > URL: http://jira.jboss.com/jira/browse/JBWS-1289 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: binding > Affects Versions: jbossws-1.0.2 > Environment: windows, linux, jdk1.5 > Reporter: George Gan > > Jbossws fails to locat any xsd imports in the wsdl's "types" section. -- 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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1290) WS-Eventing and subscription expiration time

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1290?page=all ] Thomas Diesler updated JBWS-1290: --------------------------------- Fix Version/s: jbossws-1.0.5 Assignee: Heiko Braun > WS-Eventing and subscription expiration time > -------------------------------------------- > > Key: JBWS-1290 > URL: http://jira.jboss.com/jira/browse/JBWS-1290 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-eventing > Affects Versions: jbossws-1.0.2, jbossws-1.0.3, jbossws-1.0.3.SP1 > Reporter: Stefano Maestri > Assigned To: Heiko Braun > Fix For: jbossws-1.0.5 > > Attachments: eventing.patch > > > We just made a patch for jbossws implementing two features: > 1. The max expiration time and the default expiration time are hard coded in source code. Our patch made these values configurable in SubscriptionManager MBEAN > 2. We noticed jbossws throws an InvalideExpirationTime Excetion when we try to subscribe with an expiration time longer than maxLeaseTime. According to specification (5.4) this exception should be used only when the expiration time is in the past or the expiration duration is zero. It should answer with a valid registration forcing expiration time to maxLeaseTime (Specification 3.1). > http://www.javalinux.it/blogs/index.php?title=ws_eventing_and_subscriptio... -- 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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1290) WS-Eventing and subscription expiration time

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1290?page=all ] Thomas Diesler updated JBWS-1290: --------------------------------- Issue Type: Bug (was: Patch) > WS-Eventing and subscription expiration time > -------------------------------------------- > > Key: JBWS-1290 > URL: http://jira.jboss.com/jira/browse/JBWS-1290 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-eventing > Affects Versions: jbossws-1.0.2, jbossws-1.0.3, jbossws-1.0.3.SP1 > Reporter: Stefano Maestri > Fix For: jbossws-1.0.5 > > Attachments: eventing.patch > > > We just made a patch for jbossws implementing two features: > 1. The max expiration time and the default expiration time are hard coded in source code. Our patch made these values configurable in SubscriptionManager MBEAN > 2. We noticed jbossws throws an InvalideExpirationTime Excetion when we try to subscribe with an expiration time longer than maxLeaseTime. According to specification (5.4) this exception should be used only when the expiration time is in the past or the expiration duration is zero. It should answer with a valid registration forcing expiration time to maxLeaseTime (Specification 3.1). > http://www.javalinux.it/blogs/index.php?title=ws_eventing_and_subscriptio... -- 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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1128) Add provison to specify a JassSecurityDomain in WS-SECURITY config

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1128?page=all ] Thomas Diesler updated JBWS-1128: --------------------------------- Fix Version/s: jbossws-1.0.5 (was: jbossws-1.0.4) > Add provison to specify a JassSecurityDomain in WS-SECURITY config > ------------------------------------------------------------------ > > Key: JBWS-1128 > URL: http://jira.jboss.com/jira/browse/JBWS-1128 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-1.0.2 > Reporter: Magesh Kumar B > Assigned To: Magesh Kumar B > Priority: Optional > Fix For: jbossws-1.0.5 > > > Ideally the existing SecurityStore and configuration will remain for doing per-deployment keystore configuration. > Optionally they should be able to refer to a JaasSecurityDomain, which would be globaly configured. This needs to be optional because we deploy against the mc, which is not necessarily jboss (could be tomcat). > -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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1125) Support doc/lit with empty soap body elements

by Jason T. Greene (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1125?page=all ] Jason T. Greene updated JBWS-1125: ---------------------------------- Fix Version/s: jbossws-1.0.4 (was: jbossws-1.0.3) > Support doc/lit with empty soap body elements > --------------------------------------------- > > Key: JBWS-1125 > URL: http://jira.jboss.com/jira/browse/JBWS-1125 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.2 > Reporter: Darran Lofthouse > Assigned To: Thomas Diesler > Fix For: jbossws-1.0.4 > > > There is some conflicting information in the different specifications regarding how to handle a method in an endpoint interface that does not take any parameters, at the moment we only support this type of method by using wrapped style. > From the BasicProfile: - > [Section 5.3.1] > .... > Use of wsdl:message elements with zero parts is permitted in Document styles to permit operations that can send or receive messages with empty soap:Bodys. > From JSR-181 > JSR-181 which states: > - If the operation is marked @Oneway, it MUST have a void return value, a > single non-header parameter marked as IN, and zero or more header > parameters. > - If the operation is not marked @Oneway, it may have one of the following > forms: > o A non-header parameter marked as IN, a non-header parameter marked > as OUT, a void return value, and zero or more header parameters. > o A single non-header parameters marked as IN_OUT, a void return > value, and zero or more header parameters. > o A single non-header parameter marked as IN, non-void return value > and zero or more header parameters. > This clearly requires there to be at least one parameter for a bare doc/lit message. > From JAX-WS (Although not the current spec we implement does show how this has been clarified) > In order to qualify for use of bare mapping mode a Java method must > fulfill all of the following criteria: > 1. It must have at most one in or in/out non-header parameter. > 2. If it has a return type other than void it must have no in/out or > out non-header parameters. > 3. If it has a return type of void it must have at most one in/out or > out non-header parameter. -- 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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Reopened: (JBWS-1125) Support doc/lit with empty soap body elements

by Jason T. Greene (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1125?page=all ] Jason T. Greene reopened JBWS-1125: ----------------------------------- This test case is invalid, only the bare parameter style is a valid use of an empty message. > Support doc/lit with empty soap body elements > --------------------------------------------- > > Key: JBWS-1125 > URL: http://jira.jboss.com/jira/browse/JBWS-1125 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.2 > Reporter: Darran Lofthouse > Assigned To: Thomas Diesler > Fix For: jbossws-1.0.4 > > > There is some conflicting information in the different specifications regarding how to handle a method in an endpoint interface that does not take any parameters, at the moment we only support this type of method by using wrapped style. > From the BasicProfile: - > [Section 5.3.1] > .... > Use of wsdl:message elements with zero parts is permitted in Document styles to permit operations that can send or receive messages with empty soap:Bodys. > From JSR-181 > JSR-181 which states: > - If the operation is marked @Oneway, it MUST have a void return value, a > single non-header parameter marked as IN, and zero or more header > parameters. > - If the operation is not marked @Oneway, it may have one of the following > forms: > o A non-header parameter marked as IN, a non-header parameter marked > as OUT, a void return value, and zero or more header parameters. > o A single non-header parameters marked as IN_OUT, a void return > value, and zero or more header parameters. > o A single non-header parameter marked as IN, non-void return value > and zero or more header parameters. > This clearly requires there to be at least one parameter for a bare doc/lit message. > From JAX-WS (Although not the current spec we implement does show how this has been clarified) > In order to qualify for use of bare mapping mode a Java method must > fulfill all of the following criteria: > 1. It must have at most one in or in/out non-header parameter. > 2. If it has a return type other than void it must have no in/out or > out non-header parameters. > 3. If it has a return type of void it must have at most one in/out or > out non-header parameter. -- 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

18 years, 1 month

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 October 2006