Thanks Mike, for the hints. Now I have recreate the project starting
with a new project. Now also the builded war works in WO5.4 (obviously
the javaxml.jar issue stays). But I can't revert to the default build
mode (no ssd/war) without manually edit the build.xml.
I think that the TargetBuilder option do nothing
Regards
Paolo
Il giorno 07/dic/07, alle ore 17:25, Mike Schrag ha scritto:
The option for Servlet Deployment ONLY works if you are using the
most recent build.xml files (i.e. it will not work on your older
projects). There's an obnoxious dance that happens between your
build.xml and WOLips UI for certain build controls. I'm assuming
you're using an older build.xml file. You can tell by searching
your build.xml for "servletDeployment". If it doesn't appear,
you're using an older build.xml.
TargetBuilder has been there for a very long time ... I don't use
JavaClient, so I can't tell you how well it works (or even exactly
how to use it), but it somehow allows you to build both server and
client versions of your WO app in WOLips. I don't believe anyone
actually manages the code that corresponds to this, so it's probably
pretty dated. Somewhere on google I found a document that talked
about using it, but I can't seem to find it now.
ms
On Dec 7, 2007, at 11:20 AM, Paolo Sommaruga wrote:
previously in order to build ssd/war I edited build.xml
uncommenting the ssd/war comments.
Now I have tryed to select in WOLips Build properties window the
Ant radio buttom as Build Style, and Servlet Deployment and
autogenerate web.xml checkbox, then right-click on build-xml under
Package Explorer and Run As > Ant Build, but not ssd neither war
are builded.
A question, what is the "Use Target Builder for JavaClient"
checkbox in WOLips Build properties window ?
Paolo
Il giorno 07/dic/07, alle ore 14:24, Mike Schrag ha scritto:
I don't know about 5.4 ... I haven't done any testing with it for
this (there is nothing WOLips can do about javaxml.jar in 5.4 --
until that is broken out into separate jars, it will not work in a
servlet deployment). In 5.3, a fairly simple WO app will be about
27M. SSDD requires that you embed all the system frameworks,
hence the much larger size. I'm not sure what project you're
using, but until a few days ago, the build.xml's did not produce
proper war targets. If you were to create a new project with the
latest wolips, you would get the new proper build.xml (again,
tested only against 5.3 -- Presumably it shouldn't matter, but who
knows). To enable SSDD/war builds, add JavaWOJSP framework to
your app, and then in WOLips Build properties for your project
(right-click on project=>Properties=>WOLips Build), check "Servlet
Deployment" and "autogenerate web.xml", then build the default
target and it should produce an SSDD and a war of the SSDD. Note
that even now, the war target is neither technically a "war
deployment" or a "true war deployment", rather it is a straight
war of the SSDD folder -- suitable for deploying on an app server
that is configured to unpackage the war.
ms
On Dec 7, 2007, at 8:07 AM, Paolo Sommaruga wrote:
for me SSDD deploy in tomcat, builded with eclipse 3.3.2, latest
WOLips, WO 5.4, leopard, produces a very huge SSDD folder (about
122 MB) with the already talked problem with javaxml.jar - jar
not loaded. It works if the application don't use any xml
processing.
War deploy produces a WAR (about 28 MB) which don't works at all.
The error reported is:
java.lang.ClassNotFoundException:
com.webobjects.foundation.NSProperties
at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at
java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:
188) at java.lang.ClassLoader.loadClass(ClassLoader.java:316)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
com
.webobjects
.jspservlet
.WOServletAdaptor._applicationInit(WOServletAdaptor.java:329)
....
Regards
Paolo
Il giorno 06/dic/07, alle ore 07:16, Mike Schrag ha scritto:
Has anyone looked into exactly what the problem is with
deploying a war with framework embedding? It APPEARS that you
either have an exploded war (SSDD) and embedding works fine, or
you have a war file and you have to install WO frameworks
outside of the war, but you can't have both? I'm assuming it's
that NSBundle must be File-based rather than URL-based, so it
can't load embedded frameworks from inside a war because it's
expecting to be able to generate File references? Before I go
exploring this, though, I thought I'd see if anyone else has
already done the legwork for explaining it ...
ms
_______________________________________________
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/psomma%40jpaso.com
This email sent to [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
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/psomma%40jpaso.com
This email sent to [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
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/psomma%40jpaso.com
This email sent to [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
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]
