Using a dynamic client in a JavaBean using Tomcat

I am trying to create a JavaBean which uses a dynamic web service client which will call the web service but I keep getting the following error:
The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: javax/xml/rpc/ServiceFactory
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:256)
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
root cause
java.lang.NoClassDefFoundError: javax/xml/rpc/ServiceFactory
I have these import statements at the top:
import javax.xml.rpc.Service;
import javax.xml.rpc.ServiceFactory;
I think the problem is I need to include the service factory folder or file in Tomcat but I'm not sure where the folder is and where it goes in Tomcat. Is it a folder or jar file? Any advice is really appreciated.
Thanks

You'll need to include the following jars
jaxrpc-api.jar
jaxrpc-impl.jar
jaxrpc-spi.jar
You should find them in %JWSDP_HOME%\jaxrpc\lib

Similar Messages

How to pass in complex data to a web service using dynamic client

I wrote to dynamic client to access the complex example in weblogic 7.000, I would
like to know how I passed in a complex type to a dynamic client.

An example of using dynamic client is attached:
regards,
-manoj
"fkeita" <[email protected]> wrote in message
news:3d051775$[email protected]..
>
I wrote to dynamic client to access the complex example in weblogic 7.000,I would
like to know how I passed in a complex type to a dynamic client.[call4.jar]

How to use wsdl in dynamic client

In wls 700, I want to know how to write a dynamic client to invoke a webservice by
passing wsdl?
In the example directory, there is an example, but I would like to know how I can
customize to use my own wsdl? clientgen puts wsdl in client jar file why is that?

Hi fkeita,
If you haven't already done so, you should check out the following link in the BEA
product documentation:
http://edocs.bea.com/wls/docs70/webServices/client.html#1049007
Outside of that, you can always stayed tuned to the "dev2dev" page :-)
Regards,
Mike Wooten
"fkeita" <[email protected]> wrote:
>
Hi Mike,
Can you elaborate more how I can find the url of wsdl?
Do you know any documentation which explains the process of using dynamic
clinet?
Thanks.
"Michael Wooten" <[email protected]> wrote:
Hi fkeita,
The client.jar contains a "static" WSDL, because some folks like to avoid
making
a network (or internet) call to retrieve the "dynamic" one :-)
If you try to use "user-defined" types, with a WSDL and a "dynamic" client,
you will
experience "difficulties". This is due to the way the JAX-RPC defines the
createService()
method on the ServiceFactory class. Normally, this is the method you pass
the URL
to the WSDL you want to use. Currently, we call the WSDL parser in this
method, which
has a "side-effect" of needing to have the type mappings for your "user-defined"
types, already registered when it is called. With "stub-style" clients,
this is not
a problem (because the plumbing does this for you), but with "dynamic"ones
it doesn't.
Right now, the only real workaround is to have your client class extend
our weblogic.webservice.core.soap.SOAPElementImpl
class, as in the following code fragment:
#### START OF EXTRACT #####
import javax.xml.rpc.Call;
import javax.xml.rpc.namespace.QName;
import weblogic.webservice.core.rpc.ServiceImpl;
public class ServiceClient extends ServiceImpl
     public ServiceClient(String schemeHostPort) throws Exception
// We pass the URL for the "dynamic" WSDL in the
// first argument. The second argument is the
// path to the XML file that the <clientgen> Ant
// task recorded your typemapping info in. It is
// in your client.jar, along with the "static"
// WSDL I mentioned :-)
          super(
               (schemeHostPort == null ? "http://localhost:7001" : schemeHostPort)
+
"/mea/gateway?WSDL",
               "examples/webservices/jaxrpc/consumer/anamitra/dii/MEAGatewayService"
          //define qnames
          String targetNamespace = "http://www.bea.com/examples/MEAGateway";
          QName serviceName = new QName( targetNamespace, "MEAGatewayService" );
          QName portName = new QName( targetNamespace, "MEAGatewayServicePort");
          //create call
          Call call = super.createCall(
               portName,
               new QName(targetNamespace, "processExternalDataBatch")
          ArrayList alist = new ArrayList();
          alist.add(new String("One"));
          alist.add(new String("Two"));
          alist.add(new String("Three"));
          alist.add(new String("Four"));
          alist.add(new String("Five"));
          String result = (String)call.invoke( new Object[]{ alist } );
          System.out.println("result=" + result);
     public static void main( String[] args ) throws Exception
          System.setProperty("javax.xml.soap.MessageFactory", "weblogic.webservice.core.soap.MessageFactoryImpl");
          System.setProperty("javax.xml.rpc.ServiceFactory", "weblogic.webservice.core.rpc.ServiceFactoryImpl");
          new ServiceClient(args[0]);
//private:
     private final static boolean debug = false;
### END OF EXTRACT ###
Happy coding :-)
Regards,
Mike Wooten
"fkeita" <[email protected]> wrote:
In wls 700, I want to know how to write a dynamic client to invoke a webservice
by
passing wsdl?
In the example directory, there is an example, but I would like to know
how I can
customize to use my own wsdl? clientgen puts wsdl in client jar file why
is that?

Exception while invoking webservices using Dynamic client without WSDL

Hi All,
I am getting the below exception while invoking webservices using Dynamic client without WSDL.
javax.xml.rpc.soap.SOAPFaultException: Exception during processing: java.lang.RuntimeException: Missing license file for: WebLogic Platform 8.1 (see Fault Detail for stacktrace)
at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
at atthi.webservice.TestWSWithWSDL.main(TestWSWithWSDL.java:41)
Exception in thread "main"
Please find my source file below....
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.Service;
import javax.xml.rpc.Call;
import javax.xml.rpc.ParameterMode;
import javax.xml.namespace.QName;
public class TestWSWithoutWSDL {
public static void main(String[] args) {
try{
String address = "<WSDL's SOAP Address>";
String namespaceURI = "<namespaceURI>";
String serviceName = "<serviceName>";
String portName = "<portName>";
String ENCODING_STYLE_PROPERTY = "javax.xml.rpc.encodingstyle.namespace.uri";
String URI_ENCODING = "http://schemas.xmlsoap.org/soap/encoding/";
String agencyID = "AGN00533";
String fileName = "testWS";
String xmlString = "<?xml version=\"1.0\" encoding=\"UTF-8\"?><web-services>Sample Application</web-services>";
System.setProperty( "javax.xml.rpc.ServiceFactory", "weblogic.webservice.core.rpc.ServiceFactoryImpl");
ServiceFactory factory = ServiceFactory.newInstance();
* Create an instance of the Service with the given service QName
Service service = factory.createService(new QName(serviceName));
Call call = service.createCall(new QName(portName));
call.setTargetEndpointAddress(address);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(ENCODING_STYLE_PROPERTY, URI_ENCODING);
QName stringQName = new QName("http://www.w3.org/2001/XMLSchema", "string");
* Set operation name to invoke.
call.setOperationName(new QName(namespaceURI,"<operationName>"));
* Add parameters definitions in the call object.
call.addParameter("string", stringQName, String.class, ParameterMode.IN);
call.addParameter("string0", stringQName, String.class, ParameterMode.IN);
call.addParameter("string1", stringQName, String.class, ParameterMode.IN);
* Set definition of the return type.
call.setReturnType(stringQName);
Object[] inParams = new Object[3];
inParams[0] = new String(agencyID);
inParams[1] = new String(fileName);
inParams[2] = new String(xmlString);
String result = ((String)call.invoke(inParams)).toString();
System.out.println(result);
}catch (Exception e){
e.printStackTrace();
Please give your suggestions for the above said exception....
Thanks & Regards....

Hi All,
I am getting the below exception while invoking webservices using Dynamic client without WSDL.
javax.xml.rpc.soap.SOAPFaultException: Exception during processing: java.lang.RuntimeException: Missing license file for: WebLogic Platform 8.1 (see Fault Detail for stacktrace)
at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
at atthi.webservice.TestWSWithWSDL.main(TestWSWithWSDL.java:41)
Exception in thread "main"
Please find my source file below....
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.Service;
import javax.xml.rpc.Call;
import javax.xml.rpc.ParameterMode;
import javax.xml.namespace.QName;
public class TestWSWithoutWSDL {
public static void main(String[] args) {
try{
String address = "<WSDL's SOAP Address>";
String namespaceURI = "<namespaceURI>";
String serviceName = "<serviceName>";
String portName = "<portName>";
String ENCODING_STYLE_PROPERTY = "javax.xml.rpc.encodingstyle.namespace.uri";
String URI_ENCODING = "http://schemas.xmlsoap.org/soap/encoding/";
String agencyID = "AGN00533";
String fileName = "testWS";
String xmlString = "<?xml version=\"1.0\" encoding=\"UTF-8\"?><web-services>Sample Application</web-services>";
System.setProperty( "javax.xml.rpc.ServiceFactory", "weblogic.webservice.core.rpc.ServiceFactoryImpl");
ServiceFactory factory = ServiceFactory.newInstance();
* Create an instance of the Service with the given service QName
Service service = factory.createService(new QName(serviceName));
Call call = service.createCall(new QName(portName));
call.setTargetEndpointAddress(address);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(ENCODING_STYLE_PROPERTY, URI_ENCODING);
QName stringQName = new QName("http://www.w3.org/2001/XMLSchema", "string");
* Set operation name to invoke.
call.setOperationName(new QName(namespaceURI,"<operationName>"));
* Add parameters definitions in the call object.
call.addParameter("string", stringQName, String.class, ParameterMode.IN);
call.addParameter("string0", stringQName, String.class, ParameterMode.IN);
call.addParameter("string1", stringQName, String.class, ParameterMode.IN);
* Set definition of the return type.
call.setReturnType(stringQName);
Object[] inParams = new Object[3];
inParams[0] = new String(agencyID);
inParams[1] = new String(fileName);
inParams[2] = new String(xmlString);
String result = ((String)call.invoke(inParams)).toString();
System.out.println(result);
}catch (Exception e){
e.printStackTrace();
Please give your suggestions for the above said exception....
Thanks & Regards....

Using javabean in tomcat(unable to compile class)

Hello, I am using jakarta-tomcat-5.0.28, OS:WinXP
I am getting the following error when i use javabean in tomcat (the example is executed just fine in another web server:Blazix)
I am very new to this (JSP, Servlets and tomcat) so any help would be greatly appreciate.
THE ERROR IS:
==============================================================
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: 1 in the jsp file: /SaveName.jsp
Generated servlet error:
C:\Programs\internet\jakarta-tomcat-5.0.28\work\Catalina\localhost\JSPSession\org\apache\jsp\SaveName_jsp.java:42: cannot resolve symbol
symbol : class UserData
location: class org.apache.jsp.SaveName_jsp
UserData user = null;
^
An error occurred at line: 1 in the jsp file: /SaveName.jsp
Generated servlet error:
C:\Programs\internet\jakarta-tomcat-5.0.28\work\Catalina\localhost\JSPSession\org\apache\jsp\SaveName_jsp.java:44: cannot resolve symbol
symbol : class UserData
location: class org.apache.jsp.SaveName_jsp
user = (UserData) jspxpage_context.getAttribute("user", PageContext.SESSION_SCOPE);
^
An error occurred at line: 1 in the jsp file: /SaveName.jsp
Generated servlet error:
C:\Programs\internet\jakarta-tomcat-5.0.28\work\Catalina\localhost\JSPSession\org\apache\jsp\SaveName_jsp.java:46: cannot resolve symbol
symbol : class UserData
location: class org.apache.jsp.SaveName_jsp
user = new UserData();
^
3 errors
     org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
     org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:332)
     org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:412)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:472)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:451)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
note The full stack trace of the root cause is available in the Apache Tomcat/5.0.28 logs.
===============================================================
ERROR END
I use the folowing files:
GetName.html
SaveName.jsp
NextPage.jsp
UserData.java
My Dir Structure is:
/JSPSession
    GetName.html
     SaveName.jsp
     NextPage.jsp
   /WEB-INF
      /classes
         UserData.java
         UserData.class
   /libThe Code for the files is:
GetName.html
<HTML>
<BODY>
<FORM METHOD=POST ACTION="SaveName.jsp">
What's your name? <INPUT TYPE=TEXT NAME=username SIZE=20><BR>
What's your e-mail address? <INPUT TYPE=TEXT NAME=email SIZE=20><BR>
What's your age? <INPUT TYPE=TEXT NAME=age SIZE=4>
<P><INPUT TYPE=SUBMIT>
</FORM>
</BODY>
</HTML>---------------------------------------------------------------------------------------------------
SaveName.jsp
<jsp:useBean id="user" class="UserData" scope="session"/>
<jsp:setProperty name="user" property="*"/>
<HTML>
<BODY>
<A HREF="NextPage.jsp">Continue</A>
</BODY>
</HTML>-----------------------------------------------------------------------------------------------------
NextPage.jsp
<jsp:useBean id="user" class="UserData" scope="session"/>
<HTML>
<BODY>
You entered<BR>
Name: <%= user.getUsername() %><BR>
Email: <%= user.getEmail() %><BR>
Age: <%= user.getAge() %><BR>
</BODY>
</HTML>------------------------------------------------------------------------------------------------------------
UserData.java
public class UserData {
    String username;
    String email;
    int age;
    public void setUsername( String value ) {
        username = value;
    public void setEmail( String value ) {
        email = value;
    public void setAge( int value ) {
        age = value;
    public String getUsername() { return username; }
    public String getEmail() { return email; }
    public int getAge() { return age; }
}

A very common question. Tomcat dislikes classes which are not packaged. So, add a package statement in your UserBean.java
package beans; // or something like thatand then place the compiled class file UserBean.class into WEB-INF/classes/beans.
Put the import statement into the JSP accordingly and try again.
***Annie***

Dynamically set database url using tomcat jndi

By using Tomcat JNDI, database url information needs to be hardcoded in server.xml file according to the documentation. Is there a way to change the URL information in the code dynamically if necessary?
And also we need multiple connection pools and the connection information about those pools are only known during run time. So the TOMCAT JNDI is still the right way to go???
By the way, does anybody ever use tomcat DBCP package to get datasource and set url dynamically?
Thanks in advance.

By using Tomcat JNDI, database url information needs
to be hardcoded in server.xml file according to the
documentation. Is there a way to change the URL
information in the code dynamically if necessary?
Not that I know of.
And also we need multiple connection pools and the
connection information about those pools are only
known during run time. So the TOMCAT JNDI is still the
right way to go???
I think so. Since it's just a JDNI lookup, perhaps you can set up multiple data sources and decide on the lookup name at the last minute, depending on circumstances. That might work. I haven't tried it myself. - MOD
By the way, does anybody ever use tomcat DBCP package
to get datasource and set url dynamically?
Thanks in advance.

Invoking a web service from dynamic client in weblogic 7

Is it possible to invoke a webservice from dynamic client in weblogic 7. Because i tried and it doesn't work. But it works with WL 8.1
I don't see any samples on the net for weblogic 7.

Hello rss,
If you want to invoke a web service from a JCD you will have to build the SOAP message using JAX-RPC or AXIS and then programmatically creat an HTTP connection.
Or you can leverage the HTTP(S) eWay and then you only have to build the SOAP message.
Or use eInsight. You can import a WSDL into eInsight and eInsight will offer you a business process Activity to invoke the web service operations defined in the WSDL.

Dynamic client in weblogic 9

I have created a dynamic client to invoke a Web Service that uses non-built-in data types as parameter and return type in weblogic8.1 using ant task autotype and JAX-RPC. Now we are moving toward weblogic 9.0 but i could find equivalent way of creating dynamic client. So how can we create dynamic client in weblogic 9.0? I would also like to mention that our clients are standalone client. Thanks in advance for your help.

Thanks for your response.My requirement is, if we change interface means return object or parameters then we don't want to do redeployment of client jar. we want if there is any changes to the interface then it should be taken automatically.

Dynamic client problem

I modified the EchoDom example (http://webservice.bea.com/dom.zip) client to be
dynamic (with WSDL) and deployed the service as a document type service. The ear
file is deployed correctly and I am able to execute the service from the URL without
any errors. However when I run the dynamic client, I see the following exception
trace. I see a similar error (serialization fails on class weblogic.apache.xerces.dom.DocumentImpl)
when I deploy the service as rpc. What am I doing incorrectly? Please help.
Sriram
run:
[java] javax.xml.rpc.JAXRPCException: failed to invoke operation 'echoDom
' due to an error in the soap layer (SAAJ); nested exception is: Message[ failed
to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.Se
rializationException: mapping lookup failure. class=interface javax.xml.soap.SOA
PElement class context=TypedClassContext{schemaType=['http://examples.org']:echo
Dom}]StackTrace[
[java]
[java] javax.xml.soap.SOAPException: failed to serialize interface javax.x
ml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping
l
ookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedCla
ssContext{schemaType=['http://examples.org']:echoDom}
[java] at weblogic.webservice.core.DefaultPart.invokeSerializer(Default
Part.java:328)
[java] at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:2
97)
[java] at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.
java:619)
[java] at weblogic.webservice.core.ClientDispatcher.send(ClientDispatch
er.java:206)
[java] at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDisp
atcher.java:143)
[java] at weblogic.webservice.core.DefaultOperation.invoke(DefaultOpera
tion.java:444)
[java] at weblogic.webservice.core.DefaultOperation.invoke(DefaultOpera
tion.java:430)
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:53
9)
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:39
2)
[java] at examples.dom.Client.diiCall(Client.java:132)
[java] at examples.dom.Client.main(Client.java:164)
[java] Caused by: weblogic.xml.schema.binding.SerializationException: mappi
ng lookup failure. class=interface javax.xml.soap.SOAPElement class context=Type
dClassContext{schemaType=['http://examples.org']:echoDom}
[java] at weblogic.xml.schema.binding.RuntimeUtils.lookup_serializer(Ru
ntimeUtils.java:151)
[java] at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(Ru
ntimeUtils.java:187)
[java] at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(Ru
ntimeUtils.java:174)
[java] at weblogic.webservice.core.DefaultPart.invokeSerializer(Default
Part.java:324)
[java] ... 10 more
[java] ]
[java]
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:55
9)
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:39
2)
[java] at examples.dom.Client.diiCall(Client.java:132)
[java] at examples.dom.Client.main(Client.java:164)
[java] Exception in thread "main"
[java] Java Result: 1

Hi Bruce,
I made the changes that you suggested. It didn't work. I still see the same deserialization
exception.
Sriram
Bruce Stephens <[email protected]> wrote:
Hi,
Try this format in your dynamic client:
call.setProperty("javax.xml.rpc.security.auth.username", "username");
call.setProperty("javax.xml.rpc.security.auth.password", "password");
HTHs,
Bruce
Sriram Chavali wrote:
If I had a weblogic security role enforcement in place for my WS EJB,how do I
pass the user credentials from a dynamic client? I set the USERNAME_PROPERTYand
PASSWORD_PROPERTY properties on the Call, but I see a deserializationerror on
the response and the SOAPElement interface.
A static client works fine when I pass the user credentials from thegetMyWSPort(String,
String) call.
Please help,
Sriram
"Sriram Chavali" <[email protected]> wrote:
Hi Bruce,
It worked perfectly.
Thanks for your help
Sriram
Bruce Stephens <[email protected]> wrote:
Hi Sriram,
OK, we are getting close. It looks like the problem is with the
helloComplexWorldResponse so looking at the client, I would change
the
invoke to look something like this:
String result = (String) call.invoke(new Object[] {doc});
If that still has problems, then try it without the return, i.e.make
it
a void return in the HelloWorldServiceEJB.java and go from there.
Regards,
Bruce
Sriram Chavali wrote:
Hi Brue,
Your example works fine for me. I am building an EJB implementationthat follows
your example where I see the error. The attached zip file has the
server
and client
(dynamic, which follows your example). The build file is build1.xml.
Thanks
Sriram
Bruce Stephens <[email protected]> wrote:
Hi Sriram,
hmmm...the sample I provided sends a Document with a dynamic client,
so
I'm confused as to where/why you are still seeing the same failure
as
the original post. Would you go back and look carefully at the
client
code (ClientHotelDyn.java) and note two important features:
1) adding the call.setProperty(Call.OPERATION_STYLE_PROPERTY,
"document");
2) adding the typemapping for the Document
If you are still experiencing problems, please post your codeand/or
open a dialog with our super support team: http://support.bea.com
or
[email protected]
Thanks,
Bruce
Hi Bruce,
The consumers for the service that I am building will be non-java
clients.
I wish
to demonstrate a reference implementation for them without using
the
generated
client side classes and hence the dynamic client.
Thanks for your example code. It worked fine. Just to add a
twist
to
your latest
example, I modified sample10 from Manoj's website (an EJB example)to accept an
org.w3c.dom.Document. I took your build file and tailored it
to
building
the sample10
and it worked fine for a static client, however when I modified
the
client to
be dynamic, I see the trace pasted at the end of this message.
Any
suggestions
run:
[java] javax.xml.rpc.JAXRPCException: failed to invoke
operation
'helloComp
lexWorld' due to an error in the soap layer (SAAJ); nested exceptionis: Message
[failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException:
mapping lookup failure for xml type ['http://www.bea.com/servers/wls70/samples/
examples/webservices/basic/javaclass']:helloComplexWorldResponse
and
java interf
ace javax.xml.soap.SOAPElement]StackTrace[
[java]
[java] javax.xml.soap.SOAPException: failed to deserialize
xml:weblogic.xml
schema.binding.DeserializationException: mapping lookup failurefor
xml type
http://www.bea.com/servers/wls70/samples/examples/webservices/basic/javaclass']:
helloComplexWorldResponse and java interface javax.xml.soap.SOAPElement
[java] at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:
389)
[java] at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage
java:458)
[java] at weblogic.webservice.core.ClientDispatcher.receive(ClientDispa
tcher.java:297)
[java] at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDisp
atcher.java:144)
[java] at weblogic.webservice.core.DefaultOperation.invoke(DefaultOpera
tion.java:444)
[java] at weblogic.webservice.core.DefaultOperation.invoke(DefaultOpera
tion.java:430)
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:53
9)
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:39
2)
[java] at tutorial.sample10.client.Main.<init>(Main.java:105)
[java] at tutorial.sample10.client.Main.main(Main.java:40)
[java] Caused by: weblogic.xml.schema.binding.DeserializationException:map
ping lookup failure for xml type ['http://www.bea.com/servers/wls70/samples/exam
ples/webservices/basic/javaclass']:helloComplexWorldResponse
and
java
interface
javax.xml.soap.SOAPElement
[java] at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(
RuntimeUtils.java:325)
[java] at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:
384)
[java] ... 9 more
[java] ]
[java]
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:55
9)
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:39
2)
[java] at tutorial.sample10.client.Main.<init>(Main.java:105)
[java] at tutorial.sample10.client.Main.main(Main.java:40)
BUILD SUCCESSFUL
Thanks
Sriram
Bruce Stephens <[email protected]> wrote:
Hi Sriram,
Give this example a spin and see if it fits your needs.
Just curious, why do you need to have a dynamic client?
Thanks,
Bruce
Sriram Chavali wrote:
I am using WLS 8.1 on Windows XP.
Sriram
"Sriram Chavali" <[email protected]> wrote:
I modified the EchoDom example (http://webservice.bea.com/dom.zip)
client
to be
dynamic (with WSDL) and deployed the service as a document
type
service.
The ear
file is deployed correctly and I am able to execute the
service
from
the URL without
any errors. However when I run the dynamic client, I see
the
following
exception
trace. I see a similar error (serialization fails on class
weblogic.apache.xerces.dom.DocumentImpl)
when I deploy the service as rpc. What am I doing incorrectly?Please
help.
Sriram
run:
[java] javax.xml.rpc.JAXRPCException: failed to invoke
operation
'echoDom
' due to an error in the soap layer (SAAJ); nested exceptionis:
Message[
failed
to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.Se
rializationException: mapping lookup failure. class=interface
javax.xml.soap.SOA
PElement class context=TypedClassContext{schemaType=['http://examples.org']:echo
Dom}]StackTrace[
[java]
[java] javax.xml.soap.SOAPException: failed to serializeinterface
javax.x
ml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException:
mapping
l
ookup failure. class=interface javax.xml.soap.SOAPElement
class
context=TypedCla
ssContext{schemaType=['http://examples.org']:echoDom}
[java] at weblogic.webservice.core.DefaultPart.invokeSerializer(Default
Part.java:328)
[java] at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:2
97)
[java] at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.
java:619)
[java] at weblogic.webservice.core.ClientDispatcher.send(ClientDispatch
er.java:206)
[java] at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDisp
atcher.java:143)
[java] at weblogic.webservice.core.DefaultOperation.invoke(DefaultOpera
tion.java:444)
[java] at weblogic.webservice.core.DefaultOperation.invoke(DefaultOpera
tion.java:430)
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:53
9)
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:39
2)
[java] at examples.dom.Client.diiCall(Client.java:132)
[java] at examples.dom.Client.main(Client.java:164)
[java] Caused by: weblogic.xml.schema.binding.SerializationException:
mappi
ng lookup failure. class=interface javax.xml.soap.SOAPElement
class
context=Type
dClassContext{schemaType=['http://examples.org']:echoDom}
[java] at weblogic.xml.schema.binding.RuntimeUtils.lookup_serializer(Ru
ntimeUtils.java:151)
[java] at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(Ru
ntimeUtils.java:187)
[java] at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(Ru
ntimeUtils.java:174)
[java] at weblogic.webservice.core.DefaultPart.invokeSerializer(Default
Part.java:324)
[java] ... 10 more
[java] ]
[java]
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:55
9)
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:39
2)
[java] at examples.dom.Client.diiCall(Client.java:132)
[java] at examples.dom.Client.main(Client.java:164)
[java] Exception in thread "main"
[java] Java Result: 1
Name: sample10.zip
sample10.zip Type: Zip Compressed Data (application/x-zip-compressed)
Encoding: base64

Workshop : webservices : Dynamic Client

I am using WebLogic Workshop 8.1 to crate a test Web Service.
I have created a webservice with two methods to support
1. SOAP RPC call
2. SOAP document call
This is working fine with the test harness provided by workshop.
I have written two Dynamic clients to test this web service (one for soap RPC
type call and another for soap "document" type call).
The SOAP RPC type call dynamic client is working fine.
The SOAP "document" type call dynamic client is throwing the following exception
javax.xml.rpc.JAXRPCException: failed to invoke operation 'ReservationRQ' due
to an error in the soap layer (SAAJ); nested exception is: Message[ failed to
serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException:
mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.openuri.org/']:ReservationRQ}]StackTrace[
javax.xml.soap.SOAPException: failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException:
mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.openuri.org/']:ReservationRQ}
at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:328)
at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:297)
at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:619)
at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:206)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:444)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:430)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:539)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:392)
at TestWSClientDoc.main(TestWSClientDoc.java:74)
Caused by: weblogic.xml.schema.binding.SerializationException: mapping lookup
failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.openuri.org/']:ReservationRQ}
at weblogic.xml.schema.binding.RuntimeUtils.lookup_serializer(RuntimeUtils.java:151)
at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:187)
at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:174)
at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:324)
... 9 more
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:559)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:392)
at TestWSClientDoc.main(TestWSClientDoc.java:74)
Failed to send doc.
I have attached a zip file conatining the following files with this.
TestWebService.jws - web service code
TestWSClientDoc.java - dynamic client to test "document" type call
TestWSClientRpc.java - dynamic client to test "rpc" type call
test.xml â€“ test document.
Could you please let me know here am I doing wrong?
Thanks
Purna
[webservice.zip]

Hi Mike,
Your code worked for me. I will go from here.
Thanks,
Purna
"Michael Wooten" <[email protected]> wrote:
>
>
>
Hi Purna,
I have attached the source for a DII client that I think may work for
you.
It contains comments that describe what I think is causing the problem
you are
having in WLW 8.1, because I was having the same problem in WLW 7.0 :-)
You'll need to have %WL_HOME%\server\lib\webservices.jar in the client's
CLASSPATH,
because that's where the ElementCodec (and DocumentCodec) is. Let me
know if it
works.
Regards,
Mike Wooten
"Purna" <[email protected]> wrote:
Hi Bruce,
The example you provided is working fine. In fact I had used your example
to write
the Dynamic client.
Background on my requirement:
I had created a web service out of my application, which has set ofenterprise
java beans. The web service is working fine with WLW test harness and
static client.
I want to write a Dynamic Cient for this web service. Inside this web
service
the methods are expecting a document object. I am getting the exceptions
for
the Dynamic Client.
Please find the attached zip file containg the wsdl files.
It would be great if you can provide a working document style web service
(*.jws
file - generated from WL workshop) and Dynamic Client code.
Thanks,
Purna
Bruce Stephens <[email protected]> wrote:
Hi,
I would suggest trying to narrow down the problem. I suspect that there
are server side issues. Try going back to this example and making
sure
it works OK.
http://newsgroups.bea.com/cgi-bin/dnewsweb/domdocdyn.zip?cmd=article&group=weblogic.developer.interest.webservices&item=4127&part=2&utag=&/domdocdyn.zip
Spin up WLW and compare the two WSDLs. I suspect there will be some
differences that could be causing your problem.
Could you tell us a bit about your goal?
Thanks,
Bruce
Purna wrote:
Hi Bruce,
I have removed the "rpc" style method and now I have only "document"style method,
but still I am getting the same exception with Dynamic Client.
Do you have any suggetions?.
Thanks,
Purna
Bruce Stephens <[email protected]> wrote:
Hello,
Take a look at "style" attribute:
http://edocs.bea.com/wls/docs81/webserv/wsp.html#1015120 in the
web-service element, it states the "style" attribute applies to
an
entire Web Service, all operations specified in a single <web-service>
element must be either RPC-oriented or documented-oriented; WebLogic
Server does not support mixing the two styles within the same Web
Service.
Hope this helps,
Bruce
purna wrote:
I am using WebLogic Workshop 8.1 to crate a test Web Service.
I have created a webservice with two methods to support
1. SOAP RPC call
2. SOAP document call
This is working fine with the test harness provided by workshop.
I have written two Dynamic clients to test this web service (one
for
soap RPC
type call and another for soap "document" type call).
The SOAP RPC type call dynamic client is working fine.
The SOAP "document" type call dynamic client is throwing the followingexception
javax.xml.rpc.JAXRPCException: failed to invoke operation 'ReservationRQ'due
to an error in the soap layer (SAAJ); nested exception is: Message[failed to
serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException:
mapping lookup failure. class=interface javax.xml.soap.SOAPElement
class context=TypedClassContext{schemaType=['http://www.openuri.org/']:ReservationRQ}]StackTrace[
javax.xml.soap.SOAPException: failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException:
mapping lookup failure. class=interface javax.xml.soap.SOAPElement
class context=TypedClassContext{schemaType=['http://www.openuri.org/']:ReservationRQ}
at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:328)
at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:297)
at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:619)
at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:206)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:444)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:430)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:539)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:392)
at TestWSClientDoc.main(TestWSClientDoc.java:74)
Caused by: weblogic.xml.schema.binding.SerializationException:
mapping
lookup
failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.openuri.org/']:ReservationRQ}
at weblogic.xml.schema.binding.RuntimeUtils.lookup_serializer(RuntimeUtils.java:151)
at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:187)
at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:174)
at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:324)
... 9 more
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:559)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:392)
at TestWSClientDoc.main(TestWSClientDoc.java:74)
Failed to send doc.
I have attached a zip file conatining the following files with
this.
TestWebService.jws - web service code
TestWSClientDoc.java - dynamic client to test "document" type
call
TestWSClientRpc.java - dynamic client to test "rpc" type call
test.xml â€“ test document.
Could you please let me know here am I doing wrong?
Thanks
Purna
Name: webservice.zip
webservice.zip Type: Zip Compressed Data (application/x-zip-compressed)
Encoding: base64

Dynamic client invocation (6.1) question

Hi
I am invoking an external webservice using a WL6.1 based client.
Since I have the WSDL, I use WebSeviceProxy.getServiceAt(wsdl)
to get the proxy based on the given wsdl URL. The external
webservice has the following signature :
void notification(Measurement[])
Measurement { long timestamp; double value }
In my client code, I have my own test.telemetry.Measurement
class. In the WSDL, the Measurement datastructure's QName is
http://www.6d.com/Measurement.
I am thinking that the WL webservices machinery will be able
to serialize my test.telemetry.Measurement object into the WSDL
specificed format for the Measurement datastructure. But that
doesn't seem to be happening - the QName in the serialization
is java:test.telemetry.Measurement; and hence the external
endpoint doesn't recogonize it.
I guess my above assumption is wrong ? (WHY ?)
Any workarounds ? Note that I have to use the dynamic client
mode, not the static mode.
thanx
-john

Hi John,
I'm don't think that you will be able to get WLS 6.1's Web Services Platform (i.e.
SOAP processor, WSDL processor, etc), to use your Measurement Java Bean in its
serialization/deserialization, unless the namespace prefix for it (the Measurement
complex type in the WSDL) is "java:" in the WSDL :-)
WLS 6.1 assumes that namespace URIs that start with "java:" are Java package names,
and that the corresponding elements are Java classes (i.e. <xsd:element name="Measurement">)
in that Java package. You might be able to get WLS 6.1 to use your Measurement
Java Bean using public methods on the SoapEncodingCodec class, but not if you
use the WSDL. It will still be a dynamic client. It just won't start with using
the WSDL to define stuff for you.
Regards,
Mike Wooten
"john" <[email protected]> wrote:
>
Hi
I am invoking an external webservice using a WL6.1 based client.
Since I have the WSDL, I use WebSeviceProxy.getServiceAt(wsdl)
to get the proxy based on the given wsdl URL. The external
webservice has the following signature :
void notification(Measurement[])
Measurement { long timestamp; double value }
In my client code, I have my own test.telemetry.Measurement
class. In the WSDL, the Measurement datastructure's QName is
http://www.6d.com/Measurement.
I am thinking that the WL webservices machinery will be able
to serialize my test.telemetry.Measurement object into the WSDL
specificed format for the Measurement datastructure. But that
doesn't seem to be happening - the QName in the serialization
is java:test.telemetry.Measurement; and hence the external
endpoint doesn't recogonize it.
I guess my above assumption is wrong ? (WHY ?)
Any workarounds ? Note that I have to use the dynamic client
mode, not the static mode.
thanx
-john

Out parameters and a dynamic client

In the 7.0 manuals for web services (http://e-docs.bea.com/wls/docs70/webServices/client.html#1011066)
there are two examples, one for dynamic client, the other for out parameters. My
question is there a way to use out parameters WITH the dynamic client or do you need
a stub for it?
Larry

sachin
1) make sure there is no Optional Redirect defined on the OK button. That is, make sure the page is really submitted.
2) in the PL/SQL body generating the query, print out the query using htp.p() so you get to see it and test it.
3) use the session state link in the developer toolbar in conjunction with the technique in step 2) to debug your query
Maybe the report region is refreshing, but it just isn't returning any results.
Sergio

Dynamic Client Exception - Need help

Hi,
Need help.......
I am getting following exception, when I run
my dynamic client.
Attached below is my code as well as WSDL.
Thanks in advance..
Regards
-Shakeel
[java] javax.xml.rpc.JAXRPCException: failed to invoke operation 'Print' du
e to an error in the soap layer (SAAJ); nested exception is: Message[ failed to
serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.Serial
izationException: mapping lookup failure. class=interface javax.xml.soap.SOAPEle
ment class context=TypedClassContext{schemaType=['http://learn.technologies.com/
WS']:PrintRequest}]StackTrace[
[java] javax.xml.soap.SOAPException: failed to serialize interface javax.x
ml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping l
ookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedCla
ssContext{schemaType=['http://learn.technologies.com/WS']:PrintRequest}
[java] at weblogic.webservice.core.DefaultPart.invokeSerializer(Default
Part.java:328)
CODE
// Setup the global SAAJ message factory
System.setProperty("javax.xml.soap.MessageFactory", "weblogic.webservice.core.soap.MessageFactoryImpl");
// Setup the global JAX-RPC service factory
System.setProperty( "javax.xml.rpc.ServiceFactory", "weblogic.webservice.core.rpc.ServiceFactoryImpl");
ServiceFactory serviceFactory = ServiceFactory.newInstance();
// define qnames
String targetNamespace = "http://learn.technologies.com/WS";
QName serviceName = new QName(targetNamespace, "PersonalDataService");
QName portName = new QName(targetNamespace, "PersonalDataInterface");
QName operationName = new QName(targetNamespace, "Print");
URL wsdlLocation = new URL("http://localhost:7001/simpleexample/PersonalDataInterface?WSDL");
// create service
Service service = serviceFactory.createService(wsdlLocation, serviceName);
// create call
Call call = service.createCall(portName, operationName);
WSDL
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://learn.technologies.com/WS"
targetNamespace="http://learn.technologies.com/WS">
<types>
<schema targetNamespace="http://learn.technologies.com/WS"
xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<element name="PrintRequest">
<complexType>
<sequence>
<element name="firstName" type="string"/>
<element name="age" type="int"/>
<element name="salary" type="double"/>
</sequence>
</complexType>
</element>
<element name="PrintResponse">
<complexType>
<sequence/>
</complexType>
</element>
<element name="QueryRequest">
<complexType>
<sequence>
<element name="id" type="double"/>
</sequence>
</complexType>
</element>
<element name="QueryResponse">
<complexType>
<sequence>
<element name="return" type="tns:ArrayOfPersonalData"/>
</sequence>
</complexType>
</element>
<complexType name="PersonalData">
          <sequence>
          <element name="name" type="string"/>
          <element name="age" type="int"/>
          <element name="salary" type="double"/>
          </sequence>
</complexType>
<complexType name="ArrayOfPersonalData">
          <sequence>
          <element maxOccurs="unbounded" minOccurs="0" name="Item" type="tns:PersonalData"/>
          </sequence>
</complexType>
</schema>
</types>
     <message name="PrintRequestMessage">
     <part name="PrintRequest" element="tns:PrintRequest"/>
     </message>
     <message name="PrintResponseMessage">
     <part name="PrintResponse" element="tns:PrintResponse"/>
     </message>
     <message name="QueryRequestMessage">
     <part name="QueryRequest" element="tns:QueryRequest"/>
     </message>
     <message name="QueryResponseMessage">
     <part name="QueryResponse" element="tns:QueryResponse"/>
     </message>
     <portType name="PersonalDataInterface">
          <operation name="Print">
               <input name="PrintRequestMessage" message="tns:PrintRequestMessage"/>
          <output name="PrintResponseMessage" message="tns:PrintResponseMessage"/>
          </operation>
          <operation name="Query">
               <input name="QueryRequestMessage" message="tns:QueryRequestMessage"/>
               <output name="QueryResponseMessage" message="tns:QueryResponseMessage"/>
          </operation>
     </portType>
     <binding name="PersonalDataIntfBinding" type="tns:PersonalDataInterface">
     <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
     <operation name="Print">
          <soap:operation/>
          <input> <soap:body use="literal"/> </input>
          <output> <soap:body use="literal"/> </output>
     </operation>
     <operation name="Query">
          <soap:operation/>
          <input> <soap:body use="literal"/> </input>
          <output> <soap:body use="literal"/> </output>
     </operation>
     </binding>
     <service name="PersonalDataService">
     <port name="PersonalDataInterface" binding="tns:PersonalDataIntfBinding">
          <soap:address location="http://localhost:7001/simpleexample/PersonalDataInterface"/>
     </port>
     </service>
</definitions>

Exception is coming on following line (forgot
to paste in first post)
     Object result = call.invoke(new Object[] { "Shakeel", new Integer (30), new Double(2000) });

Web service dynamic client property for Call

Hi, Hope this is the right forum for web service questions. The oracle document (6 Developing JAX-RPC Web Service Clients) on web service client only shows the stub and properties can be set in stub. I would like to use dynamic client. Can Call object have some properties? what are they?
Thanks

Can any one please help :-(

Unable to load Applet in JSP using Tomcat 5.5.12

Hi
I am aunable to applet in jsp using Tomcat 5.5.12 and JRE 1.5. Below is the code that I am using
                                   <applet
                                   codebase = "."
                                   archive = "WebPOSApplet.jar"
                                   code = "webposprint.WPMainApplet.class"
                                   name = "Trans Applet"
                                   width = "450"
                                   height = "115"
                                   hspace = "0"
                                   vspace = "0"
                                   align = "middle"
                                   >
<param name = "redirectInfo" value = "SearchProducts.do">
                                   </applet>
<%/*%>
<OBJECT
                                   classid = "clsid:CAFEEFAC-0014-0002-0000-ABCDEFFEDCBA"
                                   codebase = "http://java.sun.com/products/plugin/autodl/jinstall-1_4_2-windows-i586.cab#Version=1,4,2,0"
                                   WIDTH = 450 HEIGHT = 115 >
<PARAM NAME = CODE VALUE = webposprint.WPMainApplet.class>
<PARAM NAME = archive VALUE = WebPOSApplet.jar>
<PARAM NAME = "type" VALUE = "application/x-java-applet;jpi-version=1.4.2">
<param name = "redirectInfo" value = "SearchProducts.do">
<PARAM NAME = "scriptable" VALUE = "false">
<PARAM NAME = model VALUE=models/buckminsterfullerine.xyz>
<embed width="450" height="115" code="webposprint.WPMainApplet.class" archive="WebPOSApplet.jar" type="application/x-java-applet;jpi-version=1.4.2" redirectinfo="SearchProducts.do" scriptable="false" model="models/buckminsterfullerine.xyz" src="webposprint.WPMainApplet.class">
</embed> <COMMENT> <EMBED
                                   type = "application/x-java-applet;jpi-version=1.4.2" \
                                   CODE = webposprint.WPMainApplet.class\
                                             archive = WebPOSApplet.jar\
                                   WIDTH = 373 \
                                   HEIGHT = 167 \
                                   model =models/buckminsterfullerine.xyz \
                                        scriptable = false \
                                        pluginspage = "http://java.sun.com/products/plugin/index.html#download"> <NOEMBED>
alt="Your browser understands the <APPLET>
tag but isn't running the applet, for some reason."
Your browser is completely ignoring the <APPLET>
tag! </NOEMBED> </EMBED> </COMMENT>
</OBJECT>
<%*/%>
This code doesn't seems working with Tomcat 5.5.12. I works fine with Tomcat 4.1.31
Please help
Thanks

Applets run client side - which means the relevant class files need to be downloaded to the client.
Anything under the WEB-INF directory is not directly accessible by the client. Nothing under WEB-INF can be downloaded.
ergo, specifying the WEB-INF directory as part of your applet codebase is a bad idea.
I would suggest try copying the applet classes from under WEB-INF to some other place in your application.
Also, you should probably specify the full class name of your Applet in the plugin tag.
<%@ page import="com.util.MyApplet" %>
<jsp:plugin type="applet" code="com.util.MyApplet" codebase="/classes" width="250" height="100" jreversion="1.6">
     <jsp:fallback>
          <B>Unable to start plugin!</B>
     </jsp:fallback>
</jsp:plugin>cheers,
evnafets

Using a dynamic client in a JavaBean using Tomcat

Similar Messages

Maybe you are looking for