My point was there is no way to UNDEPLOY. But I guess since simply replacing the war should trigger a redeployment, it's good enough. Not mentioned anywhere in the docs though.
I was scratching around looking for deploy targets, not thinking of copying anything to any deploy dir.
I know docs are the last to arrive with these projects, but I followed verbatim the instructions, once for Tomcat 4 and once for Tomcat 5. Same results. Pretty irritating given that the maven build takes a good 15 minutes each time....
As I mentioned compilation was fine, and given I used completely clean tomcat installations (only required tomcat-users.xml modif) thought perhaps something more serious was wrong.
cheers wh
Scott T. Weaver wrote:
It seems the jetspeed-2 stuff, while having many good things such as tag libs etc, half-assed deployment etc, is not even close to being ready to run for anything other than bleeding edge development.
No need to get abrasive. I worked my ass off on the deployment engine, and while it is not perfect, it does a pretty good job. You can drop a war in WEB-INF/deploy, app deploys, delete it and it undeploys, touch it or copy over with a newer file and it redploys (preserves all portlet preferences). IMOHO, far from half-assed. There is also currently work being done on a administrative portlet that allows you to do this from the UI.
1. Did you follow the getting started page: http://portals.apache.org/jetspeed-2/getting-started.html
2. Did you review information on the wiki: http://wiki.apache.org/portals/Jetspeed2
Just because you say it is broken does mean it is. There is a good chance you are missing a small pace somewhere, or failed to follow directions or ignored them completely.
I assume someone has screwed around with cvs commits which haven't been fully verified, but since no binary distribs for jetspeed-2 are provided, we have no choice but to use the cvs copy.
I build and deploy a fresh copy of J2 every morning to verify the CVS HEAD is always in a consistent state. As with any software, a bug might creep in but the CVS WILL COMPILE and WILL RUN 99.99% of the time.
[EMAIL PROTECTED] wrote:
It seems the jetspeed-2 stuff, while having many good things such as tag libs etc, half-assed deployment etc, is not even close to being ready to run for anything other than bleeding edge development.
After buggering around for three hours trying to build it under Tomcat 4 :
Caused by: org.apache.jetspeed.exception.JetspeedException: Jetspeed Initialization exception!
at org.apache.jetspeed.engine.AbstractEngine.init(AbstractEngine.java:154)
at org.apache.jetspeed.Jetspeed.createEngine(Jetspeed.java:64)
... 46 more
Caused by: java.lang.VerifyError: Cannot inherit from final class
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1679)
at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:968)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1409)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1289)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.createContentDispatcher(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.<init>(XMLDocumentFragmentScannerImpl.java:248)
at org.apache.xerces.impl.XMLDocumentScannerImpl.<init>(XMLDocumentScannerImpl.java:245)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.<init>(Unknown Source)
It got a bit better using Tomcat 5, but still pretty badly broken :
CNF: java.lang.ClassNotFoundException: org.apache.jetspeed.portlets.layout.MultiColumnPortlet:org.apache.jetspeed.portle
ts.layout.MultiColumnPortlet
Which renders the entire interface unusable.
I assume someone has screwed around with cvs commits which haven't been fully verified, but since no binary distribs for jetspeed-2 are provided, we have no choice but to use the cvs copy.
Think I'd better have a look around at some of the other portal offerings to see if I'm not being to hasty in choosing jetspeed.
Anyone have any good experience with other portals who have minimum functionalities such as being able to package a portlet in a war file, deploy/undeploy them?
cheers wh
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
