Menu
▾
▴
imbrium-developer — Imbrium mailing list for developers
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(20) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <ben...@id...> - 2004-05-22 12:09:28
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
|
From: Paul V. <p.t...@hc...> - 2003-12-19 23:06:11
|
Hello Gerard, Thank you for the fast repley. No i did not install MySQL. I will do and create a database called 'imbrium' . Are there more install topics needed for a good working imbrium Portal? Paul Gerard van de Looi wrote: >Paul, > >Did you install a MySQL database named imbrium? This could prevent the >underlying content management system from starting. > >Regards, >Gerard van de Looi > >----- Original Message ----- >From: "Paul Voors" <p.t...@hc...> >To: <imb...@li...> >Sent: Wednesday, December 17, 2003 10:48 PM >Subject: [Imbrium-developer] installing / starting Imbrium 1.3 > > > > >>Hello groupmembers, >> >>I have downloaded the Imbrium 1.3 war file and placed it in the webapp >>directory of tomcat (4.1.24)/windows2000. >>Then is started tomcat, but imbruim was not started. I found an error >>about an tld file which could not >>be found (imbrium.tld). >> >>In the specified directory, indeed there was no imbrium.tld, but an >>template.tld. >> >>In the web.xml of imbrium I changed the reference form /imbrium to >>/template and I let point this reference to the template.tld file. >> >>Now Tomcat started normally, a whole bunch of imbrium comment passed >>the dos box. I could not not find any error messages. >> >>When I pointed my browser (Mozilla 1.4) >>to:http://localhost:8080/imbrium-1.3/index.jsp The portal started, but >>with some errormessages, >>in th dosbox and in the contentspace of the portal. >> >>1. A jsp file (default.jsp) could not be found (see second error message >>in this mail >>and >>2 that MMbase was not started? >> >>Wat went worng? >> >>Is there an install procedure, or is it enough toplace the war file in >>the webapp directory? >> >>Paul Voors >> >> >> >> >>Error/stacktrace show in portalwindow of the browser: >>-------------------------------------------------------------------------- >> >> >---------- > > >>Error encountered processing a template: >>/layouts/html/default.jsporg.apache.jasper.JasperException: >>org.mmbase.bridge.BridgeException at >> >> >> >org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 >54) > > >>at >>org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) >>at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. >java:684) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch >er.java:575) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher >.java:498) > > >>at >> >> >> >org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:8 >22) > > >>at org.apache.jsp.content_jsp._jspService(content_jsp.java:45) at >>org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 >10) > > >>at >>org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) >>at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. >java:684) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch >er.java:575) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher >.java:498) > > >>at >> >> >> >org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:8 >22) > > >>at org.apache.jsp.default_jsp._jspService(default_jsp.java:83) at >>org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 >10) > > >>at >>org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) >>at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. >java:684) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch >er.java:575) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher >.java:498) > > >>at >> >> >> >org.apache.turbine.services.jsp.TurbineJspService.handleRequest(TurbineJspSe >rvice.java:192) > > >>at >> >> >> >org.apache.jetspeed.modules.layouts.JetspeedJspLayout.doBuild(JetspeedJspLay >out.java:101) > > >>at org.apache.turbine.modules.Layout.build(Layout.java:91) at >>org.apache.turbine.modules.LayoutLoader.exec(LayoutLoader.java:123) at >>org.apache.turbine.modules.pages.DefaultPage.doBuild(DefaultPage.java:169) >>at org.apache.turbine.modules.Page.build(Page.java:90) at >>org.apache.turbine.modules.PageLoader.exec(PageLoader.java:123) at >>org.apache.turbine.Turbine.doGet(Turbine.java:510) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. >java:684) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatch >er.java:432) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher >.java:356) > > >>at >> >> >> >org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:430) > > >>at org.apache.jsp.index_jsp._jspService(index_jsp.java:42) at >>org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 >10) > > >>at >>org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) >>at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application >FilterChain.java:247) > > >>at >> >> >> >org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh >ain.java:193) > > >>at >> >> >> >org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja >va:256) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok >eNext(StandardPipeline.java:643) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > > >>at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) >>at >> >> >> >org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja >va:191) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok >eNext(StandardPipeline.java:643) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > > >>at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) >>at >>org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) >>at >> >> >> >org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 >) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok >eNext(StandardPipeline.java:643) > > >>at >> >> >> >org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. >java:171) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok >eNext(StandardPipeline.java:641) > > >>at >> >> >> >org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 >) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok >eNext(StandardPipeline.java:641) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > > >>at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) >>at >> >> >> >org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java >:174) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok >eNext(StandardPipeline.java:643) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > > >>at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) >>at >>org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) >>at >>org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) >>at >> >> >> >org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne >ction(Http11Protocol.java:392) > > >>at >>org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) >>at >> >> >> >org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav >a:619) > > >>at java.lang.Thread.run(Thread.java:536) Horrible Exception: >>org.apache.jasper.JasperException: org.mmbase.bridge.BridgeException at >> >> >> >org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 >54) > > >>at >>org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) >>at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. >java:684) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch >er.java:575) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher >.java:498) > > >>at >> >> >> >org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:8 >22) > > >>at org.apache.jsp.content_jsp._jspService(content_jsp.java:45) at >>org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 >10) > > >>at >>org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) >>at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. >java:684) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch >er.java:575) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher >.java:498) > > >>at >> >> >> >org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:8 >22) > > >>at org.apache.jsp.default_jsp._jspService(default_jsp.java:83) at >>org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 >10) > > >>at >>org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) >>at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. >java:684) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch >er.java:575) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher >.java:498) > > >>at >> >> >> >org.apache.turbine.services.jsp.TurbineJspService.handleRequest(TurbineJspSe >rvice.java:192) > > >>rethrown as org.apache.turbine.util.TurbineException: Error encountered >>processing a template:/layouts/html/default.jsp: >>org.mmbase.bridge.BridgeException at >> >> >> >org.apache.turbine.services.jsp.TurbineJspService.handleRequest(TurbineJspSe >rvice.java:210) > > >>at >> >> >> >org.apache.jetspeed.modules.layouts.JetspeedJspLayout.doBuild(JetspeedJspLay >out.java:101) > > >>at org.apache.turbine.modules.Layout.build(Layout.java:91) at >>org.apache.turbine.modules.LayoutLoader.exec(LayoutLoader.java:123) at >>org.apache.turbine.modules.pages.DefaultPage.doBuild(DefaultPage.java:169) >>at org.apache.turbine.modules.Page.build(Page.java:90) at >>org.apache.turbine.modules.PageLoader.exec(PageLoader.java:123) at >>org.apache.turbine.Turbine.doGet(Turbine.java:510) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. >java:684) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatch >er.java:432) > > >>at >> >> >> >org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher >.java:356) > > >>at >> >> >> >org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:430) > > >>at org.apache.jsp.index_jsp._jspService(index_jsp.java:42) at >>org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 >10) > > >>at >>org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) >>at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at >>javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at >> >> >> >org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application >FilterChain.java:247) > > >>at >> >> >> >org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh >ain.java:193) > > >>at >> >> >> >org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja >va:256) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok >eNext(StandardPipeline.java:643) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > > >>at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) >>at >> >> >> >org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja >va:191) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok >eNext(StandardPipeline.java:643) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > > >>at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) >>at >>org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) >>at >> >> >> >org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 >) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok >eNext(StandardPipeline.java:643) > > >>at >> >> >> >org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. >java:171) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok >eNext(StandardPipeline.java:641) > > >>at >> >> >> >org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 >) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok >eNext(StandardPipeline.java:641) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > > >>at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) >>at >> >> >> >org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java >:174) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok >eNext(StandardPipeline.java:643) > > >>at >> >> >> >org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > > >>at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) >>at >>org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) >>at >>org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) >>at >> >> >> >org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne >ction(Http11Protocol.java:392) > > >>at >>org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) >>at >> >> >> >org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav >a:619) > > >>at java.lang.Thread.run(Thread.java:536) >> >>Erromessages shown in dosbox: >>-------------------------------------------------------------------------- >> >> >------------ > > >>12-17 22:13:39 ERROR mmbase.bridge.implementation.BasicCloudContext - >>MMBase h >>as not been started, and cannot be started by this Class. >>(org.mmbase.bridge.Loc >>alContext) >>12-17 22:13:39 ERROR Portal engine - Turbine.handleException: Error >>encountere >>d processing a template:/layouts/html/default.jsp: >>org.mmbase.bridge.BridgeExcep >>tion >>12-17 22:13:39 ERROR Portal engine - [Exception : Error encountered >>processin >>g a template:/layouts/html/default.jsp: org.mmbase.bridge.BridgeException] >>12-17 22:13:39 INFO Portal engine - JetspeedJspLayout: set response >>content t >>ype to text/html >>12-17 22:13:39 INFO Portal engine - JetspeedJspLayout: set >>'screenJSP' to: /W >>EB-INF/templates/jsp/screens/Error.jsp >>12-17 22:13:39 INFO Portal engine - JetspeedJspLayout: forward >>request to: /l >>ayouts/default.jsp >>12-17 22:13:39 ERROR Portal engine - Template /layouts/default.jsp not >>found i >>n template paths [Exception : Template /layouts/default.jsp not found in >>templat >>e paths] >> >> >> >>------------------------------------------------------- >>This SF.net email is sponsored by: IBM Linux Tutorials. >>Become an expert in LINUX or just sharpen your skills. Sign up for IBM's >>Free Linux Tutorials. Learn everything from the bash shell to sys admin. >>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >>_______________________________________________ >>Imbrium-developer mailing list >>Imb...@li... >>https://lists.sourceforge.net/lists/listinfo/imbrium-developer >> >> > > > >------------------------------------------------------- >This SF.net email is sponsored by: IBM Linux Tutorials. >Become an expert in LINUX or just sharpen your skills. Sign up for IBM's >Free Linux Tutorials. Learn everything from the bash shell to sys admin. >Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >_______________________________________________ >Imbrium-developer mailing list >Imb...@li... >https://lists.sourceforge.net/lists/listinfo/imbrium-developer > >. > > > |
|
From: Gerard v. de L. <gv...@e-...> - 2003-12-19 13:27:31
|
Paul, Did you install a MySQL database named imbrium? This could prevent the underlying content management system from starting. Regards, Gerard van de Looi ----- Original Message ----- From: "Paul Voors" <p.t...@hc...> To: <imb...@li...> Sent: Wednesday, December 17, 2003 10:48 PM Subject: [Imbrium-developer] installing / starting Imbrium 1.3 > Hello groupmembers, > > I have downloaded the Imbrium 1.3 war file and placed it in the webapp > directory of tomcat (4.1.24)/windows2000. > Then is started tomcat, but imbruim was not started. I found an error > about an tld file which could not > be found (imbrium.tld). > > In the specified directory, indeed there was no imbrium.tld, but an > template.tld. > > In the web.xml of imbrium I changed the reference form /imbrium to > /template and I let point this reference to the template.tld file. > > Now Tomcat started normally, a whole bunch of imbrium comment passed > the dos box. I could not not find any error messages. > > When I pointed my browser (Mozilla 1.4) > to:http://localhost:8080/imbrium-1.3/index.jsp The portal started, but > with some errormessages, > in th dosbox and in the contentspace of the portal. > > 1. A jsp file (default.jsp) could not be found (see second error message > in this mail > and > 2 that MMbase was not started? > > Wat went worng? > > Is there an install procedure, or is it enough toplace the war file in > the webapp directory? > > Paul Voors > > > > > Error/stacktrace show in portalwindow of the browser: > -------------------------------------------------------------------------- ---------- > Error encountered processing a template: > /layouts/html/default.jsporg.apache.jasper.JasperException: > org.mmbase.bridge.BridgeException at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 54) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch er.java:575) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher .java:498) > at > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:8 22) > at org.apache.jsp.content_jsp._jspService(content_jsp.java:45) at > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch er.java:575) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher .java:498) > at > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:8 22) > at org.apache.jsp.default_jsp._jspService(default_jsp.java:83) at > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch er.java:575) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher .java:498) > at > org.apache.turbine.services.jsp.TurbineJspService.handleRequest(TurbineJspSe rvice.java:192) > at > org.apache.jetspeed.modules.layouts.JetspeedJspLayout.doBuild(JetspeedJspLay out.java:101) > at org.apache.turbine.modules.Layout.build(Layout.java:91) at > org.apache.turbine.modules.LayoutLoader.exec(LayoutLoader.java:123) at > org.apache.turbine.modules.pages.DefaultPage.doBuild(DefaultPage.java:169) > at org.apache.turbine.modules.Page.build(Page.java:90) at > org.apache.turbine.modules.PageLoader.exec(PageLoader.java:123) at > org.apache.turbine.Turbine.doGet(Turbine.java:510) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) > at > org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatch er.java:432) > at > org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher .java:356) > at > org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:430) > at org.apache.jsp.index_jsp._jspService(index_jsp.java:42) at > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:256) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > at > org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) > at > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:171) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > at > org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:392) > at > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:619) > at java.lang.Thread.run(Thread.java:536) Horrible Exception: > org.apache.jasper.JasperException: org.mmbase.bridge.BridgeException at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 54) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch er.java:575) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher .java:498) > at > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:8 22) > at org.apache.jsp.content_jsp._jspService(content_jsp.java:45) at > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch er.java:575) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher .java:498) > at > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:8 22) > at org.apache.jsp.default_jsp._jspService(default_jsp.java:83) at > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch er.java:575) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher .java:498) > at > org.apache.turbine.services.jsp.TurbineJspService.handleRequest(TurbineJspSe rvice.java:192) > rethrown as org.apache.turbine.util.TurbineException: Error encountered > processing a template:/layouts/html/default.jsp: > org.mmbase.bridge.BridgeException at > org.apache.turbine.services.jsp.TurbineJspService.handleRequest(TurbineJspSe rvice.java:210) > at > org.apache.jetspeed.modules.layouts.JetspeedJspLayout.doBuild(JetspeedJspLay out.java:101) > at org.apache.turbine.modules.Layout.build(Layout.java:91) at > org.apache.turbine.modules.LayoutLoader.exec(LayoutLoader.java:123) at > org.apache.turbine.modules.pages.DefaultPage.doBuild(DefaultPage.java:169) > at org.apache.turbine.modules.Page.build(Page.java:90) at > org.apache.turbine.modules.PageLoader.exec(PageLoader.java:123) at > org.apache.turbine.Turbine.doGet(Turbine.java:510) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) > at > org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatch er.java:432) > at > org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher .java:356) > at > org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:430) > at org.apache.jsp.index_jsp._jspService(index_jsp.java:42) at > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:256) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > at > org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) > at > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:171) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > at > org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:392) > at > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:619) > at java.lang.Thread.run(Thread.java:536) > > Erromessages shown in dosbox: > -------------------------------------------------------------------------- ------------ > 12-17 22:13:39 ERROR mmbase.bridge.implementation.BasicCloudContext - > MMBase h > as not been started, and cannot be started by this Class. > (org.mmbase.bridge.Loc > alContext) > 12-17 22:13:39 ERROR Portal engine - Turbine.handleException: Error > encountere > d processing a template:/layouts/html/default.jsp: > org.mmbase.bridge.BridgeExcep > tion > 12-17 22:13:39 ERROR Portal engine - [Exception : Error encountered > processin > g a template:/layouts/html/default.jsp: org.mmbase.bridge.BridgeException] > 12-17 22:13:39 INFO Portal engine - JetspeedJspLayout: set response > content t > ype to text/html > 12-17 22:13:39 INFO Portal engine - JetspeedJspLayout: set > 'screenJSP' to: /W > EB-INF/templates/jsp/screens/Error.jsp > 12-17 22:13:39 INFO Portal engine - JetspeedJspLayout: forward > request to: /l > ayouts/default.jsp > 12-17 22:13:39 ERROR Portal engine - Template /layouts/default.jsp not > found i > n template paths [Exception : Template /layouts/default.jsp not found in > templat > e paths] > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Imbrium-developer mailing list > Imb...@li... > https://lists.sourceforge.net/lists/listinfo/imbrium-developer |
|
From: Paul V. <p.t...@hc...> - 2003-12-17 20:30:28
|
Hello groupmembers, I have downloaded the Imbrium 1.3 war file and placed it in the webapp directory of tomcat (4.1.24)/windows2000. Then is started tomcat, but imbruim was not started. I found an error about an tld file which could not be found (imbrium.tld). In the specified directory, indeed there was no imbrium.tld, but an template.tld. In the web.xml of imbrium I changed the reference form /imbrium to /template and I let point this reference to the template.tld file. Now Tomcat started normally, a whole bunch of imbrium comment passed the dos box. I could not not find any error messages. When I pointed my browser (Mozilla 1.4) to:http://localhost:8080/imbrium-1.3/index.jsp The portal started, but with some errormessages, in th dosbox and in the contentspace of the portal. 1. A jsp file (default.jsp) could not be found (see second error message in this mail and 2 that MMbase was not started? Wat went worng? Is there an install procedure, or is it enough toplace the war file in the webapp directory? Paul Voors Error/stacktrace show in portalwindow of the browser: ------------------------------------------------------------------------------------ Error encountered processing a template: /layouts/html/default.jsporg.apache.jasper.JasperException: org.mmbase.bridge.BridgeException at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:498) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:822) at org.apache.jsp.content_jsp._jspService(content_jsp.java:45) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:498) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:822) at org.apache.jsp.default_jsp._jspService(default_jsp.java:83) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:498) at org.apache.turbine.services.jsp.TurbineJspService.handleRequest(TurbineJspService.java:192) at org.apache.jetspeed.modules.layouts.JetspeedJspLayout.doBuild(JetspeedJspLayout.java:101) at org.apache.turbine.modules.Layout.build(Layout.java:91) at org.apache.turbine.modules.LayoutLoader.exec(LayoutLoader.java:123) at org.apache.turbine.modules.pages.DefaultPage.doBuild(DefaultPage.java:169) at org.apache.turbine.modules.Page.build(Page.java:90) at org.apache.turbine.modules.PageLoader.exec(PageLoader.java:123) at org.apache.turbine.Turbine.doGet(Turbine.java:510) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:430) at org.apache.jsp.index_jsp._jspService(index_jsp.java:42) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) Horrible Exception: org.apache.jasper.JasperException: org.mmbase.bridge.BridgeException at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:498) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:822) at org.apache.jsp.content_jsp._jspService(content_jsp.java:45) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:498) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:822) at org.apache.jsp.default_jsp._jspService(default_jsp.java:83) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:498) at org.apache.turbine.services.jsp.TurbineJspService.handleRequest(TurbineJspService.java:192) rethrown as org.apache.turbine.util.TurbineException: Error encountered processing a template:/layouts/html/default.jsp: org.mmbase.bridge.BridgeException at org.apache.turbine.services.jsp.TurbineJspService.handleRequest(TurbineJspService.java:210) at org.apache.jetspeed.modules.layouts.JetspeedJspLayout.doBuild(JetspeedJspLayout.java:101) at org.apache.turbine.modules.Layout.build(Layout.java:91) at org.apache.turbine.modules.LayoutLoader.exec(LayoutLoader.java:123) at org.apache.turbine.modules.pages.DefaultPage.doBuild(DefaultPage.java:169) at org.apache.turbine.modules.Page.build(Page.java:90) at org.apache.turbine.modules.PageLoader.exec(PageLoader.java:123) at org.apache.turbine.Turbine.doGet(Turbine.java:510) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:430) at org.apache.jsp.index_jsp._jspService(index_jsp.java:42) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) Erromessages shown in dosbox: -------------------------------------------------------------------------------------- 12-17 22:13:39 ERROR mmbase.bridge.implementation.BasicCloudContext - MMBase h as not been started, and cannot be started by this Class. (org.mmbase.bridge.Loc alContext) 12-17 22:13:39 ERROR Portal engine - Turbine.handleException: Error encountere d processing a template:/layouts/html/default.jsp: org.mmbase.bridge.BridgeExcep tion 12-17 22:13:39 ERROR Portal engine - [Exception : Error encountered processin g a template:/layouts/html/default.jsp: org.mmbase.bridge.BridgeException] 12-17 22:13:39 INFO Portal engine - JetspeedJspLayout: set response content t ype to text/html 12-17 22:13:39 INFO Portal engine - JetspeedJspLayout: set 'screenJSP' to: /W EB-INF/templates/jsp/screens/Error.jsp 12-17 22:13:39 INFO Portal engine - JetspeedJspLayout: forward request to: /l ayouts/default.jsp 12-17 22:13:39 ERROR Portal engine - Template /layouts/default.jsp not found i n template paths [Exception : Template /layouts/default.jsp not found in templat e paths] |
|
From: Kees J. <ke...@dd...> - 2003-05-16 17:55:57
|
On the MMBase mailing list we are trying to make a appointment to discus the applications project the applications project will hopefully do most of the things required by imbrum. I think i would be good is an Imbrium developer joins the project any body. the first meeting is just for anyone who is interested |
|
From: Edvard S. <edv...@xs...> - 2003-05-12 17:50:51
|
The easiest way should be using the java.util.jar.JarFile This is what I'm currently using to read the deployment descriptor as it first was proposed. Then I read the files for Jetspeed the same way. Jetspeed also has the problem that most methods passes a File as parameter, but it is quite easy to get around to that. Maybe we should try to get the interface from MMBase extended so we could pass an InputSource in stead of a File. The InputSource should be the way to pass references to XML files. -----Original Message----- From: imb...@li... [mailto:imb...@li...] On Behalf Of Kees Jongenburger Sent: maandag 12 mei 2003 12:57 To: imb...@li... Subject: Re: [Imbrium-developer] dynamic deployment of portlets On Monday 12 May 2003 12:32 pm, Gerard van de Looi wrote: > Isn't is possible to list all files in de config/applications > directory within the archive? Well if you know it's a archive yes, but what you wil get back are not files but ZipEntries and no functions to actualy list directories by definition ZipEntries with names terminating with "/" are directories so its possible to list all zip entries stating with config/applications but MMBase often passed File as paramters to function. so if you realy want the files you will need to unzip/jar the archive ------------------------------------------------------- Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com _______________________________________________ Imbrium-developer mailing list Imb...@li... https://lists.sourceforge.net/lists/listinfo/imbrium-developer |
|
From: Kees J. <kee...@om...> - 2003-05-12 10:56:49
|
On Monday 12 May 2003 12:32 pm, Gerard van de Looi wrote: > Isn't is possible to list all files in de config/applications directory > within the archive? Well if you know it's a archive yes, but what you wil get back are not files but ZipEntries and no functions to actualy list directories by definition ZipEntries with names terminating with "/" are directories so its possible to list all zip entries stating with config/applications but MMBase often passed File as paramters to function. so if you realy want the files you will need to unzip/jar the archive |
|
From: Gerard v. de L. <gv...@e-...> - 2003-05-12 10:32:38
|
Isn't is possible to list all files in de config/applications directory
within the archive?
----- Original Message -----
From: "Kees Jongenburger" <ke...@dd...>
To: <imb...@li...>
Sent: Sunday, May 11, 2003 10:59 AM
Subject: Re: [Imbrium-developer] dynamic deployment of portlets
> On Friday 09 May 2003 01:02 pm, Gerard van de Looi wrote:
> > Maybe it's even better to do it the same way as a war file. We can give
the
> > various components their own subdirectory within the archive, so we
don't
> > have to mention them all in the deployment descriptor. This can avoid
> > errors in the deployment descriptor.
>
> Yes. this i a good idea. for mmbase applications (apps1) this is possible
, I
> have a working example here. once you have loded the jar in the
classloader
> it's possible to do something like
> MyClas.class.getResources("config/applications/MyApp.xml");
> but still you need an entry point because you don't want/can't gues the
last
> prat of the code (MyApp.xml). I think there are 2 solutions
> -add some info to the manifest of the jar
> (Mainclass/applicationName/RequiredApps)
> -create an interface that some classes might implement
(ConfigurationProvider)
>
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> Imbrium-developer mailing list
> Imb...@li...
> https://lists.sourceforge.net/lists/listinfo/imbrium-developer
|
|
From: Kees J. <ke...@dd...> - 2003-05-11 20:47:51
|
On Sunday 11 May 2003 09:35 pm, Rogier Schaaf wrote: > I would prefer the manifest file option. This doesn't impose any > constraints on people who want to develop portlets. How does Tomcat do > this? I don't think it's done through the manifest file. If I remember > correctly that thing always very empty.... tomcat uses a virtual file system (jakarta-commons-vfs) |
|
From: Rogier S. <rs...@e-...> - 2003-05-11 19:35:56
|
I would prefer the manifest file option. This doesn't impose any constraints
on people who want to develop portlets. How does Tomcat do this? I don't
think it's done through the manifest file. If I remember correctly that
thing always very empty....
----- Original Message -----
From: "Kees Jongenburger" <ke...@dd...>
To: <imb...@li...>
Sent: Sunday, May 11, 2003 10:59
Subject: [imbrium] Re: [Imbrium-developer] dynamic deployment of portlets
> On Friday 09 May 2003 01:02 pm, Gerard van de Looi wrote:
> > Maybe it's even better to do it the same way as a war file. We can give
the
> > various components their own subdirectory within the archive, so we
don't
> > have to mention them all in the deployment descriptor. This can avoid
> > errors in the deployment descriptor.
>
> Yes. this i a good idea. for mmbase applications (apps1) this is possible
, I
> have a working example here. once you have loded the jar in the
classloader
> it's possible to do something like
> MyClas.class.getResources("config/applications/MyApp.xml");
> but still you need an entry point because you don't want/can't gues the
last
> prat of the code (MyApp.xml). I think there are 2 solutions
> -add some info to the manifest of the jar
> (Mainclass/applicationName/RequiredApps)
> -create an interface that some classes might implement
(ConfigurationProvider)
>
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> Imbrium-developer mailing list
> Imb...@li...
> https://lists.sourceforge.net/lists/listinfo/imbrium-developer
|
|
From: Kees J. <ke...@dd...> - 2003-05-11 08:59:14
|
On Friday 09 May 2003 01:02 pm, Gerard van de Looi wrote:
> Maybe it's even better to do it the same way as a war file. We can give the
> various components their own subdirectory within the archive, so we don't
> have to mention them all in the deployment descriptor. This can avoid
> errors in the deployment descriptor.
Yes. this i a good idea. for mmbase applications (apps1) this is possible , I
have a working example here. once you have loded the jar in the classloader
it's possible to do something like
MyClas.class.getResources("config/applications/MyApp.xml");
but still you need an entry point because you don't want/can't gues the last
prat of the code (MyApp.xml). I think there are 2 solutions
-add some info to the manifest of the jar
(Mainclass/applicationName/RequiredApps)
-create an interface that some classes might implement (ConfigurationProvider)
|
|
From: Gerard v. de L. <gv...@e-...> - 2003-05-09 11:02:25
|
Maybe it's even better to do it the same way as a war file. We can give the various components their own subdirectory within the archive, so we don't have to mention them all in the deployment descriptor. This can avoid errors in the deployment descriptor. ----- Original Message ----- From: "Edvard Scheffers" <edv...@xs...> To: <imb...@li...> Sent: Friday, May 09, 2003 12:47 PM Subject: RE: [Imbrium-developer] dynamic deployment of portlets > Of course, all necessary mmbase parts must be included in the deployment > descriptor. > This includes the builder configuration and the application > configuration. > It is best to define all files in the archive with it's function. This > means that although the mmbase application configuration already > describes it's builders, the builders must also be specified in the > deployment descriptor. It could be possible that an application > configuration uses new and default builders from mmbase. > It is hard to find out which is new and which not. > > Edvard Scheffers > E-ID! Internet Strategies > > -----Original Message----- > From: imb...@li... > [mailto:imb...@li...] On Behalf Of > Rogier Schaaf > Sent: vrijdag 9 mei 2003 12:22 > To: imb...@li... > Subject: Re: [Imbrium-developer] dynamic deplyment of portlets > > > I agree. By deploying applications you assure a consistent definition of > all necessary relations between builders used by your portlet. However, > you should of course also supply the builders in packaged file. > > ----- Original Message ----- > From: "Gerard van de Looi" <gv...@e-...> > To: <imb...@li...> > Sent: Friday, May 09, 2003 10:23 AM > Subject: Re: [Imbrium-developer] dynamic deplyment of portlets > > > > Instead of defining builders, I think it should be possible to > > describe mmbase applications in the deployment descriptor. In this way > > > it's also possible to define relations between builders ans to > > initialize your application with data. > > > > ----- Original Message ----- > > From: "Rogier Schaaf" <rs...@e-...> > > To: "Imbrium Developer List" <imb...@li...> > > Sent: Friday, May 09, 2003 7:54 AM > > Subject: [Imbrium-developer] dynamic deplyment of portlets > > > > > > > Below is the draft design posted by Edvard to support dynamic > > > deployment > > of > > > portlets, including MMBase content types and relations. > > > > > > I will try to tie this as document to outstanding Feature request on > > > > SF. > > > > > > Any comments? > > > > > > > > > Support dynamic deployment of portlets > > > > > > It should be possible to place a file in a specified directory > (specified > > in > > > a config file) which makes it possible to deploy new portlets. The > > > file should be a kind of archive preferably in the jar format (zip). > > > > The file should contain a deployment descriptor describing the > > > contents > of > > > the file. > > > The file can not only contain an implementation of a portlet, but > > > also several mmbase components. These components can include > > > builders and content. > > > > > > The goal of the dynamic deployment is to automatically pickup the > > > new archive and dynamically use it's contents in the running server. > > > > This should be done without unpacking the file. So, the contents is > > > read > > in > > > the memory but is not stored on disk. > > > With the deployment a running Imbrium instance should be able to > > initialize > > > the new builders (create needed tables), > > > insert content into the database, add and start portlets, controls > > > etc. Also, it should be possibly do load any class from included jar > > > > files. An alternative approach which is available is to unpack the > > > archive to > an > > > appropriate directory on the server. Then from here the > > > initialization will take place. > > > > > > Deployment of an archive will never result in visable changes in a > > > users portal. It will only add the possibillity to add a new portlet > > > > to a > users > > > portal. So changes are only visible in customize mode. > > > > > > The files which containes the new deployment information should be > > described > > > in the deployment descriptor. > > > The descriptor describes which files should be deployed. The > > > deployment descriptor could look something like this: <imbrium-app> > > > <portlets> > > > <portlet>new_portlets1.xreg</portlet> > > > <portlet>new_portlets2.xreg</portlet> > > > </portlets> > > > <controls> > > > <control>new_control.xreg</control> > > > </controls> > > > <controllers> > > > <controller>new_controller.xreg</controller> > > > </controllers> > > > <medias> > > > <media>new_media.xreg</media> > > > </medias> > > > <skins> > > > <skin>new_skin.xreg</skin> > > > </skins> > > > <builders> > > > <builder>new_builder1.xml</builder> > > > <builder>new_builder2.xml</builder> > > > <builder>new_builder3.xml</builder> > > > </builders> > > > <contents> > > > <content>content.xml</content> > > > </contents> > > > <libraries> > > > <library>portlets.jar</library> > > > </libraries> > > > </imbrium-app> > > > > > > > > > > > > ------------------------------------------------------- > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa > > > Clara The only event dedicated to issues related to Linux enterprise > > > > solutions www.enterpriselinuxforum.com > > > > > > _______________________________________________ > > > Imbrium-developer mailing list > > > Imb...@li... > > > https://lists.sourceforge.net/lists/listinfo/imbrium-developer > > > > > > > > > > > ------------------------------------------------------- > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > The only event dedicated to issues related to Linux enterprise > > solutions www.enterpriselinuxforum.com > > > > _______________________________________________ > > Imbrium-developer mailing list Imb...@li... > > https://lists.sourceforge.net/lists/listinfo/imbrium-developer > > > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Imbrium-developer mailing list Imb...@li... > https://lists.sourceforge.net/lists/listinfo/imbrium-developer > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Imbrium-developer mailing list > Imb...@li... > https://lists.sourceforge.net/lists/listinfo/imbrium-developer |
|
From: Edvard S. <edv...@xs...> - 2003-05-09 10:47:31
|
Of course, all necessary mmbase parts must be included in the deployment descriptor. This includes the builder configuration and the application configuration. It is best to define all files in the archive with it's function. This means that although the mmbase application configuration already describes it's builders, the builders must also be specified in the deployment descriptor. It could be possible that an application configuration uses new and default builders from mmbase. It is hard to find out which is new and which not. Edvard Scheffers E-ID! Internet Strategies -----Original Message----- From: imb...@li... [mailto:imb...@li...] On Behalf Of Rogier Schaaf Sent: vrijdag 9 mei 2003 12:22 To: imb...@li... Subject: Re: [Imbrium-developer] dynamic deplyment of portlets I agree. By deploying applications you assure a consistent definition of all necessary relations between builders used by your portlet. However, you should of course also supply the builders in packaged file. ----- Original Message ----- From: "Gerard van de Looi" <gv...@e-...> To: <imb...@li...> Sent: Friday, May 09, 2003 10:23 AM Subject: Re: [Imbrium-developer] dynamic deplyment of portlets > Instead of defining builders, I think it should be possible to > describe mmbase applications in the deployment descriptor. In this way > it's also possible to define relations between builders ans to > initialize your application with data. > > ----- Original Message ----- > From: "Rogier Schaaf" <rs...@e-...> > To: "Imbrium Developer List" <imb...@li...> > Sent: Friday, May 09, 2003 7:54 AM > Subject: [Imbrium-developer] dynamic deplyment of portlets > > > > Below is the draft design posted by Edvard to support dynamic > > deployment > of > > portlets, including MMBase content types and relations. > > > > I will try to tie this as document to outstanding Feature request on > > SF. > > > > Any comments? > > > > > > Support dynamic deployment of portlets > > > > It should be possible to place a file in a specified directory (specified > in > > a config file) which makes it possible to deploy new portlets. The > > file should be a kind of archive preferably in the jar format (zip). > > The file should contain a deployment descriptor describing the > > contents of > > the file. > > The file can not only contain an implementation of a portlet, but > > also several mmbase components. These components can include > > builders and content. > > > > The goal of the dynamic deployment is to automatically pickup the > > new archive and dynamically use it's contents in the running server. > > This should be done without unpacking the file. So, the contents is > > read > in > > the memory but is not stored on disk. > > With the deployment a running Imbrium instance should be able to > initialize > > the new builders (create needed tables), > > insert content into the database, add and start portlets, controls > > etc. Also, it should be possibly do load any class from included jar > > files. An alternative approach which is available is to unpack the > > archive to an > > appropriate directory on the server. Then from here the > > initialization will take place. > > > > Deployment of an archive will never result in visable changes in a > > users portal. It will only add the possibillity to add a new portlet > > to a users > > portal. So changes are only visible in customize mode. > > > > The files which containes the new deployment information should be > described > > in the deployment descriptor. > > The descriptor describes which files should be deployed. The > > deployment descriptor could look something like this: <imbrium-app> > > <portlets> > > <portlet>new_portlets1.xreg</portlet> > > <portlet>new_portlets2.xreg</portlet> > > </portlets> > > <controls> > > <control>new_control.xreg</control> > > </controls> > > <controllers> > > <controller>new_controller.xreg</controller> > > </controllers> > > <medias> > > <media>new_media.xreg</media> > > </medias> > > <skins> > > <skin>new_skin.xreg</skin> > > </skins> > > <builders> > > <builder>new_builder1.xml</builder> > > <builder>new_builder2.xml</builder> > > <builder>new_builder3.xml</builder> > > </builders> > > <contents> > > <content>content.xml</content> > > </contents> > > <libraries> > > <library>portlets.jar</library> > > </libraries> > > </imbrium-app> > > > > > > > > ------------------------------------------------------- > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa > > Clara The only event dedicated to issues related to Linux enterprise > > solutions www.enterpriselinuxforum.com > > > > _______________________________________________ > > Imbrium-developer mailing list > > Imb...@li... > > https://lists.sourceforge.net/lists/listinfo/imbrium-developer > > > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise > solutions www.enterpriselinuxforum.com > > _______________________________________________ > Imbrium-developer mailing list Imb...@li... > https://lists.sourceforge.net/lists/listinfo/imbrium-developer > ------------------------------------------------------- Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com _______________________________________________ Imbrium-developer mailing list Imb...@li... https://lists.sourceforge.net/lists/listinfo/imbrium-developer |
|
From: Kees J. <kee...@om...> - 2003-05-09 10:41:17
|
Keeping the resources in a jar (and making them avaiable) is quites easy create an URLClassLoader that a parent classloader and add the url to the jar At the moment deploying mmbase apps1 is only possible from a local file system but it is already possible to create node managers and relation manager via the bridge. so some more work would be required to load mmbase applications from a jar. I think in mmbase 1.7 this wil be possible. On Friday 09 May 2003 12:22 pm, Rogier Schaaf wrote: > I agree. By deploying applications you assure a consistent definition of > all necessary relations between builders used by your portlet. However, you > should of course also supply the builders in packaged file. > > ----- Original Message ----- > From: "Gerard van de Looi" <gv...@e-...> > To: <imb...@li...> > Sent: Friday, May 09, 2003 10:23 AM > Subject: Re: [Imbrium-developer] dynamic deplyment of portlets > > > Instead of defining builders, I think it should be possible to describe > > mmbase applications in the deployment descriptor. > > In this way it's also possible to define relations between builders ans > > to initialize your application with data. > > > > ----- Original Message ----- > > From: "Rogier Schaaf" <rs...@e-...> > > To: "Imbrium Developer List" <imb...@li...> > > Sent: Friday, May 09, 2003 7:54 AM > > Subject: [Imbrium-developer] dynamic deplyment of portlets > > > > > Below is the draft design posted by Edvard to support dynamic > > > deployment > > > > of > > > > > portlets, including MMBase content types and relations. > > > > > > I will try to tie this as document to outstanding Feature request on > > > SF. > > > > > > Any comments? > > > > > > > > > Support dynamic deployment of portlets > > > > > > It should be possible to place a file in a specified directory > > (specified > > > in > > > > > a config file) which makes it possible to deploy new portlets. > > > The file should be a kind of archive preferably in the jar format > > > (zip). The file should contain a deployment descriptor describing the > > > contents > > of > > > > the file. > > > The file can not only contain an implementation of a portlet, but also > > > several mmbase components. > > > These components can include builders and content. > > > > > > The goal of the dynamic deployment is to automatically pickup the new > > > archive and dynamically use it's contents in the running server. > > > This should be done without unpacking the file. So, the contents is > > > read > > > > in > > > > > the memory but is not stored on disk. > > > With the deployment a running Imbrium instance should be able to > > > > initialize > > > > > the new builders (create needed tables), > > > insert content into the database, add and start portlets, controls etc. > > > Also, it should be possibly do load any class from included jar files. > > > An alternative approach which is available is to unpack the archive to > > an > > > > appropriate directory on the server. Then from here the initialization > > > will take place. > > > > > > Deployment of an archive will never result in visable changes in a > > > users portal. It will only add the possibillity to add a new portlet to > > > a > > users > > > > portal. So changes are only visible in customize mode. > > > > > > The files which containes the new deployment information should be > > > > described > > > > > in the deployment descriptor. > > > The descriptor describes which files should be deployed. > > > The deployment descriptor could look something like this: > > > <imbrium-app> > > > <portlets> > > > <portlet>new_portlets1.xreg</portlet> > > > <portlet>new_portlets2.xreg</portlet> > > > </portlets> > > > <controls> > > > <control>new_control.xreg</control> > > > </controls> > > > <controllers> > > > <controller>new_controller.xreg</controller> > > > </controllers> > > > <medias> > > > <media>new_media.xreg</media> > > > </medias> > > > <skins> > > > <skin>new_skin.xreg</skin> > > > </skins> > > > <builders> > > > <builder>new_builder1.xml</builder> > > > <builder>new_builder2.xml</builder> > > > <builder>new_builder3.xml</builder> > > > </builders> > > > <contents> > > > <content>content.xml</content> > > > </contents> > > > <libraries> > > > <library>portlets.jar</library> > > > </libraries> > > > </imbrium-app> > > > > > > > > > > > > ------------------------------------------------------- > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > > The only event dedicated to issues related to Linux enterprise > > > solutions www.enterpriselinuxforum.com > > > > > > _______________________________________________ > > > Imbrium-developer mailing list > > > Imb...@li... > > > https://lists.sourceforge.net/lists/listinfo/imbrium-developer > > > > ------------------------------------------------------- > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > The only event dedicated to issues related to Linux enterprise solutions > > www.enterpriselinuxforum.com > > > > _______________________________________________ > > Imbrium-developer mailing list > > Imb...@li... > > https://lists.sourceforge.net/lists/listinfo/imbrium-developer > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Imbrium-developer mailing list > Imb...@li... > https://lists.sourceforge.net/lists/listinfo/imbrium-developer -- Kees Jongenburger Mediapark C101 Hilversum +31 (0)35 6772910 |
|
From: Rogier S. <rs...@e-...> - 2003-05-09 10:22:34
|
I agree. By deploying applications you assure a consistent definition of all necessary relations between builders used by your portlet. However, you should of course also supply the builders in packaged file. ----- Original Message ----- From: "Gerard van de Looi" <gv...@e-...> To: <imb...@li...> Sent: Friday, May 09, 2003 10:23 AM Subject: Re: [Imbrium-developer] dynamic deplyment of portlets > Instead of defining builders, I think it should be possible to describe > mmbase applications in the deployment descriptor. > In this way it's also possible to define relations between builders ans to > initialize your application with data. > > ----- Original Message ----- > From: "Rogier Schaaf" <rs...@e-...> > To: "Imbrium Developer List" <imb...@li...> > Sent: Friday, May 09, 2003 7:54 AM > Subject: [Imbrium-developer] dynamic deplyment of portlets > > > > Below is the draft design posted by Edvard to support dynamic deployment > of > > portlets, including MMBase content types and relations. > > > > I will try to tie this as document to outstanding Feature request on SF. > > > > Any comments? > > > > > > Support dynamic deployment of portlets > > > > It should be possible to place a file in a specified directory (specified > in > > a config file) which makes it possible to deploy new portlets. > > The file should be a kind of archive preferably in the jar format (zip). > > The file should contain a deployment descriptor describing the contents of > > the file. > > The file can not only contain an implementation of a portlet, but also > > several mmbase components. > > These components can include builders and content. > > > > The goal of the dynamic deployment is to automatically pickup the new > > archive and dynamically use it's contents in the running server. > > This should be done without unpacking the file. So, the contents is read > in > > the memory but is not stored on disk. > > With the deployment a running Imbrium instance should be able to > initialize > > the new builders (create needed tables), > > insert content into the database, add and start portlets, controls etc. > > Also, it should be possibly do load any class from included jar files. > > An alternative approach which is available is to unpack the archive to an > > appropriate directory on the server. Then from here the initialization > > will take place. > > > > Deployment of an archive will never result in visable changes in a users > > portal. It will only add the possibillity to add a new portlet to a users > > portal. So changes are only visible in customize mode. > > > > The files which containes the new deployment information should be > described > > in the deployment descriptor. > > The descriptor describes which files should be deployed. > > The deployment descriptor could look something like this: > > <imbrium-app> > > <portlets> > > <portlet>new_portlets1.xreg</portlet> > > <portlet>new_portlets2.xreg</portlet> > > </portlets> > > <controls> > > <control>new_control.xreg</control> > > </controls> > > <controllers> > > <controller>new_controller.xreg</controller> > > </controllers> > > <medias> > > <media>new_media.xreg</media> > > </medias> > > <skins> > > <skin>new_skin.xreg</skin> > > </skins> > > <builders> > > <builder>new_builder1.xml</builder> > > <builder>new_builder2.xml</builder> > > <builder>new_builder3.xml</builder> > > </builders> > > <contents> > > <content>content.xml</content> > > </contents> > > <libraries> > > <library>portlets.jar</library> > > </libraries> > > </imbrium-app> > > > > > > > > ------------------------------------------------------- > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > The only event dedicated to issues related to Linux enterprise solutions > > www.enterpriselinuxforum.com > > > > _______________________________________________ > > Imbrium-developer mailing list > > Imb...@li... > > https://lists.sourceforge.net/lists/listinfo/imbrium-developer > > > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Imbrium-developer mailing list > Imb...@li... > https://lists.sourceforge.net/lists/listinfo/imbrium-developer > |
|
From: Gerard v. de L. <gv...@e-...> - 2003-05-09 08:23:52
|
Instead of defining builders, I think it should be possible to describe mmbase applications in the deployment descriptor. In this way it's also possible to define relations between builders ans to initialize your application with data. ----- Original Message ----- From: "Rogier Schaaf" <rs...@e-...> To: "Imbrium Developer List" <imb...@li...> Sent: Friday, May 09, 2003 7:54 AM Subject: [Imbrium-developer] dynamic deplyment of portlets > Below is the draft design posted by Edvard to support dynamic deployment of > portlets, including MMBase content types and relations. > > I will try to tie this as document to outstanding Feature request on SF. > > Any comments? > > > Support dynamic deployment of portlets > > It should be possible to place a file in a specified directory (specified in > a config file) which makes it possible to deploy new portlets. > The file should be a kind of archive preferably in the jar format (zip). > The file should contain a deployment descriptor describing the contents of > the file. > The file can not only contain an implementation of a portlet, but also > several mmbase components. > These components can include builders and content. > > The goal of the dynamic deployment is to automatically pickup the new > archive and dynamically use it's contents in the running server. > This should be done without unpacking the file. So, the contents is read in > the memory but is not stored on disk. > With the deployment a running Imbrium instance should be able to initialize > the new builders (create needed tables), > insert content into the database, add and start portlets, controls etc. > Also, it should be possibly do load any class from included jar files. > An alternative approach which is available is to unpack the archive to an > appropriate directory on the server. Then from here the initialization > will take place. > > Deployment of an archive will never result in visable changes in a users > portal. It will only add the possibillity to add a new portlet to a users > portal. So changes are only visible in customize mode. > > The files which containes the new deployment information should be described > in the deployment descriptor. > The descriptor describes which files should be deployed. > The deployment descriptor could look something like this: > <imbrium-app> > <portlets> > <portlet>new_portlets1.xreg</portlet> > <portlet>new_portlets2.xreg</portlet> > </portlets> > <controls> > <control>new_control.xreg</control> > </controls> > <controllers> > <controller>new_controller.xreg</controller> > </controllers> > <medias> > <media>new_media.xreg</media> > </medias> > <skins> > <skin>new_skin.xreg</skin> > </skins> > <builders> > <builder>new_builder1.xml</builder> > <builder>new_builder2.xml</builder> > <builder>new_builder3.xml</builder> > </builders> > <contents> > <content>content.xml</content> > </contents> > <libraries> > <library>portlets.jar</library> > </libraries> > </imbrium-app> > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Imbrium-developer mailing list > Imb...@li... > https://lists.sourceforge.net/lists/listinfo/imbrium-developer > |
|
From: Rogier S. <rs...@e-...> - 2003-05-09 05:54:23
|
Below is the draft design posted by Edvard to support dynamic deployment of portlets, including MMBase content types and relations. I will try to tie this as document to outstanding Feature request on SF. Any comments? Support dynamic deployment of portlets It should be possible to place a file in a specified directory (specified in a config file) which makes it possible to deploy new portlets. The file should be a kind of archive preferably in the jar format (zip). The file should contain a deployment descriptor describing the contents of the file. The file can not only contain an implementation of a portlet, but also several mmbase components. These components can include builders and content. The goal of the dynamic deployment is to automatically pickup the new archive and dynamically use it's contents in the running server. This should be done without unpacking the file. So, the contents is read in the memory but is not stored on disk. With the deployment a running Imbrium instance should be able to initialize the new builders (create needed tables), insert content into the database, add and start portlets, controls etc. Also, it should be possibly do load any class from included jar files. An alternative approach which is available is to unpack the archive to an appropriate directory on the server. Then from here the initialization will take place. Deployment of an archive will never result in visable changes in a users portal. It will only add the possibillity to add a new portlet to a users portal. So changes are only visible in customize mode. The files which containes the new deployment information should be described in the deployment descriptor. The descriptor describes which files should be deployed. The deployment descriptor could look something like this: <imbrium-app> <portlets> <portlet>new_portlets1.xreg</portlet> <portlet>new_portlets2.xreg</portlet> </portlets> <controls> <control>new_control.xreg</control> </controls> <controllers> <controller>new_controller.xreg</controller> </controllers> <medias> <media>new_media.xreg</media> </medias> <skins> <skin>new_skin.xreg</skin> </skins> <builders> <builder>new_builder1.xml</builder> <builder>new_builder2.xml</builder> <builder>new_builder3.xml</builder> </builders> <contents> <content>content.xml</content> </contents> <libraries> <library>portlets.jar</library> </libraries> </imbrium-app> |
|
From: Gizzo <gi...@wa...> - 2003-05-08 19:05:32
|
si! ----- Original Message ----- From: "Rogier Schaaf" <rs...@e-...> To: "Imbrium Developer List" <imb...@li...> Sent: Thursday, May 08, 2003 8:09 PM Subject: [Imbrium-developer] test > test > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Imbrium-developer mailing list > Imb...@li... > https://lists.sourceforge.net/lists/listinfo/imbrium-developer > |
|
From: Rogier S. <rs...@e-...> - 2003-05-08 18:34:21
|
test |
|
From: Rogier S. <rs...@e-...> - 2003-05-08 18:09:19
|
test |
|
From: Rogier S. <rs...@xs...> - 2003-05-08 10:24:52
|
reply by xs4all ----- Original Message ----- From: <edv...@xs...> To: <imb...@li...> Sent: Thursday, May 08, 2003 12:19 PM Subject: [Imbrium-developer] Test > Testje > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Imbrium-developer mailing list > Imb...@li... > https://lists.sourceforge.net/lists/listinfo/imbrium-developer |
|
From: Edvard S. <exz...@ya...> - 2003-05-08 10:22:34
|
to lijst --- edv...@xs... wrote: > Testje > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, > 2003, Santa Clara > The only event dedicated to issues related to Linux > enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Imbrium-developer mailing list > Imb...@li... > https://lists.sourceforge.net/lists/listinfo/imbrium-developer > > __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com |
|
From: <edv...@xs...> - 2003-05-08 10:19:28
|
Testje |
|
From: Rogier S. <rs...@xs...> - 2003-05-02 09:35:17
|
test |
|
From: Rogier S. <rs...@xs...> - 2003-04-06 20:56:14
|
test |