Calling a WebService from Java Applet

Question

Hi all,
In my application I have 3 projects:
1. server - for all the business logic.
2. view - for web app.
3. swing - for applet.
In the view project I wrote a WS, and I want to call it from my applet. So I created a WS using the Jdev (10.1.3.2) wizard in the view project (I tested it and it worked fine), and in the swing project I created a proxy for this WS, tested it and it worked fine. Then I created a JAR containing the swing project with the WS proxy classes, opened the Applet and find out that I have some classes missing, so I started adding all the relevant Jars and ended with a ~13MB JAR containing all the swing project jars that in the class path for a simple Applet.
I know that I'm missing something but I dont know what. Do I really need all those Jars. Is there a simple way to call to a WS via Applet?
This is the list of all the Jars:
activation.jar
commons-logging-api.jar
commons-logging.jar
ejb.jar
http_client.jar
jaxb-api.jar
jaxb-impl.jar
jaxen.jar
jaxr-api.jar
jaxrpc-api.jar
jazncore.jar
jdom.jar
jms.jar
jta.jar
mail.jar
mdds.jar
oc4jclient.jar
ojdl2.jar
ojmisc.jar
ojpse.jar
oraclepki.jar
orajaxr.jar
orasaaj.jar
orawsdl.jar
orawsrm.jar
osdt_cert.jar
osdt_core.jar
osdt_saml.jar
osdt_wss.jar
osdt_xmlsec.jar
relaxngDatatype.jar
saaj-api.jar
saaj-impl.jar_old
servlet.jar
wsclient.jar
wsdl.jar
wssecurity.jar
wsserver.jar
xdb.jar
xml.jar
xmlparserv2.jar
xsdlib.jar
By the way at the end of all this annoying process I got the next exception:
[failed to localize] typemapping.nested.exception.initialization(javax.xml.rpc.JAXRPCException: javax.xml.soap.SOAPException: Unable to create SOAP Factory: Provider com.sun.xml.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl not found)
     at oracle.j2ee.ws.client.BasicService.createLiteralMappings(BasicService.java:282)
     at oracle.j2ee.ws.client.BasicService.createStandardTypeMappingRegistry(BasicService.java:244)
     at com.tm.view.ws.misc.runtime.WSMisc_Service_SerializerRegistry.getRegistry(WSMisc_Service_SerializerRegistry.java:26)
     at com.tm.view.ws.misc.runtime.WSMisc_Service_Impl.<init>(WSMisc_Service_Impl.java:26)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
     at java.lang.reflect.Constructor.newInstance(Unknown Source)
     at java.lang.Class.newInstance0(Unknown Source)
     at java.lang.Class.newInstance(Unknown Source)
     at oracle.j2ee.ws.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:92)
     at oracle.j2ee.ws.client.ServiceFactoryImpl.loadService(ServiceFactoryImpl.java:121)
     at com.tm.view.ws.misc.WSMiscSoap12HttpPortClient.<init>(WSMiscSoap12HttpPortClient.java:20)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
     at java.lang.reflect.Constructor.newInstance(Unknown Source)
     at java.lang.Class.newInstance0(Unknown Source)
     at java.lang.Class.newInstance(Unknown Source)
     at client.base.connectivity.ClientRequestAgent.runWS(ClientRequestAgent.java:135)
     at client.base.connectivity.ClientRequestAgent.run(ClientRequestAgent.java:44)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
Shachar

Answer 1

Try this:
1. open the webService data controll in the Data Controls section and drag the method from the webService onto the method call activity in your task flow. This will overwrite the current method property (the one which pints to your bean, make a copy of this entry if you can't reproduce it by hand). This too will create an entry in the pageDef of the method call activity.
2. reenter (or paste) the original value in the method property, so that it again points to your bean. The entry in the pageDef will remain!
3. now in the bean method you can access the method via its binding like you access any other method from the binding:
// GET A METHOD FROM PAGEDEF AND EXECUTE IT
// get the binding container
BindingContainer bindings = BindingContext.getCurrent().getCurrentBindingsEntry();
// get an Action or MethodAction
OperationBinding method = bindings.getOperationBinding("YourMethodActionNAME");
if (method == null)
// handle method not found error...
// if there are parameters to set...
Map paramsMap = method.getParamsMap();
paramsMap.put("param","value")  ;    
// execute the method
method.execute();
List errors = method.getErrors();
if (!errors.isEmpty())
   // handle errors here errors is a list of exceptions!
// no error resume normal workTimo