JWSDP 1.2

Hi Folks,
I'm trying to get WLS8.1 to work with the latest web services developer pack.
In particular I want to use the JAAS (SOAP with attachments) stuff. My servlet
fails with method not found exceptions on some of the SOAPMessage stuff. Anyone
get this to work with the latest web services developer pack. How do I make WLS8.1
use JWSDP-1.2.
Thanks,
Ed

Hi Ed,
You're probably going to have to have to go back to version 6.1, to work with
JWSDP :-)
The primary reason for this, is that JWSDP contains Sun's implementation of the
JAX-RPC, SAAJ (what you called JAAS in your post) and JAXM, which is not a 100%
replacement for BEA's implementation of these same APIs. You will have the issues
you have brought up in both WLS 7.0 and 8.1, but not in 6.1, because that version
doesn't have an implementation of the aforementioned APIs.
What you are witnessing here, is a situation where classes in the JWSDP are unknowingly
creating objects using the factories from BEA's implementation. When this code
then goes to call methods on these objects, it thinks they are from their implementation,
and the call fails.
I have spent about 10 hours tracking down what's going on with WLS 7.0, and I
was able to get past a lot of issues with JAXM. But, I ended up not being able
to get things to behave 100%, because the JWSDP was calling lots of code that
had no equivalent in the BEA implementation. This is not a slight on either product.
It's merely a testament that JAX implementations are not exactly 100% replaceable
:-) If you are interested in a document that provides the steps for getting JWSDP
1.2 to work with WLS 6.1, e-mail me and I'll send you a copy.
HTH,
Mike Wooten
"Ed Loyot" <[email protected]> wrote:
>
Hi Folks,
I'm trying to get WLS8.1 to work with the latest web services developer
pack.
In particular I want to use the JAAS (SOAP with attachments) stuff.
My servlet
fails with method not found exceptions on some of the SOAPMessage stuff.
Anyone
get this to work with the latest web services developer pack. How do
I make WLS8.1
use JWSDP-1.2.
Thanks,
Ed

Similar Messages

JWSDP installation problem on Windows 2000

Hi,
I downloaded the JWSDP1.0ea1 today, but I could not install the downloaded file (which is an executable). The install program tells me there is no JDK1.3.1 on my system, but there sure is (since I use the computer on which I try to install it everyday to write java programs :-) ).
(following commands on the prompt confirms this:
C:\>echo %java_home%
C:\java\jdk1.3.1
C:\>java -version
java version "1.3.0_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0_02)
Java HotSpot(TM) Client VM (build 1.3.0_02, mixed mode)
Could it be that this is a bug in the installer for the JWSDP on Win2k? Has someone experienced the same problem?
regards,
Wim.

My freshly installed J2SE1.4RC was recognized by the installer, but it put the files into c:\jwsdp-1_0-ea1\ instead of into the
J2SE dir tree as the installer implied that it would.
Is this right? A Bug? and it begs the general question:
WHERE IS THE INSTALLATION README LINK on the JWSDP download page? See email to feedback as follows....
Your web page
http://java.sun.com/webservices/downloads/webservicespack.html
doesnt link to install instructions for the Java Web Services Developer Pack.
The link provided is only for the Java 2 SDK, Standard Edition
Version 1.3.1 !!
The installer of the Java WSDP (on Win2K at any rate) leads one
to believe that it will be "integrated" with (i.e. loaded into the dir tree of)
the JDK that it finds on the system (in my case the J2SE1.4 RC).
It, in fact, installed into its own area (c:\jwsdp-1_0-ea1\) PLUS it already
included the tutorial that we are led to believe needs a separate download
according to the instructions on the download page
[ again as above: http://java.sun.com/webservices/downloads/webservicespack.html ]
So, WHERE are the instructions that say what (if anything) is needed
to finish installation such that, say, Tomcat can be fired up (for example).
P.S. Before you point me to the page
http://java.sun.com/j2ee/documentation/windows_guide.html
note that I am looking for how to finish installation/integration
with a J2SE installation (*as the download page says is already
tested) and NOT a J2EE installation.
So, again where is the SE instructions page (not an EE page)?
* - "This release of the Java Web Services Developer Pack has
been tested with various configurations with the JavaTM 2 SDK,
Standard Edition version 1.3.1_01, 1.3.1_02, and 1.4..."

Upgrading to JAXB/JWSDP1.3 from JAXB/JWSDP 1.2 -- problems

I am seeing 2 problems after upgrading to the JAXB found in WSDP 1.3 (from 1.2)
We are using JAXB in a client/server style app where the server is accessed via a web interface and the client is delivered via Java Web Start (JWS). Both the server and client use JAXB-generated classes.
We have an ant build.xml file that invokes xjc and this was working for us as expected.
For the JWS piece, we need to sign the jars we use and for testing purposes we were self-signing them, including the jar files needed for JAXB also self-signed. This is also coordinated through an ant task.
After replacing the jar files in our lib area with the ones from my recent download of the 1.3 version of JAXB the following happens.
1. I am seeing compiler deprecation warnings for the generated code -- this did not happen in our use of JAXB from 1.2. For example:
[javac] /Users/jjs/Projects/SGS-Install-Fixed/sgs/src/com/gestalt/sgs/uobdif/impl/runtime/SAXMarshaller.java:259: warning: ERR_MISSING_OBJECT in com.sun.xml.bind.marshaller.Messages has been deprecated
[javac] Messages.format(Messages.ERR_MISSING_OBJECT), null,
[javac] ^
I am using Java 1.4.1 on Max OS X (I know... not supported but this doesn't seem like a platform dependency) and these warnings go away if I revert back to the JAXB jars from the 1.2 release of WSDP.
2. These are only warnings, so my build proceeds with ant. But, when I get to the jar signing step I see:
[signjar] Signing Jar : /Users/jjs/Projects/SGS-Install-Fixed/sgs/lib/jaxb-libs.jar
[signjar] jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry compressed size (expected 63854 but got 19845 bytes)
I looked at the jar file using the jar command and there are entries there:
4038 Wed Dec 03 22:16:20 EST 2003 META-INF/MANIFEST.MF
3303 Wed Dec 03 22:16:20 EST 2003 META-INF/SUN_MICR.RSA
3780 Wed Dec 03 22:16:20 EST 2003 META-INF/SUN_MICR.SF
0 Wed Dec 03 22:16:20 EST 2003 META-INF/pack.properties
that suggest to me that perhaps the jar is now sigend by Sun and therefore can't be signed again. If I look at the corresponding jar from the JAXB/1.2, these SUN_MICR entries do not appear.
Is this assumption correct? Can I deliver my app through web start with my apps own jars self-signed and the JAXB jars signed by Sun? I suppose I can un-jar the JAXB jars, remove the manifest material and then re-jar the files and sign those. I expect this might work.
I am looking to share migration experiences (1.2 to 1.3) and to see what work-arounds there might be.
Thanks
Jim

Replying to my own post.
It seems that with the JWSDP 1.3 release, most (if not all) of the included jars are signed by Sun. You can NOT include jars with different signatures in the same web start application -- that's the error I get when I tried to do this.
This means that if I want to package my jars using a self-signed certificate, I have to first un-jar all of the JAXB lib jars I want to include, get rid of the parts of the manifest that deal with signing, re-jar them and then sign all of the jars in my web start app using my own cert. More work for me, but not a show-stopper.
I still am not sure why I am getting deprecated warnings from javac though.
Jim

Creating And Deploying A JWSDP Web Service Client to Weblogic 8.1

This setup produces an EAR containing a message driven bean in a jar file. When the MDB receives a message
it checks to see if there is any data in a database table and if so calls the web service with that data. These instructions
are for MS-Windows environments.
In my setup I have:
the weblogic domain at c:\b2b80
the jwsdp at c:\apps\jwsdp-1.3
extra jar files for the app server in c:\b2b80\lib
the main weblogic installation at c:\apps\weblogic810\
1> Download the the JWSDP version you wish to use and install it. (In this example I'm using 1.3)
2> Create a project structure for you client like this:
     /project
          /earbuild
               /META-INF
          /ejbbuild
               /META-INF
          /ejbsource
          /wssource
3> in the /project directory you will need a build.xml file that looks something like this: (the ant build targets are described at the end of this document)
==============================================================
<?xml version="1.0"?>
<project name="svcowner" default="buildall" basedir=".">
     <property file="classpath.settings"/>
     <property name="wssource" value="wssource"/>
     <property name="ejbsource" value="ejbsource"/>
     <property name="compileejbdest" value="ejbbuild"/>
     <property name="earbuilddest" value="earbuild"/>
     <property name="jarfilename" value="svcownerejb.jar"/>
     <property name="earfilename" value="svcowner.ear"/>
     <property name="debug" value="true"/>
     <property name="deprecation" value="true"/>
     
     <target name="cmdline_wscompile">
          <exec executable="wssource/create.bat"/>
     </target>
     <target name="compileejb" depends="cmdline_wscompile">
          <javac debug="${debug}" srcdir="${wssource}" classpath="${BUILD_CLASSPATH}"
               destdir="${compileejbdest}" includes="**/*.java" deprecation="${deprecation}"/>
          <javac debug="${debug}" srcdir="${ejbsource}" classpath="${BUILD_CLASSPATH}"
               destdir="${compileejbdest}" includes="**/*.java" deprecation="${deprecation}"/>
     </target>
     <target name="buildejbjar" depends="compileejb">
          <jar jarfile="${earbuilddest}/${jarfilename}" manifest="${compileejbdest}/META-INF/MANIFEST.txt">
               <fileset dir="${compileejbdest}">
                    <include name="**/*.*"/>
               </fileset>
          </jar>
     </target>
     <target name="buildear" depends="buildejbjar">
          <jar jarfile="${earfilename}">
               <fileset dir="${earbuilddest}">
                    <include name="**/*.*"/>
               </fileset>
          </jar>
     </target>
     <target name="deploy">
          <copy file="${earfilename}" todir="../../config/domain/applications"/>
     </target>
     <target name="buildall" description="build everything" depends="buildear, deploy">
     </target>
</project>
==============================================================
4> You need a matching classpath.settings file in the same directory, something like this:
==============================================================
BUILD_CLASSPATH=/b2b80/lib/saaj-impl.jar;/b2b80/lib/saaj-api.jar;/b2b80/lib/jaxrpc-api.jar;/b2b80/lib/jaxrpc-impl.jar;c:/b2b80/lib/jaxrpc-spi.jar/b2b80/classes/;/b2b80/classes;/apps/weblogic810/server/lib/weblogic.jar;/apps/weblogic810/server/lib/weblogic_sp.jar;/apps/weblogic810/server/lib/xmlx.jar;/apps/weblogic810/server/ext/weblogic-tags.jar;/apps/weblogic810/server/ext/jdbc/oracle/920/ojdbc14_g.jar;/b2b80/lib/log4j.jar
==============================================================
5> In the /project/earbuild/META-INF directory you need an application.xml file:
==============================================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN' 'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
<application>
<display-name>svcownerb2b</display-name>
<description>Application description</description>
<module>
<ejb>svcownerejb.jar</ejb>
</module>
</application>
==============================================================
6> The /project/ejbsource directory contains the source for the client application. In my case this is a message driven bean (note that code below isn't complete). The most important part of the code below is the setting of the javax.xml.soap.MessageFactory system property.
System.getProperties().put("javax.xml.soap.MessageFactory","com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl");
If you don't do this a weblogic class will be used and the code will fail.
==============================================================
package com.svcclient.ejb.svcownershipment;
import java.text.*;
import java.io.*;
import java.sql.*;
import java.util.Properties;
import javax.ejb.*;
import javax.jms.*;
import javax.naming.*;
import javax.sql.DataSource;
import com.svcclient.util.*;
import org.w3c.dom.*;
import com.svcclient.websvc.svcowner.*;
import javax.xml.rpc.Stub;
public class SvcOwnerShipmentSubscriberMDB implements MessageDrivenBean, MessageListener
private transient MessageDrivenContext mdc = null;
private static Context context;
private final static String CLASSNAME = "SvcOwnerShipmentSubscriberMDB";
private String DATASOURCE_JNDI = "svcclient.b2b";
private static DataSource mDS = null;
private SimpleDateFormat dateFormat = new SimpleDateFormat("yyyy-MM-dd");
public SvcOwnerShipmentSubscriberMDB()
System.getProperties().put("javax.xml.soap.MessageFactory","com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl");
try
if (context == null)
context = new InitialContext() ;
if (mDS == null)
mDS = (DataSource)context.lookup(DATASOURCE_JNDI);
catch (NamingException ex)
ex.printStackTrace();
catch(Exception ex)
ex.printStackTrace();
public void onMessage(javax.jms.Message message)
TextMessage msg = null;
String ordernumber = null;
String lineid = null;
try
if (message instanceof TextMessage)
msg = (TextMessage) message;
ordernumber = msg.getStringProperty("ordernumber");
               // the JMS message contains a property that is an order number
createAndSendXML(ordernumber);
catch (Throwable ex)
ex.printStackTrace();
private void createAndSendXML(String ordernumber)
if(ordernumber==null)
return;
PreparedStatement statement = null;
ResultSet rset = null;
java.sql.Connection conn = null;
try
conn = DBHelper.getConnection(mDS,"SvcOwnerShipmentSubscriberMDB.createAndSendXML");
statement = conn.prepareStatement("select * from ..."); // you SQL here
statement.setString(1,ordernumber);
rset = statement.executeQuery();
StringBuffer data = new StringBuffer();
data.append("<? version=\"1.0\"?>\n");
data.append("<shippingRequest>\n");
while(rset.next())
data.append("\t<order_date>"+dateFormat.format(new java.util.Date(rset.getTimestamp("SCHEDULE_SHIP_DATE").getDate()))+"</order_date>\n");
data.append("\t<brand_name>svcclient</brand_name>\n");
data.append("\t<shipRequestType>Sale</shipRequestType>\n");
data.append("</shippingRequest>\n");
          // call the web service with the data from the database
DataExchanger_Impl impl = new DataExchanger_Impl();
Stub stub = (Stub)(impl.getDataExchangerSoap());
DataExchangerSoap dx = (DataExchangerSoap)stub;
String resp = dx.exchangeData("svcclient", "mypassword", "Sales", data.toString());
catch(SQLException sqle)
sqle.printStackTrace();
catch(Exception e)
e.printStackTrace();
finally
try
if (rset != null)
rset.close();
if (statement != null)
statement.close();
if (conn != null)
conn.close();
catch(Exception x){}
public void ejbCreate() { System.out.println("In SvcOwnerShipmentSubscriberMDB.ejbCreate()"); }
public void setMessageDrivenContext(MessageDrivenContext mdc) { this.mdc = mdc; }
public void ejbRemove() throws javax.ejb.EJBException { System.out.println("In SvcOwnerShipmentSubscriberMDB.remove()"); }
==============================================================
7> The /project/ejbbuild/META-INF directory needs a MANIFEST.txt file.
Manifest-Version: 1.0
8> The /project/ejbbuild/META-INF directory needs a ejb-jar.xml file. This just sets up the MDB which is the client.
==============================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<display-name>SvcOwnerShipmentSubscriberMDB</display-name>
<enterprise-beans>
<message-driven>
<display-name>SvcOwnerShipmentSubscriberMDB</display-name>
<ejb-name>SvcOwnerShipmentSubscriberMDB</ejb-name>
<ejb-class>com.svcclient.ejb.svcownershipment.SvcOwnerShipmentSubscriberMDB</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>SvcOwnerShipmentSubscriberMDB</ejb-name>
<method-name>onMessage</method-name>
<method-params>
<method-param>javax.jms.Message</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
==============================================================
9> The /project/ejbbuild/META-INF directory needs a weblogic-ejb-jar.xml file.
==============================================================
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN" "http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>SvcOwnerShipmentSubscriberMDB</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>5</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>

<destination-jndi-name>jms.svcownerShipmentsTopic</destination-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
==============================================================
10> The /project/wssource directory needs a dataexchange.wsdl file. This is the WSDL describing the web service
we want to connect to with our client.
==============================================================
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="https://www.svcowner.com/mfg/DataExchange/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
targetNamespace="https://www.svcowner.com/mfg/DataExchange/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
name="">
<wsdl:types>
<s:schema elementFormDefault="qualified"
targetNamespace="https://www.svcowner.com/mfg/DataExchange/">
<s:element name="exchangeData">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="sender" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="password" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="transactionType" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="data" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="exchangeDataResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="exchangeDataResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="exchangeDataSoapIn">
<wsdl:part name="parameters" element="tns:exchangeData" />
</wsdl:message>
<wsdl:message name="exchangeDataSoapOut">
<wsdl:part name="parameters" element="tns:exchangeDataResponse" />
</wsdl:message>
<wsdl:portType name="DataExchangerSoap">
<wsdl:operation name="exchangeData">
<wsdl:input message="tns:exchangeDataSoapIn" />
<wsdl:output message="tns:exchangeDataSoapOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="DataExchangerSoap" type="tns:DataExchangerSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="exchangeData">
<soap:operation soapAction="https://www.svcowner.com/mfg/DataExchange/exchangeData"
style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="DataExchanger">
<wsdl:port name="DataExchangerSoap" binding="tns:DataExchangerSoap">
<soap:address location="https://svc.svcowner.com/mfg/dataexchange.php" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
==============================================================
10> The /project/wssource directory needs a websvc_config.xml file. This file tells wscompile where
to find the WSDL file and the package name for the generated classes.
==============================================================
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
     <wsdl location="wssource/dataexchange.wsdl" packageName="com.svcclient.websvc.svcowner"/>
</configuration>
==============================================================
11> The /project/wssource directory needs a create.bat file. This just sets up the environment
and calls the wscompile batch file in the JWSDP. I had to tweak the wscompile.bat file to match
my environment as well.
==============================================================
SETLOCAL
SET WSDP=C:\apps\jwsdp-1.3\
SET ANT_HOME=%WSDP%;apache-ant
SET PATH=%ANT_HOME%\bin;%WSDP%jaxrpc\bin;%PATH%
SET JAVA_HOME=c:\apps\weblogic810\jrockit81sp2_141_05
call wscompile -gen:client -s ./wssource -keep -g -d ejbbuild wssource/websvc_config.xml
==============================================================
12> The /project directory needs a build.bat file. Just a way for me to make sure my
environment is set up right before doing the build.
==============================================================
SETLOCAL
SET ANT_HOME=c:\apps\jakarta-ant-1.4.1
SET PATH=%ANT_HOME%\bin;%PATH%
SET JAVA_HOME=c:\apps\weblogic810\jrockit81sp2_141_05
call ant -buildfile build.xml %1 %2 %3 %4 %5 %6 %7 %8 %9
==============================================================
13> You need to copy the following jar files from the JWSDP into a location they can be used by the
app server during run time and also for the build process. In my set up this is c:\b2b80\lib. Note that
these are pointed to by the file in step 4.
c:\apps\jwsdp-1.3\jaxrpc\lib\jaxrpc-api.jar
c:\apps\jwsdp-1.3\jaxrpc\lib\jaxrpc-impl.jar
c:\apps\jwsdp-1.3\jaxrpc\lib\jaxrpc-spi.jar
c:\apps\jwsdp-1.3\saaj\lib\saaj-api.jar
c:\apps\jwsdp-1.3\saaj\lib\saaj-impl.jar
14> You must make sure that the jar file in step 13 are at the front of the classpath for the
weblogic server. WL comes with classes that conflict with these jars.
15> I also had to add the root ssl certificate from the partners certificate authority to the java keystore
using the keytool because this service uses SSL:
C:\apps\weblogic810\jrockit81sp2_141_05\jre\bin>keytool -import -keystore ..\lib\security\cacerts -alias svcownerroot -keypass password -file c:\temp\svcownerroot.cer
==============================================================
So the idea is this, you run the /project/build.bat file from within the /project directory. This
calls ant which uses the build.xml file to create everything and copy the EAR to the weblogic deployment
directory. The default ant target is buildall.
The cmdline_wscompile target runs the /project/wssource/create.bat file which in turn runs the wscompile.bat
file from the jwsdp. This causes the dataexchange.wsdl file to processed and the client files to be generated.
The generated java files go into the /project/wssource directory. The generated class files go into the
/project/ejbbuild directory. They need to be there so the MDB can use them.
Next the compileejb ant target compiles the MDB java file and places the resulting class file into the
/project/ejbbuild directory.
Next the buildejbjar ant target takes everything in the /project/ejbbuild directory and creates the ejb jar
file that will be included in the EAR. This file is placed in the /project/earbuild directory.
Finally the buildear ant target takes everything in the /project/ejbbuild directory and produces the EAR
file for deployment. The EAR file is placed in the /project directory.
The deploy task simply copies the EAR file into the weblogic domain applications directory.

It's really the web service that determines what kind of authentication is required. You can't just use any old strategy. If the web service isn't expecting it in that form, it won't work. Typically, either HTTP BASIC Auth or WS-Security is used. You'd have to contact the people responsible for the web service to know what kind of auth it requires.

Where shall i save the jar file when i'm using a parser(JDOM) in jwsdp

I'm using jwsdp These errors are coming
when i compile.where shall i save the jdom.jar file?
do i have to change the server.xml file in jwsdp-1_0\conf directory ?
import org.w3c.dom.*;
^
MetaBuilder.java:4: cannot resolve symbol
symbol : class DocumentImpl
location: package dom
import org.apache.xerces.dom.DocumentImpl;
^
MetaBuilder.java:5: cannot resolve symbol
symbol : class DOMImplementationImpl
location: package dom
import org.apache.xerces.dom.DOMImplementationI
^
MetaBuilder.java:6: cannot resolve symbol
symbol : class Document
location: package dom
import org.w3c.dom.Document;
^
MetaBuilder.java:7: cannot resolve symbol
symbol : class OutputFormat
location: package serialize
import org.apache.xml.serialize.OutputFormat;
^
MetaBuilder.java:8: cannot resolve symbol
symbol : class Serializer
location: package serialize
import org.apache.xml.serialize.Serializer;
^
MetaBuilder.java:9: cannot resolve symbol

Hello,
the *.jar file thing is a common problem in Java. One simple solution to the problem is by saving the *.jar file in the C:\j2sdk1.4.0\jre\lib\ext\ folder. This directory is an extension to the regular java files and by doing this, java will look in this directory if you import some other files not included in the java package. This does not work if you are using JBuilder, couse JBuilder installs its own jsdk, which is uses, probably under the JBuilder folder.
TheLaw

Error message when using xrpcc in JWSDP 1_0_01

Dear all,
I've got the following error message when using xrpcc of JWSDP 1_0_01 for my config.xml file.
D:\jwsdp-1_0_01\Message>xrpcc -classpath build -both -d build config.xml
error: invalid element "{http://java.sun.com/jax-rpc-ri/xrpcc-config}configurati
on" in configuration file (line 2)
The content of 'config.xml' is shown as follows.
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://java.sun.com/jax-rpc-ri/xrpcc-config">
<rmi name="MessageService"
targetNamespace="http://messageuri.com/wsdl"
typeNamespace="http://messageuri/types">
<service name="MyMessage" packageName="Message">
<interface name="Message.MessageIF"
servantName="Message.MessageImpl"/>
</service>
</rmi>
</configuration>
Thank you for your kind attention!
Regards,
Eddie

Thanks all! I've already solved my previous problem, however, i got another one now.
=========================================================
error: unknown model info in configuration file (line 5)
=========================================================
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<rmi name="MessageService"
targetNamespace="http://messageuri.com/wsdl"
typeNamespace="http://messageuri.com/types">
<service name="MyMessage" packageName="Message">
<interface name="Message.MessageIF"
servantName="Message.MessageImpl" />
</service>
</rmi>
</configuration>
Thanks,
Eddie

Install error JWSDP 2.0 in linux 2.6.9-55.ELsmp

Hi All,
I m trying to install JWSDP 2.0 but i am getting the follwoing error:
[root@pc25 ~]# /home/jimmy/soap/jwsdp-2_0-unix.sh
For help, type '/home/jimmy/soap/jwsdp-2_0-unix.sh -help'
Using /var/tmp as temporary directory...
Searching for Java(TM) 2 Platform, Standard Edition...
Initializing InstallShield Wizard...
Exception in thread "main" java.lang.NoClassDefFoundError: JWSDP
Caused by: java.lang.ClassNotFoundException: JWSDP
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
Could not find the main class: JWSDP. Program will exit.
[root@pc25 ~]#
same error is there when i try from other user.
The linux version i m using is 2.6.9-55.ELsmp
and java installed is
[root@pc25 ~]# uname -r
2.6.9-55.ELsmp
[root@pc25 ~]# java -version
java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode)
[root@pc25 ~]#
i have installed Java 2 Platform Second Edition also in /opt/SDK path
but and this service is running.
from some searching i tried to
Here is a work-around for installing JWSDP 2.0:
1) Make a copy of the JWSDP shell script (as a backup);
2) Edit the JWSDP shell-script with a text-editor like vi, emacs, etc.
3) Find the section that defines the cleanup() function:
4) Comment out the line that removes the jarfile; when correctly done, it should look like this:
Code:
# Cleanup function
cleanup() {
rm -f "$listfile"
rm -f "$outputfile"
#rm -f "$jarfile"
rm -f "$tmp_error_log"
if [ -n "$1" ]; then
exit "$1"
else
exit 0
fi
5) Save the file and execute the shell script; you will continue to get the same error, but ignore it;
6) The execution will have now left behind a jwsdp-2_0-unix.sh.4032.jar file in the /tmp or /usr/tmp directory (the number - 4032 - will vary for you based on the PID your process used for execution); go to that directory;
7) Extract all contents of the jar file with jar xvf jwsdp-2_0-unix.sh.4032.jar;
8.) Run the JWSDP class directly with java -cp . JWSDP
9) You should see the installation window now; if it does not work in GUI mode, use "java -cp . JWSDP -console" to install in ASCII text-mode.
10) Because of another bug in the text scripts, don't just press the Enter key for default answers when you see the prompt; type in the answer even if it is the same as the default and then press Enter - this will ensure the script sees the input and continues installation instead of silently exiting (which occurred to us many time on Gentoo).
Still i m not able to move ahead to complete the installation,
Please help me.

Submitted On 04-MAY-2007
exaid6
Further investigation reveals that if I unpack the jar file in a directory (jar xvf xxxx.jar) and change the classpath to "." instead of the jarfile, the program launches perfectly. This is definintely a bug in the classpath handling of big jar files on certain systems, or something of that sort. (Note: I'm using java sdk 6u1, 32 bit CentOS Linux.)
Submitted On 27-SEP-2007
I've encountered the same problem on RH FC6.
If you take a look at the script you will see this line tail +368 "$0" which attempts to extract the remaining lines into a separate jar file. This line may not work on all versions of Linux. A proper way to use Linux version of tail utility is: tail -n +368 "$0". Anyways, you can manually extract the jar file if you are getting tail +368 file not found error message when running the script.
After you extract the jar file you can run it via the command line like so
java -classpath .:./tmp/jwsdp.jar -Djava.ext.dirs= -D.java.endorsed.dirs= -Dtemp.dir=/opt/java/jwsdp/tmp -Dis.debug=1 JWSDP
You should be able to install JWSDP 2.0 successfully on your Linux machine.

JWSDP and J2EE Integration: Doesn't work. What's the point?

My problems involve the integration of JWSDP and J2EE as described in these two documents:
http://developer.java.sun.com/developer/technicalArticles/WebServices/wsj2ee/
http://java.sun.com/j2ee/documentation/windows_guide.html
It looks like a long one, but it�s really not that bad. All comments are appreciated.
I�ve numbered each line-paragraph-section for easy reference later.
(1) My ultimate goal is to setup a website that displays data from a database. I will use Java, Apache, Oracle, and whatever else I need to create a website that uses servlets, JavaServer Pages (JSP), and JDBC.
(2) I�ve got four Pentium III computers:
1. Windows 2000 Server to be the web server (MyWebServer, IP = 10.10.1.1).
2. Windows 2000 Professional to be the database server (MyDatabaseServer, IP = 10.10.1.2).
3. Windows 2000 Professional that I use to develop and test (MyDeveloperPC, IP = 10.10.1.3).
4. Windows 2000 Professional that I use as a client to connect to the website (MyClientPC, IP = 10.10.1.4).
(3) On MyWebServer I installed the following:
Java 2 Standard Edition (J2SE)
Java 2 Enterprise Edition (J2EE)
Java Web Services Developer Pack (JWSDP)
The JWSDP tutorial
Apache HTTP Server
(4) The files I downloaded and installed are as follows:
j2sdk-1_4_0-rc-win.exe
j2sdkee-1_3_1-win.exe
jwsdp-1_0-ea1-win.exe
jwsdp-1_0-ea1_01-tutorial.zip
apache_1.3.23-win32-x86-no_src.exe
(5) After installing these products, I set the environment variables as follows:
JAVA_HOME = c:\j2se
J2EE_HOME = c:\j2ee
JWSDP_HOME = c:\jwsdp
Path = c:\j2se\bin;c:\j2ee\bin;c:\jwsdp\bin; [and other previous statements]
(6) I checked to see that Apache is running as a service. It is.
On MyWebServer I start Tomcat and J2EE. Both start properly and are operating simultaneously.
(7) From MyClientPC I open Internet Explorer and in the address box I type:
http://10.10.1.1
This displays the page c:\ApacheHTTP\apache\htdocs\index.html.en (The Apache default server installation page.)
(8) I then enter this address in IE:
http://10.10.1.1:8080
This displays the page c:\jwsdp\webapps\root\index.html (The default JWSDP page).
(9) I then enter this address in IE:
http://10.10.1.1:8000
This displays the page c:\j2ee\public_html\index.html (The J2EE 1.3 Default Home Page).
(10) So far so good. Now I want to test JWSDP as a container for JSP pages.
(11) I use ant to build the converter app found in the tutorial examples (in folder c:\jwsdp\�\tutorial\examples\gs). I then deploy the converter app to the c:\jwsdp\webapps\gs folder.
(12) From MyClientPC I open Internet Explorer and in the address box I type:
http://10.10.1.1:8080/gs
The converter app works perfectly.
(13) To eliminate the need to enter the port number, I create a link from the Apache default server installation page to the converter app. From MyClientPC and enter this address into IE:
http://10.10.1.1
I then click on the link to the converter app and it works perfectly.
(14) Question: Is this the best way to display JSP pages without having to enter the port number?
(15) Now it�s time to integrate JWSDP and J2EE as described in these two documents:
http://developer.java.sun.com/developer/technicalArticles/WebServices/wsj2ee/
http://java.sun.com/j2ee/documentation/windows_guide.html
(16) After I complete this integration I cannot start both Tomcat and J2EE at the same time. This makes sense because they both share port 8080.
I start Tomcat.
(17) From MyClientPC and use Internet Explorer to test the various relevant addresses. Everything works the same as it did before except this one:
http://10.10.1.1:8000
The page cannot be displayed. The J2EE default home page is not displayed, which makes sense because the J2EE port is no longer 8000; it has been changed to 8080.
(18) Now I shutdown Tomcat and start J2EE.
From MyClientPC and use Internet Explorer to test the various relevant addresses:
(19) http://10.10.1.1:8080
Displays the JWSDP default home page.
(20) http://10.10.1.1:8080/gs
The page cannot be displayed. The converter app no longer works.
(21) From MyWebServer and use Internet Explorer to test localhost:
http://localhost:8080
This displays the J2EE default home page.
(22) Question: Why does localhost give me a different page than the IP address?
(23) Question: What was the point of integrating JWSDP and J2EE?
(24) I want to get the converter app working, so I create a .war file and attempt to add it to the J2EE deploytool (see the two integration documents listed above at section 15.) I create the .war file following the instructions in the JWSDP tutorial:
http://java.sun.com/webservices/docs/ea1/tutorial/doc/WebApp3.html#64606
(25) I change to the c:\jwsdp\�\tutorial\examples\gs\build folder.
I then type:
jar cvf converter.war .
A .war file is created.
(26) I open the deploytool: File, New, Application, and I name it �converter�.
I attempt to add the .war file: File, Add to Application, Web WAR.
(27) When I attempt to add the converter.war file I get this error:
�converter.war does not appear to be a valid web JAR.�
I tried a few different attempts, all with the same result. I�m stuck.
(28) I ask again, What was the point of integrating JWSDP and J2EE?
(29) If this is the preferred configuration, how do I display my JSP pages like the converter app?
Please help!!!

The JWSDP tutorial says to be in the �build� folder of the example when issuing the jar command to create the .war file. The build folder is created when I run the �ant build� command.
Attempt 1 from the command prompt in folder c:\jwsdp\tutorial\examples\gs\build>
I typed this command:
jar cvf c:\jaxmservices\converter.war .
In this case I directed the .war file to be placed in a different folder as you suggested. Here�s the output:
added manifest
adding: index.jsp(in = 921) (out= 525)(deflated 42%)
adding: WEB-INF/(in = 0) (out= 0)(stored 0%)
adding: WEB-INF/classes/(in = 0) (out= 0)(stored 0%)
adding: WEB-INF/classes/Converter.class(in = 582) (out= 358)(deflated 38%)
Didn�t work. Same error as before.
Attempt 2 from the same folder:
I typed this command as you suggested (I tried it with and without the final dot):
jar tvf converter.war
Here is the output:
java.io.FileNotFoundException: converter.war (The system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at sun.tools.jar.Main.run(Main.java:185)
at sun.tools.jar.Main.main(Main.java:904)
I tried a few other variations on these attempts with no luck. I�m stuck.
I�m attempting to create a .war file out of two files: index.jsp and converter.class.
Now that I�ve integrated JWSDP and J2EE, is there some other way that I can run the converter app instead of a .war file and the deploytool? In other words, if I go back to using ant to build and deploy converter, where would I deploy it so that it will work with J2EE?
By the way, it doesn�t have to be converter. I�d be happy if I could get any JSP page to work in J2EE after the integration.
Forever grateful,
Logan

Error in deploying cardemo.war in JWSDP?

To run cardemo example i copy cardemo.war to webapps folder in my jwsdp home, but the example can run. I see the log file jwsdp_log.2003-03-13.txt, the following is the error message about loading cardemo.war:
2003-03-13 12:14:49 HostConfig[localhost]: Deploying web application archive cardemo.war
2003-03-13 12:14:49 StandardHost[localhost]: Installing web application at context path /cardemo from URL jar:file:D:\jwsdp-1.1\webapps\cardemo.war!/
2003-03-13 12:14:49 WebappLoader[cardemo]: Deploying class repositories to work directory D:\jwsdp-1.1\work\Standard Engine\localhost\cardemo
2003-03-13 12:14:49 WebappLoader[cardemo]: Deploy class files /WEB-INF/classes to D:\jwsdp-1.1\work\Standard Engine\localhost\cardemo\WEB-INF\classes
2003-03-13 12:14:49 WebappLoader[cardemo]: Deploy JAR /WEB-INF/lib/commons-beanutils.jar to D:\jwsdp-1.1\work\Standard Engine\localhost\cardemo\WEB-INF\lib\commons-beanutils.jar
2003-03-13 12:14:49 WebappLoader[cardemo]: Deploy JAR /WEB-INF/lib/commons-collections.jar to D:\jwsdp-1.1\work\Standard Engine\localhost\cardemo\WEB-INF\lib\commons-collections.jar
2003-03-13 12:14:49 WebappLoader[cardemo]: Deploy JAR /WEB-INF/lib/commons-digester.jar to D:\jwsdp-1.1\work\Standard Engine\localhost\cardemo\WEB-INF\lib\commons-digester.jar
2003-03-13 12:14:49 WebappLoader[cardemo]: Deploy JAR /WEB-INF/lib/commons-logging.jar to D:\jwsdp-1.1\work\Standard Engine\localhost\cardemo\WEB-INF\lib\commons-logging.jar
2003-03-13 12:14:49 WebappLoader[cardemo]: Deploy JAR /WEB-INF/lib/demo-components.jar to D:\jwsdp-1.1\work\Standard Engine\localhost\cardemo\WEB-INF\lib\demo-components.jar
2003-03-13 12:14:49 WebappLoader[cardemo]: Deploy JAR /WEB-INF/lib/jsf-api.jar to D:\jwsdp-1.1\work\Standard Engine\localhost\cardemo\WEB-INF\lib\jsf-api.jar
2003-03-13 12:14:49 WebappLoader[cardemo]: Deploy JAR /WEB-INF/lib/jsf-ri.jar to D:\jwsdp-1.1\work\Standard Engine\localhost\cardemo\WEB-INF\lib\jsf-ri.jar
2003-03-13 12:14:49 WebappLoader[cardemo]: Deploy JAR /WEB-INF/lib/jstl.jar to D:\jwsdp-1.1\work\Standard Engine\localhost\cardemo\WEB-INF\lib\jstl.jar
2003-03-13 12:14:49 WebappLoader[cardemo]: Deploy JAR /WEB-INF/lib/jstl_el.jar to D:\jwsdp-1.1\work\Standard Engine\localhost\cardemo\WEB-INF\lib\jstl_el.jar
2003-03-13 12:14:49 WebappLoader[cardemo]: Deploy JAR /WEB-INF/lib/standard.jar to D:\jwsdp-1.1\work\Standard Engine\localhost\cardemo\WEB-INF\lib\standard.jar
2003-03-13 12:14:49 StandardManager[cardemo]: Seeding random number generator class java.security.SecureRandom
2003-03-13 12:14:49 StandardManager[cardemo]: Seeding of random number generator has been completed
2003-03-13 12:14:50 StandardContext[cardemo]: Exception sending context initialized event to listener instance of class cardemo.CarDemoServletContextListener
javax.faces.FacesException: com.sun.faces.renderkit.RenderKitFactoryImpl
     at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:301)
     at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:214)
     at cardemo.CarDemoServletContextListener.contextInitialized(Unknown Source)
     at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3202)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:3476)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:821)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579)
     at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:257)
     at org.apache.catalina.core.StandardHost.install(StandardHost.java:773)
     at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:516)
     at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:410)
     at org.apache.catalina.startup.HostConfig.start(HostConfig.java:882)
     at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:368)
     at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1198)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:739)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1190)
     at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347)
     at org.apache.catalina.core.StandardService.start(StandardService.java:499)
     at org.apache.catalina.core.StandardServer.start(StandardServer.java:2187)
     at org.apache.catalina.startup.Catalina.start(Catalina.java:504)
     at org.apache.catalina.startup.Catalina.execute(Catalina.java:399)
     at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
     at java.lang.reflect.Method.invoke(Native Method)
     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
     at java.lang.reflect.Method.invoke(Native Method)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
2003-03-13 12:14:50 StandardContext[cardemo]: Context startup failed due to previous errors

it was recommanded to work with JWSDP 1.0.01, maybe that is the reason.
http://java.sun.com/j2ee/javaserverfaces/docs/ReleaseNotes.html

Problem running car demo jwsdp-1.3,Tomcat 5.0

Hello. I am having problems running the car demo on the jwsdp-1.3 with Tomcat 5.0.
I get the following error message:
"A jar file containing the Servlet 2.3 and JSP1.2 classes is required to compile
carstore. Please define the property servlet.jar in your build.properties file and ensure
that the file exists."
I replaced the jsf EA 4 with the beta, and cleared out the cache in catalina as per the
installation documents. I am probably missing something here. I checked my path,
(I am using windows xp) and made sure the jsf directory was in the path.
Any help would be greatly appreciated. Thanks in advance.
regards,
cyuno

Thanks for your response.
I changed the path to the tomcat 5.0 that came with the jwsdp-1.3.
However, I am still getting the same error message. I have checked the build.properties file, the path, the path where ant is located, and the path is pointing to the jwsdp-1.3 directory.
I have been working with the examples in the java web services tutorial, and for the most part have not had any problems running the examples using the jwsdp-1.3, ant and tomcat 5.0(except for CH 11, on the jaxb examples)
Thanks again for your help
regards,
cy unpingco

Deploying JAXRPC service on NON-JWSDP Tomcat

Hi,
I saw a similar question earlier, but not an answer..
I'm in a situation where I want to deploy a JAXRPC service on a Tomcat 4.1.12. I use the JSWDP kit from Sun to develop and test, and then I would like to be able to package my service as a .war file and deploy in on a Tomcat 4.1.12 - and still be able to use it as when its deployed in the JWSDP Tomcat. That should not be a problem - right?!
Unfortunatly (for me) I can't make it work.....not even with the veeery simple JAXRPC hello example program included in the JWSDP tutorial.
Under the JWSDP Tomcat everything is fine..
Then I try to use the Tomcat 4.1.12: I copy the .war file to the /webapps directory and restarts Tomcat - it shows up in the Manager as deployed, but I can't create a communication to it from the client!! I get a RemoteException: "Cannot connect to server: /hello-jaxrpc/hello..".
Can someonegive me a pointer on this one??
Thanks in advance,
Kim Vestergaard

Hi again,
I did try for a few days without getting near to a solution.
Instead I started to look at the Apache Axis kit (http://xml.apache.org/axis) - In the latest version it includes support for JAXRPC, and thats what I need. The kit is easier (for me anyway ;-) to figure out, because it is not tight bundled with Tomcat as JWSDP is - Tomcat is still the servletengine-of-choice.
When I found http://www.javaworld.com/javaworld/jw-01-2002/jw-0125-axis-p3.html the installation and setup was straight forward. I now have Tomcat 4.1.12 / Axis 1.0 running my JAXRPC based webservice....
/Kim

Tomcat 5.0 and JWSDP

Hi Everyone,
We are looking into using the Tomcat 5.0 that works with the JWSDP as a container for our initial SOA Infrastructure, but I see in the release notes that this is NOT intended for production us, can anyone provide any insight into why the Tomcat is not production ready?
The reason we are looking into this is that my client who is using JBoss does not want to use JBossWS since it is not production ready. The JWSDP provides considerable value to us given it's features and we where thinking we could deploy the JWSDP version of tomcat into a production JBoss instance.
Any help or pointers appreciated.
Ernie

Hi,
Try to download stable Tomcat5.0.28 with the stable JWSDP.
I think Tomcat 5.0.28 is stable for the production release.
Cheers
Rajesh R

I am new with webservices. what platform should i use? wasp, glue, jwsdp .

hello i just study web services. i am very new of this. there
are many soap-based web services platform such as axis,
glue, wasp ,jwsdp etc. i don't know much about these
platform. what platform should i use in my project ? i use
java in my project. anyone have any recommend for me?
every recommend is important for me. thank you

If you're not currently involved with a web service project that is using a particular server (e.g., WebSphere, WebLogic, etc.), I suggest starting with Axis. Apache software tends to be adopted by other vendors as a basis for their products. Also, the Axis mailing lists are very active and you're more likely to get your questions answered quickly. Once you're comfortable with Axis, it's probably worthwhile to download the evaluation version of WebSphere or WebLogic to learn how to deploy web services on a commercial platform.
Good luck,
Mike W.

JWSDP 2.0 and SAAJ SOAP - envelope error

I've integrated JWSDP 2.0 SAAJ security into a J2EE servlet that sends and receives SAAJ SOAP. I have tested and verified all sample security configurations except encryptv1.xml and encryptv2.xml. My issues is that although I am able to encrypt messages within the servlet, I am unable to decrypt. I have a java client running on the command line that interacts with the servlet and it is able to encrypt and decrypt (actually decrypts the encrypted error response raised by the servlet). I am also able to get the client to interact (encrypt/decrypt) successfully with a simpler servlet on standalone tomcat. I am using jboss 4.0.3RC2 and jboss 4.0.4GA both with tomcat55 and java 5. The error I receive is as follows:
[STDOUT] ERROR: 'NOT_FOUND_ERR: An attempt is made to reference a node in a context where it does not exist.'
[STDOUT] Jun 5, 2006 12:16:13 PM com.sun.xml.messaging.saaj.soap.EnvelopeFactory createEnvelope
SEVERE: SAAJ0511: Unable to create envelope from given source
[STDOUT] Jun 5, 2006 12:16:13 PM com.sun.xml.wss.impl.SecurableSoapMessage findSoapHeader
SEVERE: WSS0369: Error getting SOAPHeader from SOAPEnvelope due to Unable to create envelope from given source:
[STDOUT] com.sun.xml.wss.XWSSecurityException: com.sun.xml.wss.XWSSecurityException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to create envelope from given source:
[STDOUT] at com.sun.xml.wss.impl.misc.XWSSProcessor2_0Impl.verifyInboundMessage(XWSSProcessor2_0Impl.java:115)
Any help will be greatly appreciated...

I figured it out! I needed to remove the Timestamp in the server config file.
Thanks

Does JWSDP 1.6 support STR transform?

Does anyone know whether JWSDP 1.6 supports STR transform? Thanks in advance for your help.

"http://www.w3.org/2001/12/soap-envelope" is a namespace from SOAP 1.2 working draft. The correct SOAP 1.2 namespace is "http://www.w3.org/2003/05/soap-envelope".
JWSDP 1.4 does not support SOAP 1.2 anyway.
-Arun

Jwsdp vs. Apache Tomcat

Hello,
I have installed Jwsdp and separately Tomcat 4.1.27 from apache.org
I compiled sample with name "date" from jwsdp.
When I run it in jwsdp (tomcat), everything OK.
But when I try to run it in Tomcat 4.1.27, I return this exception:
org.apache.jasper.JasperException: This absolute uri (http://java.sun.com/jsp/jstl/core) cannot be resolved in either web.xml or the jar files deployed with this application
I don't know where is problem...
thanx, miso

u need to copy all the jar files into your tomcat application web-inf/lib folder.
here's what i've done.
http://forum.java.sun.com/thread.jsp?forum=45&thread=456667&tstart=0&trange=15
if u're using only the standard jstl then it should work for u.
hth

JWSDP 1.2

Similar Messages

Maybe you are looking for