Re: Glassfish 3.0.1 on the AS/400. Console App not running

Den 24/09/10 20.04, Pete Helgren skrev:

One more attempt at this and now I am going to set this aside until
someone has an idea on how to handle this:

I made a change to the jvm settings in the domain.xml file based on this
article:

http://forums.sun.com/thread.jspa?tstart=30&forumID=34&threadID=542044&trange=15

I added the following:

<jvm-options>-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
</jvm-options>

The good news is that it seemed to change things. The bad news is that
it cannot find the class:


[#|2010-09-24T11:48:51.497-0600|WARNING|glassfish3.0.1|org.jvnet.hk2.osgimain|_ThreadID=1;_ThreadName=Thread-5;|Exception
while starting bundle com.sun.enterprise.osgi-adapter [88]
org.osgi.framework.BundleException: Activator start error in bundle
com.sun.enterprise.osgi-adapter [88].
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1751)

...

Caused by: javax.xml.transform.TransformerFactoryConfigurationError:
Provider org.apache.xalan.processor.TransformerFactoryImpl not found

...

I have stuffed the xalan.jar, et al jar into every /lib folder I can
think of and still no joy. I spent some time looking into how Glassfish
V3 is doing class loading but I can't figure out why what I have done is
still not working. I could script some explicit class loading but I
have already invested 10 more hours into this than I wanted to.

You are right in concluding that classloading has changed from version 2 to version 3.

My _guess_ from some experimentations is that the Xalan version you are trying to use, is not an OSGi bundle, and the major architectural change from version 2 to version 3 was to go modular and use OSGi to do so (just like Eclipse did a while back).

So for your replacement code to work, it must have additional meta-information allowing the OSGi container to know where to put it for asking code, and I don't believe you've updated that.

(And I know that because I've started looking into OSGi to see if it could easily solve some dynamic classloader problems we have instead of reinventing the wheel).

The deployed apps run fine but the nice thing about Glassfish is
administration and right now the command line method and autodeploy
method is a step backward, even from Tomcat. Hoping someone else has
some insight here.

I don't quite agree on that :) The autodeploy method is quite convenient.