JAXM in JWSDP 1.2

I can't find JAXM in JWSDP 1.2, yet it was there in 1.1. Is there a reason why it is no longer included in the JWSDP? There is no information about this on the website, and yet nowhere does it say that you even need JAXM anymore. What's the deal?

I got the following reply from a technology evangelist (which, I believe, might be someone who sends emails to God...):
JAXM is removed from the Java WSDP due to the following reasons:
-JAXM is not part of J2EE 1.4
-Given that SAAJ is taken out as a separate package from JAXM,
there is nothing much left in JAXM
-JAX-RPC is "the" Java API for Web services. It does support
document-driven model (with "doc/literal" and "attachment"
-MDB (of EJb 2.1) will support asynchronous messaging
Which doesn't explain why there was no announcement made, nor does it explain why JAXM is still prominently promoted on the Sun web site. But as we are mere mortals, I suppose we are not expected to understand.

Similar Messages

  • Has anyone successfully installed JAXM 1.1.2 with JWSDP 1.2?

    I'm unable to get the /jaxm-provider app from jaxm 1.1.2 running on jwsdp 1.2. Tomcat gives a failure message when I try to start the app manually but no detailed error message is logged. The jaxm samples that do not use a messaging provider are working fine. Has anyone else gotten the jaxm 1.1.2 provider to run?
    Thanks,
    Mike

    Problem solved. I had installed Axis 1.1 as a web app. log4j-1.2.8.jar is copied to JWSDP_HOME/common/lib as part of the Axis installation. When I removed that jar, /jaxm-provider started with no problem. Axis complains about the missing jar but it seems to work anyway.
    Mike

  • Error in using Jaxm provider deployed in j2ee 1.3.1 (RI)

    We were able to successfully deploy/test all JWSDP v1.0 samples into the
    J2ee 1.3.1 (RI) in preparation for our next projects.
    We have problems, however, in deploying the JAXM-provider and
    JAXM-providerAdmin samples. Please, help us.
    We followed the procedures defined in your article; we even re-deployed the
    same war files that came out of running jwsdponj2ee.bat.
    We always get the same errors. We even switch back and forth the port for
    webservices in our desperation; but to no avail. THe scenarion went like this:
    After deployment of the modified jaxm-provider.war and
    jaxm-provideradmin.war, we then point our browser to
    http://127.0.0.1:8080/jaxm-provideradmin. We then enter "j2ee" as user and
    password. So, far so good and we get to the next page that has the frame
    (http://127.0.0.1:8080/jaxm-provideradmin/index.jsp). So far so good at this
    point. But when we click on the "HTTP" icon under ebXML profile, we get some of
    these error messages:
    "Internal server error"
    javax.servlet.ServletException
         at
    org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:463)
         at org.apache.jsp.ebxml_0005fhttp$jsp._jspService(ebxml_0005fhttp$jsp.java:941)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at
    org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    root cause
    java.lang.NoClassDefFoundError
         at org.apache.jsp.ebxml_0005fhttp$jsp._jspService(ebxml_0005fhttp$jsp.java:149)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at
    org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    And if we click on the "HTTP" icon of SOAPRP, we get these messages:
    Internal Server Error
    javax.servlet.ServletException
         at
    org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:463)
         at
    org.apache.jsp.soaprp_0005fhttp$jsp._jspService(soaprp_0005fhttp$jsp.java:941)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    Root Cause
    java.lang.NoClassDefFoundError
         at
    org.apache.jsp.soaprp_0005fhttp$jsp._jspService(soaprp_0005fhttp$jsp.java:149)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    Although our setup of J2EE 1.3.1 (R.I.) is able to successfully run all the
    other JWSDP v1.0 Samples, we are obviously missing something in deploying the
    JAXM-provider and provider admin samples.
    Any ideas to help us, Please...
    Thanks in advance for your possible time and effort....
    adler

    I was really hoping someone could/would answer your question, I have having the exact same issues. After looking through release notes for J2SE 1.4.0_01, J2EE 1.3.1, and JWSDP 1.0, the only thing I can come up with is that there is a conflict between the JAXM version that the JWSDP installer and the XML packages included with J2SE. This is purely conjecture, but it's all I have to go on right now. If you figure out or find the solution please post it.
    Thanks,
    tc

  • JAXM RI asynchronous delivery -- how does it work?

    After struggling with using a one-way remote messaging with JAXM provider for several days, I finally got two simple clients working on two machines, one message producer on server1 and the other consumer on server2 (no reply message the other way) -- but only on the condition of both servlets are up. If the producer sends message while the consumer is undeployed or the consumer's container is stopped, the consumer does NOT get the message after it is back on line. But isn't that the whole point of "asynchronousness" which the RI spec says "The application itself may be active or quiescent, but the remote provider continues to try to ... receive any incoming messages on the application's behalf. When an application comes up and establishes a connection to the remote provider, messages received by the provider for that application are delivered to it."?
    There are quite some discussions on the confusing topic about configuring the sender and receiver. But I didn't find any discussion on this "asynchronousness" and how it works. any insights would be appreciated. posting my configuration files here.
    ============================================
    Producer side
    client.xml:
    <Endpoint>
    http://Producer
    </Endpoint>
    <CallbackURL>
    http://server1:8080/HelloProducer/Producer
    </CallbackURL>
    <Provider>
    <URI>http://java.sun.com/xml/jaxm/provider</URI>
    <URL>http://127.0.0.1:8081/jaxm-provider/sender</URL>
    </Provider>
    provider.xml
    URI: http://Consumer
    URL: http://server2:8080/jaxm-provider/receiver/soaprp
    ============================================
    Consumer side:
    client.xml
    <Endpoint>
    http://Consumer
    </Endpoint>
    <CallbackURL>
    http://server2:8080/HelloConsumer/Consumer
    </CallbackURL>
    <Provider>
    <URI>http://java.sun.com/xml/jaxm/provider</URI>
    <URL>http://127.0.0.1:8081/jaxm-provider/sender</URL>
    </Provider>
    provider.xml
    No mapping (there is no reply message)
    ============================================
    Bianca

    I've only quickly scanned through your post, but one point is that if you stop the web container, then the messaging provider will also stop and will not receive any messages.
    Although the documentation mentions being able to retrieve messages from a provider once it re-connects, this would only work if you left the container running and re-deployed the application the message is intended for. I haven't read all of the JAXM specs in detail, but I have found in several instances that the documentation/specs will suggest a specific functionality is available, but then I find it has not been implemented at this time.
    Generally, JAXM applications (servlets) tend to initiate a connection to their provider early on, and do not disconnect, so if the JAXM application has an onMessage method, it will receive the SOAP message and process it.
    Additionally, if you configure the provider through the GUI tool provided with JWSDP, then you can set how many times the message should be re-sent by a provider (and some other properties).
    Finally, the definition of asynchronicity should not be confused with the ability discussed above of providers to deliver messages to an application which has been offline. Synchronous messaging is basically the same as a regular function call. For example,
    double ReturnDouble (){
    return 4.35;
    If this method is called by a class, then it will wait for a double to be returned and the calling class is said to be 'blocked'. Only when the function returns a response to the calling class is the method unblocked and the program execution continues. Similarly with synchronous JAXM (SAAJ) messaging (without providers), the method in a listening servlet is:
    SOAPMessage onMessage(SOAPMessage message){
    // Create SOAP
    return soapMessage;
    This method returns a SOAPMessage object to the client, and this client is blocked until it receives this SOAPMessage as a reply.
    With asynchronous messaging, the listening servlet does not return a response to an incoming message (and the sending servlet does not expect one), so the sending application (a JAXM servlet) can send a SOAP message to the listening servlet, and then execute the rest of its code without waiting for a response.
    (Although the onMessage method in asynchronous messaging using providers has a return type of void, using a return type of void in JAX-RPC messaging does NOT imply an asynchronous method call :) )
    Hope that is clear - I haven't had coffee yet ;)
    Simon

  • Reg: JAXM support on BEA Weblogic 7.0

    BACKGROUND: I am developing a Point-to-point SOAP sender/receiver application.
    A client sends a SOAP message directly to the ultimate recipient
    using a SOAPConnection object. Here client to the intended recipient
    rather than to a messaging provider. Therefore, when the application
    sends a message, the message goes directly to the intended recipient.
    This kind of SOAP message exchange uses the APIs in the javax.xml.soap package.
    SOAPConnection (and its related classes) is a pure library implementation
    that lets you send SOAP messages directly to a remote party.
    CODE:
    try
    String endpoint="http://localhost:7001/WholesaleVendor/wsv";
    URLEndpoint urlEndpoint= new URLEndpoint(endpoint);
    SOAPConnectionFactory soapConnFct = SOAPConnectionFactory.newInstance();
    SOAPConnection soapConnection = soapConnFct.createConnection();
    MessageFactory messageFactory = MessageFactory.newInstance();
    SOAPMessage requestSoapMsg = messageFactory.createMessage();
    //REST OF THE CODE FOLLOWS
    PROBLEM: It works on Sun's JWSDP 1.0. Howerver, on BEA Weblogic 7.0, I get error.
    The error is in the following line:
    ============================
    javax.xml.soap.SOAPException: Unable to create SOAP connection factory:
    Provider com.sun.xml.messaging.client.p2p.HttpSOAPConnectionFactory not found
    at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
    at supermarket.InventoryBuilder.placePOOnWholeSaleVendor(InventoryBuilder.java:74)
    ============================
    QUERY: Is Point-to-point JAXM communication supported on BEA Weblogic 7.0?
    If not, what is alternative?
    What is the scope of JAXM support on BEA Weblogic 7.0?
    Thanking you in anticipation.
    Sachin Raverkar

    We have not implemented JAXM, nor has JAXM been included in J2EE 1.4.
    JAXM has not gotten much traction in the marketplace, and we have
    focused instead on JAX-RPC, which is available in 7.0 and 8.1. From
    your description, it sounds like JAX-RPC would meet your requirements.
    Note that we do support the SAAJ APIs, which were previously part of JAXM.
    -Don
    Sachin Raverkar wrote:
    BACKGROUND: I am developing a Point-to-point SOAP sender/receiver application.
    A client sends a SOAP message directly to the ultimate recipient
    using a SOAPConnection object. Here client to the intended recipient
    rather than to a messaging provider. Therefore, when the application
    sends a message, the message goes directly to the intended recipient.
    This kind of SOAP message exchange uses the APIs in the javax.xml.soap package.
    SOAPConnection (and its related classes) is a pure library implementation
    that lets you send SOAP messages directly to a remote party.
    CODE:
    try
    String endpoint="http://localhost:7001/WholesaleVendor/wsv";
    URLEndpoint urlEndpoint= new URLEndpoint(endpoint);
    SOAPConnectionFactory soapConnFct = SOAPConnectionFactory.newInstance();
    SOAPConnection soapConnection = soapConnFct.createConnection();
    MessageFactory messageFactory = MessageFactory.newInstance();
    SOAPMessage requestSoapMsg = messageFactory.createMessage();
    //REST OF THE CODE FOLLOWS
    PROBLEM: It works on Sun's JWSDP 1.0. Howerver, on BEA Weblogic 7.0, I get error.
    The error is in the following line:
    ============================
    javax.xml.soap.SOAPException: Unable to create SOAP connection factory:
    Provider com.sun.xml.messaging.client.p2p.HttpSOAPConnectionFactory not found
    at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
    at supermarket.InventoryBuilder.placePOOnWholeSaleVendor(InventoryBuilder.java:74)
    ============================
    QUERY: Is Point-to-point JAXM communication supported on BEA Weblogic 7.0?
    If not, what is alternative?
    What is the scope of JAXM support on BEA Weblogic 7.0?
    Thanking you in anticipation.
    Sachin Raverkar

  • 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.

  • JAXM 1.1.2 and Tomcat 4.1.29

    Dear all,
    After fiddling with the configs of JAXM and Tomcat, (besides searching the mail archives), I still can't figure how to make them work together.
    I copied dom4j.jar, jaxm-api.jar and jaxm-runtime.jar to $CATALINA_HOME/common/lib. Then I copied jaxm-provider.war and jaxm-provideradmin.war to $CATALINA_HOME/webapps.
    I can access http://localhost/jaxm-provideradmin. However, when I clicked on "Profiles" on the left frame, I got the error message below. So I thought, may be I need to copy saaj-impl.jar and saaj-api.jar to $CATALINA_HOME/common/lib. This time I got different error message. (See below)
    I have also tried to include the CLASSPATH specified in catalina.sh of jwsdp-1.3. However, still no luck.
    For your info, I am doing all these on HP-UX 11.00, running JDK 1.3.1.
    Any pointer would be greatly appreciated.
    Thanks.
    org.apache.jasper.JasperException: javax/xml/soap/SOAPElement
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
    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:256)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:553)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:577)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:781)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:549)
    at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
    at java.lang.Thread.run(Unknown Source)
    ----- Root Cause -----
    javax.servlet.ServletException: javax/xml/soap/SOAPElement
    at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:536)
    at org.apache.jsp.jaxm_profile_default_jsp._jspService(jaxm_profile_default_jsp.java:351)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
    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:256)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:553)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:577)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:781)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:549)
    at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
    at java.lang.Thread.run(Unknown Source)
    ========================================================================
    HTTP Status 500 -
    type Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    org.apache.jasper.JasperException
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
         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:256)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:553)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:577)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:781)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:549)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
         at java.lang.Thread.run(Unknown Source)
    root cause
    javax.servlet.ServletException
         at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:536)
         at org.apache.jsp.jaxm_profile_default_jsp._jspService(jaxm_profile_default_jsp.java:351)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
         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:256)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:553)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:577)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:781)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:549)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
         at java.lang.Thread.run(Unknown Source)
    Apache Tomcat/4.1.29

    Dear all,
    Problem solved. Once I upgraded to JDK 1.4.2, the problem seems to go away.

  • JAXM - SOAP Faults

    Hi,
    I have an almost working JAXM standalone client. However i have one problem, i cant seem to get SOAP Faults back from the SOAP Server (MS SOAP), instead i get a java exception as shown below. All other calls work fine, i would like to be able to retrieve the error information from the fault.
    I am using the JAXM version that comes with the JWSDP.
    I am wondering if anyone has JAXM working with SOAP faults?.. i dont want to have to change my implementation.
    Kris
    java.io.FileNotFoundException: http://TAZ//MeridioSOAP//MeridioSOAP.asp
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:549)
         at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:198)
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:105)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:84)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendSOAPMessage(DMSMeridioSOAPOperations.java:1597)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendInformationRequest(DMSMeridioSOAPOperations.java:283)
         at com.kainos.edms.meridio.DMSMeridioSOAPHelper.getDocumentVersionInfo(DMSMeridioSOAPHelper.java:1073)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:735)
    javax.xml.soap.SOAPException: java.security.PrivilegedActionException <<javax.xml.messaging.JAXMException: Message send failed>>
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:88)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendSOAPMessage(DMSMeridioSOAPOperations.java:1597)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendInformationRequest(DMSMeridioSOAPOperations.java:283)
         at com.kainos.edms.meridio.DMSMeridioSOAPHelper.getDocumentVersionInfo(DMSMeridioSOAPHelper.java:1073)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:735)
    java.lang.NullPointerException
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.debugSOAPMessage(DMSMeridioSOAPOperations.java:1548)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendInformationRequest(DMSMeridioSOAPOperations.java:288)
         at com.kainos.edms.meridio.DMSMeridioSOAPHelper.getDocumentVersionInfo(DMSMeridioSOAPHelper.java:1073)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:735)

    It seems no one has ever had a SOAP fault and cant answer my question. Anyway more information. I have tracked the problem down to the following :
    As per the SOAP Specification, a normal SOAP response returns with the HTTP Post code 200 OK, and a fault returns with the HTTP Post code 500 Internal Server Error.
    The class sun.net.www.protocol.http.HttpURLConnection seems to throw an exception if the code returned isnt 200. Obvously this isnt any good for SOAP faults. Any ideas as to ways around this?
    btw, i changed the version of the JDK i was using from 1.3.0 to 1.3.1_02 and the exception message changes from what i stated in my first message to the following which makes a bit more sense.
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://TAZ//MeridioSOAP//MeridioSOAP.asp
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:562)
         at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:198)
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:105)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:84)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendSOAPMessage(DMSMeridioSOAPOperations.java:1597)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendAuthenticationRequest(DMSMeridioSOAPOperations.java:164)
         at com.kainos.edms.meridio.DMSMeridioSOAPHelper.login(DMSMeridioSOAPHelper.java:153)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:655)
    javax.xml.soap.SOAPException: java.security.PrivilegedActionException <<javax.xml.messaging.JAXMException: Message send failed>>
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:88)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendSOAPMessage(DMSMeridioSOAPOperations.java:1597)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendAuthenticationRequest(DMSMeridioSOAPOperations.java:164)
         at com.kainos.edms.meridio.DMSMeridioSOAPHelper.login(DMSMeridioSOAPHelper.java:153)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:655)
    java.lang.NullPointerException
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.debugSOAPMessage(DMSMeridioSOAPOperations.java:1548)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendAuthenticationRequest(DMSMeridioSOAPOperations.java:166)
         at com.kainos.edms.meridio.DMSMeridioSOAPHelper.login(DMSMeridioSOAPHelper.java:153)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:655)
    java.lang.NullPointerException
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:657)

  • Error accessing protocols with JAXM 1.1.2 Provider Admin Tool

    I installed JAXM 1.1.2 with JWSDP 1.2 on W2K Pro according the instructions under the JAXM doc's "Integration with JWSDP" link. The samples seem to be working. However, when I start the JAXM Provider Admin tool and drill down to one of the protocols (e.g., Profiles > SOAPRP > HTTP), the server throws an exception. I tried this on two different machines and got the same result. The jaxm-provider webapp's provider.xml looks reasonable. Anyone have any idea what's going on?
    Thanks,
    Mike
    Here's the stack trace:
    HTTP Status 500 -
    type Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    org.apache.jasper.JasperException
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:367)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:293)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:288)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:562)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:196)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:558)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:562)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2748)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:186)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:562)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:163)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:512)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:562)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:199)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:637)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:463)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:568)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:631)
         at java.lang.Thread.run(Thread.java:536)
    root cause
    java.lang.NullPointerException
         at provideradmin.util.MessageUtil.initializeConfig(MessageUtil.java:281)
         at org.apache.jsp.soaprp_005fhttp_jsp._jspService(soaprp_005fhttp_jsp.java:112)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:320)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:293)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:288)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:562)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:196)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:558)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:562)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2748)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:186)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:562)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:163)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:512)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:562)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:199)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:637)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:463)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:568)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:631)
         at java.lang.Thread.run(Thread.java:536)
    Java Web Services Developer Pack/1.2

    Problem solved. JWSDP_HOME/common/lib had log4j-1.2.8.jar from the Axis 1.1 distribution. After I moved the jar to JWSDP_HOME/jwsdp-shared/lib, the jaxm provider admin works (and Axis still finds the log4j jar file).
    Mike

  • JAXM support in wls 7.0?

    Does Bea WLS 7.0 (sp 2 or newer) support JAXM?
    It looks like the majority of the packages is there (SOAP Message
    Handler Chain Operations use them also), but at least an
    implementation of HttpSOAPConnectionFactory seems to be missing.
    So, what is the status with JAXM, is it going to be bundled in the
    WLS, or do we have to use jwsdp packages for that functionality?
    When I invoke the following
    SOAPConnectionFactory.newInstance();
    the exception looks like this:
    javax.xml.soap.SOAPException: Unable to create SOAP connection
    factory: Provider
    com.sun.xml.messaging.client.p2p.HttpSOAPConnectionFactory not found
    at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
    at testclient.WsTestDynamicClient.<init>(WsTestDynamicClient.java:45)
    at testclient.WsTestDynamicClient.main(WsTestDynamicClient.java:189)
    Regards,
    Toni N.

    Hi Toni,
    HttpSOAPConnectionFactory and the related classes you are
    using, are now part of a SAAJ [1] and WLS 8.1 [2] supports it.
    regards,
    -manoj
    [1] http://java.sun.com/xml/saaj/
    [2] http://commerce.bea.com/showproduct.jsp?family=WLP&major=8.1&minor=-1
    "toni nykanen" <[email protected]> wrote in message
    news:3e6deb8d$[email protected]..
    >
    Does Bea WLS 7.0 (sp 2 or newer) support JAXM?
    It looks like the majority of the packages is there (SOAP Message
    Handler Chain Operations use them also), but at least an
    implementation of HttpSOAPConnectionFactory seems to be missing.
    So, what is the status with JAXM, is it going to be bundled in the
    WLS, or do we have to use jwsdp packages for that functionality?
    When I invoke the following
    SOAPConnectionFactory.newInstance();
    the exception looks like this:
    javax.xml.soap.SOAPException: Unable to create SOAP connection
    factory: Provider
    com.sun.xml.messaging.client.p2p.HttpSOAPConnectionFactory not found
    at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
    at testclient.WsTestDynamicClient.<init>(WsTestDynamicClient.java:45)
    at testclient.WsTestDynamicClient.main(WsTestDynamicClient.java:189)
    Regards,
    Toni N.

  • JWSDP Compile Problem

    I recently installed the Java Web Services Developer Pack and added the following to the Environment variables on my Windows NT control panel:
    CLASSPATH: d:\jwsdp-1_1\common\lib\servlet.jar;
    PATH: d:\jwsdp-1_1\jakarta-ant-1.5.1\bin; d:\jwsdp-1_1\bin;
    d:\jwsdp-1_1\jwsdp-shared\bin;d:\jdk1.4.1\bin;
    However, the packages that come with the JWSDP are not being found when I try to compile a program. How do I resolve this? Also, I would like to include the Java mail package in the compile.
    Thanks,
    Robin
    build:
    [javac] Compiling 1 source file to D:\jwsdp-1_1\webapps\Waverly\build\WEB-INF\classes
    [javac] D:\jwsdp-1_1\webapps\Waverly\src\UPSTransmit.java:7: package javax.xml.soap does not exist
    [javac] import javax.xml.soap.*;
    [javac] ^
    [javac] D:\jwsdp-1_1\webapps\Waverly\src\UPSTransmit.java:8: package javax.mail.internet does not exist
    [javac] import javax.mail.internet.*;
    [javac] ^
    [javac] D:\jwsdp-1_1\webapps\Waverly\src\UPSTransmit.java:12: package org.dom4j does not exist
    [javac] import org.dom4j.*;
    [javac] ^
    [javac] D:\jwsdp-1_1\webapps\Waverly\src\UPSTransmit.java:30: cannot resolve symbol
    [javac] symbol : class SOAPConnectionFactory
    [javac] location: class UPSTransmit
    [javac] SOAPConnectionFactory scf = SOAPConnectionFactory.newInstance();
    [javac] ^
    [javac] D:\jwsdp-1_1\webapps\Waverly\src\UPSTransmit.java:30: cannot resolve symbol
    [javac] symbol : variable SOAPConnectionFactory
    [javac] location: class UPSTransmit
    [javac] SOAPConnectionFactory scf = SOAPConnectionFactory.newInstance
    [javac] ^
    [javac] D:\jwsdp-1_1\webapps\Waverly\src\UPSTransmit.java:31: cannot resolve symbol
    [javac] symbol : class SOAPConnection
    [javac] location: class UPSTransmit
    [javac] SOAPConnection connection = scf.createConnection();
    [javac] ^
    [javac] D:\jwsdp-1_1\webapps\Waverly\src\UPSTransmit.java:33: cannot resolve symbol
    [javac] symbol : class MessageFactory
    [javac] location: class UPSTransmit
    [javac] MessageFactory mf = MessageFactory.newInstance();
    [javac] ^
    [javac] D:\jwsdp-1_1\webapps\Waverly\src\UPSTransmit.java:33: cannot resolve symbol
    [javac] symbol : variable MessageFactory
    [javac] location: class UPSTransmit
    [javac] MessageFactory mf = MessageFactory.newInstance();
    [javac] ^
    [javac] D:\jwsdp-1_1\webapps\Waverly\src\UPSTransmit.java:36: cannot resolve symbol
    [javac] symbol : class SOAPMessage
    [javac] location: class UPSTransmit
    [javac] SOAPMessage msg = mf.createMessage();
    [javac] ^
    [javac] D:\jwsdp-1_1\webapps\Waverly\src\UPSTransmit.java:38: cannot resolve symbol
    [javac] symbol : class SOAPPart
    [javac] location: class UPSTransmit
    [javac] SOAPPart soapPart=msg.getSOAPPart();
    [javac] ^
    [javac] D:\jwsdp-1_1\webapps\Waverly\src\UPSTransmit.java:39: cannot resolve symbol
    [javac] symbol : class SOAPEnvelope
    [javac] location: class UPSTransmit
    [javac] SOAPEnvelope envelope = soapPart.getEnvelope();
    [javac] ^
    [javac] D:\jwsdp-1_1\webapps\Waverly\src\UPSTransmit.java:73: cannot resolve symbol
    [javac] symbol : class SOAPMessage
    [javac] location: class UPSTransmit
    [javac] SOAPMessage reply = connection.call(msg, endpoint);
    [javac] ^
    [javac] 12 errors
    BUILD FAILED
    file:D:/jwsdp-1_1/webapps/Waverly/build.xml:98: Compile failed; see the compiler error output for details.

    I received the following response from Sun's JWSDP team:
    I think the classes you say are missing are spread out across a number
    of jars and you would have to include them in your CLASSPATH in order to compile an application that imported those packages. For example,
    javax.xml.bind is in d:\jwsdp-1_1\jaxb-1.0\lib\jaxb-api.jar and
    javax.xml.messaging is in d:\jwsdp-1_1\jaxm-1.1.1\lib\jaxm-api.jar and
    the namespace.jar is in d:\jwsdp-1_1\jwsdp-shared\lib, etc.
    Robin

  • Xletview , java tv,  webservices and jaxm.properties..

    Hi.
    I am running C:\jwsdp-1.2 and C:\j2sdk1.4.2_05 .. I am doing a test
    on JavaTv using XletView. It failed when I run it in the XletView emulator. Where can i obtain the jaxm.properties..
    xjava.io.File - C:\j2sdk1.4.2_05\jre\lib\jaxm.properties
    java.lang.NullPointerException
    at com.sun.xml.rpc.soap.message.SOAPMessageContext.createMessage(SOAPMes
    sageContext.java:114)
    at com.sun.xml.rpc.client.StreamingSenderState.<init>(StreamingSenderSta
    te.java:32)
    at com.sun.xml.rpc.client.StreamingSender._start(StreamingSender.java:48
    at com.francetelecom.rd.orion.webservice.OrionWebServicePortType_Stub.ge
    tArrayOfMembers(OrionWebServicePortType_Stub.java:1620)
    at com.francetelecom.rd.orion.webservice.OrionWebServicePortTypeClient.g
    etArrayOfMembers(OrionWebServicePortTypeClient.java:72)
    at com.francetelecom.rd.orion.controller.Welcome.setUp(Welcome.java:79)
    at com.francetelecom.rd.orion.xlet.OrionXlet.initXlet(OrionXlet.java:58)
    at net.beiker.xletview.xlet.XletManager.initXlet(Unknown Source)
    at net.beiker.xletview.xlet.XletManager.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:534)

    My question is where is this file .. I can't see it anywhere.. I am using C:\jwsdp-1.2

  • JAXM HELP!!

    After compiling and running the following code:
    import javax.xml.soap.SOAPConnectionFactory;
    import javax.xml.soap.SOAPConnection;
    import javax.xml.soap.MessageFactory;
    import javax.xml.soap.SOAPMessage;
    import javax.xml.soap.SOAPPart;
    import javax.xml.soap.SOAPEnvelope;
    import javax.xml.soap.SOAPBody;
    import javax.xml.soap.SOAPElement;
    public class Soap1 {
    public static void main(String Args[]) {
    try {
    SOAPConnectionFactory soapConnFactory =SOAPConnectionFactory.newInstance();
    SOAPConnection Connection=soapConnFactory.createConnection();
    MessageFactory messageFactory=MessageFactory.newInstance();
    SOAPMessage message=messageFactory.createMessage();
    SOAPPart soapPart = message.getSOAPPart();
    SOAPEnvelope envelope = soapPart.getEnvelope();
    SOAPBody body= envelope.getBody();
    SOAPElement bodyElement=body.addChildElement(envelope.createName("schedule","cal","http://example.com"));
    message.saveChanges();
    System.out.println("\nREQUEST: \n");
    message.writeTo(System.out);
    System.out.println();
    Connection.close();
    catch(Exception e){
    e.printStackTrace();
    ... I get the following error:
    javax.xml.soap.SOAPException: Unable to create SOAP connection factory: Provider
    com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnectionFactory not found
    at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
    at Soap1.main(Soap1.java:17)
    I have already included the saaj-api.jar file in my classpath.
    Can you please help me?
    Regards,
    George Drepaniotis
    Electrical Engineer
    Univercity of Patras
    Greece

    only the saj-api.jar is not enough to run.
    try the following classpath, hope it solves ur problem.
    set JWSDP_HOME=c:\jwsdp-1.1
    set JAXM_LIB=c:\jwsdp-1.1\jaxm-1.1.1\lib
    set JAXP_HOME=c:\jwsdp-1.1\jaxp-1.2.2
    set SAAJ_HOME=c:\jwsdp-1.1\saaj-1.1.1
    set CLASSPATH=%classpath%;%SAAJ_HOME%\lib\dom4j.jar;%JWSDP_HOME%\jwsdp-shared\lib\activation.jar;%JAXM_LIB%\jaxm-api.jar;%SAAJ_HOME%\lib\saaj-api.jar;%JWSDP_HOME%\jwsdp-shared\lib\mail.jar;%JWSDP_HOME%\jwsdp-shared\lib\commons-logging.jar;%JAXM_LIB%\jaxm-runtime.jar;%SAAJ_HOME%\lib\saaj-ri.jar;%JAXP_HOME%\lib\jaxp-api.jar;%JAXP_HOME%\lib\endorsed\sax.jar;%JAXP_HOME%\lib\endorsed\dom.jar;%JAXP_HOME%\lib\endorsed\xercesImpl.jar;%JAXP_HOME%\lib\endorsed\xalan.jar;%JAXP_HOME%\lib\endorsed\xsltc.jar;

  • 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

  • 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

Maybe you are looking for

  • Copying a single file from one project to another????

    Hello, New to Mac from a PC, tried search with no results. I have a single image I would like to display in 2 separate projects in Aperture. (As I will be writing to a disc and print later). How do I copy the image from Project A to Project B, making

  • How to remove element namespaces in XML file using DOM or SAX?

    Hi Guys, I developed a JAVA mapping in XI to add name spaces for XML file, after mapping,name spaces xmlns="http://www.mro.com/mx/integration" and xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" were added correctly, but for some nodes, such as

  • How to connect to BO from Excel 2007

    Hi everyone, as I am new to BO I need help how to establish connection to a BO Universe from Excel 2007 - what components I need to install to be able to make the connection, and steps for creating the connection Thanks in advance, Maria

  • Vision M 60Gb spare pa

    We managed to lose the USB host adapter cable for our ZVM 60 Gb whilst travelling so couldn't directly transfer from our camera any more - the whole reason we bought it! Does anyone know the best place to get spare parts for Creative MP3 players? I h

  • ERROR: Failed to retrieve character view of the report.

    While trying to get HTML representation of report I am getting following error trying to get report from crystal reports web services XI R2 (Product: 11.5): Source code to reproduce:                     ViewSupport htmlViewSupport = new ViewSupport()