Request dispatcher method--help needs

Hi,
I used request dispatcher method to redirect the from one servlet to another servlet.But when i use get method it is functioning well.
But when i use post method it is giving error...
I need to use post method...
How can it possible..
Thanks,
Babu B

you have code for request.RequestDispatcher.forward(""); method in both doPost and
doGet methods for the servlet. However your initial form is not set with method
to POST.
By default the method is GET and it will execute code in doGet and not code in
doPost() method. so in your first form use method as POST instead of keeping
it to default i.e no method specified.
let me know where are you using RequestDispatcher.
//rohit

Similar Messages

Object SELFITEM/SENDTASKDESCRIPTION method help needed

Hi All,
I am working on Credit Release workflow for SD documents.
-     I have a mail sending step in workflow definition.
-     In this step I have created a task which is using SELFITEM object & SENDTASKDESCRIPTION method.
-     When I logged into the system with default language (EN) I can see all the details in the mail body.
-     When I logged into the system with some other language (Say JA) I can not see all the information in mail body
-     Some information like currency of the order value is not shown in mail body when logged in with some other language.
Can anybody will help me to resolve this issue.
Thank you all in advance.
Best Regards,
Deepa Kulkarni

Try like below:
Data: lv_logon TYPE t002-spras,
          lv_text   TYPE char80.
             lv_logon = sy-langu
             if lv_logon EQ 'E'.
                 lv_text = "English text"
             elsif lv_logon EQ 'J'.
               lv_text = " Japanese text".
            endif.
SWC_SET_ELEMENT CONTAINER 'TEXT' lv_text.
Note...if your content is having multiple lines...then you can go with table parameter instead of variable.

Doubt in working of Arrays.sort method. help needed !!!!

Hello Friends,
I am not able to understand output of Arrays.sort method. Here is the detail of problem
I wrote one program :
public static void main(String[] args) throws ClassNotFoundException
     Object[] a = new Object[10];
     a[0] = new String("1");
     a[1] = new String("2");
     a[2] = new String("4");
     a[3] = new String("3");
     a[4] = new String("5");
     a[5] = new String("20");
     a[6] = new String("6");
     a[7] = new String("9");
     a[8] = new String("7");
     a[9] = new String("8");
/* Sort entire array.*/
     Arrays.sort(a);
     for (int i = 0; i < a.length; i++)
     System.out.println(a);
and output is :
1
2
20
3
4
5
6
7
8
9
Question : Does this output is correct? If yes then on which basis api sort an array? I assume output should be 1 2 3 4 5 6 7 8 9 20.
Can here any one please explain this?
Thanks in advance.
Regards,
Rajesh Rathod

jverd wrote:
"20" and "3" are not numbers. They are strings, and "20" < "3" is exactly the same as "BA" < "C"The above is
... quote 20 quote less than quote 3 quote...
but shows up as
... quote 20 quote less than quote...
Weird.

Ejb-ql method help needed plz!

Dear All,
I get the following error: the details are given below!
Unknown query: public abstract java.util.Collection com.sextanttech.entities.implementations.UserBean.ejbSelectUsers(int,int,int) throws javax.ejb.FinderException
The relevant part of my ejb-jar.xml file
<query>
<query-method>
<method-name>ejbSelectUsers</method-name>
<method-params>
<method-param>int</method-param>
<method-param>int</method-param>
<method-param>int</method-param>
</method-params>
</query-method>
<ejb-ql><![CDATA[
SELECT user.userName
FROM UserTable user
WHERE user.flag1 = ?1
AND user.flag2 = ?2
AND user.flag3 = ?3]]>
</ejb-ql>
</query>
The relevant part of my entity bean class:
public Collection getselectedusers() throws FinderException // this is my business method impl.
Collection cc = this.ejbSelectUsers(1,1,1);
return cc;
public abstract Collection ejbSelectUsers( int flag1,int flag2,int flag3 ) throws FinderException;
Thanks in advance!
alex.

hi buddy,
select method cannot be declared in both home or remote interfaces...only in bean impl class
and i did exactly that...plz notify me if u get any ideas.
regards

Help needed: Handling web service requests from a J2SE application

I want to write an J2SE application that is able to receive and parse web service requests. I want the application to, when started, start listen for incoming requests on a specific port.
So far, I have embedded Apache Tomcat and Apache Axis in my application so that they parse the incoming requests and pass them on to my application logic.
This seems like a very cumbersome way of doing it. I have included an almost full J2EE server in my application just to be able to parse web service requests.
Is there an easier way? What technologies could I use? Any help would be greatly appreciated.

Thanks for the help!
It seems awfully complex though. Couldn't one just
listen to incoming requests on a socket and use some
good tool to parse them?
Of course you could. One of the projects in that list is a 1 class java file. It could listen for requests, then you could parse the posted SOAP messages using JAXP and pass the requests on to your application. This will require a good understanding of SOAP however, and it may end up taking more time than simply using the JWSDP with a slightly beefier server.
Given that there is only a handful carefully
specified requests that the application needs to be
able to respond to it seems overkill to include a
full servlet enabled server...

Help need for badi method me_process_po_cust~check

Dear All expert
Pl see following thread
I am stuck
Help needed
http://scn.sap.com/thread/3610303

See the issue here is HOLD feature in PO should not be there if it meets the error condition.
For this you can refer another BADI for this purpose ME_HOLD_PO.
Refer one of my previous threads below , it might be helpful :
Held Purchase order need not be created.
Reiterating a thread related to same topic is not a good practice.

JAX-WS web service - "Cannot find dispatch method"

I'm getting the same error response every time I send a request to my JAX-WS web service:
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
   <faultcode>ns2:Client</faultcode>
   <faultstring>Cannot find dispatch method for {http://www.w3.org/2003/05/soap-envelope}Envelope</faultstring>
</ns2:Fault>I've tried using JAX-WS RI 2.1.7 and 2.2 on my Tomcat server, but both return the same error response. It will return the WSDL just fine (when "?wsdl" is appended to the endpoint URL). I used "wsimport" to generate the necessary Java classes from my WSDL--it used JAX-WS RI 2.1.6 (the one included with the JDK I guess) to generate the Java source files.
Other people online have had similar problems, but never with the SOAP element "{http://www.w3.org/2003/05/soap-envelope}Envelope", always with things specific to their WSDLs like "{}reqParams" or "{http://www.telekom.at/eai/WSToCramerCSIRead}CSIRead". I set a debug breakpoint at the start of my SIB method and it doesn't even get that far.
Any ideas? Thanks for your help.
WSDL:
<?xml version="1.0" encoding="utf-8"?>

<definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ihe="urn:ihe:iti:xds-b:2007" xmlns:iherad="urn:ihe:rad:xdsi-b:2009" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
targetNamespace="urn:ihe:rad:xdsi-b:2009" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" name="ImagingDocumentSource">
<documentation>IHE XDS-I.b Imaging Document Source</documentation>
<types>
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:ihe:iti:xds-b:2007"
      xmlns:ihe="urn:ihe:iti:xds-b:2007">
      
      <xsd:include schemaLocation="../schema/IHE/XDS.b_DocumentRepository.xsd"/>
    </xsd:schema>
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:ihe:rad:xdsi-b:2009"
      xmlns:ihe="urn:ihe:iti:xds-b:2007"
      xmlns:iherad="urn:ihe:rad:xdsi-b:2009">
      
      <xsd:include schemaLocation="../schema/IHE/XDSI.b_ImagingDocumentSource.xsd"/>
    </xsd:schema>
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
      xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0">
      
      <xsd:include schemaLocation="../schema/ebRS/rs.xsd"/>
    </xsd:schema>
    
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0"
      xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0">
      
      <xsd:include schemaLocation="../schema/ebRS/lcm.xsd"/>
    </xsd:schema>
   <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
      xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0">
      
      <xsd:include schemaLocation="../schema/ebRS/rim.xsd"/>
    </xsd:schema>
</types>
<message name="RetrieveImagingDocumentSetRequest_Message">
    <documentation>Retrieve Imaging Document Set</documentation>
    <part name="body" element="iherad:RetrieveImagingDocumentSetRequest"/>
</message>
<message name="RetrieveDocumentSetResponse_Message">
    <documentation>Retrieve Document Set Response</documentation>
    <part name="body" element="ihe:RetrieveDocumentSetResponse"/>
</message>
<portType name="ImagingDocumentSource_PortType">
    <operation name="ImagingDocumentSource_RetrieveImagingDocumentSet">
      <input message="iherad:RetrieveImagingDocumentSetRequest_Message"
        wsaw:Action="urn:ihe:rad:xdsi-b:2009:RetrieveImagingDocumentSet"/>
      <output message="iherad:RetrieveDocumentSetResponse_Message"
        wsaw:Action="urn:ihe:iti:2007:RetrieveDocumentSetResponse"/>
    </operation>
</portType>
<binding name="ImagingDocumentSource_Binding" type="iherad:ImagingDocumentSource_PortType">
    <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="ImagingDocumentSource_RetrieveImagingDocumentSet">
      <soap12:operation soapAction="urn:ihe:rad:xdsi-b:2009:RetrieveImagingDocumentSet"/>
      <input>
        <soap12:body use="literal"/>
      </input>
      <output>
        <soap12:body use="literal"/>
      </output>
    </operation>
</binding>
<service name="ImagingDocumentSource_Service">
    <port name="ImagingDocumentSource_Port_Soap12" binding="iherad:ImagingDocumentSource_Binding">
      <soap12:address location="http://localhost:8080/webservice-test/ridsService"/>
    </port>
</service>
</definitions>
Request:
<soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:urn="urn:ihe:rad:xdsi-b:2009"
xmlns:urn1="urn:ihe:iti:xds-b:2007"
xmlns:a="http://www.w3.org/2005/08/addressing">
   <soap:Header>
     <a:Action soap:mustUnderstand="1">urn:ihe:rad:2009:RetrieveImagingDocumentSet</a:Action>
     <a:MessageID>urn:uuid:0fbfdced-6c01-4d09-a110-2201afedaa02</a:MessageID>
     <a:ReplyTo soap:mustUnderstand="1">
          <a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
     </a:ReplyTo>
     <a:To>http://localhost:8080/webservice-test/ridsServer</a:To>
   </soap:Header>
   <soap:Body>
      <urn:RetrieveImagingDocumentSetRequest>
         
         <urn:StudyRequest studyInstanceUID="test1">
            
            <urn:SeriesRequest seriesInstanceUID="test2">
               
               <urn1:DocumentRequest>
                  
                  <urn1:HomeCommunityId>test3</urn1:HomeCommunityId>
                  <urn1:RepositoryUniqueId>test4</urn1:RepositoryUniqueId>
                  <urn1:DocumentUniqueId>test5</urn1:DocumentUniqueId>
               </urn1:DocumentRequest>
            </urn:SeriesRequest>
         </urn:StudyRequest>
         <urn:TransferSyntaxUIDList>
            
            <urn:TransferSyntaxUID>?</urn:TransferSyntaxUID>
         </urn:TransferSyntaxUIDList>
      </urn:RetrieveImagingDocumentSetRequest>
   </soap:Body>
</soap:Envelope>
Response (HTTP 500):
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
   <faultcode>ns2:Client</faultcode>
   <faultstring>Cannot find dispatch method for {http://www.w3.org/2003/05/soap-envelope}Envelope</faultstring>
</ns2:Fault>

I posted here to benefit anybody who is looking for a solution.
The solution is to use WebServiceContext to get ServletContext, then use ServletContext to get parameters defined in web.xml.
@Resource private WebServiceContext m_wsCxt;
Then in method
SOAPMessageContext soapCxt = (SOAPMessageContext) m_wsCxt.getMessageContext();
ServletContext servletCxt = (ServletContext) soapCxt.get(javax.xml.ws.handler.MessageContext.SERVLET_CONTEXT);
}

Request dispatcher null

          The forward code we have is like
          public void forward(String url, HttpServletRequest request,
          HttpServletResponse response)
          throws ServletException, IOException
          RequestDispatcher dispatcher = getServletConfig().getServletContext().getRequestDispatcher(url);
          dispatcher.forward(request, response);
          My question is:
          As per the documents
          The pathname must begin with a "/" and is interpreted as relative to the current
          context root.
          if my URL is "http://www.abcz.com/<somepage>
          request dispatcher is null? and on one server (say A) that is a problem but other
          server(say B) when given the full URL behaves ok.
          on server A I am getting a null pointer exception , which on tracing happens to
          be the request dispatcher is null.(If http://www.abcz.com/<somepage> is URL) but
          no null pointer exception if url is "/<somepage>"
          On B its behaving fine when given the "http://www.abcz.com/<somepage> " as URL
          to the method.
          Both server A and B are running wl6. Is the difference in service pack cause of
          the problem?
          Internally does wl6 parses the URL to find a relative URL?
          Any help will be greatly appreciated.
          Thanks
          Rumpa


And the reason for that is, RequestDispatcher is per application
          scope. And RequestDispatcher comes from the ServletContext which is
          the current application scope. So it has to be relative url. If you
          need to forward to an absolute url, you can use sendRedirect instead.
          Bhaskar
          "Matt Krevs" <[email protected]> wrote in message news:<[email protected]>...
          > as far as i know, you should always specify relative urls when using request
          > dispatchers
          >
          > eg
          >
          > if the entire url is
          > http://myserver/theurl
          > you would code as follows
          >
          > RequestDispatcher dispatcher =
          > getServletConfig().getServletContext().getRequestDispatcher("/theurl");
          > dispatcher.forward(request, response);
          >
          > You definitely should not use complete URLs when calling
          > getRequestDispatcher()
          >
          > what happens on the server that returns a null dispatcher if you manually
          > type the address into the browser? Does weblogic find the resource? If not
          > then you have something specified differently in your server that doesn
          > work.
          >
          >
          > "RUMPA GIRI" <[email protected]> wrote in message
          > news:[email protected]...
          > >
          > > The forward code we have is like
          > > /**********************************************/
          > >
          > > public void forward(String url, HttpServletRequest request,
          > > HttpServletResponse response)
          > > throws ServletException, IOException
          > > {
          > > RequestDispatcher dispatcher =
          > getServletConfig().getServletContext().getRequestDispatcher(url);
          > > dispatcher.forward(request, response);
          > > }
          > > /***********************************************/
          > >
          > > My question is:
          > > As per the documents
          > > The pathname must begin with a "/" and is interpreted as relative to the
          > current
          > > context root.
          > > if my URL is "http://www.abcz.com/<somepage>
          > > request dispatcher is null? and on one server (say A) that is a problem
          > but other
          > > server(say B) when given the full URL behaves ok.
          > > on server A I am getting a null pointer exception , which on tracing
          > happens to
          > > be the request dispatcher is null.(If http://www.abcz.com/<somepage> is
          > URL) but
          > > no null pointer exception if url is "/<somepage>"
          > > On B its behaving fine when given the "http://www.abcz.com/<somepage> " as
          > URL
          > > to the method.
          > > Both server A and B are running wl6. Is the difference in service pack
          > cause of
          > > the problem?
          > >
          > > Internally does wl6 parses the URL to find a relative URL?
          > >
          > > Any help will be greatly appreciated.
          > > Thanks
          > > Rumpa
          > >
          > >

URGENT HELP NEEDED ... Tomcat Realm and JRE1.4 plug-in problem

I have tried the Security Realm of Tomcat. Since I do not have
an LDAP server, I decided to use the Tomcat-users.xml file in
Tomcat\conf directory.
I added the following lines of code in the web.xml file.
<security-constraint>
<web-resource-collection>
<web-resource-name>Entire Application</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<auth-constraint>

<role-name>webviewer</role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>Tomcat Manager Application</realm-name>
</login-config>
The <role-name> "webviewer" is added into "Tomcat-Users.xml" as the following:
<tomcat-users>
<user name="test" password="password" roles="webviewer" />
</tomcat-users>
So, now when we type the url: http://localhost:8080/adbpdbre/default.htm, TOMCAT shows a dialog box asking for UserName: and Password:Now, only when we give the username and password, it shows the page. This is exactly what we want.
But the problem now is, this default.htm page, has 5 links to 5 applets. The first time that I click on one of these links, the JRE plug of 1.4 shows a dialog again asking for the username and password. Till I dont provide the username and password the system doesnt go ahead and applet doesnt load. I do not want the JRE to ask me for the username/passwords again..How to avoid this ?
Can you give me some more information on this. Ultimately in the production usage, we will be using LDAP and not Tomcat's memory realm.
URGENT HELP NEEDED ... I need to get back to my client on this.
Help would be v. much appreciated.

In the config file, you 're essentially saying that you want Tomcat to prompt for usr/passw on every request (url-pattern = /*) made by a 'webviewer', and that's exactly what Tomcat is doing.
Consider using specific url-patterns & roles for resources to be protected. If for now, all you need is to protect the first page, use a more specific url-pattern.
Just an advice : if you'll be using LDAP in production, do not waste time with Tomcat's Security Realm and the BASIC authentication type, since the two have not much in common. Start reading doc on LDAP, and code a prototype, or even better, a vertical slice of the app (i.e a proof of concept).

Help needed to run JSTL 1.1 in Tomcat 6.0.16

Hi All,Help needed to run JSTL 1.1 in Tomcat 6.0.16. I am trying to run the example given in http://tomcat.apache.org/tomcat-6.0-doc/jndi-datasource-examples-howto.html The example tries to connect to MySQL database from JSP using JSTL and JNDI Datasource.I am running the example using Eclipse 3.4.2 using Sysdeo plugin to start and stop Tomcat server from Eclipse IDE.
My web.xml file has <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
</web-app>
and test.jsp has proper taglib directives
<%@ taglib prefix="sql" uri="http://java.sun.com/jsp/jstl/sql" %>
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
I have placed the jstl.jar and standard.jarof the jakarta-taglibs-standard-1.1.2.zip under E:\Deepa\workspace\DBTest\WebContent\WEB-INF\lib directory also placedcontext.xml file under E:\Deepa\workspace\DBTest\WebContent\META-INF and the content of context.xml is as below
<Context path="/DBTest" docBase="DBTest"
debug="5" reloadable="true" crossContext="true">
<Resource name="jdbc/TestDB" auth="Container" type="javax.sql.DataSource"
maxActive="100" maxIdle="30" maxWait="10000"
username="deepa" password="mysql" driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/javatest?autoReconnect=true"/>
</Context>
Now while running the example, Eclipse creates one DBTest.xml file under C:\Program Files\Apache Software Foundation\Tomcat 6.0\conf\Catalina\localhost
which has the following line:
<Context path="/DBTest" reloadable="true" docBase="E:\Deepa\workspace\DBTest" workDir="E:\Deepa\workspace\DBTest\work" />
I am getting the following error when running http://localhost/DBTest/WebContent/test.jsp
in Browser:
<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: The absolute uri: http://java.sun.com/jsp/jstl/sql cannot be resolved in either web.xml or the jar files deployed with this application
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:51)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:116)
org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:315)
org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:148)
org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:431)
org.apache.jasper.compiler.Parser.parseDirective(Parser.java:494)
org.apache.jasper.compiler.Parser.parseElements(Parser.java:1444)
org.apache.jasper.compiler.Parser.parse(Parser.java:138)
org.apache.jasper.compiler.ParserController.doParse(ParserController.java:216)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:103)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:154)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:315)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:295)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:282)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:586)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
In the Tomcat Server console, I am getting the following error:
INFO: Server startup in 7295 ms
May 20, 2009 6:36:48 AM org.apache.jasper.compiler.TldLocationsCache processWebDotXml
WARNING: Internal Error: File /WEB-INF/web.xml not found
May 20, 2009 6:36:48 AM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: The absolute uri: http://java.sun.com/jsp/jstl/sql cannot be resolved in either web.xml or the jar files deployed with this application
what is the problem with my code?
When running the same example, by creating a local server in Eclipse(creating new Server connection pointing to same Tomcat 6.0 installation) it runs fine without any error.

Hi evnafets,
Wow, very helpful information, great insight into working of Eclipse. Thanks a lot.
I have one more question. I have a context.xml file under {color:#0000ff}E:\Deepa\workspace\DBTest\WebContent\META-INF{color} folder and that has the Resource element to connect to MySQL database:
{code{color:#000000}}{color}<Context path="/DBTest" docBase="DBTest" debug="5" reloadable="true" crossContext="true">
<Resource name="jdbc/TestDB" auth="Container" type="javax.sql.DataSource" maxActive="100" maxIdle="30" maxWait="10000" username="deepa" password="mysql" driverClassName="com.mysql.jdbc.Driver"
{color:#0000ff}url="jdbc:mysql://localhost:3306/javatest?autoReconnect=true"/>{color}
{color:#0000ff}</Context>{color}As usual when running application in local Tomcat server of Eclipse, this data source works fine. But when I run the application on Tomcat, by starting Sysdeo plugin from Eclipse, the DBTest.xml file created in C:\Tomcat 6.0\conf\Catalina\localhost has the context entry as<Context path="/DBTest" reloadable="true" docBase="E:\Deepa\workspace\DBTest\WebContent" workDir="E:\Deepa\workspace\DBTest\work">
</Context>The<Resource> element I have specified in the context.xml of \WebContent\META-INF folder is not taken into account by Tomcat and it gives the following error:May 21, 2009 5:20:04 AM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet jsp threw exception
javax.servlet.jsp.JspException: Unable to get connection, DataSource invalid: "org.apache.tomcat.dbcp.dbcp.SQLNestedException_: Cannot create JDBC driver of class '' for connect URL 'null'"
_at org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.getConnection(_QueryTagSupport.java:276_)
at org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.doStartTag(_QueryTagSupport.java:159_)
at org.apache.jsp.test_jsp._jspx_meth_sql_005fquery_005f0(_test_jsp.java:113_)
at org.apache.jsp.test_jsp._jspService(_test_jsp.java:66_)
at org.apache.jasper.runtime.HttpJspBase.service(_HttpJspBase.java:70_)
at javax.servlet.http.HttpServlet.service(_HttpServlet.java:717_)
at org.apache.jasper.servlet.JspServletWrapper.service(_JspServletWrapper.java:374_)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(_JspServlet.java:342_)
at org.apache.jasper.servlet.JspServlet.service(_JspServlet.java:267_)
at javax.servlet.http.HttpServlet.service(_HttpServlet.java:717_)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(_ApplicationFilterChain.java:290_)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(_ApplicationFilterChain.java:206_)
at org.apache.catalina.core.StandardWrapperValve.invoke(_StandardWrapperValve.java:233_)
at org.apache.catalina.core.StandardContextValve.invoke(_StandardContextValve.java:191_)
at org.apache.catalina.core.StandardHostValve.invoke(_StandardHostValve.java:128_)
at org.apache.catalina.valves.ErrorReportValve.invoke(_ErrorReportValve.java:102_)
at org.apache.catalina.core.StandardEngineValve.invoke(_StandardEngineValve.java:109_)
at org.apache.catalina.connector.CoyoteAdapter.service(_CoyoteAdapter.java:286_)
at org.apache.coyote.http11.Http11Processor.process(_Http11Processor.java:845_)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(_Http11Protocol.java:583_)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(_JIoEndpoint.java:447_)
at java.lang.Thread.run(_Thread.java:619_)
{code}
So to overcome this error I had to place the <Resource> element in DBTest.xml under C:\Tomcat 6.0\conf\Catalina\localhost {color:#000000}and then it works fine. {color}{color:#ff0000}*Why is the context.xml file in META-INF not considered by Tomcat server using Sysdeo Plugin?*
*Thanks,*
*Deepa*{color}
{color}
Edited by: Deepa76 on May 26, 2009 9:32 PM

Help NeEDED. How to link to soap web service from objective c

Hello , HELP
I'm trying to connect to a SOAP based web service using objective C as my programming language. Although the little bit of information on the Apple Dev centre documents is should be straight forward, im struggling like **.
What im trying to do is connect via a small username and password text-box plus 'login' button from interface builder to
https://api.betfair.com/global/v3/BFGlobalService.wsdl and parameter called login.
then pass it my username and password from the interface text-boxes plus a few other standard set bits of information which are required.
in turn the soap request will pass back a session token which i need to store.
I've tried using WSMakestubs, which builds successfully the classes, but when calling them method nothing happens.

Hello Etresoft
Thanks again for coming back to me.. I would like to add that maybe on my first thread i wasn't as clear on what i was asking for, and also what avenues have have stepped down before asking for help.. Believe me i hate nothing more than not being able to resolve something myself. I'm currently reading 'another' programming in cocoa book by Arron Hillgrass, although he touches on the web service call to a Amazon web service example, he doesn't go into detail about how to actually do this.
So again thank you for trying to help me.. its greatly appreciated.
Ok back to the subject, and your response below.. I will try and be as informative as i can.
I'm want to create a application using the interface builder which has a username and password textfield plus a button called <login>..
On entering the username and password and pressing the login button, i was to send a request to the a .wdsl (SOAP) web service and login.! the webservice in return will send back a session token, which i need to store for further web service calls.
In xcode i have been trying now for 1 week..!!! and the more i read up on how to make the Soap request call the more i fail to understand if this is simple or complex.
* A bit more info if i may, on clicking the login button i need to send information to the below address as a soap type request.
https://api.betfair.com/global/v3/BFGlobalService.wsdl
i need to also tell the request the method name which is loginreq
and also i need to pass these parameters in the request.
username (from textfield)
password (from textfield)
productId = '82'
vendorsoftwareId = '0'
locationId = '0'
ipAddress = '0'
The stage I've got to is, I've used wsmakestubs and I've tried 'wdsl2objc' to create the classes required. I have then created a app controller class and a interface build app with the textfields and login button. I have then linked up the textfields and button to the nsobject appcontroller with a action ibaction loginreq etc. On build and go the app builds without error's but fails to do anything when i press the login button.. (more i think about this the more i think its either two things, one im not passing the parameters and two im not invoking the loginreq method from the class.)
I feel like im wading in treacle and getting nowhere fast.!
All i would like is for some help from someone to point me the correct direction..
Im thinking that with all the Soap web services out there in the WWW, this must now be a easy thing to do in xcode. Im starting to think im stupid..
Thanks again for you Help
Regards
Iain Smith
[email protected]

Pi 7.1: Exception when contacting WS - "Cannot find dispatch method"

Hi All,
I have been receiving the following error message as shown in ICM log, where the trace level is set to 3, when a request is sent to a Web Server.
...<SOAP:Faultmlns:SOAP='htt//schemas.xmlsp.org/soap/envope/'><faultco>SOAP:Client</ultcode><faultring>Cannot find dispatch method for arg0</faultstring/SOAP:Fault>..
No error message is returned using a soap client (as soapUI), after loading the same wsdl file.
About the configuration of the SOAP Communication Channel, no conversion parameter have been set and no SOAP Action has been set because the seme exception is also raised by setting "arg0" as SOAP Action.
The structure of the response message is like this.
<Field1>
   <arg0>
       <field2>
       <field3>
Any help will be well appreciated.
Many thanks in advacne for your kind support.
Regards,
       Giovanni

Hi All !!
This problem has been solved with the last SAP_XI* Patches.
We install:
SAP_XIESR SP06 Patch 11
SAP_XIAF   SP06 Patch 11
SAP_XITOOL SP06 Patch 10
and the problem...... SOLVED !!!
Regards,
Juan.

Weird soap issue: Cannot find the dispatch method

Hi,
I'm having strange problem with SOAP message.
I created a simple web service using jax-ws, wsgen, and so on. I deployed it on sun app server 9.0. I wrote client application (i'm using SAAJ 1.3) for testing. The response I'm getting is something like this:
<soapenv:Envelope xmlns:ns1="http://put/"
   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>soapenv:Client</faultcode>
         <faultstring>Cannot find the dispatch method</faultstring>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>First I thought there's a problem with webservice I created. So I downloaded soapui (www.soapui.org) for testing. I provided it with wsdl and endpoint. And web sevice seems to work corectly - response I got back was ok.
The strange part is: soap messages sent from soapui and from client application written by me seem to be identical. Both look like this:
<SOAP-ENV:Envelope
   xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:put="http://put">
   <SOAP-ENV:Body>
      <put:sayHello>
         <arg0>test</arg0>
      </put:sayHello>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>I even sniffed packets (WinDump) sent to application server and in both cases soap message is the same. There's only a slight difference in http headers. Here's what server log contains after receiving a soap message from my client application:
DetailsTimestamp:     2006-09-14 13:28:03.315
Log Level:      SEVERE
Logger:     javax.enterprise.resource.webservices.jaxws.server.soapmd
Name-Value Pairs:     _ThreadID=13;
Record Number:     443
Message ID:     Error in decoding SOAP Message Error in decoding SOAP Message at com.sun.xml.ws.encoding.
soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java
Complete Message
86)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.
toMessageInfo(SOAPMessageDispatcher.java:168)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher$SoapInvoker.
invoke(SOAPMessageDispatcher.java:533)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:144)
     at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
     at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.handle(WSServletDelegate.java:279)
     at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:232)
     at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:77)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
     at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:189)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doProcess(ProcessorTask.java:604)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:475)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:371)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:264)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:281)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:83)
Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot find the dispatch method
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.raiseFault(SOAPDecoder.java:662)
     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.decodeDispatchMethod(SOAPXMLDecoder.java:151)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBodyContent(SOAPDecoder.java:335)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBody(SOAPDecoder.java:325)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeEnvelope(SOAPDecoder.java:248)
     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:78)
     ... 39 moreI'm new to web services and I'm completely out of ideas what is the problem. I googled a lot but I can't find any solution. Any help would be appreciated :)
null

Are you saying I can't just write jax-ws based web service using @WebService and @WebMethod and then, on client side, write code like this?
SOAPConnectionFactory soapConnectionFactory = SOAPConnectionFactory.newInstance();
SOAPConnection connection = soapConnectionFactory.createConnection();
MessageFactory factory = MessageFactory.newInstance(SOAPConstants.SOAP_1_1_PROTOCOL);
SOAPMessage request = factory.createMessage();
// create proper message elements
URL endpoint = new URL(endpoint_url);
SOAPMessage response = connection.call(request, endpoint);
// process response
//

Soap fault, cannot find the dispatch method

I deploy the HelloService example from "The Java EE 5 Tutorial
For Sun Java System Application Server Platform Edition 9, chapter 1" to Sun Java System Application Server Platform Edition 9.0 Beta (build b32g), I tested it and it works find but when I invoked it from Servicemix-3.0 which use org.apache.servicemix.components.saaj.SaajBinding i got the following response:
<?xml version="1.0" ?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://endpoint.helloservice/"><soapenv:Body><soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>soapenv:Client</faultcode><faultstring>Cannot find the dispatch method</faultstring></soapenv:Fault></soapenv:Body></soapenv:Envelope>
Using the Monitor to look at the request message I could not see any significant difference, follows both requests:
Test:
<?xml version="1.0" ?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://endpoint.helloservice/"><soapenv:Body><ns1:sayHello><arg0>ffg</arg0></ns1:sayHello></soapenv:Body></soapenv:Envelope>
servicemix:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Envelope xmlns:ns1="http://endpoint.helloservice/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> <ns1:sayHello> <arg0>Leopoldo</arg0> </ns1:sayHello> </SOAP-ENV:Body> </SOAP-ENV:Envelope></SOAP-ENV:Body></SOAP-ENV:Envelope>
The log entry detail asociate is:
Message ID: Error in decoding SOAP Message Error in decoding SOAP Message at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java
Complete Message
86)     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.toMessageInfo(SOAPMessageDispatcher.java:168)     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher$SoapInvoker.invoke(SOAPMessageDispatcher.java:533)     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:144)     at com.sun.xml.ws.server.Tie.handle(Tie.java:88)     at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:174)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:822)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:585)     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:262)     at java.security.AccessController.doPrivileged(Native Method)     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:295)     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:178)     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:390)     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279)     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174)     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)     at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:223)     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:664)     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:571)     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:846)     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:345)     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:237)     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:240)     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot find the dispatch method     at com.sun.xml.ws.encoding.soap.SOAPDecoder.raiseFault(SOAPDecoder.java:662)     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.decodeDispatchMethod(SOAPXMLDecoder.java:151)     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBodyContent(SOAPDecoder.java:335)     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBody(SOAPDecoder.java:325)     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeEnvelope(SOAPDecoder.java:248)     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:78)     ... 40 more
I shall appreciate any help on this issue

Any luck? I'm having the same problem with the HelloService deployed on AS9. The service tests ok and the client code in the jwsdk2.0 runs ok. When I attempt to access the service using axis 1.4, the same error occurs. I'll keep working on it, and post a solution if/when this is resolved.
Client code:
* Copyright 2001-2004 The Apache Software Foundation.
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*      http://www.apache.org/licenses/LICENSE-2.0
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
import javax.xml.namespace.QName;
public class TestClient
   public static void main(String [] args) {
       try {
           String endpoint =
                    "http://localhost:9090/helloservice/HelloService";
           Service service = new Service();
           Call     call    = (Call) service.createCall();
           call.setTargetEndpointAddress( new java.net.URL(endpoint) );
           call.setOperationName(new QName("http://soapinterop.org/", "sayHello") );
           // Call to addParameter/setReturnType as described in user-guide.html
           //call.addParameter("testParam",
           //                  org.apache.axis.Constants.XSD_STRING,
           //                  javax.xml.rpc.ParameterMode.IN);
           //call.setReturnType(org.apache.axis.Constants.XSD_STRING);
           String ret = (String) call.invoke( new Object[] { "Hello!" } );
           System.out.println("Sent 'Hello!', got '" + ret + "'");
       } catch (Exception e) {
           e.printStackTrace();
}Error in decoding SOAP Message Error in decoding SOAP Message at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java
89)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.toMessageInfo(SOAPMessageDispatcher.java:187)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher$SoapInvoker.invoke(SOAPMessageDispatcher.java:571)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:145)
     at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
     at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:191)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot find the dispatch method
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.raiseFault(SOAPDecoder.java:674)
     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.decodeDispatchMethod(SOAPXMLDecoder.java:152)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBodyContent(SOAPDecoder.java:337)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBody(SOAPDecoder.java:327)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeEnvelope(SOAPDecoder.java:250)
     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:81)
     ... 31 more
Mesage:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:sayHello soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://soapinterop.org/"><ns1:arg0 xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">Hello!</ns1:arg0></ns1:sayHello></soapenv:Body></soapenv:Envelope>

UCM Web Form, help needed

Hi,
I just have started working on Oracle UCM. I am majorly stuck with web form (HCSF).
Below is the form code,
<form name="CommentsPageForm" method="POST" action="">
          <input type=hidden name="IdcService" value="SUBMIT_HTML_FORM">
          <input type=hidden name="dID" value="">
          <input type="hidden" name="RevisionSelectionMethod" value="Latest">
          <input type=hidden name="FormDocTitleScript" value="">
          <input type="hidden" name="RedirectURL" value="?IdcService=GET_FILE&dDocName=&Rendition=Web&RevisionSelectionMethod=Latest">

</form>
If I keep the dID input field then it throws an error message like following
Content Server Request Failed
Unable to submit HTML form. The HTML form is not the latest revision.
If I remove the dID input field then it throws an error message like following
Unable to execute service (null) and function computeDocID.
(System Error: Either dID must be specified or RevisionSelectionMethod must not force the choice of a dID.)
I have tried to remove and add other input fields but nothing has worked.
Please help me out with this. Please point out where I made the mistake. I copied
codepieces from Bex Huff's book, that too had same error.
Regards
Udita

hi All,
I'm facing the same issue, I have a soap request which will update the metadata field on the service call.
The request url is coded as
var requestUrl = httpCgiPath + "?IdcService=UPDATE_DOCINFO" + "&dID=" + datafileID +"&dDocName=" + datafileDocName + "&xComments=" + inputComments.value + "&dDocTitle=" + inputTitle.value + &idcToken=#active.IdcToken" + "&IsSoap=1";
When I fetch the dynamic url and tried in browser then I get following error:
Content Server Request Failed
Unable to update the field. The authorization token is invalid. It has either expired or is not appropriate for the current request.
You may need to reload an earlier page in order to proceed.
See I have added idcToken as you guys suggested still token issue :(
Any pointer for this issue will be helpful.
Thanks

Request dispatcher method--help needs

Similar Messages

Maybe you are looking for