Extra JAR's for Apache Soap w/ JDK 1.4.1

Hi Folks,
I've seen all kinds of confusing info about what additional packages you need to have available for the Soap JAR from apache.org to work with various JDK's.
Does anyone know what's required beyond the basic JDK JAR's that are part of 1.4.1? Presumably, I need pieces of the WSDP, but if anyone knows what, I'd appreciate hearing it.
Do you have to adjust the classloader so that Tomcat gets the right XML parser loaded (as I've seen mentioned in various places for earlier versions of the JDK)?
Thanks much,
John

Y'all missed out on the Duke Dollars!
The full install of Tomcat 4.1.18 includes the following XML
Parser JAR:
jaxp-parser-impl.jar (found in $CATALINA_HOME/common/endorsed)
When I replaced this with the Xerces parser JAR from the Sun Web
Services Development Pack
jswdp-1_0_01/common/endorsed/xercesImpl.jar
The Soap server started up happily.
So, if you're using a recent version of Tomcat, that's all you need to replace.
HTH someone save the hours it took me to figure it out!
JMC

Similar Messages

Apache SOAP 2.2 - Weblogic 6.1SP2

Hi,
Has anyone managed to get Apache SOAP working with Weblogic 6x?
I can get everything up and running, but for some reason the classloader
for the web application (ie; the actual Apache SOAP app) doesn't load the
classes in my jar file containing the EJB files, serializers, etc.
Therefore whenever I make a SOAP request I get a server side error reported
via SOAP that some class or another (one of my own ones) cannot be found.
I can cure this by sticking my jar file in the server's classpath - however
this isn't great as it means the JVM's classloader is picking everything up
and I lose the ability to redeploy.
Any ideas? In the absence of any other information it would seem that
Weblogic's classloaders are buggy...
Cheers,
Trev

Hi Trev,
Let's recap here:
1. You are deploying the .war file for Apache SOAP, into WLS 6.1 SP2, right? If
yes, you copied the .war file into the $WL_HOME/config/examples/applications directory,
or something similar, right?
2. It (some class or classes in soap.war) couldn't find the classes for your EJB
so, you "unwarred" it, created a WEB-INF/lib directory, and copied the .jar for
your EJB into that directory. Then you re-jarred the soap.war, right? If so, did
you put a <ejb-ref> element in the web.xml (for soap.war), so it (the SOAP webapp)
would know about the ejb?
The <ejb-ref> should look something like this:
<ejb-ref>
<description></description>
<ejb-ref-name>examples.webservices.security.PhoneBookService</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>examples.webservices.security.PhoneBookServiceHome</home>
<remote>examples.webservices.security.PhoneBookService</remote>
</ejb-ref>
You'd also need to create a WEB-INF/weblogic.xml file and put something like this
in it:
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>examples.webservices.security.PhoneBookService</ejb-ref-name>
<jndi-name>examples.webservices.security.PhoneBookService</jndi-name>
</ejb-reference-description>
</reference-descriptor>
But, I would do any of this because your EJB doesn't have "diddly squat" to do
with Apache SOAP ;-) The Apache SOAP web app is a "standalone" thing, right? You
want to use your EJB "with it", not be part "of it" right? Exactly! So, let's
abandon that route...
3. Next, you tried to turn the Apache SOAP Web Application (.war) into the Apache
SOAP Enterprise Application (.ear). I'm assuming that you created a META-INF/application.xml
that looked something like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application
1.2//EN' 'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
<application>
<display-name>Apache SOAP 2.2</display-name>
<module>
<web>
<web-uri>soap.war</web-uri>
<context-root>/soap</context-root>
</web>
</module>
<module>
<ejb>{name of the .jar for your ejb}</ejb>
</module>
</application>
But, you didn't create the <ejb-ref> stuff in #2 above. Again, I don't think it
makes a lot of sense to put "your EJB" in the "Apache SOAP" Enterprise application
What's going on here (the Apache SOAP code not being able to find your EJB classes)
is "expected behavior" as far as the BEA docs go. Everyone I know (including me!)
that deploys the Apache SOAP web app in WebLogic, creates a .jar that contains
a copy of all the remote (and home) interface classes that the rpcrouter servlet
will call, and puts this in the -classpath used to start WebLogic. That way, it
(the Apache SOAP web app) will be able to find them. I don't put the jar for the
EJB in the -classpath, though. To be honest, I don't use Apache SOAP because it
doesn't support WSDL yet ;-)
Regards,
Mike Wooten
"ts" <[email protected]> wrote:
Hi Mike,
Cheers for the response. I've read the documentation you've linked to
and I
understand how WLS performs class loading.
However, the documentation implies that I could either;
A) Package the SOAP war file together with my EJB jar file in an EAR
file
and deploy, and the SOAP web app would subsequently be able to reference
classes/beans. (Ref: "Although you could deploy the .war and .jar files
separately, deploying them together in an .ear file produces a classloader
arrangement that allows the servlets and JSPs to find the EJB classes.")
B) Simply place my EJB jar file in the WEB-INF\lib subdirectory of the
deployed SOAP web app. (Ref: J2EE specification).
In fact, neither of these work, and I am forced to include the EJB jar
in
the server's classpath.
Surely theres some kind of problem here?
Cheers,
Trev
"Michael Wooten" <[email protected]> wrote in message
news:[email protected]...
Hi Trev,
Technically, this is not so much an issue with the classloader(s) inWLS,
as it
is with J2EE packaging. WLS uses a pretty sophisticated, hierarchicalclass loading
architecture. The main reason for using this approach, was to supportundeploying/redeploying
J2EE components (i.e. Servlets, EJBs) without shutting down the JVM.
What you are encountering is a phenomena where Apache SOAP is deployedas
a Web
Application, with it's own ServletContext and classloader.
See the following links for specifics on class loading and J2EE packagingin WLS:
http://e-docs.bea.com/wls/docs60/programming/packaging.html#1048725
After reading this, you will see why the classloader associated withthe
Apache
SOAP web app, cannot see the classes (i.e. serializer, EJBs, etc.)you are
using
to implement your web service.
Regards,
Mike Wooten
"ts" <[email protected]> wrote:
Hi,
Has anyone managed to get Apache SOAP working with Weblogic 6x?
I can get everything up and running, but for some reason the classloader
for the web application (ie; the actual Apache SOAP app) doesn't load
the
classes in my jar file containing the EJB files, serializers, etc.
Therefore whenever I make a SOAP request I get a server side error
reported
via SOAP that some class or another (one of my own ones) cannot befound.
I can cure this by sticking my jar file in the server's classpath-
however
this isn't great as it means the JVM's classloader is picking everything
up
and I lose the ability to redeploy.
Any ideas? In the absence of any other information it would seem that
Weblogic's classloaders are buggy...
Cheers,
Trev

Linkage Error when using Apache SOAP 2.2 with Weblogic 6.1

Has anyone seen this error before? Apparently I've got some incompatible versions of xerces being loaded. I tried putting different versions of xerces.jar in the front of my classpath, and creating an XML Registry to point to org.apache.xerces.jaxp..., but I always get the same error message.
D:\soap>java -classpath "/soap-2_2/lib/soap.jar;activation.jar;mail.jar;xerces.jar;." org.apache.soap.server.Servic
eManagerClient http://localhost:8001/App/servlet/rpcrouter list
Ouch, the call failed:
Fault Code = SOAP-ENV:Server.Exception:
Fault String = loader constraints violated when linking org/xml/sax/InputSource class

Has anyone seen this error before? Apparently I've got some incompatible versions of xerces being loaded. I tried putting different versions of xerces.jar in the front of my classpath, and creating an XML Registry to point to org.apache.xerces.jaxp..., but I always get the same error message.
D:\soap>java -classpath "/soap-2_2/lib/soap.jar;activation.jar;mail.jar;xerces.jar;." org.apache.soap.server.Servic
eManagerClient http://localhost:8001/App/servlet/rpcrouter list
Ouch, the call failed:
Fault Code = SOAP-ENV:Server.Exception:
Fault String = loader constraints violated when linking org/xml/sax/InputSource class

Can anybody provide type 4 jar file for oracle 9i + jdk 1.5

Hello,
I want to connect my java application(jdk 1.5) to oracle.Can any body provide the jar file for that one and whre I want to put that jar file.Please send me one sample code for jdbc connection to oracle for calling a stored procedure in oracle.
Bipin.V

Wouldn't it be easier to google on e.g. oracle jdbc download?
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
Kaj

For using SOAP at receiver side

Hi We have XI Sp19, we are using SOAP adpater with transport protocal is Http and message protocal as SOAP 1.1.
We are using https URL.   As we are using first time SOAP on the system.
Here every thing is fine we are unable to send the doc to vendor side
Please let me know what extra configuration I need to do for usiong SOAP with https.   TIA
Ram Singhal

Ram,
check SAP Note 856597 Question 5.
I get the SSL handshaking error. I get some error when I call my SSL web service.
           A: First, please make sure that the SSL server is working correctly with another client. If the server is working and you still have the problem, the most likely cause is that your J2EE engine is not configured appropriately to be able to use the unrestricted strong features of the cryptographic library. Please make sure that:
           - The JDK java security lib directory ($JAVAHOME/jre/lib/security) contains the unrestricted strong version of local_policy.jar and US_export_policy.jar, which are about 5KB and not the restricted version that are about 3KB each. If you have the restricted version, please refer to http://java.sun.com/ to obtain the unrestricted version.
           - The full version of IAIK is available in the J2EE engine's Security Provider. To check this, go to Service -> Security Provider -> Cryptography Providers, and select IAIK. The Provider Information field should show the full version (e.g., IAIK Security Provider v3.12) and not the evaludation version (e.g., IAIK Security Provider v3.01, evaluation version). If you have the evaludation version, please refer to the security setting section of the SAP J2EE documentation.
regards
sreeram.g.reddy

Problems with client.jar - generated from webservices toolkit from JDK 1.1.7

We have deployed a web application using the webservices in WL 6.1 using JDK 1.3.1.
The clients were able to successfully access the servlet it generated and download
the client.jar. Unfortunately this client.jar seems to be dependent on JDK 1.2
and beyond. It seems to use java.util.Map class in the JNDI-SOAP SPI.
Is there any workaround or fix to this problem, so this jar can be used from a
JDK 1.1.7 env?.
Our objective is to use WL 6.1 EJB's from WL 4.5.1 using Webservices. Are there
any known problems with this approach (Ofcourse other than this).
Thank you.
Dora Potluri
Here is the stack trace from using the client.jar
Class not found java.lang.ClassNotFoundException: java.util.Map
[Root exception is java.lang.ClassNotFoundException: java.util.Map]javax.naming.
NamingException: Class not found java.lang.ClassNotFoundException: java.util.Map
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at javax.naming.NamingException.<init>(Compiled Code)
at weblogic.soap.http.SoapContext.throwNamingException(Compiled Code)
at weblogic.soap.http.SoapContext.lookup(Compiled Code)
at javax.naming.InitialContext.lookup(Compiled Code)
at weatherEJB.WeatherBean.getTemp(Compiled Code)
at weatherEJB.WeatherBeanEOImpl.getTemp(Compiled Code)
at weatherEJB.WeatherBeanEOImpl_WLSkel.invoke(Compiled Code)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(Compiled Code
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(Compiled
Co
de)
at weblogic.rmi.extensions.BasicRequestDispatcher$BasicExecuteRequest.ex
ecute(Compiled Code)
at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
Fri Sep 21 10:47:12 CDT 2001:<I> <EJB> Transaction: '1001087185816_1' rolled bac
k due to EJB exception:

Yes, there is an expectation that the client jar will be run on JDK 1.3x. WLS 6.1 is certified on JDK 1.3x only. This
applies to the WebServices client as well. For details on platform support see
http://e-docs.bea.com/wls/platforms/index.html
Thanks,
Jim
Jim Rivera
Product Manager, WebLogic Server
BEA Systems, Inc.
Dora Potluri wrote:
I started testing using the client.jar generated by webservices WL 6.1 and found
that it uses reflection API interfaces that are not available til JDK 1.3. Is
there an expectation that the clients of Webservices are all going to be JDK 1.3.X.
Here is the stack trace we get.
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.soap.http.SoapContext.lookup(SoapContext.java:76)
at javax.naming.InitialContext.lookup(InitialContext.java:280)
at weatherEJB.WeatherBean.getTemp(WeatherBean.java:106)
at weatherEJB.WeatherBeanEOImpl.getTemp(WeatherBeanEOImpl.java:47)
at weatherEJB.WeatherBeanEOImpl_WLSkel.invoke(WeatherBeanEOImpl_WLSkel.java:90)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:261)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:56)
at weblogic.rmi.extensions.BasicRequestDispatcher$BasicExecuteRequest.execute(BasicRequestDispatcher.java:166)
at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)

Apache SOAP 2.2 and WL 6.1

When trying to use Apache SOAP 2.2 with WL Server 6.1, I get the following error
when attempting a call.invoke():
"Unable to resolve namespace 'SOAPSDK3'"
I can successfully make the SOAP call using a stand-alone application (not inside
weblogic). I found the following FAQ which described the same problem for WL
Server 6.1 (beta):
http://xml.apache.org/soap/faq/faq-for-WL6.1beta.html
I have not been able to get a working solution though. The XML Registry was already
setup as described, using the org.apache.xerces.*. I also put xerces.jar in front
of weblogic.jar in the WL Classpath (not sure if this would have any effect).
Originally, I had put XERCES 1.3.1 there and had no problem starting WL, but
got the same error as before - Unable to resolve namespace 'SOAPSDK3'. When I
placed another version of XERCES, namely 1.4.3 - I could not even start WL properly,
it crapped out with a memory exception and quit the JVM. I read on WL docs that
XERCES 1.3.1 is required and you cannot put another version in front of the weblogic.jar,
otherwise you have problems (they were right on that one). Here are the WL docs:
http://e-docs.bea.com/wls/docs61/faq/xml.html
So, I'd be interested to see if you anyone has suggestion as to what I might try.
It appears that I MUST use XERCES 1.3.1, but when I put the in front of weblogic.jar
I don't solve the problem. If you know of anything I might try, please let me
know. Thanks.
Configuration:
WL 6.1 on Windows 2000 - application inside EAR file.
SOAP Client - Apache SOAP 2.2
SOAP Server - MS SOAP Toolkit (ISAPI - VB dll)
Christopher Hurley
Tallán, Inc.
[email protected]
cell 201.739.2194

Don't know whether below is related to your problem:
https://discussions.apple.com/thread/4831752?tstart=0

Failing silently when trying to construct org.apache.soap.rpc.SOAPContext

OK This is really weird. I have an app that runs fine in eclipse. I have deployed to using webstart but when I try to instantiate org.apache.soap.rpc.SOAPContext default constructor it fails.
All my jars are signed and I have given all permissions in the jnlp
here is the jnlp
<?xml version="1.0" encoding="utf-8"?>
<jnlp spec="1.0+" codebase="http://cs12895.adm.bju.edu/dc" href="dc.jnlp">
     <information>
          <title>DC App</title>
          <vendor>Bob Jones University</vendor>
          <homepage href="http://www.bju.edu"/>
          <description kine="one-line">The Discipline Committee Application</description>
          <description kind="short">The Discipline Committee Application</description>
           <icon href="imageIcon.gif"/>
           <shortcut online="false">
           <desktop/>
           </shortcut>
           <offline-allowed/>
      </information>
      <security>
          <all-permissions/>
      </security>
     <resources>
          <j2se version="1.5+" max-heap-size="256m"/>
          <jar href="dc.jar"/>
          <jar href="looks-2.0.2.jar"/>
          <jar href="log4j-1.2.12.jar"/>
          <jar href="jdnc20060529003752.jar"/>
          <jar href="hibernate3.jar"/>
          <jar href="forms-1.0.7.jar"/>
          <jar href="soap.jar"/>
          <jar href="swingx20060529003241.jar"/>
     </resources>
     <application-desc main-class="edu.bju.dc.rich.LoginFrame"/>
</jnlp>Here is the code. In this cod ethe first debug messageI see but i do not see the second message. Which is how I now it is not getting constructed.
     log.debug("Setting up call to auth ws");
    Call call = new Call();
    log.debug("Finished setting Call up");
    String soapActionURI = "urn:AuthService";

OK I got it working. It was not throwing an exception but when I put I try catch looking for throwables I discovered it was looking for mail.jar. So all better now :-)

PLEASE HELP! Using Apache SOAP with WL61

Hi,
I am trying to run the Apache soap within the WL61.
I have the Apache soap servlet deployed under WL61.
I am trying to use org.apache.soap.server.ServiceManagerClient
to deploy the sample AddressBook service. I get the following error: "Unable to
resolve namespace URI for 'xsd'".
Now, the Apache SOAP faq says, I need to use the 1.3.0 xeces.jar
on both server and client to solve this problem.
However, WL61 server wont come up with the 1.3.0 xerces.jar file
I am in a catch 22 situation, please help.
thanks

I had exactly this problem and by following the advice below I got it to work using
crimson.jar from apache.
Step 1: put crimson.jar frst in classpath
Step 2: put the following in config.xml
<XMLRegistry DocumentBuilderFactory="org.apache.crimson.jaxp.DocumentBuilderFactoryImpl"
Name="Xerces JAXP" SAXParserFactory="org.apache.crimson.jaxp.SAXParserFactoryImpl"
/>
Step 3: updated Server entry in config.xml to point to "Xerces JAXP" as explained
below.
I know this does not add a lot to the idea below but it is an alternative.
Thanks,
George
Manoj Cheenath <[email protected]> wrote:
>
This is something i found in apache soap mailing list:
------- Original Message --------That fixed it! Thanks, Stefan!
-----Original Message-----
From: Stefan Dube [mailto:[email protected]]
Sent: Wednesday, June 13, 2001 4:15 AM
To: [email protected]
Subject: RE: compatibility with weblogic 6.1 beta
Hi!
I believe the problem is that SOAP 2.2 uses JAXP and WL uses their
bundled
xerces as JAXP parser.
To override this you have to modify the config.xml like this: (or
use the web
console)
Add following element as child of the <Domain> element:
<XMLRegistry
DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
Name="Xerces JAXP"
SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl"
/>
and modify the <Server> element like this:
<Server
InstrumentStackTraceEnabled="true"
ListenPort="80"
LogRemoteExceptionsEnabled="true"
Name="myServer"
NativeIOEnabled="true"
XMLRegistry="Xerces JAXP" <-- only this line is important
>
Hope that helps,
-sd
-----Original Message-----
From: Erik Onnen [mailto:[email protected]]
Sent: Wednesday, June 13, 2001 1:33 AM
To: '[email protected] '
Subject: RE: compatibility with weblogic 6.1 beta
The "unable to resolve namespace" problem is because BEA in
their infinite
wisdom chose to mesh Xerces into their own libraries.
Unfortunately they
used an old version and because it is so embedded, you can't
just replace a
JAR. I was able to get 2.1 working on 6.0 sp1 by moving
Xerces to the front
of the classpath in the startup script. Ed, when WL won't
start, what is the
error you get? I haven't heard of that happening before.
Steve, when you say
Xerces is in your classpath, is it at the front, before weblogic.jar?
-----Original Message-----
From: Steve Livingston
To: [email protected]
Sent: 6/12/01 6:46 PM
Subject: RE: compatibility with weblogic 6.1 beta
1) I get the same error (with NT, soap-2.2 and wl-6.1beta) andhave
found no solution:
E:\apache\soap-2_2\samples\addressbook>java
org.apache.soap.server.ServiceManagerClient
http://slivings:7001/soap/servlet/rpcrouter list
Deployed Services:
E:\apache\soap-2_2\samples\addressbook>java
org.apache.soap.server.ServiceManagerClient
http://slivings:7001/soap/servlet/rpcrouter deploy dd.xml
Ouch, the call failed:
Fault Code = SOAP-ENV:Client
Fault String = Unable to resolve namespace URI for 'ns2'.
2) My wl-6.1b will start with xerces in classpath, but same error
occurs.
Can anyone help?
Steve
-----Original Message-----
From: Ed Keen [mailto:[email protected]]
Sent: Monday, June 11, 2001 6:36 PM
To: '[email protected]'
Subject: compatibility with weblogic 6.1 beta
Has anyone gotten Apache soap version 2.2 to work with Weblogic6.1
beta?
There seems to be a xerces incompatibility. The weblogic.jarfile
contains
the xerces library. If you put xerces.jar first in the classpath,
weblogic
won't even start. However, if you put weblogic.jar first in the
classpath,
you get this error when attempting to deploy services using the
ServiceManagerClient: "Unable to resolve namespace URI for 'ns2.'"
This obviously seems to be a xerces parsing issue. Does
anyone know of
a
workaround for this?
Thanks,
EdSanjeev Hegde wrote:
Hi,
I am trying to run the Apache soap within the WL61.
I have the Apache soap servlet deployed under WL61.
I am trying to use org.apache.soap.server.ServiceManagerClient
to deploy the sample AddressBook service. I get the following error:"Unable to
resolve namespace URI for 'xsd'".
Now, the Apache SOAP faq says, I need to use the 1.3.0 xeces.jar
on both server and client to solve this problem.
However, WL61 server wont come up with the 1.3.0 xerces.jar file
I am in a catch 22 situation, please help.
thanks

Installation apache soap in nb 5.5

anyone can help me how can i install apache soap in nb 5.5?
coz i've tried it, it ran, but not completely. especially when i clicked the deploy/undeploy/list button. It showed an exception (HTTP 500).
i put the activation.jar, mail.jar, a complete xerces jar (resolver.jar, serializer.jar, xercesImpl.jar, xml-apis.jar), soap.jar in NB 5.5 home/enterprise3/apache-tomcat <its version>/commons/lib/
i put the soap directory & soap.war under NB 5.5 home/webapps/ROOT/
thx b4 in advance...

Hi,
Apache documentation can be found at http://httpd.apache.org/docs/
You could also refer to (Note: 330250.1 - Tips & Tricks To Make Apache Work With Jserv) for details and explanation about those configuration files.
Regards,
Hussein

Tomcat & Apache Soap Installation

I have install the Tomcat successfully and also install the Apache Soap.
But when I tried to do the test (from: http://xml.apache.org/soap/docs/index.html):
Point my browser to:
http://localhost:port/soap/servlet/rpcrouter
there is no expected answer like following appears:
The browser should display the following:
SOAP (RPC|Message) Router
Sorry, I don't speak via HTTP GET- you have to use HTTP POST to talk to me.
the brower only says it cannot find the webpage!
does anyone know the reason? your help is appreciated in advance now!!
Gang

This may be due to the classpath problem. xerces.jar should be first in the classpath. Otherwise for xml related files tomcat goes to jaxp.jar
U read the following document. It'll help u a lot in installing apache soap.
http://www.javaworld.com/javaworld/jw-04-2001/jw-0427-soap.html
-seenu_ch

Virus scan failed Error on deploying a web application having a jar file for calling the applet on the jsp page

Hi,
I have an applet application that i want to deploy on the Oracle cloud.
So i have created a jar file for the applet application and i am using this jar to call the applet on a jsp page.
But when i am delpoying my application on the java cloud, its giving me the below error:
2014-10-28 03:16:41 CDT: Starting action "Virus Scan"
2014-10-28 03:16:41 CDT: Virus Scan started
2014-10-28 03:16:49 CDT: ----------------------------------------------------------------------
2014-10-28 03:16:49 CDT: File Scanned: "Application7.ear".
2014-10-28 03:16:49 CDT: File Size: "106698122".
2014-10-28 03:16:49 CDT: File Status: "INFECTED".
2014-10-28 03:16:49 CDT: ----------------------------------------------------------------------
2014-10-28 03:16:49 CDT: Virus scan failed.
2014-10-28 03:16:49 CDT: "Virus Scan" complete: status FAILED
Can't we deploy any application having applet or swing component's onto the cloud?
Or do we need to request for any extra permissions for the same?
Thanks,
Manoj

I don't see applets mentioned in the supported features nor in the unsupported features so not sure if they are supported you would likely need to contact the operations team to confirm.
Jani Rautiainen
Fusion Applications Developer Relations
https://blogs.oracle.com/fadevrel/

Include an in-memory jar file for JSR-199 compilation

I want to compile a source file in memory, which requires a jar file that is also represented in memory. I used the JavaSourceFromString class recommended in the documentation for the class JavaCompiler and in a demo I found online that shows how to compile sources represented as String in memory. To represent the jar file, I used a similar trick to JavaSourceFromString:
public class JarJavaFileObjectFromByteArray extends SimpleJavaFileObject {
   * The contents of this jar file.
private final byte[] contents;
   * Constructs a new JarJavaFileObjectFromByteArray given the name and binary
   * contents of a jar file.
   * @param name the name of this jar file
   * @param contents the contents of this jar file
public JarJavaFileObjectFromByteArray(String name, byte[] contents) {
    super(newURI(name), Kind.OTHER);
    this.contents = contents;
... // code not shown ensures that the URI returned from newURI is of the form,
      // for instance, bytes:///MathConstants.jar, if the name of the jar file is MathConstants.jar
@Override
public InputStream openInputStream() throws IOException {
    return new ByteArrayInputStream(contents);
}However, I do not know how to alert the compiler that this jar file should be on the classpath. I tried this:
List<String> options = Arrays.asList(" -classpath bytes:///MathConstants.jar ");
CompilationTask task = compiler.getTask(null, fileManager, null, options, null, compilationUnits);but I get the following error when calling getTask:
java.lang.IllegalArgumentException: invalid flag: -classpath bytes:///MathConstants.jarI assume there is some way to tell the compiler, "look at the MathConstants.jar file that I am storing in memory when searching the classpath", but I do not know how to do this. I assumed that the options parameter for getTask represents command-line flags that would be passed to the compiler if this were happening on the command line (such as "-cp .", which also does not work), but perhaps this assumption is wrong.

Hi Bruce,
I have a question regarding loading a jar file by the compiler to dynamically compile with a source file. I hope you can probably offer me an idea on what has been missing or wrong with the source codes I have written for my application.
I am using Eclipse compiler to dynamically compile a class. In the class, I want it to make a reference to a jar file for compilation dynamically.
Here is the source of a test class I wrote:
import javax.servlet.http.HttpServlet;
class MyServlet extends HttpServlet {
}The import statement refers to the class javax.servlet.http.HttpServlet from the jar file C:\\Program Files\\Apache Software Foundation\\Tomcat 6.0\\lib\\servlet-api.jar placed in the file system.
In the method called compileClass (shown below), I used the path of the jar file to add to the option -classpath as you suggested.
     private static CompileClassResult compileClass(Writer out, String className, String classSource) {
          try {
               JavaCompiler javac = new EclipseCompiler();
               StandardJavaFileManager sjfm = javac.getStandardFileManager(null, null, null);
               SpecialClassLoader scl = new SpecialClassLoader();
               SpecialJavaFileManager fileManager = new SpecialJavaFileManager(sjfm, scl);
               List<String> options = new ArrayList<String>();
               options.addAll(Arrays.asList("-classpath", "C:\\Program Files\\Apache Software Foundation\\Tomcat 6.0\\lib\\servlet-api.jar"));
               List<MemorySource> compilationUnits = Arrays.asList(new MemorySource(className, classSource));
               DiagnosticListener<JavaFileObject> diagnosticListener = null;
               Iterable<String> classes = null;
               if (out == null) {
                    out = new PrintWriter(System.err);
               JavaCompiler.CompilationTask compile = javac.getTask(out, fileManager, diagnosticListener, options, classes, compilationUnits);
               boolean res = compile.call();
               if (res) {
                    //Need to modify the api to return an array of two elements - one classes and other bytecodes for all classes in the same class file.
                    return CompileClassResult.newInstance(scl.findClasses(), scl.findByteCodes());
          } catch (Exception e) {
               e.printStackTrace();
          return null;
     }I also extended the class ForwardingJavaFileManager as you suggested and have it delegated to the StandardJavaFileManager sent to the compiler mentioned in the method compileClass above. The extended class (called SpecialJavaFileManager) is as follows:
public class SpecialJavaFileManager extends ForwardingJavaFileManager<StandardJavaFileManager> {
     private SpecialClassLoader xcl;
     public SpecialJavaFileManager(StandardJavaFileManager sjfm, SpecialClassLoader xcl) {
          super(sjfm);
          System.out.println("SpecialJavaFileManager");
          this.xcl = xcl;
     public JavaFileObject getJavaFileForOutput(Location location, String name, JavaFileObject.Kind kind, FileObject sibling) throws IOException {
          System.out.println("getJavaFileForOutput");
          MemoryByteCode mbc = new MemoryByteCode(name);
          xcl.addClass(name, mbc);
          return mbc;
     public Iterable<JavaFileObject> list(JavaFileManager.Location loc, String pkg, Set kinds, boolean recurse) throws IOException {
          System.out.println("list ");
        List<JavaFileObject> result = new ArrayList<JavaFileObject>();
        for (JavaFileObject f : super.list(loc, pkg, kinds, recurse)) {
             System.out.println(f);
            result.add(f);
          return result;
}I run the application and the result shows that it didn't load the jar file into the memory as expected. From the output (below) I got, it doesn't seem to invoke the method list(...) in the class SpecialJavaFileManager.
SpecialJavaFileManager
1. ERROR in \MyServlet.java (at line 1)
     import javax.servlet.http.*;
            ^^^^^^^^^^^^^
The import javax.servlet cannot be resolved
2. ERROR in \MyServlet.java (at line 3)
     class MyServlet extends HttpServlet {
                             ^^^^^^^^^^^
HttpServlet cannot be resolved to a typeWould you please let me know what has possibly be missing or wrong?
Thanks.
Jonathan
Edited by: jonathanlam on Aug 10, 2009 6:47 PM

Validating xml-files inside jar-files for JWS

I want to use xml-files inside a jar-file and want to validate them with dtd-files,
located in the same jar-file. This does work, but only as long as the dtd-file is
in the same directory as the xml-file.
For example, I have no problem, with a DOC Type-statement like
<!DOCTYPE questestinterop SYSTEM "ims_qtiv1p1.dtd" >
With this statement, however, one needs an approprate dtd in every directory containing an XML-file of that type.
If however i want to gather the necessary dtd's in a directory one (or more) levels above with a DOCTYPE-statement of the form
<!DOCTYPE questestinterop SYSTEM "../ims_qtiv1p1.dtd" >
I get error messages of the form
java.io.FileNotFoundException: JAR entry Mikro/Marshall/BookQuestions/../ims_qtiv1p1.dtd not found in C:\Dokumente und Einstellungen\wreiss\Anwendungsdaten\Sun\Java\Deployment\javaws\cache\http\Dwiwi.upb.de\P80\DM~vwl08\DMOViSS\DMoviss_current\RMMikro.jar
     at org.apache.crimson.parser.Parser2.fatal(Unknown Source)
     at org.apache.crimson.parser.Parser2.externalParameterEntity(Unknown Source)
     at org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Unknown Source)
     at org.apache.crimson.parser.Parser2.parseInternal(Unknown Source)
     at org.apache.crimson.parser.Parser2.parse(Unknown Source)
     at org.apache.crimson.parser.XMLReaderImpl.parse(Unknown Source)
     at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(Unknown Source)
     at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
     at oviss.competenceCenter.XMLExpert.setElements(XMLExpert.java:245)
though the dtd-file is in the parent-directory (inside the jar) and the unpacked xml-file can be successfully validated.
Why does this happen. How can one use a single dtd for multiple xml-files (of the same type) in different directories?.
Thanks
Winfried Reiss

In reply to myself, replacing the HTMLBrowser constructor with this;
public HTMLBrowser()
              URL url;
              try
                   // Construct the URL
                   url= this.getClass().getResource('/'+dir+'/'+startPage);
                   setPage(url);
              catch (Exception e)
              System.out.println( "Problem setting help homepage");
             setEditable(false);
             addHyperlinkListener(new LinkListener(this));
        }made it work. This is because seemingly you need '/' at the start of the resouce's path and '/' as the separator, regardless of platform.
I hope this helps someone else.
John

Package org.apache.soap does not exist

Hi,
I'm trying to deploy a webservice made out of stateless session bean.
When i run the service by invoking its method through browser then I get an exception as
Servlet error: Cannot generate Class:
package org.apache.soap does not exist
import org.apache.soap.Header;
-- It seems that the oc4j is not loading soap.jar under soap/lib
But when I add soap.jar to WEB-INF/lib then I get an exception as
java.lang.LinkageError: Class org/apache/soap/rpc/SOAPContext violates loader constraints
Which means soap.jar is loaded previosuly
The required classes are present in soap.jar
Can you please help me on this
Regards
~Anil

Yippee... problem solved... classpath setting problem

Extra JAR's for Apache Soap w/ JDK 1.4.1

Similar Messages

Maybe you are looking for