eclipse-ee4j / eclipse-ee4j/metro-wsit
Docs update needed for Metro 1.2 with GF TP2 and NB6.1
- Dominant language
- Java
- Stars
- 6
- Forks
- 21
- Avg merge
- 10h 2m
- Merged PRs (30d)
- 1
Description
The following are the issues seen with the security examples in chapter 11 of
the doc:
_Common to all Examples:_
Service Creation
Step 1
b) Skip the section on adding Reliable Messaging.(Not clear why we need this).
Client Creation
1)In the page at
*[https://metro.dev.java.net/guide/Creating_a_Client_to_Consume_a_WSIT_Enabled_Web_Service.html#ahibs*/](https://metro.dev.java.net/guide/Creating_a_Client_to_Consume_a_WSIT_Enabled_Web_Service.html#ahibs*/)
/
Step 5 asks the user to copy the wsdl url
[http://localhost:8080/CalculatorApplication/CalculatorWSService?wsdl](http://localhost:8080/CalculatorApplication/CalculatorWSService?wsdl) while
creating the web service client. The wsdl url should be
[http://localhost:8080/CalculatorApplication/CalculatorWS?wsdl](http://localhost:8080/CalculatorApplication/CalculatorWS?wsdl)
Step 6 asks the user to enter some package name, but the package name field is
disabled.
2) In the docs for "Deploying and Testing a Web Service" as mentioned at the link**
*[https://metro.dev.java.net/guide/Deploying_and_Testing_a_Web_Service.html#ahibr*](https://metro.dev.java.net/guide/Deploying_and_Testing_a_Web_Service.html#ahibr*),
step2 says "Type /CalculatorWSService?wsdl in the Relative URL field and click
OK". But the wsdl's url pattern is /CalculatorWS?wsdl.
3) In all the cases where user is asked to check the "Use Development Defaults"
checkbox in the steps where a web service is secured, the checkbox is shown in
unchecked state though the user has already checked it.
Snapshot: CheckboxNotShownAsChecked.gif
4) The keystore entries "xws-security-server" and "xws-security-client" are
absent in the keystores"cacerts.jks" and "keystore.jks" (that come with the
Glassfish V3 distribution) respectively. To get the examples running we had to
copy these keystores from a Glassfish V2 installation.
5) To get the SSL based examples running, we had to make the following changes
to the "domain.xml":
i) Comment out the http-listener for port 8181-
ii) Add a listener for port 8181 as -
6\. Junk characters are seen all over the examples.
*_Examples_
11.8.1\. Example: Username Authentication with Symmetric Key (UA)*
*Service Creation
*
1) Step 2 shows some junk c
step 7 Click OK to close the CalculatorWSService dialog.
change the service name to CalculatorWS.
2)Junk Chars
Step 2 shows some junk char's
step 7 shows some junk char's
*Client Creation
*
Search **
To Secure the Example Web Service Client Application (UA)
1)Junk Chars
Step 6 shows some junk chars
**11.8.2\. Example: Mutual Certificates Security (MCS)**
Junk Chars
--------
Search **
To Secure the Example Web Service Client Application (MCS)
step 2
If you'd like, in the tree, drill down from the project to Source Packagesââ€
’META-INF. Double-click on CalculatorWSService.xml, click the Source tab, and
look at the section in the section to see the WSIT code that has been
added to this configuration file.
**11.8.3\. Example: Transport Security (SSL)**
Junk Chars in step 2,7 and 8 of service creation
<[https://metro.dev.java.net/guide/Example_Applications.html#Example__SAML_Authorization_over_SSL__SA_](https://metro.dev.java.net/guide/Example_Applications.html#Example__SAML_Authorization_over_SSL__SA_)>
11.8.4\. Example: SAML Authorization over SSL (SA)
The following compile time failures are seen in the "SamlCallbackHandler"
created by following the steps mentioned in step 3 of the instructions to create
a client for the service:
a. import com.sun.xml.wss.impl.callback.*; --> package does not exist
b. import com.sun.xml.wss.saml.*; --> package does not exist
This has blocked the testing of this example.
11.8.5.Example: SAML Sender Vouches with Certificates (SV)
The following compile time failures are seen in the "SamlCallbackHandler"
created by following the steps mentioned in step 3 of the instructions to create
a client for the service:
a. import com.sun.xml.wss.impl.callback.*; --> package does not exist
b. import com.sun.xml.wss.saml.*; --> package does not exist
This has blocked the testing of this example.
11.8.6\. Example: STS Issued Token (STS)
When we try to access the wsdl of the STS created by following the steps
mentioned in [https://metro.dev.java.net/guide/Example_Applications.html#gfrlq](https://metro.dev.java.net/guide/Example_Applications.html#gfrlq),
we get a 503 error. Since this wsdl is unavailable we could not test this example.
11.8.7\. Example: Kerberos Token (Kerb)
The following exception is thrown while deploying the service:
SEVERE: WSSERVLET11: failed to parse runtime descriptor:
java.lang.NoClassDefFoundError: Could not initialize class
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder
java.lang.NoClassDefFoundError: Could not initialize class
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder
at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:286)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
at
com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:153)
at
com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:149)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIModelImpl.java:148)
at
com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelImpl.java:87)
This has blocked the execution of this example.
The issues seen in the examples 4, 5, 6 and 7 were not seen when executed with
Glassfish v2.
Here are my comments regarding 1.3 docs covering chapter 1,7,13,16 from
url [https://metro.dev.java.net/guide](https://metro.dev.java.net/guide) running on GF V3 TP2 build gfv3-preview2
(gfv3-preview2.zip) using netbeans 6.1 (netbeans-6.1-javaee-solaris-sparc.sh)
with the following plugins:
org-netbeans-modules-glassfish-common.nbm
org-netbeans-modules-glassfish-javaee.nbm
===============================================================
Section 1\.
1.1\. Required Software
[https://metro.dev.java.net/guide//Required_Software.html](https://metro.dev.java.net/guide//Required_Software.html)
================================================================
1. The latest Java SE 5.0 (Update 14) or JDK 6.0 (Update 4) with which Metro has
been extensively tested
2. While Metro can be run on any servlet container, using all the advanced
featues of Metro requires one of the following web containers:
* Application Server 9.1 Update 1
* GlassFish V2 Update 1
**************************************************************************
COMMENT: should reference latest Java SE 5.0 (Update 16) or JDK 6.0 (Update
6)or whatever latest version is at time of editting this page
**************************************************************************
**************************************************************************
COMMENT: Also should reference Glassfish V3 TP2, not Glassfish V2 Update 1
**************************************************************************
1. Metro Version 1.2 binary, which includes the WSIT Version 1.2 software that
you install into your Application Server 9.1 Update 1 (or Glassfish V2 Update 1)
installation.
2. NetBeans IDE 6.0
**************************************************************************
COMMENT: should refer to Metro Version 1.3, not WSIT Version 1.2
COMMENT: should refere to Netbeans 6.1, not Netbeans 6.0
**************************************************************************
See the WSIT Installation Instructions, located at
[https://wsit-docs.dev.java.net/releases/1.2/install.html](https://wsit-docs.dev.java.net/releases/1.2/install.html), for instructions about
downloading and installing all the required software.
**************************************************************************
COMMENT: should reference 1.3, not 1.2 release WSIT Installation Instructions.
**************************************************************************
To run the examples described in this tutorial, you must also download the WSIT
samples kits. Download the sample kits from the following locations:
*
[https://wsit.dev.java.net/source/browse/*checkout*/wsit/wsit/docs/howto/wsit-enabled-fromjava.zip](https://wsit.dev.java.net/source/browse/*checkout*/wsit/wsit/docs/howto/wsit-enabled-fromjava.zip)
*
[https://wsit.dev.java.net/source/browse/*checkout*/wsit/wsit/docs/howto/wsit-enabled-fromwsdl.zip](https://wsit.dev.java.net/source/browse/*checkout*/wsit/wsit/docs/howto/wsit-enabled-fromwsdl.zip)
*
[https://wsit.dev.java.net/source/browse/*checkout*/wsit/wsit/docs/howto/client-enabled-fromjava.zip](https://wsit.dev.java.net/source/browse/*checkout*/wsit/wsit/docs/howto/client-enabled-fromjava.zip)
* [https://wsit-docs.dev.java.net/releases/1.2/wsittutorial.zip](https://wsit-docs.dev.java.net/releases/1.2/wsittutorial.zip)
**************************************************************************
COMMENT: last link should refer to 1.3, not 1.2
**************************************************************************
===============================================================
1.2\. What is WSIT?
===============================================================
**************************************************************************
COMMENT: Should WSIT be changed to Metro? (throughout this entire document)
**************************************************************************
===============================================================
Section 7\. WSIT Example Using a Web Container and NetBeans IDE
================================================================
[https://metro.dev.java.net/guide/Registering_GlassFish_with_the_IDE.html](https://metro.dev.java.net/guide/Registering_GlassFish_with_the_IDE.html)
7.1\. Registering GlassFish with the IDE
3\. Select GlassFish V2 or Sun Java System Application Server, and click
Next.
**************************************************************************
COMMENT: Should refer to Glassfish V3 TP2
**************************************************************************
Answer: For registering V3 with NB6.1 we need to add two plugins as noted above.
Goto Tools->Plugins and from Downloaded Plugins tag chose downloaded
Glassfish V3 Modules .nbm files noted above. After that it can recognize
the V3.
**************************************************************************
COMMENT: We need to tell users about this requirement to install these plugins.
**************************************************************************
5\. Type the server username and password that you supplied when you installed
the web container (the defaults are admin and adminadmin), then click Close.
**************************************************************************
COMMENT: There is no place to enter this information.
**************************************************************************
7.3\. Configuring WSIT Features in the Web Service
[https://metro.dev.java.net/guide//Configuring_WSIT_Features_in_the_Web_Service.html](https://metro.dev.java.net/guide//Configuring_WSIT_Features_in_the_Web_Service.html)
**************************************************************************
COMMENT: the text displayed at the bottom on this page should match what is
contained in the actual .xml file, it should look like this:
The page currently shows this:
Notice the difference in wsaw vs. wsaws
**************************************************************************
7.4\. Deploying and Testing a Web Service
[https://metro.dev.java.net/guide//Deploying_and_Testing_a_Web_Service.html](https://metro.dev.java.net/guide//Deploying_and_Testing_a_Web_Service.html)
**************************************************************************
COMMENT: in section 3\. , the following text needs a space between the
words "Following" and "WSIT"
The followingWSIT tags display in the WSDL file:
should be
The following WSIT tags display in the WSDL file:
**************************************************************************
7.4\. Deploying and Testing a Web Service
[https://metro.dev.java.net/guide//Deploying_and_Testing_a_Web_Service.html](https://metro.dev.java.net/guide//Deploying_and_Testing_a_Web_Service.html)
**************************************************************************
COMMENT:
Should tell user that URL to access wsdl is
[http://localhost:8080/CalculatorApplication/CalculatorWS?wsdl](http://localhost:8080/CalculatorApplication/CalculatorWS?wsdl)
Text displayed at the bottom of this page should be:
but the text displayed at the bottom of this url currently shows:
**************************************************************************
7.5\. Creating a Client to Consume a WSIT-Enabled Web Service
[https://metro.dev.java.net/guide//Creating_a_Client_to_Consume_a_WSIT_Enabled_Web_Service.html](https://metro.dev.java.net/guide//Creating_a_Client_to_Consume_a_WSIT_Enabled_Web_Service.html)
Text:
5\. For example, here is the URL for the CalculatorWS web service:
[http://localhost:8080/CalculatorApplication/CalculatorWSService?wsdl](http://localhost:8080/CalculatorApplication/CalculatorWSService?wsdl)
When JAX-WS generates the web service, it appends Service to the class name by
default.
Type org.me.calculator.client in the Package field, and click Finish.
**************************************************************************
COMMENTS: The URL actually is
[http://localhost:8080/CalculatorApplication/CalculatorWS?wsdl](http://localhost:8080/CalculatorApplication/CalculatorWS?wsdl)
it doesn't contain extra Service appended to the class name by default
as mentioned above.
You also cannot enter org.me.calculator.client in the Package field because
the package field is greyed out, with value set to "default package"
**************************************************************************
[https://metro.dev.java.net/guide//Creating_a_Client_to_Consume_a_WSIT_Enabled_Web_Service.html](https://metro.dev.java.net/guide//Creating_a_Client_to_Consume_a_WSIT_Enabled_Web_Service.html)
If Reliable Messaging is enabled, the client needs to close the port when done
or the server log will be overwhelmed with messages. To close the port, first
add the following line to the import statements at the top of the file:
import com.sun.xml.ws.Closeable;
Then add the line in bold at the end of the try block, as shown below.
((Closeable)port).close();
**************************************************************************
COMMENT:
The comments about text to add being shown in BOLD is not happening, there is
nothing showing in bold on my firefox browser on Solaris 10 platform.
Also, you can't add Closeable import statement and line at the end of try/ catch
block because program won't compile, instead get this error:
Compiling 1 source file to
/home/jbenoit/NetBeansProjects/CalculatorWSServletClient1/build/web/WEB-INF/classes
/home/jbenoit/NetBeansProjects/CalculatorWSServletClient1/src/java/org/me/calculator/client/ClientServlet.java:8:
package com.sun.xml.ws does not exist
import com.sun.xml.ws.Closeable;
1 error
/home/jbenoit/NetBeansProjects/CalculatorWSServletClient1/nbproject/build-impl.xml:393:
The following error occurred while executing this line:
/home/jbenoit/NetBeansProjects/CalculatorWSServletClient1/nbproject/build-impl.xml:214:
Compile failed; see the compiler error output for details.
BUILD FAILED (total time: 1 second)
When you click on the client servlet project and select run, it tries to enter
url
[http://localhost:8080/CalculatorWSServletClient1/](http://localhost:8080/CalculatorWSServletClient1/) /ClientServlet in a browser
so something is wrong with how the url gets cobbled together.
**************************************************************************
**************************************************************************
COMMENT: URL should be with no extra slash and no extra space:
[http://localhost:8080/CalculatorWSServletClient1/](http://localhost:8080/CalculatorWSServletClient1/) /ClientServlet in a browser
should be:
[http://localhost:8080/CalculatorWSServletClient1/ClientServlet](http://localhost:8080/CalculatorWSServletClient1/ClientServlet)
**************************************************************************
=====================================================================
Section "13\. WSIT Example Using a Web Container Without NetBeans IDE"
=====================================================================
0). [https://metro.dev.java.net/guide//Environment_Configuration_Settings.html](https://metro.dev.java.net/guide//Environment_Configuration_Settings.html)
**************************************************************************
COMMENT: wsit-enabled-fromjava/etc/wsit-fromjava.server.AddNumbersImpl.xml file
contained ^M's and i had to run dos2unix on Soalris 10 box to get rid
of extra control-M's. in fact all files in etc dir have this same problem.
**************************************************************************
also the IP of url is not correct for my box:
Should be localhost:8080, not 129.150.24.33
0a). [https://metro.dev.java.net/guide//Creating_a_Web_Service_without_NetBeans.html](https://metro.dev.java.net/guide//Creating_a_Web_Service_without_NetBeans.html)
**************************************************************************
COMMENT: all the text examples shows up grabled, i.e.
**************************************************************************
@WebService
public? class? AddNumbersImpl? {
? ? ? ? @WebMethod(action="addNumbers")
? ? ? ? public? int? addNumbers(int? number1,? int? number2)
? ? ? ? ? ? ? ? ? ? ? ? throws? AddNumbersException? {
? ? ? ? ? ? ? ? if? (number1?
—
>
105,106c105
<
<
—
>
117,124c116,121
<
<
<
<
<
<
—
>
>
>
>
>
>
**************************************************************************
COMMENT: Next i ran into this error:
**************************************************************************
jbenoit/galapago 1714 >ant server
Buildfile: build.xml
BUILD FAILED
/net/galapago.east/files/share/workspaces/gfv3TP2/UsersGuide/wsit-enabled-fromjava/build.xml:138:
taskdef class com.sun.tools.ws.ant.Apt cannot be found
Total time: 3 seconds
3).
[https://metro.dev.java.net/guide/Building_and_Deploying_the_Web_Service.html](https://metro.dev.java.net/guide/Building_and_Deploying_the_Web_Service.html)
13.4.2\. Building and Deploying a Web Service Created From WSDL
To build and deploy the web service, open a terminal window, go to the
tut-install/wsit-enabled-fromjava/ directory, and type the following:
ant server
**************************************************************************
COMMENT: this should say tut-install/wsit-enabled-fromwsdl/ directory
**************************************************************************
4).
% cd ../wsit-enabled-fromwsdl
% ant server
Buildfile: build.xml
BUILD FAILED
/wsit-enabled-fromwsdl/build.xml:129:
/workspaces/gfv3TP2/glassfish/lib/endorsed not found.
**************************************************************************
COMMENT: same problem as noted in the wsit-enabled-fromjava example.
**************************************************************************
5). had to make these changes to get past this error:
% diff wsit-enabled-fromwsdl/build.xml wsit-enabled-fromwsdl/orig.build.xml
102c102
<
—
>
106c106
<
—
>
117,124c117,122
<
<
<
<
<
<
—
>
>
>
>
>
>
6). [https://metro.dev.java.net/guide/Creating_a_Web_Service_Client.html](https://metro.dev.java.net/guide/Creating_a_Web_Service_Client.html)
13.5\. Creating a Web Service Client
[snip]
Typically, you retrieve the WSDL directly from a web service provider
using the wsimport tool. The wsimport tool then generates the
corresponding Java source code for the interface described by the WSDL.
13.5.1.2\. Client Configuration File (fromjava)
The client configuration file defines the URL of the web service WSDL
file. It is used by the web container wsimport tool to access and
consume the WSDL and to build the stubs that are used to communicate
with the web service.
[https://metro.dev.java.net/guide/Building_and_Deploying_a_Client.html](https://metro.dev.java.net/guide/Building_and_Deploying_a_Client.html)
[snip]
This command runs wsimport, which retrieves the web service?s WSDL, and
then it runs javac to compile the source.
**************************************************************************
COMMENT: I don't see wsimport tool in GF V3 TP2:
**************************************************************************
% ls /gfv3TP2/glassfish/bin/
asadmin* startserv* stopserv*
asadmin.bat startserv.bat stopserv.bat
% find /gfv3TP2/glassfish/ | grep -i wsimport
7a). 13.4.4\. Verifying Deployment
[https://metro.dev.java.net/guide//Building_and_Deploying_the_Web_Service.html](https://metro.dev.java.net/guide//Building_and_Deploying_the_Web_Service.html)
Before testing, make sure your web container is running.
*
[http://localhost:8080/wsit-enabled-fromjava/addnumbers?wsdl](http://localhost:8080/wsit-enabled-fromjava/addnumbers?wsdl)
*
[http://localhost:8080/wsit-enabled-fromwsdl/addnumbers?wsdl](http://localhost:8080/wsit-enabled-fromwsdl/addnumbers?wsdl)
If the browser displays a page of XML tags, the web service has been deployed
and is working. If not, check the web container log for any error messages
related to the sample WAR you have just deployed. For GlassFish, the log can be
found at as-install/domains/domain1/logs/server.log. For Apache Tomcat, the
appropriate log file can be found at tomcat-home/logs/catalina.out.
**************************************************************************
COMMENT: these two urls results in 404 error despite the fact that the
autodeploy directory is populated with these two .war files representing
these to modules.
[http://localhost:8080/wsit-enabled-fromjava/addnumbers?wsdl](http://localhost:8080/wsit-enabled-fromjava/addnumbers?wsdl)
[http://localhost:8080/wsit-enabled-fromwsdl/addnumbers?wsdl](http://localhost:8080/wsit-enabled-fromwsdl/addnumbers?wsdl)
HTTP Status 404
type Status report
message
description The requested resource () is not available
**************************************************************************
**************************************************************************
7b). COMMENT: Both samples fail to run:
**************************************************************************
benoit/galapago 1749 >pwd
/net/galapago.east/files/share/workspaces/gfv3TP2/UsersGuide/wsit-enabled-fromjava
jbenoit/galapago 1750 >ant run
Buildfile: build.xml
j
run:
[java] Exception in thread "main" java.lang.NoClassDefFoundError:
fromjava/client/AddNumbersClient
[java] Caused by: java.lang.ClassNotFoundException:
fromjava.client.AddNumbersClient
[java] at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
[java] at java.security.AccessController.doPrivileged(Native Method)
[java] at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
[java] at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
[java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
[java] at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
[java] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
[java] Java Result: 1
BUILD SUCCESSFUL
Total time: 3 seconds
jbenoit/galapago 1753 >cd wsit-enabled-fromwsdl
jbenoit/galapago 1754 >ant run
Buildfile: build.xml
run:
[java] Exception in thread "main" java.lang.NoClassDefFoundError:
fromwsdl/client/AddNumbersClient
[java] Caused by: java.lang.ClassNotFoundException:
fromwsdl.client.AddNumbersClient
[java] at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
[java] at java.security.AccessController.doPrivileged(Native Method)
[java] at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
[java] at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
[java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
[java] at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
[java] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
[java] Java Result: 1
BUILD SUCCESSFUL
Total time: 3 seconds
jbenoit/galapago 1755 >
7c). [https://metro.dev.java.net/guide//Creating_a_Web_Service_Client.html](https://metro.dev.java.net/guide//Creating_a_Web_Service_Client.html)
[https://metro.dev.java.net/guide//Building_and_Deploying_a_Client.html](https://metro.dev.java.net/guide//Building_and_Deploying_a_Client.html)
**************************************************************************
COMMENT: wsimport too is not found in the GF/bin dir, yet it's referenced from
this page. Should remove reference to wsimport.
**************************************************************************
**************************************************************************
COMMENT: ant client encounters error since wsdl is unreachable:
**************************************************************************
[wsimport] [ERROR] [http://localhost:8080/wsit-enabled-fromjava/addnumbers?wsdl](http://localhost:8080/wsit-enabled-fromjava/addnumbers?wsdl)
is unreachable
[wsimport] Failed to parse the WSDL.
[wsimport] Command invoked: wsimport
/net/jse.east/users/jbenoit-save/jdk1.6.0_04/jre/bin/java -d
/net/galapago.east/files/share/workspaces/gfv3TP2/UsersGuide/wsit-enabled-fromjava/build/classes
-keep [http://localhost:8080/wsit-enabled-fromjava/addnumbers?wsdl](http://localhost:8080/wsit-enabled-fromjava/addnumbers?wsdl) -b
/net/galapago.east/files/share/workspaces/gfv3TP2/UsersGuide/wsit-enabled-fromjava/etc/custom-schema.xml
-b
/net/galapago.east/files/share/workspaces/gfv3TP2/UsersGuide/wsit-enabled-fromjava/etc/custom-client.xml
BUILD FAILED
/net/galapago.east/files/share/workspaces/gfv3TP2/UsersGuide/wsit-enabled-fromjava/build.xml:202:
wsimport failed
COMMENT: same for fromwsdl instead of fromjava too:
[wsimport] [ERROR] [http://localhost:8080/wsit-enabled-fromwsdl/addnumbers?wsdl](http://localhost:8080/wsit-enabled-fromwsdl/addnumbers?wsdl)
is unreachable
[wsimport] Failed to parse the WSDL.
[wsimport] Command invoked: wsimport
/net/jse.east/users/jbenoit-save/jdk1.6.0_04/jre/bin/java -d
/net/galapago.east/files/share/workspaces/gfv3TP2/UsersGuide/wsit-enabled-fromwsdl/build/classes
-keep [http://localhost:8080/wsit-enabled-fromwsdl/addnumbers?wsdl](http://localhost:8080/wsit-enabled-fromwsdl/addnumbers?wsdl) -b
/net/galapago.east/files/share/workspaces/gfv3TP2/UsersGuide/wsit-enabled-fromwsdl/etc/custom-client.xml
BUILD FAILED
/net/galapago.east/files/share/workspaces/gfv3TP2/UsersGuide/wsit-enabled-fromwsdl/build.xml:182:
wsimport failed
7). [https://metro.dev.java.net/guide/Running_a_Web_Service_Client.html](https://metro.dev.java.net/guide/Running_a_Web_Service_Client.html)
**************************************************************************
COMMENT: What is the expected output for a successful run?
i.e. seeing this:
[com.sun.xml.ws.rm.runtime.ClientSession] preDestroy
[java] WARNING: Error sending Last message
is this okay?
% pwd
/wsit-enabled-fromjava
% ant run
Buildfile: build.xml
run:
[java] Invoking addNumbers(10, 20)
[java] The result of adding 10 and 20 is 30.
[java] Invoking addNumbers(-10, 20)
[java] Caught AddNumbersException_Exception: Numbers: -10, 20
[java] Apr 30, 2008 9:45:19 PM
[com.sun.xml.ws.rm.runtime.ClientSession] preDestroy
[java] WARNING: Error sending Last message
BUILD SUCCESSFUL
Total time: 11 seconds
% pwd
/wsit-enabled-fromwsdl
% ant run
Buildfile: build.xml
run:
[java] Invoking addNumbers(10, 20)
[java] The result of adding 10 and 20 is 30.
[java] Invoking addNumbers(-10, 20)
[java] Caught AddNumbersFault_Exception: Numbers: -10, 20
[java] Apr 30, 2008 9:50:33 PM
[com.sun.xml.ws.rm.runtime.ClientSession] preDestroy
[java] WARNING: Error sending Last message
BUILD SUCCESSFUL
**************************************************************************
8). [https://metro.dev.java.net/guide//Undeploying_a_Web_Service.html](https://metro.dev.java.net/guide//Undeploying_a_Web_Service.html)
**************************************************************************
COMMENT: undeploy doesn't work:
**************************************************************************
jbenoit/galapago 1782 >asadmin undeploy --user admin wsit-enabled-fromjava
FAILURE : V3 cannot process this command at this time, please wait
Command undeploy failed.
jbenoit/galapago 1785 >asadmin undeploy --user admin wsit-enabled-fromwsdl
FAILURE : V3 cannot process this command at this time, please wait
Command undeploy failed.
**************************************************************************
COMMENT: V3 undeploy command doesn't work.
**************************************************************************
=======================================
Section "16\. Using Atomic Transactions"
=======================================
**************************************************************************
1). COMMENT: the TX tutorial won't work with GFv3TP2\. so we shouldn't expose
these pages/sections to the user:
"16\. Using Atomic Transactions" on url:
[https://metro.dev.java.net/guide/](https://metro.dev.java.net/guide/)
"16.1\. About the basicWSTX Example" on url:
[https://metro.dev.java.net/guide/About_the_basicWSTX_Example.html](https://metro.dev.java.net/guide/About_the_basicWSTX_Example.html)
16.2\. Building, Deploying and Running the basicWSTX Example on url:
[https://metro.dev.java.net/guide/Building__Deploying_and_Running_the_basicWSTX_Example.html](https://metro.dev.java.net/guide/Building__Deploying_and_Running_the_basicWSTX_Example.html)
and once GFV3 TP2.next or whatever it will be called supports TX, then
these files need to be properly updated to refer to GF V3 instead of
older versions of GF V2, and then they should be included in
[https://metro.dev.java.net/guide/](https://metro.dev.java.net/guide/)
**************************************************************************
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[1.2]
Source: [https://github.com/javaee/metro-wsit/issues/924](https://github.com/javaee/metro-wsit/issues/924)
Author: glassfishrobot
Contributor guide
Research direction
Start with the Required Software, Registering GlassFish with the IDE, and chapter 11 example pages linked in the issue, using GlassFish V3 TP2 and NetBeans 6.1 as the reference environment. Review each reported URL, step, keystore, configuration, encoding, and example failure; done means the affected documentation is updated or each unresolved runtime problem is clearly recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100