Yes there is a solution but not easy and not without recompiling.

I think that older version of WebObjects were using an "Undocumented Feature" of the JVM that would make the loading of the eomodel included in a jar work. This has become broken with one of the minor fixes in Java 1.4.2, I think it has been corrected with 5.3.1 but I am not sure as I have not tested it personally. Really the culprit is WO code, the problems is that you need to rewrite the NSPathUtilities class in Foundation. I have had mixed success in overwritting this class in the Tomcat environment. I think that you will have to open the jar file and replace it as the usual trick of packjaging the new class with the jar of the application does not work in the Tomcat environment. I think the reason is that Tomcat load WO libraries before your app so you have to patch the WO jars.

I do not remember the exact correction I made so I attached the corrected version. It works with our application which is deployed not with Tomcat but with a custom single directory using the same principle.

Pierre

--

Pierre Frisch

President

sPearWay Ltd.

phone: +1 604 929 9610 ext 6011

email: [EMAIL PROTECTED]

sPearCat Web Catalogs,

Custom designed in-house

with the click of a mouse.

http://www.spearcat.com/


Attachment: NSPathUtilities.java
Description: Binary data


On 12-Jan-06, at 2:04 PM, Albert Jagnow wrote:

I am trying to deploy a WO application as a WAR file under apache tomcat 5.5.12.  The application was created on Mac OS 10.3.9 with WO 5.2.3 and Java 1.4.2_09-233.  I am trying to deploy on Solaris 10 x86 with Tomcat 5.5.12 and Java 1.5.0_06.  The application works fine until it tries to load an eomodel then I get the following error:

 

com.webobjects.foundation.NSForwardException

[java.lang.IllegalArgumentException] File not found jar:file:///opt/apache-tomcat-5.5.12/webapps/TestApp/WEB-INF/lib/TestApp.jar!/Resources/DemoData.eomodeld

 

I also tried to compile the application on Mac OS 10.4.4 with WO 5.3 with Java 1.4.2 and also Java 1.5 and I encountered the same error both times when deploying.  When I expand the TestApp.jar file, the DemoData.eomodeld is included in the jar file in the Resources directory.

 

I found a few mentions of this problem when searching the lists, it sounds like the problem is that the eomodel “file” is really a directory and this causes the error.   Is there a solution or fix for this problem?

 

--

Albert Jagnow

Web Developer

The University of Iowa Foundation

 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:

This email sent to [EMAIL PROTECTED]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to