Re: Latest WOLips war build; incorrect classpath generated
Re: Latest WOLips war build; incorrect classpath generated
- Subject: Re: Latest WOLips war build; incorrect classpath generated
- From: William Hatch <email@hidden>
- Date: Mon, 16 Mar 2009 15:44:43 -0400
Hi Dom,
Yes, it can be a tricky beast. Not sure what's causing your problems,
but if you're using WOnder, you can try looking here:
http://wiki.objectstyle.org/confluence/display/WONDER/Creating+a+wonder+app+to+deploy+as+a+servlet
If you're building remotely, make sure you get the proper jars copied,
and I had to make sure my ant could find them. Not sure if you're
having any problems building anymore, so this might not be relevant.
I've had random, still unsolvable problems with "Servlet
WOServletAdaptor is currently unavailable" issue myself. Hopefully,
this will continue to get better. Hope that helps and good luck.
Bill
On Mar 16, 2009, at 3:25 PM, Dom wrote:
OK, on a brand new project, adding just one jar to the Library
folder, I still get the same problem: the generated classpath is NOT
correct. Here's the log:
INFO: validateJarFile(/usr/share/tomcat5/webapps/NCTest/WEB-INF/lib/
javaxml.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2.
Offending class: javax/servlet/Servlet.class
- Will not process jar '/usr/share/tomcat5/webapps/NCTest/WEB-INF/
Resources/NC_Util.jar' because it cannot be found ...
Not sure what the first line is from, but the second indicates it's
looking for a necessary jar under Resources/ and it's simply not
there, nor should it be there. Or, if it should be there, then one
of the targets necessary to build the war in the build.xml is
messing things up and not copying it there and is instead copying it
to WEB-INF/lib
Anyway, after deploying the war, the app spits out a few more lines
past what I've copied and then just hangs; attempts to reach it
result in 404's, although it is listed as deployed in tomcat
manager. Hopefully, this will be the last hurdle.
Anybody else out there experiencing problems deploying as war?
On Mar 13, 2009, at 9:21 PM, Don Lindsay wrote:
Hello Dom;
I created a new project and named it testing1.
Right clicked the project and chose RunAs, select WOApplication.
Selected the application class. and clicked run
Opened a browser and navigated to the URL identified in the log and
verified that the application was running.
I right clicked the project,
Chose Properties selected WOLips Deployment
checked Servlet Deployment
checked Autogenerate web.xml
clicked the Apply button.
clicked the OK button
Right clicked the project
Selected WOLips Ant Tools
From the submenu selected the first Install option
It took less than a minute to build the war file which was located
in /Library/WebObjects/Applications.
Copied the WAR archive into the webapps directory of a fresh
install of tomcat 5
Started Tomcat
navigated to http://localhost:8080/testing1 and verified the
application is running correctly.
Based on these results the WAR file is being created correctly with
the correct Jar files.
I see you have modified the build.xml file. Please replace your
build.xml file with the standard WOLips build.xml file.
If you do not want the WAR created when you are running inside of
Eclipse, then unselect Servlet Deployment, although I do not
believe the war file is actually created unless you select Install
from the WOLips Ant Tools menu. A Standard build does not build
the WAR file.
Thanks
Don
On Mar 13, 2009, at 8:22 PM, Dom wrote:
On Mar 13, 2009, at 5:44 PM, Don Lindsay wrote:
In my experience builds that consistently take a long time can be
caused by:
1. The date time on your system is wrong
Nope
2. There is some process that is touching your files and setting
the modified date which is causing them to be picked up as
modified.
Are you using a CVS or SVN for your project?
svn
I'd be willing to tolerate the slow builds, if they resulted in
something that actually worked;-) Maybe it's the newness of the
latest wolips not being ironed out yet?
Don
On Mar 13, 2009, at 4:40 PM, Dom wrote:
On Mar 13, 2009, at 3:51 PM, Don Lindsay wrote:
Hello Dom;
After removing the libraries from your project did you do clean
on the project? This should clean out your WAR directory as
well. After you do a clean the war will take a long time to
rebuild the next time it is compiled because it is copying in
all the frameworks.
Yes, I've cleaned several times, and confirmed that it does
remove the contents of the dist directory. For me, it seems that
even incremental builds take quite a long time.
Thanks Don.
Thanks,
Don
On Mar 13, 2009, at 1:04 PM, Dom wrote:
Eclipse 3.4.2
WLips 3.4.5693
WebObjects 5.4.3
Now that I resolved my previous issue with ant (turns out the
build that was on our linux box was troublesome, rebuilding a
different distribution solved the too many open files compile
problem) I'm onto the next step in my webobjects exploration:
deploying a war.
The war builds fine; I modified the build.xml slightly to skip
the packaging step for when I'm running locally using
webobjects direct connect (I think that's what it does?) as it
added significant time to the process, but otherwise all
project elements are stock. The resulting built wars' web.xml
contains an incorrect classpath entry:
WEBINFROOT/Resources/Java/testng-5.8-jdk15.jar
This jar is not available there, and was added to the
project's local Library directory and actually ends up in WEB-
INF/lib/ directory. That's problem one.
The second problem is a little more odd. I'd added some jars
to the Library directory previously, but then removed them.
They're no longer listed in the project's .classpath, but
they're still showing up (incorrectly, as above) in the
generated web.xml classpath section of the resulting war.
What the heck is going on here? How is the classpath entry in
web.xml generated? Most importantly, how can i fix this? I'm
also wondering what the WOLips deployment properties "Custom
Web-XML" section does; add to, or replace?
On a side note, does anybody have any experience using the
maven stuff for webobjects to build wars? I'd prefer that
actually, but it seems that wolips is geared towards ant and I
didn't want to further complicate my webobjects introduction.
Thanks
Dom
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-
email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@me.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden