[JBoss JIRA] Commented: (JBWS-1194) Release jbossws-1.0.4.GA binary
by Prabhat Jha (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1194?page=comments#action_12346320 ]
Prabhat Jha commented on JBWS-1194:
-----------------------------------
compile14 target while building ws internal tests fais:
Created dir: /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/output/tests/classes
[javac] Compiling 745 source files to /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/output/tests/classes
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/jbws1093/ServletTest.java:46: illegal character: \64
[javac] @Override
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/jbws1093/ServletTest.java:52: <identifier> expected
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/ApplicationClient.java:46: '(' or '[' expected
[javac] ArrayList<TestEndpoint> ports = new ArrayList<TestEndpoint>();
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/ApplicationClient.java:58: ';' expected
[javac] for (TestEndpoint port : ports)
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/ApplicationClient.java:66: illegal start of expression
[javac] }
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/EJBClient.java:47: '(' or '[' expected
[javac] ArrayList<TestEndpoint> ports = new ArrayList<TestEndpoint>();
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/EJBClient.java:60: ';' expected
[javac] for (TestEndpoint port : ports)
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/EJBClient.java:68: illegal start of expression
[javac] }
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/ServletClient.java:42: illegal character: \64
[javac] @Override
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/ServletClient.java:52: <identifier> expected
[javac] ports.add((TestEndpoint)((Service)iniCtx.lookup("java:comp/env/service1")).getPort(TestEndpoint.class));
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/ServletClient.java:52: <identifier> expected
[javac] ports.add((TestEndpoint)((Service)iniCtx.lookup("java:comp/env/service1")).getPort(TestEndpoint.class));
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/ServletClient.java:52: '{' expected
[javac] ports.add((TestEndpoint)((Service)iniCtx.lookup("java:comp/env/service1")).getPort(TestEndpoint.class));
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/ServletClient.java:53: <identifier> expected
[javac] ports.add(((TestEndpointService)iniCtx.lookup("java:comp/env/service2")).getTestEndpointPort());
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/ServletClient.java:55: illegal start of type
[javac] catch (Exception ex)
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/ServletClient.java:68: <identifier> expected
[javac] res.getWriter().print(inStr);
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/ServletClient.java:70: 'class' or 'interface' expected
[javac] }
[javac] ^
[javac] /home/pjha/sandbox/ws-test-automation/output/checkout/jbossws-1.0.4.GA/src/test/java/org/jboss/test/ws/jaxrpc/webserviceref/ServletClient.java:71: 'class' or 'interface' expected
> Release jbossws-1.0.4.GA binary
> -------------------------------
>
> Key: JBWS-1194
> URL: http://jira.jboss.com/jira/browse/JBWS-1194
> 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.4
>
>
> The release criteria for jbossws-1.1.0.GA are:
> * pass all internal jbossws tests
> * pass all portable j2ee-1.4 tests from the jboss testsuite
> * pass all tests in module jaxr,jaxrpc,saaj,webservice from the Sun compatiblity testsuite
> * generate all test artifacts with wstools
--
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
19 years, 5 months
[JBoss JIRA] Commented: (JBWS-814) JSR-181 rpc/encoded should trigger an exception
by Kenny Stainback (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-814?page=comments#action_12346316 ]
Kenny Stainback commented on JBWS-814:
--------------------------------------
+1 for supporing RPC/encoded.
> JSR-181 rpc/encoded should trigger an exception
> -----------------------------------------------
>
> Key: JBWS-814
> URL: http://jira.jboss.com/jira/browse/JBWS-814
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: wstools
> Reporter: Thomas Diesler
> Assigned To: Thomas Diesler
> Fix For: jbossws-1.0.1
>
>
> I'm trying to migrate our JBoss.NET based services to new JBossWS but I'm having trouble getting rpc/encoded styles working. I need this for my Perl (SOAP::Lite) based clients. Is rpc/encoded style still supported in JBossWS?
> My Java code looks like:
> Code:
> package com.lunatech.test.jbossws;
> import javax.ejb.Stateless;
> import javax.jws.WebMethod;
> import javax.jws.WebParam;
> import javax.jws.WebResult;
> import javax.jws.WebService;
> import javax.jws.soap.SOAPBinding;
> import org.jboss.ws.annotation.PortComponent;
> import com.lunatech.test.jbossws.dvo.GetInfoRequest;
> import com.lunatech.test.jbossws.dvo.GetInfoResponse;
> @WebService(
> targetNamespace = "http://test.lunatech.com/MutationService/",
> serviceName = "MutationService"
> )
> @PortComponent(contextRoot="/MutationService", urlPattern="/*")
> @SOAPBinding(
> style = SOAPBinding.Style.RPC,
> use = SOAPBinding.Use.ENCODED
> )
> @Stateless
> public class MutationService implements MutationServiceRemote {
>
> @WebMethod(action = "getInfo")
> @WebResult(name = "response")
> public GetInfoResponse getInfo(@WebParam(name = "request") GetInfoRequest request) {
> return new GetInfoResponse();
> }
>
> }
>
> But the relevant bit of WSDL generated still says use='literal'. Also, my soapAction seems to be missing:
> Code:
> ...
> <binding name='MutationServiceBinding' type='tns:MutationService'>
> <soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/>
> <operation name='getInfo'>
> <soap:operation soapAction=''/>
> <input>
> <soap:body namespace='http://test.lunatech.com/MutationService/' use='literal'/>
> </input>
> <output>
> <soap:body namespace='http://test.lunatech.com/MutationService/' use='literal'/>
> </output>
> </operation>
> </binding>
> ...
>
> This is with the latest 4.0.4 jboss-head checkout on 2006-03-26.
--
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
19 years, 5 months
[JBoss JIRA] Commented: (JBWS-1162) Automated release QA
by Prabhat Jha (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1162?page=comments#action_12346315 ]
Prabhat Jha commented on JBWS-1162:
-----------------------------------
I have attached the whole script and its dependencies. The size a bit big because it includes ant related jars. Please use "tar xzvf" to open the zip. It should create a ws-test-automation directory which cotains a README file. I have not run this script on windows machine so not sure if everything willgo smooth but I have tried to make the script platform independent. Basically you need to:
Pre-Requirements:
-Install SVN and have svn in your path
-If you do not have ant installed, there is an ant that comes with this zip distribution. It's under ./ws-tools
Step 1:
-Provide following properties under build.properties
jboss.jdk14.src.url=svn url for jboss to run with jdk1.4(default should be fine)
jboss.jdk15.src.url=svn url for jboss to run with jdk1.5
tomcat.url=
tomcat.zip.file=
tomcat.home.name=the directory where zip file will be extracted to
jbossws.svn.url=jboss webservices svn repository
java14=JDK1.4 home (This jdk should have bouncy castle jar)
java15=JDK1.5 home
Step 2:
-run ant
-Checking out source code from SVN will take time depending on your network connection.
Step 3:
Summary of test runs will be in output/final-report.txt. The details of test runs can be found in jdk14-output and jdk15-output.
If there is any error, please let me know.
> Automated release QA
> --------------------
>
> Key: JBWS-1162
> URL: http://jira.jboss.com/jira/browse/JBWS-1162
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: documentation
> Reporter: Heiko Braun
> Assigned To: Prabhat Jha
> Fix For: jbossws-1.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
19 years, 5 months
[JBoss JIRA] Commented: (JBWS-1125) Support doc/lit with empty soap body elements
by Jason T. Greene (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1125?page=comments#action_12346310 ]
Jason T. Greene commented on JBWS-1125:
---------------------------------------
Also, the testcase in trunk and JEE5_TCK is correct, it just needs to be merged to 1.0.x
-Jason
> 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: Jason T. Greene
> Priority: Minor
> Fix For: jbossws-1.0.5
>
>
> 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
19 years, 5 months
[JBoss JIRA] Commented: (JBWS-1125) Support doc/lit with empty soap body elements
by Jason T. Greene (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1125?page=comments#action_12346309 ]
Jason T. Greene commented on JBWS-1125:
---------------------------------------
The issue is that the wrapped convention requires that all parameters be wrapped with a single element that is a complex type whose children are a sequence of elements. So a noarg method in the wrapped convention is not an empty message, but rather an empty wrapper element. This is represented in WSDL as a message with 1 part that references an element that has a complex type with an empty sequence. In short, a wrapped message by definition requires a wrapping element.
Although there is no formal WS spec on this, the behavior I describe is consitent with .NET and with the JAX-RPC[1] and JAX-WS[2] specs. Also, its easier to implement because their is no ambiguity associated with a noarg method.
[1] JAX-RPC 1.1 Section 6.4.1
In order to qualify as using the "wrapper" style, an operation must fulfill the following
conditions:
* its input and output messages (if present) must contain exactly one part;
* such a part must refer to an element named after the operation;
* such an element (a wrapper) must be of a complex type defined using the
xsd:sequence compositor and containing only elements declarations.
[2] JAX-WS 2.0 Section 2.3.1.2
2.3.1.2 Wrapper Style
A WSDL operation qualifies for wrapper style mapping only if the following criteria are met:
(i) The operation's input and output messages (if present) each contain only a single part
(ii) The input message part refers to a global element declaration whose localname is equal to the operation
name
(iii) The output message part refers to a global element declaration
(iv) The elements referred to by the input and output message parts (henceforth referred to as wrapper
elements) are both complex types defined using the xsd:sequence compositor
(v) The wrapper elements only contain child elements, they must not contain other structures such as
wildcards (element or attribute), xsd:choice, substitution groups (element references are not permitted)
or attributes; furthermore, they must not be nillable.
} Conformance (Default mapping mode): Operations that do not meet the criteria aboveMUST be mapped
using non-wrapper style.
> 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: Jason T. Greene
> Priority: Minor
> Fix For: jbossws-1.0.5
>
>
> 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
19 years, 5 months
[JBoss JIRA] Updated: (JBWS-1196) jboss-4.2.x (jdk1.5)
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1196?page=all ]
Thomas Diesler updated JBWS-1196:
---------------------------------
Summary: jboss-4.2.x (jdk1.5) (was: jboss-4.0.x (jdk1.5))
Description:
Run these tests with jdk1.5
tdiesler@tdvaio /home/tdiesler/svn/jbossws/branches/jbossws-1.0/src/test
$ ant tests
[PASS]
tdiesler@tdvaio /home/tdiesler/svn/jbossws/branches/jbossws-1.0/output/jbossws-samples-1.0.x.GA
$ ant tests
[PASS]
tdiesler@tdvaio /home/tdiesler/svn/jbossas/branches/Branch_4_2/testsuite
$ ant tests-webservice
[PASS]
was:
Run these tests with jdk1.5
tdiesler@tdvaio /home/tdiesler/svn/jbossws/branches/jbossws-1.0/src/test
$ ant tests
[PASS]
tdiesler@tdvaio /home/tdiesler/svn/jbossws/branches/jbossws-1.0/output/jbossws-samples-1.0.x.GA
$ ant tests
[PASS]
tdiesler@tdvaio /home/tdiesler/svn/jbossas/tags/JBoss_4_0_5_GA/testsuite
$ ant tests-webservice
[PASS]
> jboss-4.2.x (jdk1.5)
> --------------------
>
> Key: JBWS-1196
> URL: http://jira.jboss.com/jira/browse/JBWS-1196
> 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.4
>
>
> Run these tests with jdk1.5
> tdiesler@tdvaio /home/tdiesler/svn/jbossws/branches/jbossws-1.0/src/test
> $ ant tests
> [PASS]
> tdiesler@tdvaio /home/tdiesler/svn/jbossws/branches/jbossws-1.0/output/jbossws-samples-1.0.x.GA
> $ ant tests
> [PASS]
> tdiesler@tdvaio /home/tdiesler/svn/jbossas/branches/Branch_4_2/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
19 years, 5 months