November 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1274) jboss-4.0.4.GA (jdk1.4)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1274?page=all ] Thomas Diesler updated JBWS-1274: --------------------------------- Assignee: Prabhat Jha (was: Alejandro Guizar) > jboss-4.0.4.GA (jdk1.4) > ----------------------- > > Key: JBWS-1274 > URL: http://jira.jboss.com/jira/browse/JBWS-1274 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Prabhat Jha > Fix For: jbossws-1.0.5 > > > Run these tests with jdk1.4 > tdiesler@tdvaio /cygdrive/d/svn/jbossws/branches/jbossws-1.0/src/test > $ ant tests > [PASS] > tdiesler@tdvaio /cygdrive/d/svn/jbossws/branches/jbossws-1.0/output/jbossws-samples-1.1.x.GA > $ ant tests > [PASS] > tdiesler@tdvaio /cygdrive/d/cvs/jboss-archive/jboss-4.0.4/testsuite > $ ant tests-webservice > [PASS] -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1141) EJB Proxy doesn't call Client.connect()

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1141?page=all ] Thomas Diesler updated JBWS-1141: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > EJB Proxy doesn't call Client.connect() > ---------------------------------------- > > Key: JBWS-1141 > URL: http://jira.jboss.com/jira/browse/JBWS-1141 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-1.0.6 > > > junit.extensions.TestSetup.run(TestSetup.java:23)Caused by: java.lang.Exception: Can not make remoting client invocation due to not being connected to server. at org.jboss.remoting.Client.invoke(Client.java:616) at org.jboss.remoting.Client.invoke(Client.java:604) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:78) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) ... 21 more -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-493) Add support for Compact Policy Expression

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-493?page=all ] Thomas Diesler updated JBWS-493: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Add support for Compact Policy Expression > ----------------------------------------- > > Key: JBWS-493 > URL: http://jira.jboss.com/jira/browse/JBWS-493 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-policy > Reporter: Thomas Diesler > Assigned To: Heiko Braun > Fix For: jbossws-1.0.6 > > > To express a policy in a more compact form while still using the XML Infoset, this > specification defines three constructs: an attribute to decorate an assertion, semantics > for recursively nested policy operators, and a policy reference/inclusion mechanism. > Each is described in the subsections below. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1212) Add support for @SecurityDomain on JSE

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1212?page=all ] Thomas Diesler updated JBWS-1212: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Add support for @SecurityDomain on JSE > -------------------------------------- > > Key: JBWS-1212 > URL: http://jira.jboss.com/jira/browse/JBWS-1212 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jaxrpc, jaxws > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-1.0.6 > > > @SecurityDomain is currently only supported for EJB3 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-759) Refactor DOMUtils

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-759?page=all ] Thomas Diesler updated JBWS-759: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Refactor DOMUtils > ----------------- > > Key: JBWS-759 > URL: http://jira.jboss.com/jira/browse/JBWS-759 > 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.6 > > > DOMUtils is not a stateless helper. It maintains state per thread (i.d. DOM Document, DocumentBuilder) > Threads can potentially be longliving objects (i.e from the tomcat worker pool) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-723) Protect access to wsdl

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-723?page=all ] Thomas Diesler updated JBWS-723: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Protect access to wsdl > ---------------------- > > Key: JBWS-723 > URL: http://jira.jboss.com/jira/browse/JBWS-723 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Fix For: jbossws-1.0.6 > > > Hello, > the reason for protecting the wsdl file, is that the wsdl file can give > valuable information for starting a Web Service related attack, > according to the bibliography (see for example: Hacking Exposed, Web Applications, Scambray J., Shema M., McGraw Hill; Hacking Exposed, > J2EE & Java, Taylor B., Buege R., Layman A., McGraw Hill). > Spyros Halkidis -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1134) Integrate and test remoting 2.0.0.CR1

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1134?page=all ] Thomas Diesler updated JBWS-1134: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Integrate and test remoting 2.0.0.CR1 > ------------------------------------- > > Key: JBWS-1134 > URL: http://jira.jboss.com/jira/browse/JBWS-1134 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Jason T. Greene > Assigned To: Heiko Braun > Fix For: jbossws-1.0.6 > > > From Tom: > > I was running the ejb3 testsuite and noticed one particular place that > > will need a code change due to remoting 2.0.0.CR1. It is in > > org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:160) > > where have to call Client.connect() immediately after creating it. This > > is backwards compatible with previous remoting releases, but in > > 2.0.0.CR1 connect() is required to be called before doing anything with > > Client (where as in previous releases, didn't enforce this requirement). > Also, NoThrowOnError needs to be set, it is also backwords compatible: > http://labs.jboss.com/portal/jbossremoting/docs/guide/ch05.html#d0e1367 > He needs us to test this by this weekend. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1036) Eclipse IDE uses an XB version that not compatible with 1.0.1

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1036?page=all ] Thomas Diesler updated JBWS-1036: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Eclipse IDE uses an XB version that not compatible with 1.0.1 > ------------------------------------------------------------- > > Key: JBWS-1036 > URL: http://jira.jboss.com/jira/browse/JBWS-1036 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.0 > Environment: JBoss Eclipse IDE 1.5.1 GA > Reporter: Heiko Braun > Assigned To: Heiko Braun > Priority: Minor > Fix For: jbossws-1.0.6 > > -- 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, 2 months

1
0
0 / 0

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

by Thomas Diesler (JIRA)

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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-798) Complete EventingTestCase

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-798?page=all ] Thomas Diesler updated JBWS-798: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Complete EventingTestCase > ------------------------- > > Key: JBWS-798 > URL: http://jira.jboss.com/jira/browse/JBWS-798 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-eventing > Reporter: Thomas Diesler > Assigned To: Heiko Braun > Fix For: jbossws-1.0.6 > > > // > // "http://schemas.xmlsoap.org/ws/2004/08/eventing/DeliveryFailure" > // This value MUST be used if the event source terminated the subscription > // because of problems delivering notifications. > // > public void testSubscriptionEndMessage() > { > System.out.println("FIXME: testSubscriptionEnd"); > } > // > // "http://schemas.xmlsoap.org/ws/2004/08/eventing/SourceShuttingDown" > // This value MUST be used if the event source terminated the subscription > // because the source is being shut down in a controlled manner; > // that is, if the event source is being shut down but has the opportunity > // to send a SubscriptionEnd message before it exits. > // > public void testShutdownMessage() > { > System.out.println("FIXME: testShutdownMessage"); > } > // > // "http://schemas.xmlsoap.org/ws/2004/08/eventing/SourceCanceling" > // This value MUST be used if the event source terminated the subscription > // for some other reason before it expired. > // > public void testCancelMessage() > { > System.out.println("FIXME: testCancelMessage"); > } -- 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, 2 months

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