I was getting some weird error (only in) weblogic when I try to load home page(applet) of web application. Home page was nothing but index.jsp which uses tag to load an applet. This applet needs a lot of libraries as part of archive values.
<jsp:plugin type="applet" name="CDApplet" code="com.cd.applet.Applet.class" codebase="." width="100" height="100" align="middle" jreversion="1.5">
<jsp:param name="id" value="CDApplet"/>
<jsp:param name="code" value="com.cd.applet.Applet"/>
<jsp:param name="codebase" value="."/>
<jsp:param name="archive" value="crimson.jar,commons-lang-2.3.jar,jdom.jar,jfreechart-0.9.16.jar,picocontainer-1.0-beta-5.jar,commons-collections-3.2.jar,jaxen-core.jar,saxpath.jar,jaxen-jdom.jar" />
</jsp:plugin>
The above code was NOT working as you see the archive values are sent as parameter. This seems to be okay with Tomcat but somehow weblogic 10.3 could not recognize that. It was throwing Applet Class Not Found Exception. It was really freaking me out. Then I tried this, instead of passing as an argument, I set archive values as part of the tag itself. Example given below:
<jsp:plugin type="applet" name="CDApplet" code="com.cd.applet.Applet.class" codebase="." width="100" height="100" align="middle" jreversion="1.5" archive="cd-applet.jar, commons-collections-3.2.jar,jaxen-core.jar,saxpath.jar,jaxen-jdom.jar">
<jsp:param name="id" value="CDApplet"/>
<jsp:param name="code" value="com.cd.applet.Applet"/>
<jsp:param name="codebase" value="."/>
</jsp:plugin>
This worked. What a relief! By the way, this code change worked in Tomcat as well.
Adios.
Xdoclet on Maven2 NOT generating Struts Config XML
I have recently involved in a migrating existing projects from maven1.2 to maven2. We used maven-xdoclet-plugin for generating struts config xml file. This plug-in used to work OK in maven1.x but failed in maven2. It was not generating those actions & forms properly in struts config xml file.
I recently found a fix (thanks to Google) for this (and it is working) in the form of maven antrun plug-in.
For more info or to see the actual code snippet, please do visit this blog
I recently found a fix (thanks to Google) for this (and it is working) in the form of maven antrun plug-in.
For more info or to see the actual code snippet, please do visit this blog
Labels:
Maven 2
Subscribe to:
Posts (Atom)