Jwsdp 1.2 & servlets

Hi all i recently have downloaded the jwsdp1.2 in order to try an application that is given to me.
first i found out that i could not compile the application because i needed the jaxm lib that was not provided with jwsdp1.2 done that and the thing is working. my questionis the following. I would like to refactor the application to use jwsdp1.2 what isthe equivalent of a JAXMServlet in jwsdp ?
are JAXMServlets supported in jwsdp1.2?
best regards
Billy Kantartzis

yes
http://java.sun.com/xml/jaxm/index.html

Similar Messages

  • Servlet not set in classpath

    I'm having the same problem with the servlet package not being accessable.
    I've tried to add the Creator/jwsdp/common/lib/servlet-api.jar to the classpath for all the compilers (external/internal/jikes etc.) but that does not seem to work.
    I've also tried to add Creator/jwsdp/common/lib/servlet-api.jar to my system classpath before launching the ide and still it does not work.
    help please

    Hi ,
    Place the jar file inside creator\java\jre\lib\ext directory.
    -Amol

  • Trying to create custom tag library

    I'm a novice trying to create a simple custom tag library application. As such I need a couple import statements like
    import javax.servlet.jsp.*;
    import javax.servlet.jsp.tagext;
    This statements will not compile. I'm using Java 2 1.4_03 and WSDP 1.3. My CLASSPATH currently holds
    c:\jwsdp\common\lib\servlet-api.jar
    and
    c:\j2sdk\lib\mysql-connector-java-3.0.11-stable-bin.jar.
    I've got JAVA_HOME set to c:\j2sdk and JWSDP_HOME set to c:\jwsdp.
    Thank you very much for any assistance you are able to render.

    Thanks for your reply. I'm using the TextPad editor, which uses CLASSPATH.
    I've figured out the answer. I needed to add
    c:\jwsdp\common\lib\jsp-api.jar
    to my CLASSPATH.
    Again, thanks.

  • JWSDP Tutorial - Servlet Example

    I am trying to run the bookstore example in the Servlet section of the JWSDP on Red Hat 7.3.I am also getting confused over ANT and the Tomcat Manager.
    I need to build the bookstore example and the instructions read: (for those who know the tutorial)
    1. In a terminal window, go to /docs/tutorial/examples/web/bookstore1
    2. Run ant build - The build target will spawn any necessary compilations and copy files to the docs/tutorial/examples/web/bookstore1/build directory.
    3. Make sure Tomcat is started.
    4. Run ant install - The install target notifies Tomcat that the new context is available.
    5. Start the Pointbase database server and populate the database if you have not done so already
    6. Open the bookstore URL http://localhost:8080/bookstore1/enter
    On the command line I can run ANT BUILD fine, but ANT INSTALL fails. (It also fails in Tomcat Manager...but not sure whether I can use this instead of ANT INSTALL?)
    I know this is sketchy but does anyone have any idea?
    Regards
    Scott

    Hi Scott,
    Thank you any way.
    Last time, I met it and carried the tutorial on by compiling and copying manually. Then, I came back to set the ant.jar into path&classpath, and it worked.(ant build)
    Today, I'm trying on "hello1" example, but can't get though.
    Maybe it's still classpath and path issue, as I can't compile two servlet classes by javac from command line, but from Forte, it passed.
    Cheers!
    Zhan

  • 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

  • Deploying servlet on Tomcat using "ant install" not working. Please help.

    Hello. Normally I can find answers by using search, but I can't today for some reason. So please bare with me if this has been mentioned before. I will try to provide as much info as possible so that helping me isn't too much a chore. Thank you.
    I have downloaded and installed the JWSDP 1.3. and Tomcat is running. I am also using Ant 1.5.4 (previous installation - not one included with JWSDP) and modeled my build.xml file after the template provided here:
    http://jakarta.apache.org/tomcat/tomcat-5.0-doc/appdev/build.xml.txt.
    When I run ant on my respository, everything builds fine. But when I run Ant with the install target, I get the following error:
    BUILD FAILED
    file:C:/owl/build.xml:366: java.io.IOException: Server returned HTTP response co
    de: 401 for URL: http://localhost:8080/manager/deploy?path=%2Fowl&war=file%3A%2F
    %2FC%3A%5Cowl%2Fbuild
    Here is line 366 build.xml:
    localWar="file://${build.home}"/>
    ...which is included in this block for the target "install":
    <target name="install" depends="compile"
    description="Install application to servlet container">
    <deploy url="${manager.url}"
    username="${manager.username}"
    password="${manager.password}"
    path="${app.path}"
    localWar="file://${build.home}"/>
    </target>
    When I point my brower to the url located in the error verbose, I get the following:
    FAIL - Encountered exception java.lang.NullPointerException
    I am trying to get my environment set up correctly before I start spending time developing servlets, but I am getting tempted to just develop to servlets and "manually" installing/deploying them either by copying and pasting or by using the Tomcat manager. I would really like to do everything from Ant though if possible. Please help.

    I don't think this is at all correct:
    localWar="file://${build.home}"/>You've got to create a real WAR file - a JAR file with WEB-INF and all its minions inside it:
    http://access1.sun.com/techarticles/simple.WAR.html
    That's the file you need to refer to there. You can manage that with Ant too, of course.
    Here's what my Ant build.xml looks like for Web apps (there's a build-web.properties file that follows):
    build-web.xml
    <project name="Tomcat Build Tasks" default="clean" basedir=".">
        <target name="init-props">
            <tstamp>
                <format property="touch.time" pattern="MM/dd/yyyy hh:mm aa" />
            </tstamp>
            <filterset id="ant.filters">
                <filter token="DATE" value="${TODAY}" />
                <filter token="TIME" value="${TSTAMP}" />
            </filterset>
            <!-- Load in all the settings in the properties file -->
            <property file="build.properties" />
            <!-- Load in all Tomcat settings in the properties file -->
            <property file="build-web.properties" />
        </target>
        <target name="prepare" depends="init-props">
            <mkdir dir="${war.classes}"/>
            <mkdir dir="${war.lib}"/>       
            <mkdir dir="${manifest}" />
        </target>
        <target name="clean" depends="init-props" description="clean up temporary files">
            <delete file="${project}.war" />   
            <delete dir="${war.root}"/>
            <delete dir="${manifest}" />
        </target>
        <target name="set-tomcat-classpath" depends="prepare">
            <path id="tomcat.class.path">                  
                <fileset dir="${tomcat.home}/bin">
                    <patternset>
                        <include name="**/*.jar" />
                    </patternset>
                </fileset>
                <fileset dir="${tomcat.home}/shared/lib">
                    <patternset>
                        <include name="**/*.jar" />
                    </patternset>
                </fileset>
                <fileset dir="${tomcat.home}/common/lib">
                    <patternset>
                        <include name="**/*.jar" />
                    </patternset>
                </fileset>
                <fileset dir="${tomcat.home}/server/lib">
                    <patternset>
                        <include name="**/*.jar" />
                    </patternset>
                </fileset>
                <fileset dir="${ant.home}/lib">
                    <patternset>
                        <include name="**/*.jar" />
                    </patternset>
                </fileset>
            </path>              
        </target>
        <target name="create" depends="set-tomcat-classpath" description="create the war file">
            <!-- All files at root level -->       
            <!-- Temporarily put the JSPs at root until you figure this out -->
            <copy todir="${war.root}">
                <fileset dir="${src.jsp}"/>
            </copy>
    <!--
            <copy todir="${war.root}">
                <fileset dir="${src.html}" includes="*.html"/>
            </copy>
    -->
            <copy todir="${war.root}/css">
                <fileset dir="${src.css}"/>
            </copy>
            <copy todir="${war.root}/images">
                <fileset dir="${src.images}"/>
            </copy>
            <copy todir="${war.root}/js">
                <fileset dir="${src.js}"/>
            </copy>
            <!-- All files at the WEB-INF level and below -->       
            <copy todir="${war.web}">
                <fileset dir="${src.etc}" includes="web.xml"/>
            </copy>
            <!-- All files in the CLASSPATH lib -->
            <copy todir="${war.web}/lib">
                <fileset dir="${src.lib}" includes="**/*.jar" excludes="**/*-tests.jar, **/junit.jar"/>
            </copy>
            <!-- Put the dispatcher XML in WEB-INF/config -->
            <copy todir="${war.web}/config">
                <fileset dir="${src.etc}" includes="${project}-config.xml"/>
            </copy>
            <!-- Put XSL stylesheets in WEB-INF/xsl -->
            <copy todir="${war.web}/xsl">
                <fileset dir="${src.xsl}" includes="**/*.xsl"/>
            </copy>
            <!-- Put the project JAR file in WEB-INF/lib -->
            <copy todir="${war.web}/lib">
                <fileset dir="${deploy}" includes="**/${project}.jar"/>
            </copy>
            <!-- Create the manifest -->
            <buildnumber />
            <manifest file="${manifest}/manifest.mf">
                <attribute name="Implementation-Title"      value="${project}" />
                <attribute name="Built-By"                  value="${user.name}"/>
                <attribute name="Build-Date"                value="${TODAY}" />
                <attribute name="Major-Version"             value="${major}" />
                <attribute name="Minor-Version"             value="${minor}" />
                <attribute name="Build-Number"              value="${build.number}" />
            </manifest>
            <!-- Create the WAR file -->
            <jar jarfile="${project}.war"
                 manifest="${manifest}/manifest.mf">
                <fileset dir="${war.root}"/>
                <metainf dir="${src.etc}" includes="context.xml"/>
            </jar>
        </target>
        <target name="create-tomcat-admin-tasks" depends="set-tomcat-classpath">
    <!--
            <pathconvert targetos="windows" refid="tomcat.class.path" property="converted.class.path" />
            <echo message="CLASSPATH: ${converted.class.path}" />
    -->       
            <taskdef name="install"     classname="org.apache.catalina.ant.InstallTask"     classpath="tomcat.class.path"/>
            <taskdef name="remove"      classname="org.apache.catalina.ant.RemoveTask"      classpath="tomcat.class.path"/>       
            <taskdef name="reload"      classname="org.apache.catalina.ant.ReloadTask"      classpath="tomcat.class.path"/>
            <taskdef name="deploy"      classname="org.apache.catalina.ant.DeployTask"      classpath="tomcat.class.path"/>       
            <taskdef name="undeploy"    classname="org.apache.catalina.ant.UndeployTask"    classpath="tomcat.class.path"/>       
            <taskdef name="start"       classname="org.apache.catalina.ant.StartTask"       classpath="tomcat.class.path"/>       
            <taskdef name="stop"        classname="org.apache.catalina.ant.StopTask"        classpath="tomcat.class.path"/>       
            <taskdef name="list"        classname="org.apache.catalina.ant.ListTask"        classpath="tomcat.class.path"/>       
            <taskdef name="resources"   classname="org.apache.catalina.ant.ResourcesTask"   classpath="tomcat.class.path"/>       
            <taskdef name="roles"       classname="org.apache.catalina.ant.RolesTask"       classpath="tomcat.class.path"/>
        </target>
        <target name="install" depends="create-tomcat-admin-tasks" description="install the war file on Tomcat">
            <install    url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}"
                        config="file:/${basedir}/${src.etc}/context.xml"
                        war="file:/${basedir}/${project}.war" />
        </target>
        <target name="remove" depends="create-tomcat-admin-tasks" description="remove the war file on Tomcat">
            <remove     url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}" />
        </target>
        <target name="reload" depends="create-tomcat-admin-tasks" description="reload the war file on Tomcat">
            <reload     url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}" />
        </target>
        <target name="deploy" depends="create-tomcat-admin-tasks" description="deploy the war file on Tomcat">
            <deploy    url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}"
                        config="file:/${basedir}/${src.etc}/context.xml"
                        war="file:/${basedir}/${project}.war" />
        </target>
        <target name="undeploy" depends="create-tomcat-admin-tasks" description="undeploy the war file on Tomcat">
            <undeploy   url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}" />
        </target>
        <target name="start" depends="create-tomcat-admin-tasks" description="start an application on Tomcat">
            <start      url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}"/>
        </target>
        <target name="stop" depends="create-tomcat-admin-tasks" description="stop an application on Tomcat">
            <stop       url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}" />
        </target>
        <target name="list" depends="create-tomcat-admin-tasks" description="list all applications running on Tomcat">
            <list       url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"/>
        </target>
        <target name="resources" depends="create-tomcat-admin-tasks" description="list all resources on Tomcat">
            <resources  url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"/>
        </target>
        <target name="data-sources" depends="create-tomcat-admin-tasks" description="list all data sources on Tomcat">
            <resources  url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        type="javax.sql.DataSource"/>
        </target>
        <target name="roles" depends="create-tomcat-admin-tasks" description="list all user roles on Tomcat">
            <roles      url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"/>
        </target>
    </project>
    build.properties
    # Properties file for setting up an Ant build.xml
    # Project specific items that change each time
    project=api-prototype
    major=1
    minor=0
    version=${major}.${minor}
    jar.name=${project}
    versiondate=${TODAY}
    # Directory structure (these should never change)
    bin=bin
    deploy=deploy
    doc=doc
    manifest=META-INF
    xml=xml
    # Everything under src should come out of a repository
    src=src
    src.bin=${src}/bin
    src.config=${src}/config
    src.data=${src}/data
    src.dtd=${src}/dtd
    src.java=${src}/java
    src.lib=${src}/lib
    src.profile=${src}/profile
    src.properties=${src}/properties
    src.schema=${src}/schema
    src.sql=${src}/sql
    src.templates=${src}/templates
    src.testdata=${src}/testdata
    src.xml=${src}/xml
    src.xsl=${src}/xsl
    # These are created and deleted by Ant each time
    javadocs=javadocs
    reports=reports
    output=output
    output.classes=${output}/classes
    output.lib=${output}/lib
    # Required for proper use of XDoclet
    xdoclet.home = C:/Tools/xdoclet-1.2b3
    build-web.properties
    war.root=war-root
    war.pages=${war.root}/pages
    war.web=${war.root}/WEB-INF
    war.classes=${war.web}/classes
    war.css=${war.web}/css
    war.js=${war.web}/js
    war.lib=${war.web}/lib
    war.tld=${war.web}/tld
    # Properties needed by Tomcat tasks
    ant.home =
    tomcat.home         =
    tomcat.manager.url  = http://localhost:8080/manager
    tomcat.username     =
    tomcat.password     = MOD

  • 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

  • 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

  • XMLSignatureFactory fails in servlet, but works in a stand-alone program.

    Hi all,
    I am trying to write a servlet which will do XML signature et al. For the same, I am using JWSDP 2.0 (Java WebServices Developers Pack) on JRE 1.4.2_5. The servlet is hosted on SAP Netweaver 7 platform on Windows.
    I am getting an exception:
    javax.xml.crypto.NoSuchMechanismException: Cannot find DOM mechanism type
    in the "XMLSignatureFactory.getInstance" line. I looked up in the documentation of XMLSignatureFactory and it says that the DOM mechanism should be provided by the provider argument -  org.jcp.xml.dsig.internal.dom.XMLDSigRI in this case.
    import javax.xml.crypto.dsig.XMLSignatureFactory;
    XMLSignatureFactory sigFactory =
    XMLSignatureFactory.getInstance("DOM", new org.jcp.xml.dsig.internal.dom.XMLDSigRI());
    I tried the above 2 lines in a stand-alone Java client and they work without any issues.
    I also used JWSDP 1.5 and the result was same.
    This means that the servlet API or container for SAP is creating some issues to make this fail.
    I tried to add the "org.jcp.xml.dsig.internal.dom.XMLDSigRI" in the jre/lib/security/java.security, but then the server0 does not start-up.
    Any hints/pointers to resolve this issue?
    Thanks in advance.

    This problem is solved. I am putting the reply here so that others who stumble upon this error can benefit.
    Add the following line to explicitly include the provider before the getInstance
    Security.addProvider(new org.jcp.xml.dsig.internal.dom.XMLDSigRI());
    XMLSignatureFactory sigFactory =
    XMLSignatureFactory.getInstance("DOM", new org.jcp.xml.dsig.internal.dom.XMLDSigRI());

  • Servlet as a client to the web-service

    Hi all, I am new to this field of developing web services.
    I have designed a simple web service, that provides some lookup and search operation. I have developed the web service using JWSDP 1.5.0, Tomcat 5.0 and jdk1.5.0_03. I have also developed client applications using the wscomp and ant tools and they are working fine. The applications talk to the web service after I type in the command ant run-client on the command prompt.
    Now, I have to develop a servlet which will be the clients to the web service. How do I do that?

    By reading a tutorial about servlets maybe?

  • Jwsdp: after more than one day live the server send a socket exception.

    Hello,
    I built a beginning of an application using bookstore2 as a template. The main difference is that I am using mysql DBMS. The application runs fine, but when I leave the server running overnight, the following day I get this error:
    Your request cannot be completed. The server got the following error:
    Communication link failure: java.net.SocketException
    every time I use a jsp involved in the database access. The other jsps like cart checking are working fine.
    I checked the database server (even thru a socket), it works fine and worse, manager: a context not depending on the database doesn't work anymore when I try to use ant reload I get this error:
    /home/jeanct/jwsdp/dvl/dciweb/build.xml:62: java.io.IOException: Server returned HTTP response code: 401 for URL: http://localhost:8080/manager/reload?path=%2Fdciweb
    After a server shutdown and a startup it works fine again.
    Thank you if you can give me any clue
    Jean-Claude Tebbal
    Senior Analyst progammer
    DCI ltd UK
    PS:
    here follow the application context an logs:
    Property Value
    JNDI Name: Localwebdb
    Data Source URL: jdbc:mysql://localhost:3306/dciweb
    JDBC Driver Class: org.gjt.mm.mysql.Driver
    User Name: root
    Password: *********
    Max. Active Connections: 4
    Max. Idle Connections: 2
    Max. Wait for Connection: 5000
    context.xml
    <Context path="/dciweb" docBase="../dvl/dciweb/build" debug="0">
    <ResourceLink name="jdbc/dciweb" global="Localwebdb" />
    </Context>
    logs:
    access_log.2002-10-16.txt:
    127.0.0.1 - - [16/Oct/2002:09:56:40 00] "GET /dciweb/ HTTP/1.1" 302 -
    127.0.0.1 - - [16/Oct/2002:09:56:42 00] "GET /dciweb/index.jsp HTTP/1.1" 200 -
    127.0.0.1 - - [16/Oct/2002:09:56:42 00] "GET /dciweb/browser_checker.js HTTP/1.1" 304 -
    127.0.0.1 - - [16/Oct/2002:09:56:42 00] "GET /dciweb/start.jsp?browser=ok HTTP/1.1" 200 -
    127.0.0.1 - - [16/Oct/2002:09:56:50 00] "GET /dciweb/offerlist.jsp HTTP/1.1" 200 -
    catalina.out:
    DbcpDataSourceFactory: driverClassName=com.informix.jdbc.IfxDriver, url=jdbc:informix-sqli://bti:3003/cell:INFORMIXSERVER=sh_bti, use
    r=informix
    DbcpDataSourceFactory: driverClassName=org.gjt.mm.mysql.Driver, url=jdbc:mysql://localhost:3306/dciweb, user=root
    Starting service Internal Services
    Java Web Services Developer Pack/1.0_01-fcs
    Starting service Java Web Services Developer Pack
    Java Web Services Developer Pack/1.0_01-fcs
    jwsdp_log.2002-10-16.txt:
    2002-10-16 09:24:34 jsp: init
    2002-10-16 09:30:51 jsp: init
    2002-10-16 09:56:42 jsp: init
    2002-10-16 09:56:50 jsp: init
    localhost_admin_log.2002-10-16.txt:
    2002-10-16 09:49:29 jsp: init
    2002-10-16 09:49:37 jsp: init
    2002-10-16 09:49:52 jsp: init
    2002-10-16 09:49:54 jsp: init
    2002-10-16 09:49:55 jsp: init
    2002-10-16 09:49:59 jsp: init
    2002-10-16 09:50:02 action: Entered TreeControlTestAction:perform()
    2002-10-16 09:50:02 action: tree param is null
    2002-10-16 09:50:02 action: Select event on Globally Administer Data Sources
    2002-10-16 09:50:03 jsp: init
    2002-10-16 09:50:11 jsp: init
    services_log.2002-10-15.txt:
    2002-10-15 13:26:43 WebappLoader[jaxm-provideradmin]: Deploying class repositories to work directory /home/jeanct/jwsdp/work/Services
    Engine/jwsdp-services/jaxm-provideradmin
    2002-10-15 13:26:43 WebappLoader[jaxm-provideradmin]: Deploy class files /WEB-INF/classes to /home/jeanct/jwsdp/services/jaxm-provide
    radmin/WEB-INF/classes
    2002-10-15 13:26:43 WebappLoader[jaxm-provideradmin]: Deploy JAR /WEB-INF/lib/provider.jar to /home/jeanct/jwsdp/services/jaxm-provid
    eradmin/WEB-INF/lib/provider.jar
    2002-10-15 13:26:43 WebappLoader[jaxm-provideradmin]: Deploy JAR /WEB-INF/lib/struts.jar to /home/jeanct/jwsdp/services/jaxm-provider
    admin/WEB-INF/lib/struts.jar
    2002-10-15 13:26:45 ContextConfig[jaxm-provideradmin]: WARNING: Security role name provider used in an <auth-constraint> without bein
    g defined in a <security-role>
    2002-10-15 13:26:47 ContextConfig[jaxm-provideradmin]: Configured an authenticator for method BASIC
    2002-10-15 13:26:47 StandardManager[jaxm-provideradmin]: Seeding random number generator class java.security.SecureRandom
    2002-10-15 13:26:47 StandardManager[jaxm-provideradmin]: Seeding of random number generator has been completed
    2002-10-15 13:26:47 StandardWrapper[jaxm-provideradmin:default]: Loading container servlet default
    2002-10-15 13:26:47 default: init
    2002-10-15 13:26:47 StandardWrapper[jaxm-provideradmin:invoker]: Loading container servlet invoker
    2002-10-15 13:26:47 invoker: init
    2002-10-15 13:26:47 action: init
    2002-10-15 13:26:49 jsp: init
    2002-10-15 13:26:52 WebappLoader[jaxm-provider]: Deploying class repositories to work directory /home/jeanct/jwsdp/work/Services Engi
    ne/jwsdp-services/jaxm-provider
    2002-10-15 13:26:52 WebappLoader[jaxm-provider]: Deploy JAR /WEB-INF/lib/provider.jar to /home/jeanct/jwsdp/services/jaxm-provider/WE
    B-INF/lib/provider.jar
    2002-10-15 13:26:53 StandardManager[jaxm-provider]: Seeding random number generator class java.security.SecureRandom
    2002-10-15 13:26:53 StandardManager[jaxm-provider]: Seeding of random number generator has been completed
    2002-10-15 13:26:53 providerservlet: init
    2002-10-15 13:26:54 StandardWrapper[jaxm-provider:default]: Loading container servlet default
    2002-10-15 13:26:54 default: init
    2002-10-15 13:26:54 StandardWrapper[jaxm-provider:invoker]: Loading container servlet invoker
    2002-10-15 13:26:54 invoker: init
    2002-10-15 13:26:54 receiverservlet: init
    2002-10-15 13:26:54 jsp: init
    2002-10-15 13:26:54 digest: init

    I found the answer to my question, I give it here for those using mysql as a DBMS.
    Two variables in MySql have to be tuned: INTERACTIVE_TIMEOUT and WAIT_TIMEOUT. They default to 8 hours, so after 8 hours the two remaining idle connections were killed
    and a socket exception was thrown to the first use of the connection pool.

  • WL 8.1 and JAX-RPC 1.1 (JWSDP 1.3) problems

    I have developed several web services using Sun's JWSDP 1.3. It deploys just fine
    in WebLogic 8.1 and I can view the WSDL, etc. with no problems. I have written
    a simple test client to call the service and this is where I get errors.
    The server error is:
    Apr 14, 2004 9:43:00 AM com.sun.xml.rpc.server.http.JAXRPCServletDelegate doPost
    SEVERE: caught throwable
    java.lang.NoSuchMethodError: javax.xml.soap.SOAPElement.normalize()V
    at com.sun.xml.rpc.streaming.XmlTreeReader.parse(XmlTreeReader.java:129)
    at com.sun.xml.rpc.streaming.XmlTreeReader.next(XmlTreeReader.java:100)
    at com.sun.xml.rpc.streaming.XMLReaderBase.nextContent(XMLReaderBase.jav
    a:24)
    at com.sun.xml.rpc.streaming.XMLReaderBase.nextElementContent(XMLReaderB
    ase.java:42)
    at com.sun.xml.rpc.server.StreamingHandler.handle(StreamingHandler.java:
    108)
    at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doPost(JAXRPCServle
    tDelegate.java:316)
    at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:6
    9)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
    (ServletStubImpl.java:971)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:402)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:305)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
    n.run(WebAppServletContext.java:6350)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
    rvletContext.java:3635)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
    pl.java:2585)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    The client error is:
    java.rmi.ServerException: JAXRPC.JAXRPCSERVLET.28: Missing port information
         at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:372)
         at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:224)
         at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:61)
         at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:339)
         at com.sun.xml.rpc.client.dii.CallInvocationHandler.doCall(CallInvocationHandler.java:99)
         at com.sun.xml.rpc.client.dii.CallInvocationHandler.invoke(CallInvocationHandler.java:71)
         at $Proxy0.getWorkList(Unknown Source)
         at com.workpoint.sample.client.webservices.WorkItemServiceClient.testGetWorkList(WorkItemServiceClient.java:124)
         at com.workpoint.sample.client.webservices.WorkItemServiceClient.main(WorkItemServiceClient.java:48)
    I have a WAR for the web services that also includes the JAX-RPC, SAAJ, and other
    JARs. This WAR is bundled in an EAR with our other applications. Like I said,
    everything deploys just fine, it's at runtime the web services don't work. This
    configuration (and test client) works with Tomcat, JBoss, OC4J, and WebSphere
    with no problems. I've tried a bunch of different things and can't figure out
    why it doesn't work with WebLogic.
    Thanks for any help on this.
    Mike

    David,
    I tried your prefer-web-inf-classes and the web services deploy, but i get an
    error trying to view the wsdl. sounds like trying to get jax-rpc 1.1 web services
    running in weblogic is going to be nothing but problems. anyways, here's the error
    i get:
    Error 500--Internal Server Error
    javax.servlet.ServletException: JAXRPC.JAXRPCSERVLET.35: failed to create a template
    object
         at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doGetDefault(JAXRPCServletDelegate.java:258)
         at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doGet(JAXRPCServletDelegate.java:102)
         at com.sun.xml.rpc.server.http.JAXRPCServlet.doGet(JAXRPCServlet.java:76)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    "David Karr" <[email protected]> wrote:
    >
    This is happening because WLS already contains the JWSDP classes, but
    an older
    release. The jars in your web applications are not used if other jars
    containing
    those classes are found first.
    Technically, you should be able to set the "prefer-web-inf-classes" parameter
    in your weblogic.xml file to make it "prefer" classes found in WEB-INF.
    There's
    one not very well documented aspect of this that would be a problem for
    trying
    to override particular classes, but it shouldn't be a problem for your
    case. The
    issue is that the ClassLoader that ends up being used if you set "prefer-web-inf-classes"
    (it might not be a different ClassLoader, but just imbued with modified
    behavior)
    actually does not allow classes in certain packages to be overridden.
    I can't
    remember all of the paths, but I do know that anything in "javax.xml.*"
    is specifically
    ALLOWED to be overridden.
    However, when I went down this path a while ago, I ran into other more
    obscure
    exceptions that i was unable to figure out. I ended up concluding that
    using the
    JWSDP included with WLS 8.1 was the path of least resistance. I never
    did try
    altering the global classpath of the appserver to include the jwsdp 1.3
    jars to
    override the classes in weblogic. This is another alternate approach,
    but I have
    a feeling that this will cause other unexpected problems.
    "Mike" <[email protected]> wrote:
    I have developed several web services using Sun's JWSDP 1.3. It deploys
    just fine
    in WebLogic 8.1 and I can view the WSDL, etc. with no problems. I have
    written
    a simple test client to call the service and this is where I get errors.
    The server error is:
    Apr 14, 2004 9:43:00 AM com.sun.xml.rpc.server.http.JAXRPCServletDelegate
    doPost
    SEVERE: caught throwable
    java.lang.NoSuchMethodError: javax.xml.soap.SOAPElement.normalize()V
    at com.sun.xml.rpc.streaming.XmlTreeReader.parse(XmlTreeReader.java:129)
    at com.sun.xml.rpc.streaming.XmlTreeReader.next(XmlTreeReader.java:100)
    at com.sun.xml.rpc.streaming.XMLReaderBase.nextContent(XMLReaderBase.jav
    a:24)
    at com.sun.xml.rpc.streaming.XMLReaderBase.nextElementContent(XMLReaderB
    ase.java:42)
    at com.sun.xml.rpc.server.StreamingHandler.handle(StreamingHandler.java:
    108)
    at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doPost(JAXRPCServle
    tDelegate.java:316)
    at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:6
    9)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
    (ServletStubImpl.java:971)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:402)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:305)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
    n.run(WebAppServletContext.java:6350)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
    rvletContext.java:3635)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
    pl.java:2585)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    The client error is:
    java.rmi.ServerException: JAXRPC.JAXRPCSERVLET.28: Missing port information
         at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:372)
         at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:224)
         at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:61)
         at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:339)
         at com.sun.xml.rpc.client.dii.CallInvocationHandler.doCall(CallInvocationHandler.java:99)
         at com.sun.xml.rpc.client.dii.CallInvocationHandler.invoke(CallInvocationHandler.java:71)
         at $Proxy0.getWorkList(Unknown Source)
         at com.workpoint.sample.client.webservices.WorkItemServiceClient.testGetWorkList(WorkItemServiceClient.java:124)
         at com.workpoint.sample.client.webservices.WorkItemServiceClient.main(WorkItemServiceClient.java:48)
    I have a WAR for the web services that also includes the JAX-RPC, SAAJ,
    and other
    JARs. This WAR is bundled in an EAR with our other applications. Like
    I said,
    everything deploys just fine, it's at runtime the web services don't
    work. This
    configuration (and test client) works with Tomcat, JBoss, OC4J, andWebSphere
    with no problems. I've tried a bunch of different things and can't figure
    out
    why it doesn't work with WebLogic.
    Thanks for any help on this.
    Mike

  • WebService with JWSDP 2.0 doesn't work on Bea 9.1

    Hi,
    I have developed a WebService based on JAX-WS 2.0 with JWSDP 2.0.
    When I deploy my application (together with all required jar-files) as a war-file on a Tomcat 5.5, then everything runs fine.
    If I deploy the same application to Bea 9.1, then I get the following error message:
    21.02.2006 18:41:54 com.sun.xml.ws.transport.http.servlet.WSServletContextListen
    er contextInitialized
    INFO: WSSERVLET12: JAX-WS context listener initializing
    <21.02.2006 18.41 Uhr CET> <Warning> <HTTP> <BEA-101162> <User defined listener
    com.sun.xml.ws.transport.http.servlet.WSServletContextListener failed: java.lang
    .NoSuchMethodError: javax.jws.WebService.portName()Ljava/lang/String;.
    java.lang.NoSuchMethodError: javax.jws.WebService.portName()Ljava/lang/String;
    at com.sun.xml.ws.modeler.RuntimeModeler.getPortName(RuntimeModeler.java
    :1215)
    at com.sun.xml.ws.server.RuntimeEndpointInfo.doPortNameProcessing(Runtim
    eEndpointInfo.java:265)
    at com.sun.xml.ws.server.RuntimeEndpointInfo.init(RuntimeEndpointInfo.ja
    va:311)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.create
    ModelAndMetadata(WSServletContextListener.java:203)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contex
    tInitialized(WSServletContextListener.java:119)
    Truncated. see log file for complete stacktrace
    >
    21.02.2006 18:41:55 com.sun.xml.ws.transport.http.servlet.WSServletContextListen
    er contextDestroyed
    As I found out, Bea has an older version of jsr181-api.jar (which contains javax.jws.WebService) in its weblogic.jar-file.
    But although I have the newer version in my war-file (and of course set prefer-web-inf-classes to true), I still get the same error. It even gets worse, when I try to add the new jsr181-api.jar to Weblogic-Classpath.
    Does anybody know a solution for this problem?

    Hi,
    I'm also developing an app that uses XFire and the Spring Framework. Whenever I try to deploy this to Weblogic 9.2 I get the following error:
    <Nov 16, 2006 4:15:45 PM CST> <Error> <Deployer> <BEA-149265> <Failure occured in the execution of deployment request with ID '1163715338849' for task '0'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:295)
         at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         Truncated. see log file for complete stacktrace
    java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory
         at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)
         at weblogic.servlet.internal.WebAppHelper.addListenerElements(WebAppHelper.java:244)
         at weblogic.servlet.internal.WebAppHelper$IOHelperImpl.parseXML(WebAppHelper.java:224)
         at weblogic.descriptor.DescriptorCache.parseXML(DescriptorCache.java:324)
         at weblogic.servlet.internal.WebAppHelper.registerTagLibListeners(WebAppHelper.java:174)
         Truncated. see log file for complete stacktrace
    If I try to add all of the JARs to the classpath it gets worse:
    <Nov 16, 2006 4:10:53 PM CST> <Error> <HTTP> <BEA-101064> <[WebAppModule(bea_wls_internal:bea_wls_internal.war)] Error parsing descriptor in Web appplication "C:\bea\weblogic92\samples\domains\genworth\.\servers\AdminServer\tmp\.internal\bea_wls_internal.war"
    java.lang.RuntimeException: [was class java.net.UnknownHostException] java.sun.com
         at com.ctc.wstx.util.ExceptionUtil.throwRuntimeException(ExceptionUtil.java:18)
         at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:706)
         at com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3557)
         at com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:804)
         at javax.xml.stream.util.StreamReaderDelegate.getText(StreamReaderDelegate.java:172)
         Truncated. see log file for complete stacktrace
    When I deploy the exact same code to Tomcat it works fine, the problem seems to be Weblogic.
    I have even tried switching JVMs (JRockit and Sun's) with no luck so far. Any solution?

  • Tomcat 4.0.4 Internal Server Error with JWSDP 1.0.01 examples

    Hi,
    I am trying to run the JWSDP 1.0.01 tutorial examples with
    Apache Tomcat 4.0.4. I have j2sdk 1.4.0.01 installed on
    Windows 2000.
    I have successfully built and installed the 'date' example
    jwsdp-1_0_01\docs\tutorial\examples\web\date. When I point my browser at http://localhost:8080/date/ I get the following:
    Apache Tomcat/4.0.4 - HTTP Status 500 - Internal Server Error
    type Exception report
    message Internal Server Error
    description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request.
    exception
    org.apache.jasper.JasperException: Unable to compile class for JSPNote: sun.tools.javac.Main has been deprecated.
    error: An error has occurred in the compiler; please file a bug report (http://java.sun.com/cgi-bin/bugreport.cgi).
    1 error, 1 warning
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:285)
         at org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:548)
         at org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:176)
         at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:188)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
         at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
         at java.lang.Thread.run(Thread.java:536)
    Any ideas ?
    Thanks,
    Mike.

    Check if you've the latest servlet.jar file
    -Dieter

  • I have just downloaded jwsdp 1.2

    1st: when i type ant build I get a message that setenv.bat is not recognized as an internal or external command. I know that this batch file is in <JWSDP_HOME>\JSWDP_SHARED\ but how can I tell ANT to look there?
    2nd: I want to use the servlet and HTTP classes from the WSDP ,in Java SDK . How can I reference them ?import them?
    Thanx

    it is not about JAVA_HOME or ANT_HOME . I have already set them as permenant Environment Variables . The problem is that setenv.batch is in another directory of the ANT_HOME's and I don't know what variable I should use to point to it.
    2nd: does the servlet library come's with JWSDP!

Maybe you are looking for