changing portlet title
Hi I've seen this problem in the mailing archive dated October 25 of 2004. Has
there been a patch yet for this issue?
> Also, the ability to change the JSR168 portlet title is missing. I
> already tried, overriding getTitle() method of GenericPortlet and
> response.setTitle("SomeTitle").
-
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
Re: Newbie: Accessing SVN
Look here: http://portals.apache.org/jetspeed-2/cvs-usage.html and for cvsview access to the Struts Bridge: http://cvs.apache.org/viewcvs.cgi/jakarta-jetspeed-2/portals-bridges/struts/ and for the site documentation for the Struts Bridge: http://portals.apache.org/jetspeed-2/multiproject/portals-bridges-struts/index.html Jetspeed-2 is still maintained in cvs although we hope to move to SVN some time soon, when someone of use finds enough time to bring this through. Regards, Ate Derek Richardson wrote: Hi. I'm new to Jetspeed and want to look at the source for the current Struts Bridge. I tried: svn co http://svn.apache.org/repos/asf/portals/site/ But that only gave me txt docs and xml, not the source. Please let me know how to get to the source. Thanks, Derek Richardson - 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]
Newbie: Accessing SVN
Hi. I'm new to Jetspeed and want to look at the source for the current Struts Bridge. I tried: svn co http://svn.apache.org/repos/asf/portals/site/ But that only gave me txt docs and xml, not the source. Please let me know how to get to the source. Thanks, Derek Richardson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jetspeed-2: Drop support for Tomcat 4...? Please comment/vote!
I am using J2MI with Tomcat 5.5.7 and there are some issues - the default portlets seem to give up because of some tag lib issue? Nested Exception is org.apache.jasper.JasperException: Unable to read TLD "META-INF/fmt.tld" from JAR file "file:/D:/apache/jakarta-tomcat-5.5.7/webapps/security/WEB-INF/lib/standard-1.0.4.jar": org.apache.jasper.JasperException: Failed to load or instantiate TagLibraryValidator class: org.apache.taglibs.standard.tlv.JstlFmtTLV I checked the bug list (jira) and seems this issue is still open. Am I missing something in the discussion -? Are we refering to J2-M1 on Tomcat 5? regards --- Archana Turaga <[EMAIL PROTECTED]> wrote: > > And, if there are no big objections, I'd like to > vote on dropping > Tomcat > > 4 support > +1 > > -Original Message- > From: Ate Douma [mailto:[EMAIL PROTECTED] > Sent: Monday, February 28, 2005 9:40 PM > To: Jetspeed Users List > Cc: Jetspeed Developers List > Subject: Re: Jetspeed-2: Drop support for Tomcat > 4...? Please > comment/vote! > > Something I forgot to add: > > I will try to upload a preliminary patch for > http://issues.apache.org/jira/browse/JS2-210 > tomorrow which for testing > purposes only and which of course will only work > with Tomcat 5.0.28 (or > higher). > > Regards, Ate > > Ate Douma wrote: > > Dear developer team and users, > > > > I've been working the last two weeks (off and on) > on a new and much > > simplified deployment implementation > > for Jetspeed-2 which builds mainly on official > Servlet specification > > (2.3) features. > > See JIRA: > http://issues.apache.org/jira/browse/JS2-210 > > > > I expect that with this solution, deployment for > Application servers > > other than Tomcat will become much easier > > to implement and support. > > > > I've got this working already beautifully on > Tomcat 5 (5.0.28) and > with > > a few nice side-effects too: > > - the Jetspeed-2 context isn't fixed at /jetspeed > any more > > - multiple layout portlet applications can be > deployed/used at the > same > > time > > for both see: > > http://issues.apache.org/jira/browse/JS2-182 > > http://issues.apache.org/jira/browse/JS2-172 > > - no more temporarily expanded wars in the > java.io.tmpdir to > workaround > > classloading issues > > - much quicker startup > > > > To be honest, my refactoring isn't finished yet > and some features > > currently available will have to be > > reimplemented (differently) like undeployment. > > > > But > > > > I can't get the redeployment working flawlessly > under Tomcat 4.1 > (tested > > with 4.1.30 and 4.1.31). > > Tomcat 4 won't always release certain jars in > deployed applications > when > > doing an undeployment or redeployment while this > > is no problem with Tomcat 5.0. > > Furthermore, auto redeployment of war files isn't > available at all in > > Tomcat 4: you need to use the TomcatManager > > to remove an existing application first (which > sometimes fails) before > a > > new application can tried to be deployed > > again. > > > > And then, There are other serious problems with > Tomcat 4 too like no > > separate sessions for the portal and portlet > applications > > (which is a *serious* security breach and the > foremost reason I myself > > > won't use Tomcat 4 for Portals anymore). > > > > The Pluto Team won't even use Tomcat 5.0 anymore > and require Tomcat > > 5.5.7 or higher because Tomcat 5.0 also has a > session bug > > in which a Portlet Application and its Web > application don't share the > > > same session when invoked independently > > (as they should according to the portlet > specification). > > > > Both the development of Tomcat 4 and Tomcat 5.0 > has largely come to an > > > end, except for really nasty bugs, but the onces I > > described above aren't regarded as such by the > Tomcat team :-( > > > > Al in all, to me the question right now is: do we > really, really need > to > > keep supporting Tomcat 4. > > For my deployment refactorings it poses a problem > I don't have time > left > > to further investigate (nor do I have any hope it > > *can* be resolved). As long as we need to support > Tomcat 4, I can't > > commit my changes... > > > > I'd like to hear from both team members and users > who absolutely > require > > Tomcat 4 support for Jetspeed-2 and why. > > And, if there are no big objections, I'd like to > vote on dropping > Tomcat > > 4 support! > > > > Please comment, > > > > Ate > > > > > > > > > - > > 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] > > > > > - > To unsubscribe, e-mail: > [EMAIL
M1 and struts App with Tiles
hello ! another problem i have: my M1 installation works fine. but the M1-version of the struts-bridge does not support tiles. when i try it, i get following message: (when i look for this problem in internet i find sites from 2003 - not really new) in the current subversion version of the bridge - tiles will be supported. but, is it possible to fix the tiles problem in the M1 version ? only changing the bridge does not work - i think there are a lot of dependencies... thanks for answer best regards tkoch 2005-03-01 14:51:59,662 FATAL tiles.TilesPlugin - TilesPlugin : Specified RequestProcessor not compatible with TilesRequestProcessor 2005-03-01 14:53:45,604 FATAL tiles.TilesPlugin - TilesPlugin : Specified RequestProcessor not compatible with TilesRequestProcessor 2005-03-01 14:53:45,604 ERROR struts.StrutsPortlet - Include exception javax.servlet.ServletException: TilesPlugin : Specified RequestProcessor not compatible with TilesRequestProcessor at org.apache.struts.tiles.TilesPlugin.initRequestProcessorClass(TilesPlugin.java:360) at org.apache.struts.tiles.TilesPlugin.init(TilesPlugin.java:164) at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServlet.java:1158) at org.apache.struts.action.ActionServlet.init(ActionServlet.java:473) at javax.servlet.GenericServlet.init(GenericServlet.java:211) at org.apache.portals.bridges.struts.PortletServlet.init(PortletServlet.java:45) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1029) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:687) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:671) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510) at org.apache.portals.bridges.struts.StrutsPortlet.processRequest(StrutsPortlet.java:283) at org.apache.portals.bridges.struts.StrutsPortlet.doView(StrutsPortlet.java:221) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247) at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) at org.apache.jetspeed.container.JetspeedContainerServlet.doGet(JetspeedContainerServlet.java:235) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510) at org.apache.jetspeed.container.invoker.ServletPortletInvoker.invoke(ServletPortletInvoker.java:213) at org.apache.jetspeed.container.invoker.ServletPortletInvoker.render(ServletPortletInvoker.java:124) at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:103) at org.apache.jetspeed.container.JetspeedPortletContainerWrapper.renderPortlet(JetspeedPortletContainerWrapper.java:88) at org.apache.jetspeed.aggregator.impl.RenderingJob.run(RenderingJob.java:109) at org.apache.jetspeed.aggregator.impl.Worker$1.run(Worker.java:171) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:437) at org.apache.jetspeed.aggregator.impl.Worker.run(Worker.java:165) 2005-03-01 15:13:36,886 FATAL tiles.TilesPlugin - TilesPlugin : Specified RequestProcessor not compatible with TilesRequestProcessor 2005-03-01 15:13:36,886 ERROR struts.StrutsPortlet - Include exception javax.servlet.ServletException: TilesPlugin : Specified RequestProcessor not compatible with TilesRequestProcessor at org.apache.struts.tiles.TilesPlugin.initRequestProcessorClass(TilesPlugin.java:360)
RE: Jetspeed-2: Drop support for Tomcat 4...? Please comment/vote!
> And, if there are no big objections, I'd like to vote on dropping Tomcat > 4 support +1 -Original Message- From: Ate Douma [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 9:40 PM To: Jetspeed Users List Cc: Jetspeed Developers List Subject: Re: Jetspeed-2: Drop support for Tomcat 4...? Please comment/vote! Something I forgot to add: I will try to upload a preliminary patch for http://issues.apache.org/jira/browse/JS2-210 tomorrow which for testing purposes only and which of course will only work with Tomcat 5.0.28 (or higher). Regards, Ate Ate Douma wrote: > Dear developer team and users, > > I've been working the last two weeks (off and on) on a new and much > simplified deployment implementation > for Jetspeed-2 which builds mainly on official Servlet specification > (2.3) features. > See JIRA: http://issues.apache.org/jira/browse/JS2-210 > > I expect that with this solution, deployment for Application servers > other than Tomcat will become much easier > to implement and support. > > I've got this working already beautifully on Tomcat 5 (5.0.28) and with > a few nice side-effects too: > - the Jetspeed-2 context isn't fixed at /jetspeed any more > - multiple layout portlet applications can be deployed/used at the same > time > for both see: > http://issues.apache.org/jira/browse/JS2-182 > http://issues.apache.org/jira/browse/JS2-172 > - no more temporarily expanded wars in the java.io.tmpdir to workaround > classloading issues > - much quicker startup > > To be honest, my refactoring isn't finished yet and some features > currently available will have to be > reimplemented (differently) like undeployment. > > But > > I can't get the redeployment working flawlessly under Tomcat 4.1 (tested > with 4.1.30 and 4.1.31). > Tomcat 4 won't always release certain jars in deployed applications when > doing an undeployment or redeployment while this > is no problem with Tomcat 5.0. > Furthermore, auto redeployment of war files isn't available at all in > Tomcat 4: you need to use the TomcatManager > to remove an existing application first (which sometimes fails) before a > new application can tried to be deployed > again. > > And then, There are other serious problems with Tomcat 4 too like no > separate sessions for the portal and portlet applications > (which is a *serious* security breach and the foremost reason I myself > won't use Tomcat 4 for Portals anymore). > > The Pluto Team won't even use Tomcat 5.0 anymore and require Tomcat > 5.5.7 or higher because Tomcat 5.0 also has a session bug > in which a Portlet Application and its Web application don't share the > same session when invoked independently > (as they should according to the portlet specification). > > Both the development of Tomcat 4 and Tomcat 5.0 has largely come to an > end, except for really nasty bugs, but the onces I > described above aren't regarded as such by the Tomcat team :-( > > Al in all, to me the question right now is: do we really, really need to > keep supporting Tomcat 4. > For my deployment refactorings it poses a problem I don't have time left > to further investigate (nor do I have any hope it > *can* be resolved). As long as we need to support Tomcat 4, I can't > commit my changes... > > I'd like to hear from both team members and users who absolutely require > Tomcat 4 support for Jetspeed-2 and why. > And, if there are no big objections, I'd like to vote on dropping Tomcat > 4 support! > > Please comment, > > Ate > > > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
error after checking out all files of J2
i forgot: the important line of course: org.apache.jetspeed.page.document.NodeSet.isEmpty()Z the "Z" ! i don't know what it is and where it's come from. the method isEmpty() is in interface and Impl ok(for me) any ideas thanks
error after checking out all files of J2
hi ! i have a problem with the current new files of J2. when i checked out an deploy etc and start J2 the first time on my tomcat 5.0.28, i get following message. m1 works fine. i looked to the nodeset.java, but i can't find any mistakes... type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: Servlet execution threw an exception org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:670) org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:637) org.apache.jsp.index_jsp._jspService(index_jsp.java:45) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause java.lang.NoSuchMethodError: org.apache.jetspeed.page.document.NodeSet.isEmpty()Z org.apache.jetspeed.page.impl.CastorXmlPageManager.filterDocumentSet(CastorXmlPageManager.java:1540) org.apache.jetspeed.page.impl.CastorXmlPageManager.expandAndProfileDocumentSet(CastorXmlPageManager.java:700) org.apache.jetspeed.page.impl.CastorXmlPageManager.computeProfiledPageContext(CastorXmlPageManager.java:359) org.apache.jetspeed.profiler.impl.ProfilerValveImpl.invoke(ProfilerValveImpl.java:118) org.apache.jetspeed.pipeline.JetspeedPipeline.invokeNext(JetspeedPipeline.java:209) org.apache.jetspeed.security.impl.PasswordCredentialValveImpl.invoke(PasswordCredentialValveImpl.java:139) org.apache.jetspeed.pipeline.JetspeedPipeline.invokeNext(JetspeedPipeline.java:209) org.apache.jetspeed.security.impl.AbstractSecurityValve$1.run(AbstractSecurityValve.java:117) java.security.AccessController.doPrivileged(Native Method) javax.security.auth.Subject.doAsPrivileged(Subject.java:437) org.apache.jetspeed.security.impl.AbstractSecurityValve.invoke(AbstractSecurityValve.java:111) org.apache.jetspeed.pipeline.JetspeedPipeline.invokeNext(JetspeedPipeline.java:209) org.apache.jetspeed.container.url.impl.PortalURLValveImpl.invoke(PortalURLValveImpl.java:55) org.apache.jetspeed.pipeline.JetspeedPipeline.invokeNext(JetspeedPipeline.java:209) org.apache.jetspeed.capabilities.impl.CapabilityValveImpl.invoke(CapabilityValveImpl.java:127) org.apache.jetspeed.pipeline.JetspeedPipeline.invokeNext(JetspeedPipeline.java:209) org.apache.jetspeed.localization.impl.LocalizationValveImpl.invoke(LocalizationValveImpl.java:122) org.apache.jetspeed.pipeline.JetspeedPipeline.invokeNext(JetspeedPipeline.java:209) org.apache.jetspeed.pipeline.JetspeedPipeline.invoke(JetspeedPipeline.java:191) org.apache.jetspeed.engine.AbstractEngine.service(AbstractEngine.java:257) org.apache.jetspeed.engine.JetspeedServlet.doGet(JetspeedServlet.java:225) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:670) org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:637) org.apache.jsp.index_jsp._jspService(index_jsp.java:45) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) best regards tkoch
Re: SQLException thrown while trying to get Connection from Datasource
You are right the answer is in JS2-187 Thank a lot ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jetspeed-2: Drop support for Tomcat 4...? Please comment/vote!
I see no reason to stick with Tomcat 4. Another vote to drop 4! Hema On Tue, 1 Mar 2005 15:26:23 +0530, Gaurav Vaish <[EMAIL PROTECTED]> wrote: > > > And, if there are no big objections, I'd like to vote on dropping > > > Tomcat 4 support! > > +1 > > -- > Cheers, > Gaurav Vaish > http://www.mastergaurav.org > http://mastergaurav.blogspot.com > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- ~~ Hema Menon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jetspeed-2: Drop support for Tomcat 4...? Please comment/vote!
>I'd like to vote on dropping Tomcat 4 support! +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jetspeed-2: Drop support for Tomcat 4...? Please comment/vote!
> > And, if there are no big objections, I'd like to vote on dropping > > Tomcat 4 support! +1 -- Cheers, Gaurav Vaish http://www.mastergaurav.org http://mastergaurav.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jetspeed-2: Drop support for Tomcat 4...? Please comment/vote!
Ate Douma schrieb: I'd like to hear from both team members and users who absolutely require Tomcat 4 support for Jetspeed-2 and why. And, if there are no big objections, I'd like to vote on dropping Tomcat 4 support! +1 Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Custom PortletMode...
hello, i've declared in my Portlet a PortletMode that suits my problem, named ADD, but i can't call it from a jsp by the tag ** or **, because ADD is not recognized... is it posible to declare it or must i use PortletUrl and set the PortletMode manually?? thx, Luc -- Luc FOUIN - Stagiaire Aptiwan 14 rue Niepce 75014 Paris Tél : 06 77 95 17 24 Mél : [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
