Pierre, why don't you simply skip the "merge" step and add the jars
into Info.plist individually? This would most likely fix the
problem, at least for bundle-based deployments?
I was just about to suggest this, too ... In fact, sometimes merging
can cause problems for jars that have info defi
Pierre, why don't you simply skip the "merge" step and add the jars
into Info.plist individually? This would most likely fix the problem,
at least for bundle-based deployments?
NSJavaPath
javaxml.jar
Cheers, Anjo
Am 03.12.2007 um 02:02 schrieb Mr. P
JavaXML is just a convenience for regular user that want a quick
deployment. It just a repackaging of the jars required by WO to run.
You can include them manually and pick and choose teh one you want,
the current list is:
axis-ant.jar
axis.jar
commons-discovery-0.2.jar
commons-logging-1.0.4
I think that the javaxml.jar is ignored by the classloader because the
application break in every task related to XML processing instead it
normally behaves in the others circumstances. Thanks for file a bug in
radar
Regards
Paolo
Il giorno 03/dic/07, alle ore 00:01, Mike Schrag ha scrit
For some reason, JavaXML.jar in 5.4 also contains the contents of
servlet.jar ... I assume that's some cascaded dependency that caused
it to be brought in. I believe the rule this refers to says that any
jar containing servlet classes will be ignored. What I don't know is
if that literall
maybe it's a WO 5.4 issue. javaxml.jar is a jar supplied with WO and
it seems that such jar has problem with Servlet Spec 2.3. Can someone
confirm this ?
org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile (/WEB-INF/lib/javaxml.jar) - jar not loaded. See
Servl
I would suggest you submit a bug report in woproject confluence and
stick with Tiger and WO 5.3.3
http://issues.objectstyle.org/jira/secure/BrowseProject.jspa?id=10001
At least you have identified WO 5.4/Leopard as being incompatible
with war/ssd build.
On Nov 30, 2007, at 2:16 PM, Paolo S
Hi Kieran,
I have found that the eclipse 3.3.2 with WOLips nightly version under
tiger and WO 5.3.3 can build a workable ssd/war but with
leopard and WO 5.4 produce a ssd and war not workable. I have tryied
with the same project, same eclipse version and with the same WOLips
nightly version
Thanks Kieran for your answer,
I can't revert to previous wolips, there is an eclipse problem
"Requested operation cannot be performed because it would invalidate
the current configuration. See details for more information"
Paolo
Il giorno 29/nov/07, alle ore 20:13, Kieran Kelleher ha scri
Can you revert to the last plugin via Eclipse Configuration Manager
and verify that it truly works?
On Nov 29, 2007, at 1:26 PM, Paolo Sommaruga wrote:
sorry for the typo. I have eclipse 3.3.2 M20071121-0800, WOLisp
nightly (yesterday), WO5.4 in leopard and I can't produce a
workable war d
sorry for the typo. I have eclipse 3.3.2 M20071121-0800, WOLisp
nightly (yesterday), WO5.4 in leopard and I can't produce a workable
war deploy neither ssd deploy (tomcat). About two week ago, all worked
(eclipse 3.3.1.1) but I can't remember what WOLips nightly version
was. I think such pr
AFAIK, Eclipse 3.3.X should be used with the latest WOLips nightly.
WOLips stable (frozen at #4118) is the last version compatible with
3.2.2.
Not sure if that will help your specific problem or not.
On Nov 29, 2007, at 2:56 AM, Paolo Sommaruga wrote:
Hi,
with the last WOLisp nightly I ca
Hi,
with the last WOLisp nightly I can't produce a workable war deploy
neither ssd deploy (tomcat). I use eclipse 3.2.2, WO5.4 in leopard. I
can't remember what was WOLips nightly which worked
Regards
Paolo Sommaruga
___
Do not post admin request
13 matches
Mail list logo
