Hello, I'm trying to set up a portal to use mongoDB for persistance and have followed the instructions at http://rave.apache.org/documentation/mongo-db.html under the "Custom Rave Extension" to create a custom portal.war. However, when I deploy the portal I get these errors, and the portal fails to start. The documentation seems to hint that it should "just work" so I'm at a loss for where to look to solve this issue. It seems to be able to connect to mongodb, as it populates the database with the default values successfully. If I replace the portal.war with one using jpa again, everything loads up fine. Any ideas? ERROR: > org.apache.rave.portal.repository.impl.MongoDbMapReduceStatisticsAggregator > - Error executing Map/Reduce Statistics Aggregation! > java.lang.IllegalStateException: ApplicationEventMulticaster not > initialized - call 'refresh' before multicasting events via the context: > Root WebApplicationContext: startup date [Tue Jun 18 14:21:29 UTC 2013]; > root of context hierarchy > at > org.springframework.context.support.AbstractApplicationContext.getApplicationEventMulticaster(AbstractApplicationContext.java:347) > at > org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334) > at > org.springframework.data.mapping.context.AbstractMappingContext.addPersistentEntity(AbstractMappingContext.java:263) > at > org.springframework.data.mapping.context.AbstractMappingContext.getPersistentEntity(AbstractMappingContext.java:165) > at > org.springframework.data.mapping.context.AbstractMappingContext.getPersistentEntity(AbstractMappingContext.java:140) > at > org.springframework.data.mapping.context.AbstractMappingContext.getPersistentEntity(AbstractMappingContext.java:65) > at > org.springframework.data.mongodb.core.MongoTemplate.findById(MongoTemplate.java:483) > at > org.apache.rave.portal.repository.impl.MongoDbMapReduceStatisticsAggregator.buildStats(MongoDbMapReduceStatisticsAggregator.java:121) > at > org.apache.rave.portal.repository.impl.MongoDbMapReduceStatisticsAggregator$1.run(MongoDbMapReduceStatisticsAggregator.java:112) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) > ERROR: org.springframework.web.context.ContextLoader - Context > initialization failed > org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean > named 'dataSource' is defined > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:549) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1096) > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:278) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:285) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:607) > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) > at > org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383) > at > org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283) > at > org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4705) > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799) > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601) > at > org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943) > at > org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778) > at > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504) > at > org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317) > at > org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324) > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065) > at > org.apache.catalina.core.StandardHost.start(StandardHost.java:840) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057) > at > org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) > at > org.apache.catalina.core.StandardService.start(StandardService.java:525) > at > org.apache.catalina.core.StandardServer.start(StandardServer.java:754) > at org.apache.catalina.startup.Catalina.start(Catalina.java:595) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) > Jun 18, 2013 2:21:41 PM org.apache.catalina.core.StandardContext > listenerStart > SEVERE: Exception sending context initialized event to listener instance > of class org.springframework.web.context.ContextLoaderListener > org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean > named 'dataSource' is defined > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:549) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1096) > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:278) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:285) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:607) > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) > at > org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383) > at > org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283) > at > org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4705) > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799) > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601) > at > org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943) > at > org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778) > at > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504) > at > org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317) > at > org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324) > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065) > at > org.apache.catalina.core.StandardHost.start(StandardHost.java:840) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057) > at > org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) > at > org.apache.catalina.core.StandardService.start(StandardService.java:525) > at > org.apache.catalina.core.StandardServer.start(StandardServer.java:754) > at org.apache.catalina.startup.Catalina.start(Catalina.java:595) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Thanks, Khazhy
Hi Chris, Responses inline below. On Mon, Jun 17, 2013 at 11:24 AM, Hossenlopp, Chris <hossenlopp@mitre.org>wrote: > Hello! > > We are trying to get our own portal set up and were wondering how to > create and set a default page template for new users. To clarify, new users > should have the default page set up for them with our layout and widgets. > We also want them to be able to change these pages without affecting the > copies that other users have. > > I've heard this is done by modifying a few things in the mongo database > after creating the page we want with an existing user. Does anyone know how > to setup this behavior? > You need to modify (or create a new) default page template in the database. This template will have a specified layout, set of regions and default widgets for those regions. When a user logs in, if they don't have any pages configured, their portal page is configured from the default template. There are two existing defaults in the database that should give you pointers on how to configure yours. > > Thanks, > Chris >
Hello! We are trying to get our own portal set up and were wondering how to create and set a default page template for new users. To clarify, new users should have the default page set up for them with our layout and widgets. We also want them to be able to change these pages without affecting the copies that other users have. I've heard this is done by modifying a few things in the mongo database after creating the page we want with an existing user. Does anyone know how to setup this behavior? Thanks, Chris
Hi, Thank you for the response. On Tue, Jun 11, 2013 at 12:03 AM, Matt Franklin <m.ben.franklin@gmail.com>wrote: > Hi Sameera, > > A bug was recently reported regarding a failure to start when using the > custom maven archetype. It should be fixed by our next release, which is > scheduled to be publicly available in July. > > > > On Mon, Jun 10, 2013 at 1:50 PM, Sameera Jayaratna < > sameerajayaratna@gmail.com> wrote: > > > Hi, > > > > I'm interested in using Apache Rave to build a portal of my own. > Therefore > > I would like to customize it. I went through the documentation and > followed > > the steps given in "Extend Apache Rave to build your own portal" [1]. I > > followed up to the steps > > > > cd myraveproject-portal > > mvn cargo:run > > > > As I understood, after this step I should be able to access it on * > > http://localhost:8080/myraveproject-portal/* . But I get a 404 for it. > > Where have I gone wrong? > > > > Thank you, > > Sameera > > > > > > [1] http://rave.apache.org/documentation/rave-extensions.html > > > -- *Sameera Jayaratna* *Undergraduate* *Department of Computer Science And Engineering* *University of Moratuwa* *Sri Lanka*
Hi, Thank you for the response. On Tue, Jun 11, 2013 at 12:03 AM, Matt Franklin <m.ben.franklin@gmail.com>wrote: > Hi Sameera, > > A bug was recently reported regarding a failure to start when using the > custom maven archetype. It should be fixed by our next release, which is > scheduled to be publicly available in July. > > > > On Mon, Jun 10, 2013 at 1:50 PM, Sameera Jayaratna < > sameerajayaratna@gmail.com> wrote: > > > Hi, > > > > I'm interested in using Apache Rave to build a portal of my own. > Therefore > > I would like to customize it. I went through the documentation and > followed > > the steps given in "Extend Apache Rave to build your own portal" [1]. I > > followed up to the steps > > > > cd myraveproject-portal > > mvn cargo:run > > > > As I understood, after this step I should be able to access it on * > > http://localhost:8080/myraveproject-portal/* . But I get a 404 for it. > > Where have I gone wrong? > > > > Thank you, > > Sameera > > > > > > [1] http://rave.apache.org/documentation/rave-extensions.html > > > -- *Sameera Jayaratna* *Undergraduate* *Department of Computer Science And Engineering* *University of Moratuwa* *Sri Lanka*
Hi Sameera, A bug was recently reported regarding a failure to start when using the custom maven archetype. It should be fixed by our next release, which is scheduled to be publicly available in July. On Mon, Jun 10, 2013 at 1:50 PM, Sameera Jayaratna < sameerajayaratna@gmail.com> wrote: > Hi, > > I'm interested in using Apache Rave to build a portal of my own. Therefore > I would like to customize it. I went through the documentation and followed > the steps given in "Extend Apache Rave to build your own portal" [1]. I > followed up to the steps > > cd myraveproject-portal > mvn cargo:run > > As I understood, after this step I should be able to access it on * > http://localhost:8080/myraveproject-portal/* . But I get a 404 for it. > Where have I gone wrong? > > Thank you, > Sameera > > > [1] http://rave.apache.org/documentation/rave-extensions.html >
Hi, I'm interested in using Apache Rave to build a portal of my own. Therefore I would like to customize it. I went through the documentation and followed the steps given in "Extend Apache Rave to build your own portal" [1]. I followed up to the steps cd myraveproject-portal mvn cargo:run As I understood, after this step I should be able to access it on * http://localhost:8080/myraveproject-portal/* . But I get a 404 for it. Where have I gone wrong? Thank you, Sameera [1] http://rave.apache.org/documentation/rave-extensions.html
Ram, I'm not sure I understand what your problem is exactly. Can you provide more context? When does it happen? Does it happen everywhere or just in one place? You didn't give us a lot to go on here. Chris On Tue, May 21, 2013 at 8:04 AM, Bahadur, Ram <rgurung@mitre.org> wrote: > packaging issue in tags resolved - local change - > org.apache.rave.portal.model.RegionWidget instead of > org.apache.rave.model.RegionWidget > > -----Original Message----- > From: Bahadur, Ram > Sent: Tuesday, May 21, 2013 9:59 AM > To: 'users@rave.apache.org' > Cc: 'dev@rave.apache.org' > Subject: FW: Error - region.tag(35,8) - Unknown attribute type > (org.apache.rave.portal.model.RegionWidget) for attribute regionWidget > > > > -----Original Message----- > From: Bahadur, Ram > Sent: Tuesday, May 21, 2013 9:58 AM > To: dev@rave.apache.org > Subject: Error - region.tag(35,8) - Unknown attribute type > (org.apache.rave.portal.model.RegionWidget) for attribute regionWidget > > Using Rave version 0.21.1 - Getting following error and fails to render > the page > > org.apache.jasper.JasperException: /WEB-INF/tags/region.tag(35,8) Unknown > attribute type (org.apache.rave.portal.model.RegionWidget) for attribute > regionWidget. > > Stacktrace > SEVERE: Servlet.service() for servlet jsp threw exception > org.apache.jasper.JasperException: /WEB-INF/tags/region.tag(35,8) Unknown > attribute type (org.apache.rave.portal.model.RegionWidget) for attribute > regionWidget. > at > org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) > at > org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407) > at > org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236) > at > org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1199) > at > org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:846) > at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1530) > at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361) > at > org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2411) > at > org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:865) > at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1530) > at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361) > at > org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2411) > at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2417) > at org.apache.jasper.compiler.Node$Root.accept(Node.java:495) > at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361) > at > org.apache.jasper.compiler.Validator.validateExDirectives(Validator.java:1763) > at > org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:198) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:354) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:334) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:321) > at > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:592) > at > org.apache.jasper.servlet.JspServletWrapper.loadTagFile(JspServletWrapper.java:224) > at > org.apache.jasper.compiler.TagFileProcessor.loadTagFile(TagFileProcessor.java:629) > at > org.apache.jasper.compiler.TagFileProcessor.access$000(TagFileProcessor.java:52) > at > org.apache.jasper.compiler.TagFileProcessor$TagFileLoaderVisitor.visit(TagFileProcessor.java:689) > at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1530) > at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361) > at > org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2411) > at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2417) > at org.apache.jasper.compiler.Node$Root.accept(Node.java:495) > at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361) > at > org.apache.jasper.compiler.TagFileProcessor.loadTagFiles(TagFileProcessor.java:707) > at > org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:210) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:354) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:334) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:321) > at > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:592) > at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313) > at > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) >
packaging issue in tags resolved - local change - org.apache.rave.portal.model.RegionWidget
instead of org.apache.rave.model.RegionWidget
-----Original Message-----
From: Bahadur, Ram
Sent: Tuesday, May 21, 2013 9:59 AM
To: 'users@rave.apache.org'
Cc: 'dev@rave.apache.org'
Subject: FW: Error - region.tag(35,8) - Unknown attribute type (org.apache.rave.portal.model.RegionWidget)
for attribute regionWidget
-----Original Message-----
From: Bahadur, Ram
Sent: Tuesday, May 21, 2013 9:58 AM
To: dev@rave.apache.org
Subject: Error - region.tag(35,8) - Unknown attribute type (org.apache.rave.portal.model.RegionWidget)
for attribute regionWidget
Using Rave version 0.21.1 - Getting following error and fails to render the page
org.apache.jasper.JasperException: /WEB-INF/tags/region.tag(35,8) Unknown attribute type (org.apache.rave.portal.model.RegionWidget)
for attribute regionWidget.
Stacktrace
SEVERE: Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: /WEB-INF/tags/region.tag(35,8) Unknown attribute type (org.apache.rave.portal.model.RegionWidget)
for attribute regionWidget.
at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236)
at org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1199)
at org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:846)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1530)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2411)
at org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:865)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1530)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2411)
at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2417)
at org.apache.jasper.compiler.Node$Root.accept(Node.java:495)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361)
at org.apache.jasper.compiler.Validator.validateExDirectives(Validator.java:1763)
at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:198)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:354)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:334)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:321)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:592)
at org.apache.jasper.servlet.JspServletWrapper.loadTagFile(JspServletWrapper.java:224)
at org.apache.jasper.compiler.TagFileProcessor.loadTagFile(TagFileProcessor.java:629)
at org.apache.jasper.compiler.TagFileProcessor.access$000(TagFileProcessor.java:52)
at org.apache.jasper.compiler.TagFileProcessor$TagFileLoaderVisitor.visit(TagFileProcessor.java:689)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1530)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2411)
at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2417)
at org.apache.jasper.compiler.Node$Root.accept(Node.java:495)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361)
at org.apache.jasper.compiler.TagFileProcessor.loadTagFiles(TagFileProcessor.java:707)
at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:210)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:354)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:334)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:321)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:592)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
-----Original Message-----
From: Bahadur, Ram
Sent: Tuesday, May 21, 2013 9:58 AM
To: dev@rave.apache.org
Subject: Error - region.tag(35,8) - Unknown attribute type (org.apache.rave.portal.model.RegionWidget)
for attribute regionWidget
Using Rave version 0.21.1 - Getting following error and fails to render the page
org.apache.jasper.JasperException: /WEB-INF/tags/region.tag(35,8) Unknown attribute type (org.apache.rave.portal.model.RegionWidget)
for attribute regionWidget.
Stacktrace
SEVERE: Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: /WEB-INF/tags/region.tag(35,8) Unknown attribute type (org.apache.rave.portal.model.RegionWidget)
for attribute regionWidget.
at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236)
at org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1199)
at org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:846)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1530)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2411)
at org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:865)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1530)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2411)
at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2417)
at org.apache.jasper.compiler.Node$Root.accept(Node.java:495)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361)
at org.apache.jasper.compiler.Validator.validateExDirectives(Validator.java:1763)
at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:198)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:354)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:334)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:321)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:592)
at org.apache.jasper.servlet.JspServletWrapper.loadTagFile(JspServletWrapper.java:224)
at org.apache.jasper.compiler.TagFileProcessor.loadTagFile(TagFileProcessor.java:629)
at org.apache.jasper.compiler.TagFileProcessor.access$000(TagFileProcessor.java:52)
at org.apache.jasper.compiler.TagFileProcessor$TagFileLoaderVisitor.visit(TagFileProcessor.java:689)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1530)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2411)
at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2417)
at org.apache.jasper.compiler.Node$Root.accept(Node.java:495)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361)
at org.apache.jasper.compiler.TagFileProcessor.loadTagFiles(TagFileProcessor.java:707)
at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:210)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:354)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:334)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:321)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:592)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
The Apache Rave team is pleased to announce immediate availability of the Apache Rave 0.21.1 release. This release improves separation between Rave's portal and core widget-management functionalities. It also adresses a number of bugs identified in the 0.21 release. About Apache Rave: Apache Rave is a new web and social mashup engine. It provides an out-of-the-box, as well as extendible, lightweight Java platform to host, serve and manage OpenSocial, W3C and other web widgets. Apache Rave is targeted as an engine for internet and intranet portals and as a building block to provide context-aware personalization and collaboration features for multi-site/multi-channel (mobile) oriented and content driven websites. The release can be obtained from the Apache Rave download page http://rave.apache.org/downloads.html
However, we do plan to support preferences for wookie widgets as well. It is our intention that an end user will not know or care about the specification a gadget / widget is using and see uniform functionality. On Tue, Apr 2, 2013 at 2:16 PM, Matt Franklin <m.ben.franklin@gmail.com> wrote: > On Tue, Apr 2, 2013 at 1:55 PM, Brian Hawkins <brianhks1@gmail.com> wrote: > >> Just to be clear you have open social gadgets (shindig) and w3c widgets >> (wookie) >> >> When I create a gadget with preferences, a menu to edit those preferences >> is automatically created (in other words I don't have to write any html to >> allow a user to edit the preferences) >> >> When I create a widget with preferences the edit menu it disabled. Is >> there plans to make that edit menu work for both gadgets and widgets? >> > > Unfortunately, this has not been implemented yet. The Wookie connector > needs to support setting/getting preferences from a remote system first. > There are a lot of Wookie committers in Rave, so I hope to see this get > resolved soon. > > >> >> Brian >> >> >> On Tue, Apr 2, 2013 at 11:32 AM, Matt Franklin <m.ben.franklin@gmail.com >> >wrote: >> >> > On Tue, Apr 2, 2013 at 12:54 PM, Erin Noe-Payne < >> erin.noe.payne@gmail.com >> > >wrote: >> > >> > > > With gadgets I'm able to add preferences and then edit those >> > preferences >> > > > from the drop down menu in the upper right corner when displayed in >> > rave. >> > > > >> > > > I'm now trying to use the widget spec and after I add a preference >> the >> > > > 'edit preferences' menu option is disabled. Is this supposed to work >> > for >> > > > widgets or am I just doing something wrong. >> > > > >> > > > Brian >> > > >> > > Hey Brian, I'm not entirely following your question. Are you making a >> > > distinction between gadgets and widgets? When you say you are using >> > > the widget spec, do you mean updating your opensocial gadget xml to >> > > support a new preference? >> > > >> > >> > Or are you referring to Wookie widgets? >> > >>
On Tue, Apr 2, 2013 at 1:55 PM, Brian Hawkins <brianhks1@gmail.com> wrote: > Just to be clear you have open social gadgets (shindig) and w3c widgets > (wookie) > > When I create a gadget with preferences, a menu to edit those preferences > is automatically created (in other words I don't have to write any html to > allow a user to edit the preferences) > > When I create a widget with preferences the edit menu it disabled. Is > there plans to make that edit menu work for both gadgets and widgets? > Unfortunately, this has not been implemented yet. The Wookie connector needs to support setting/getting preferences from a remote system first. There are a lot of Wookie committers in Rave, so I hope to see this get resolved soon. > > Brian > > > On Tue, Apr 2, 2013 at 11:32 AM, Matt Franklin <m.ben.franklin@gmail.com > >wrote: > > > On Tue, Apr 2, 2013 at 12:54 PM, Erin Noe-Payne < > erin.noe.payne@gmail.com > > >wrote: > > > > > > With gadgets I'm able to add preferences and then edit those > > preferences > > > > from the drop down menu in the upper right corner when displayed in > > rave. > > > > > > > > I'm now trying to use the widget spec and after I add a preference > the > > > > 'edit preferences' menu option is disabled. Is this supposed to work > > for > > > > widgets or am I just doing something wrong. > > > > > > > > Brian > > > > > > Hey Brian, I'm not entirely following your question. Are you making a > > > distinction between gadgets and widgets? When you say you are using > > > the widget spec, do you mean updating your opensocial gadget xml to > > > support a new preference? > > > > > > > Or are you referring to Wookie widgets? > > >
Just to be clear you have open social gadgets (shindig) and w3c widgets (wookie) When I create a gadget with preferences, a menu to edit those preferences is automatically created (in other words I don't have to write any html to allow a user to edit the preferences) When I create a widget with preferences the edit menu it disabled. Is there plans to make that edit menu work for both gadgets and widgets? Brian On Tue, Apr 2, 2013 at 11:32 AM, Matt Franklin <m.ben.franklin@gmail.com>wrote: > On Tue, Apr 2, 2013 at 12:54 PM, Erin Noe-Payne <erin.noe.payne@gmail.com > >wrote: > > > > With gadgets I'm able to add preferences and then edit those > preferences > > > from the drop down menu in the upper right corner when displayed in > rave. > > > > > > I'm now trying to use the widget spec and after I add a preference the > > > 'edit preferences' menu option is disabled. Is this supposed to work > for > > > widgets or am I just doing something wrong. > > > > > > Brian > > > > Hey Brian, I'm not entirely following your question. Are you making a > > distinction between gadgets and widgets? When you say you are using > > the widget spec, do you mean updating your opensocial gadget xml to > > support a new preference? > > > > Or are you referring to Wookie widgets? >
On Tue, Apr 2, 2013 at 12:54 PM, Erin Noe-Payne <erin.noe.payne@gmail.com>wrote: > > With gadgets I'm able to add preferences and then edit those preferences > > from the drop down menu in the upper right corner when displayed in rave. > > > > I'm now trying to use the widget spec and after I add a preference the > > 'edit preferences' menu option is disabled. Is this supposed to work for > > widgets or am I just doing something wrong. > > > > Brian > > Hey Brian, I'm not entirely following your question. Are you making a > distinction between gadgets and widgets? When you say you are using > the widget spec, do you mean updating your opensocial gadget xml to > support a new preference? > Or are you referring to Wookie widgets?
> With gadgets I'm able to add preferences and then edit those preferences > from the drop down menu in the upper right corner when displayed in rave. > > I'm now trying to use the widget spec and after I add a preference the > 'edit preferences' menu option is disabled. Is this supposed to work for > widgets or am I just doing something wrong. > > Brian Hey Brian, I'm not entirely following your question. Are you making a distinction between gadgets and widgets? When you say you are using the widget spec, do you mean updating your opensocial gadget xml to support a new preference?
With gadgets I'm able to add preferences and then edit those preferences from the drop down menu in the upper right corner when displayed in rave. I'm now trying to use the widget spec and after I add a preference the 'edit preferences' menu option is disabled. Is this supposed to work for widgets or am I just doing something wrong. Brian
On Fri, Mar 8, 2013 at 2:43 PM, Chris Geer <chris@cxtsoftware.com> wrote: > All, I've been playing with the OpenSocial Gadget href support and have run > into an issue that I'm not sure is supported or not and if it is, if it's a > Rave or Shindig issue. OpenSocial allows module definitions like this: > > <?xml version="1.0" encoding="UTF-8" ?> > <Module> > <ModulePrefs title="Report"> > <Require feature="views" /> > <Require feature="open-views" /> > <Require feature="embedded-experiences" /> > </ModulePrefs> > <Content type="html" view="home" href="http://192.168.114.131:8080/Test > "/> > </Module> > > Where the gadget data is loaded from the href directly. That works great > for static pages however if that page also loads additional items like > javascript, the request doesn't seem to be proxied to the backend server > and returns a 404 error. I think the problem is with the links because if I > have my gadget XML at http://localhost:8080/xyz/test.xml it then looks for > any secondary files in the same place, which it won't find. I would think > all those URLs would need to be rewritten during the initial render to > point to Shindig/Rave so that the real resource can be proxied properly. > > Has anyone gotten this to work before? I would look at the content re-writer: http://opensocial-resources.googlecode.com/svn/spec/2.5/Core-Gadget.xml#rfc.section.5 > > Chris
The Apache Rave team is pleased to announce immediate availability of the Apache Rave 0.20.1 release. This release addresses the security issue found in CVE-2013-1814. All users who rely on Rave's user management are encouraged to upgrade. About Apache Rave: Apache Rave is a new web and social mashup engine. It provides an out-of-the-box, as well as extendible, lightweight Java platform to host, serve and manage OpenSocial, W3C and other web widgets. Apache Rave is targeted as an engine for internet and intranet portals and as a building block to provide context-aware personalization and collaboration features for multi-site/multi-channel (mobile) oriented and content driven websites. The release can be obtained from the Apache Rave download page http://rave.apache.org/downloads.html
CVE-2013-1814: Apache Rave exposes User over API
Severity: Important
Vendor: The Apache Software Foundation
Versions Affected:
Rave 0.11 to 0.20
Description:
Rave returns the full user object, including the salted and hashed
password, via the User RPC API. This endpoint is only available to
authenticated users, but will return all User objects in the database
given the correct query.
Mitigation:
All users who rely on Rave's user management capabilities should
upgrade to 0.20.1 or later.
If an upgrade is infeasible, restrict access to the /app/api/user URL
paths via Spring Security configuration or other means.
Example:
A request to:
/app/api/rpc/users/get?offset=3DOFFSET
will return the following:
{"error":false,"errorMessage":null,"errorCode":"NO_ERROR","result":{"result=
Set":[{"entityId":1,"username":"canonical","email":"canonical@example.com",=
"displayName":"Canonical
User","additionalName":"canonical","familyName":"User","givenName":"Canonic=
al","honorificPrefix":null,"honorificSuffix":null,"preferredName":null,"abo=
utMe":null,"status":"Single","addresses":[],"organizations":[],"properties"=
:[{"entityId":1,"type":"thumbnailUrl","value":"http://opensocial2.org:8080/=
collabapp/images/avatars/BillRanney.jpg","qualifier":null,"extendedValue":n=
ull,"primary":null,"id":"1"}],"password":"$2a$10$TkEgze5kLy9nRlfd8PT1zunh6P=
1ND8WPjLojFjAMNgZMu1D9D1n4.","expired":false,"locked":false,"enabled":true,=
"openId":null,"forgotPasswordHash":null,"forgotPasswordTime":null,"defaultP=
ageLayout":{"entityId":4,"code":"columns_3","numberOfRegions":3,"renderSequ=
ence":3,"userSelectable":true},"confirmPassword":null,"defaultPageLayoutCod=
e":null,"authorities":[{"entityId":2,"authority":"ROLE_ADMIN","users":[],"d=
efaultForNewUser":false}],"id":"1","accountNonLocked":true,"credentialsNonE=
xpired":true,"accountNonExpired":true},
........ ],"pageSize":10,"offset":0,"totalResults":14,"numberOfPages":2,"cu=
rrentPage":1}}
Credit:
This issue was discovered by Andreas Guth of RWTH Aachen University.
References:
http://tomcat.apache.org/security.html
Hi, I think it's better to wait for the main developers to provide a clean solution. But I need oauth will be needed anyway. You can always provide an anonymous login to the wookie or shinding environment and do autenthication hardcoded... But... let's wait a little bit! :D E l mar, 12-03-2013 a las 11:46 +0530, rajandeep vij escribió:T he other day I was also looking on rendering of widgets on the page > > rendered simultaneously. > > For now I have planned to have a new page (a non editable page) for which > login page will have a link. The same way other links work on the login > page... new account etc.,. > > But rave has security restrictions on rendering of the widgets, for which I > should pass an authenticated/authorized user Id. Now for an anonymous user > what shall be done? > > How do I bypass authorization checks for this anonymous user? > > Any suggestions? > On Tue, Mar 12, 2013 at 1:03 AM, Gonzalo Aguilar Delgado < > gaguilar@aguilardelgado.com> wrote: > > > > > > > > > > > > > But one thing I don't understand as of now is how would I render > > widgets on > > > > Login page without a proper page being created w/o tabs etc. > > > > > > > > > > I'm not sure it's really possible given the structure of Rave. Maybe > > > someone else can give you some pointers here if there is a work around. > > > > > > > > > Hello, > > > > since I have investigated the rendering pipe in depth I think this is > > currently not possible as is on 0.21. > > > > This is because JSP tags are deeply nested and inner ones need the > > information of the outer ones, and you cannot get the inner ones out of > > current layout. You also need a layout, but I think this can be taken > > out of the page.jsp page and transferred to another one. > > > > Unfortunately TABS are needed since they define layout, loaded widgets > > and some other page requirements. Taking this apart will need some > > work. > > > > I'm developing a different frontend based on wicket instead of JSP... > > > > I will try to take this requirement on my current wicket frontend. If > > you handle to get around the need of login to show widget maybe it will > > work. > > > > Hope it helps. > > > > > > > >
Thanks Gonzalo, The other day I was also looking on rendering of widgets on the page and realized that, it is not possible to render widgets w/o pages being rendered simultaneously. For now I have planned to have a new page (a non editable page) for which login page will have a link. The same way other links work on the login page... new account etc.,. But rave has security restrictions on rendering of the widgets, for which I should pass an authenticated/authorized user Id. Now for an anonymous user what shall be done? How do I bypass authorization checks for this anonymous user? Any suggestions? On Tue, Mar 12, 2013 at 1:03 AM, Gonzalo Aguilar Delgado < gaguilar@aguilardelgado.com> wrote: > > > > > > > > But one thing I don't understand as of now is how would I render > widgets on > > > Login page without a proper page being created w/o tabs etc. > > > > > > > I'm not sure it's really possible given the structure of Rave. Maybe > > someone else can give you some pointers here if there is a work around. > > > > > Hello, > > since I have investigated the rendering pipe in depth I think this is > currently not possible as is on 0.21. > > This is because JSP tags are deeply nested and inner ones need the > information of the outer ones, and you cannot get the inner ones out of > current layout. You also need a layout, but I think this can be taken > out of the page.jsp page and transferred to another one. > > Unfortunately TABS are needed since they define layout, loaded widgets > and some other page requirements. Taking this apart will need some > work. > > I'm developing a different frontend based on wicket instead of JSP... > > I will try to take this requirement on my current wicket frontend. If > you handle to get around the need of login to show widget maybe it will > work. > > Hope it helps. > > > -- R D Vij *"Whatever it be... whatever.. Just remeber at the End you are left to make everything go good...." Luv yourself and have faith in yourself.* * * *Cheers!!!*
> > > > But one thing I don't understand as of now is how would I render widgets on > > Login page without a proper page being created w/o tabs etc. > > > > I'm not sure it's really possible given the structure of Rave. Maybe > someone else can give you some pointers here if there is a work around. > Hello, since I have investigated the rendering pipe in depth I think this is currently not possible as is on 0.21. This is because JSP tags are deeply nested and inner ones need the information of the outer ones, and you cannot get the inner ones out of current layout. You also need a layout, but I think this can be taken out of the page.jsp page and transferred to another one. Unfortunately TABS are needed since they define layout, loaded widgets and some other page requirements. Taking this apart will need some work. I'm developing a different frontend based on wicket instead of JSP... I will try to take this requirement on my current wicket frontend. If you handle to get around the need of login to show widget maybe it will work. Hope it helps.
All, I've been playing with the OpenSocial Gadget href support and have run
into an issue that I'm not sure is supported or not and if it is, if it's a
Rave or Shindig issue. OpenSocial allows module definitions like this:
<?xml version="1.0" encoding="UTF-8" ?>
<Module>
<ModulePrefs title="Report">
<Require feature="views" />
<Require feature="open-views" />
<Require feature="embedded-experiences" />
</ModulePrefs>
<Content type="html" view="home" href="http://192.168.114.131:8080/Test
"/>
</Module>
Where the gadget data is loaded from the href directly. That works great
for static pages however if that page also loads additional items like
javascript, the request doesn't seem to be proxied to the backend server
and returns a 404 error. I think the problem is with the links because if I
have my gadget XML at http://localhost:8080/xyz/test.xml it then looks for
any secondary files in the same place, which it won't find. I would think
all those URLs would need to be rewritten during the initial render to
point to Shindig/Rave so that the real resource can be proxied properly.
Has anyone gotten this to work before?
Chris
Thanks Chris. I am eagerly waiting for someone to reply me on rendering widgets on home page. Cheers!! On 8 Mar 2013 21:27, "Chris Geer" <chris@cxtsoftware.com> wrote: > On Fri, Mar 8, 2013 at 4:39 AM, rajandeep vij <rajandeepvij@gmail.com > >wrote: > > > Hey Chris, > > > > I had never used this option before, I was trying to configure tomcat > > server on which rave is running. > > Debug works perfectly now. > > > > Glad it works. > > > > > I am also trying to get few widgets to Login page.. to give a just look > and > > feel to the users of widgets. > > > > * I understand I will have to remove the authorization at few places.. > just > > for now > > * I understand I will have to pass a few dummy data.. as I don't how can > I > > create anonymous user in Rave > > > > Right now that's not possible. RAVE-897 is an open ticket we have to make > anonymous users possible. I don't have an ETA on when it will get done > though. > > > > > But one thing I don't understand as of now is how would I render widgets > on > > Login page without a proper page being created w/o tabs etc. > > > > I'm not sure it's really possible given the structure of Rave. Maybe > someone else can give you some pointers here if there is a work around. > > > > > Any idea? Any suggestions? > > > > Thanks. > > > > Regards, > > Rajan > > > > On Fri, Mar 8, 2013 at 12:02 AM, Chris Geer <chris@cxtsoftware.com> > wrote: > > > > > On Thu, Mar 7, 2013 at 4:26 AM, rajandeep vij <rajandeepvij@gmail.com > > > >wrote: > > > > > > > Hi All, > > > > > > > > I couldn't actually found where widgets are connected to page? > > > > > > > > My case is : Let's say there exists a few widgets that have > > > > been restricted for some users , so that they can't add them from > > Widget > > > > Store . Now if admin is creating a page and he could add those > widgets > > > that > > > > were restricted for a set of users as I mentioned above and shared > that > > > > page with the users, users after accepting the page would be able to > > view > > > > the widgets. > > > > > > > > > > Pages -> Regions -> RegionWidgets -> Widgets > > > > > > > > > > > So I want to understand how and where a page renderer includes > widgets > > to > > > > be displayed and renders them. > > > > > > > > I could do this easily if my I could debug.... but I am unable to > debug > > > > rave in eclipse. > > > > > > > > > > The best way to debug is (IMHO) is to run rave using cargo like normal > > "mvn > > > cargo:run". This will enable remote debugging by default on port 8000. > > Then > > > in your IDE, configure a debug configuration to attach to a remote > > process > > > on port 8000 and it should be good to go. I don't use Eclipse but this > > > works great in IntelliJ. > > > > > > > > > > > Regards, > > > > Rajan > > > > > > > > > > > > > > > -- > > R D Vij > > > > *"Whatever it be... whatever.. Just remeber at the End you are left to > make > > everything go good...." Luv yourself and have faith in yourself.* > > * > > * > > *Cheers!!!* > > >
On Fri, Mar 8, 2013 at 4:39 AM, rajandeep vij <rajandeepvij@gmail.com>wrote: > Hey Chris, > > I had never used this option before, I was trying to configure tomcat > server on which rave is running. > Debug works perfectly now. > Glad it works. > > I am also trying to get few widgets to Login page.. to give a just look and > feel to the users of widgets. > > * I understand I will have to remove the authorization at few places.. just > for now > * I understand I will have to pass a few dummy data.. as I don't how can I > create anonymous user in Rave > Right now that's not possible. RAVE-897 is an open ticket we have to make anonymous users possible. I don't have an ETA on when it will get done though. > > But one thing I don't understand as of now is how would I render widgets on > Login page without a proper page being created w/o tabs etc. > I'm not sure it's really possible given the structure of Rave. Maybe someone else can give you some pointers here if there is a work around. > > Any idea? Any suggestions? > > Thanks. > > Regards, > Rajan > > On Fri, Mar 8, 2013 at 12:02 AM, Chris Geer <chris@cxtsoftware.com> wrote: > > > On Thu, Mar 7, 2013 at 4:26 AM, rajandeep vij <rajandeepvij@gmail.com > > >wrote: > > > > > Hi All, > > > > > > I couldn't actually found where widgets are connected to page? > > > > > > My case is : Let's say there exists a few widgets that have > > > been restricted for some users , so that they can't add them from > Widget > > > Store . Now if admin is creating a page and he could add those widgets > > that > > > were restricted for a set of users as I mentioned above and shared that > > > page with the users, users after accepting the page would be able to > view > > > the widgets. > > > > > > > Pages -> Regions -> RegionWidgets -> Widgets > > > > > > > > So I want to understand how and where a page renderer includes widgets > to > > > be displayed and renders them. > > > > > > I could do this easily if my I could debug.... but I am unable to debug > > > rave in eclipse. > > > > > > > The best way to debug is (IMHO) is to run rave using cargo like normal > "mvn > > cargo:run". This will enable remote debugging by default on port 8000. > Then > > in your IDE, configure a debug configuration to attach to a remote > process > > on port 8000 and it should be good to go. I don't use Eclipse but this > > works great in IntelliJ. > > > > > > > > Regards, > > > Rajan > > > > > > > > > -- > R D Vij > > *"Whatever it be... whatever.. Just remeber at the End you are left to make > everything go good...." Luv yourself and have faith in yourself.* > * > * > *Cheers!!!* >
Hey Chris, I had never used this option before, I was trying to configure tomcat server on which rave is running. Debug works perfectly now. I am also trying to get few widgets to Login page.. to give a just look and feel to the users of widgets. * I understand I will have to remove the authorization at few places.. just for now * I understand I will have to pass a few dummy data.. as I don't how can I create anonymous user in Rave But one thing I don't understand as of now is how would I render widgets on Login page without a proper page being created w/o tabs etc. Any idea? Any suggestions? Thanks. Regards, Rajan On Fri, Mar 8, 2013 at 12:02 AM, Chris Geer <chris@cxtsoftware.com> wrote: > On Thu, Mar 7, 2013 at 4:26 AM, rajandeep vij <rajandeepvij@gmail.com > >wrote: > > > Hi All, > > > > I couldn't actually found where widgets are connected to page? > > > > My case is : Let's say there exists a few widgets that have > > been restricted for some users , so that they can't add them from Widget > > Store . Now if admin is creating a page and he could add those widgets > that > > were restricted for a set of users as I mentioned above and shared that > > page with the users, users after accepting the page would be able to view > > the widgets. > > > > Pages -> Regions -> RegionWidgets -> Widgets > > > > > So I want to understand how and where a page renderer includes widgets to > > be displayed and renders them. > > > > I could do this easily if my I could debug.... but I am unable to debug > > rave in eclipse. > > > > The best way to debug is (IMHO) is to run rave using cargo like normal "mvn > cargo:run". This will enable remote debugging by default on port 8000. Then > in your IDE, configure a debug configuration to attach to a remote process > on port 8000 and it should be good to go. I don't use Eclipse but this > works great in IntelliJ. > > > > > Regards, > > Rajan > > > -- R D Vij *"Whatever it be... whatever.. Just remeber at the End you are left to make everything go good...." Luv yourself and have faith in yourself.* * * *Cheers!!!*
On Thu, Mar 7, 2013 at 4:26 AM, rajandeep vij <rajandeepvij@gmail.com>wrote: > Hi All, > > I couldn't actually found where widgets are connected to page? > > My case is : Let's say there exists a few widgets that have > been restricted for some users , so that they can't add them from Widget > Store . Now if admin is creating a page and he could add those widgets that > were restricted for a set of users as I mentioned above and shared that > page with the users, users after accepting the page would be able to view > the widgets. > Pages -> Regions -> RegionWidgets -> Widgets > > So I want to understand how and where a page renderer includes widgets to > be displayed and renders them. > > I could do this easily if my I could debug.... but I am unable to debug > rave in eclipse. > The best way to debug is (IMHO) is to run rave using cargo like normal "mvn cargo:run". This will enable remote debugging by default on port 8000. Then in your IDE, configure a debug configuration to attach to a remote process on port 8000 and it should be good to go. I don't use Eclipse but this works great in IntelliJ. > > Regards, > Rajan >
Hi All, I couldn't actually found where widgets are connected to page? My case is : Let's say there exists a few widgets that have been restricted for some users , so that they can't add them from Widget Store . Now if admin is creating a page and he could add those widgets that were restricted for a set of users as I mentioned above and shared that page with the users, users after accepting the page would be able to view the widgets. So I want to understand how and where a page renderer includes widgets to be displayed and renders them. I could do this easily if my I could debug.... but I am unable to debug rave in eclipse. Regards, Rajan
Hi Team, I have checked out the Apache rave 0.21 and could build and run it with no issues at all.."mvn cargo:run" executes perfectly. I want to debug this now in IDE (I am using STS), I have used following steps * Imported maven project into STS * Installed wro4j * Installed FileSync * made changes to apache Shinding and portal projects for the context. * now when I run it on eclipse with Tomcat server added and Shinding and Portal projects included into server. I get this error Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'ravePermissionEvaluator' defined in URL [jar:file:/F:/ApacehRave/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rave-portal/WEB-INF/lib/rave-core-0.21-SNAPSHOT.jar!/org/apache/rave/portal/security/impl/RavePermissionEvaluator.class]: Unsatisfied dependency expressed through constructor argument with index 0 of type [java.util.List]: : Error creating bean with name 'defaultCategoryPermissionEvaluator' defined in URL [jar:file:/F:/ApacehRave/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rave-portal/WEB-INF/lib/rave-core-0.21-SNAPSHOT.jar!/org/apache/rave/portal/security/impl/DefaultCategoryPermissionEvaluator.class]: Unsatisfied dependency expressed through constructor argument with index 0 of type [org.apache.rave.portal.repository.CategoryRepository]: : Error creating bean with name 'jpaCategoryR Am I doing something wrong? H2 jar was also not present on tomcat/lib I had to put that there. Any step that I have missed? Thanks. Rajan
On Fri, Mar 1, 2013 at 2:38 PM, Benjamin Prosnitz <benjamin@nerati.com> wrote: > I built Rave 0.20 (from the Zip on windows) with *mvn clean install* > and started tomcat with *mvn cargo:run*. However, when I try to access > the running server via http://localhost:8080 on my browser, I get the > following error: Someone else reported this on the DEV list yesterday. Not everyone is experiencing this issue, but we are investigating and will notify the list when we know more. > > javax.servlet.ServletException: java.lang.LinkageError: loader > constraint violation: when resolving interface method > "javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory;" > the class loader (instance of org/apache/jasper/servlet/JasperLoader) > of the current class, org/apache/jsp/index_jsp, and the class loader > (instance of org/apache/catalina/loader/StandardClassLoader) for > resolved class, javax/servlet/jsp/JspApplicationContext, have > different Class objects for the type javax/el/ExpressionFactory used > in the signature > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:268) > javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > org.apache.shindig.gadgets.servlet.ETagFilter.doFilter(ETagFilter.java:56) > org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:359) > org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:275) > org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90) > org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83) > org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:344) > org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:272) > org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:81) > > > This is using Java 1.6.0_37 on Windows. Any idea how I can resolve this error? > > Thanks!
I built Rave 0.20 (from the Zip on windows) with *mvn clean install* and started tomcat with *mvn cargo:run*. However, when I try to access the running server via http://localhost:8080 on my browser, I get the following error: javax.servlet.ServletException: java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory;" the class loader (instance of org/apache/jasper/servlet/JasperLoader) of the current class, org/apache/jsp/index_jsp, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature org.apache.jasper.servlet.JspServlet.service(JspServlet.java:268) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.apache.shindig.gadgets.servlet.ETagFilter.doFilter(ETagFilter.java:56) org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:359) org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:275) org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90) org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83) org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:344) org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:272) org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:81) This is using Java 1.6.0_37 on Windows. Any idea how I can resolve this error? Thanks!
Hi Rajan, I have included answers inline below: On Mon, Feb 25, 2013 at 6:47 AM, rajandeep vij <rajandeepvij@gmail.com> wrote: > Hi, > > I have a requirement where, I have been asked to create a portal kind > application. > > Portal would have widgets like for Hudson?Jenkins and a few for our > knowledge Management site. > > I have created rave maven demo project and could access it on my machine, > though I am facing issues trying to add any widget as of now... I would > like to understand the process I could create widgets for the above > requirements. You can add widgets via the Widget Store ---> Add New Widget interface, or via the database directly. In Wookie's case, you will need to look at the wookie documentation for how to add new widgets: http://cwiki.apache.org/WOOKIE/wookie-server-administrators-guide.html. To create widgets, you should check the OpenSocial & W3C Widget Family specifications and resources. > > As far as I understand Shindig and wookie are provided some list of gadgets > which I should be able to add on portal, but > > * from where will I build custom widgets? In the case of OpenSocial, the gadgets are only referenced by URL. So long as they are accessible via HTTP, then you can just add them via the store. > * where will I deploy my custom widgets? Wherever you like :), per above > * how will I access them on Rave? Users should be able to add widgets that are published to their page. See the Admin section for how to publish widgets. > > Thanks. > Rajan > > > -- > R D Vij > > *"Whatever it be... whatever.. Just remeber at the End you are left to make > everything go good...." Luv yourself and have faith in yourself.* > * > * > *Cheers!!!*
Hi Derek, Sorry for the delay, many of us have been at ApacheCon and therefore a little busy with the events there. I have responded inline below: On Fri, Feb 22, 2013 at 6:21 AM, Derek Rendall <richards.rendall@gmail.com> wrote: > Hi > > I have downloaded the binary, and even checked out from SVN - both working fine. My question now, as a newbie to portal development (but not architecture), is what is the best way to implement what I need in a portal. Here is what I'm after: > > 1) I need the ability to have public as well as private widgets (I have designed similar approach for Liferay before with public and private communities). There will be anonymous access to a few key capabilities, but external users will need to signup/login to extract full value from the site. Internal users will log into the sight to access a different set of widgets etc. I presume that I will need to create my own version of the home page, but I don't know if it's best to edit directly in the downloaded code or if its best to treat Rave as a black box and create a separate project with a dependancy upon Rave (and if so, hints on how would be appreciated). My preference is to keep an ability to upgrade Rave as a separate component without introducing too many changes that require complicated merging. There is an open issue to support anonymous views. If I understand correctly, this would be what you are looking for as well. JIRA is not responding for me now, but I will follow up with a link. If you have thoughts or experience on how to tackle this issue, please feel free to start or join the conversation on the dev@ list. > 2) I need to create my own private/public widgets (with some social integration as an enhanced capability). I'm not familiar with Shindig or Wookie, so I can't tell which approach would be best, or whether its something I create "within" the Rave development or outside and deploy to a runtime? Shindig & Wookie are implementations of OpenSocial and W3C Widget Family specifications, respectively. Each of the frameworks has its tradeoffs, and it really depends on what you would like to do with the widgets. If you want activity stream integration and social data, OpenSocial might fit best. If you want to package your widgets and upload them to the widget server, wookie might be a better choice. In both cases, the development of widgets is something unrelated to Rave. Rave just references them by URL. > 3) Not at the moment, but I believe an aspect of content management will be useful in the near term - I note the presentations on Spring HMVC extension, and was wondering what is the state of the content-services sandbox? The lessons learned in that sandbox are driving a new, simpler architecture in the core Rave application. We are working toward a much more loosely coupled system and stronger separation between the "core" widget management and portal functionality. Hopefully, we can reintegrate the concepts, if not the code directly, once we have re-architected the services. > > Thanks > > Derek > >
Hi, I have a requirement where, I have been asked to create a portal kind application. Portal would have widgets like for Hudson?Jenkins and a few for our knowledge Management site. I have created rave maven demo project and could access it on my machine, though I am facing issues trying to add any widget as of now... I would like to understand the process I could create widgets for the above requirements. As far as I understand Shindig and wookie are provided some list of gadgets which I should be able to add on portal, but * from where will I build custom widgets? * where will I deploy my custom widgets? * how will I access them on Rave? Thanks. Rajan -- R D Vij *"Whatever it be... whatever.. Just remeber at the End you are left to make everything go good...." Luv yourself and have faith in yourself.* * * *Cheers!!!*
Hi I have downloaded the binary, and even checked out from SVN - both working fine. My question now, as a newbie to portal development (but not architecture), is what is the best way to implement what I need in a portal. Here is what I'm after: 1) I need the ability to have public as well as private widgets (I have designed similar approach for Liferay before with public and private communities). There will be anonymous access to a few key capabilities, but external users will need to signup/login to extract full value from the site. Internal users will log into the sight to access a different set of widgets etc. I presume that I will need to create my own version of the home page, but I don't know if it's best to edit directly in the downloaded code or if its best to treat Rave as a black box and create a separate project with a dependancy upon Rave (and if so, hints on how would be appreciated). My preference is to keep an ability to upgrade Rave as a separate component without introducing too many changes that require complicated merging. 2) I need to create my own private/public widgets (with some social integration as an enhanced capability). I'm not familiar with Shindig or Wookie, so I can't tell which approach would be best, or whether its something I create "within" the Rave development or outside and deploy to a runtime? 3) Not at the moment, but I believe an aspect of content management will be useful in the near term - I note the presentations on Spring HMVC extension, and was wondering what is the state of the content-services sandbox? Thanks Derek
Thanks Chris -- using java 1.7 I was able to get a successful build. > Welcome to Rave and sorry you ran into a problem on your first attempt. > > I believe this may be caused by a bug in your version of the JDK [1]. > You'll notice the affected version is 6u20. This particular issue shows it > was fixed in Java 7 but if you look at the related backport links lower in > the bug report it looks like it was back ported to 6u22 and above. Is > there > any chance you can try to upgrade your JDK version and try again? > > I can confirm it compiles on 6u37. > > Also, if you are just looking to run the system you can download the demo > binaries which are all setup to run from here [2]. > > Thanks, > Chris > > [1] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6302954 > [2] http://rave.apache.org/downloads.html > > On Tue, Feb 19, 2013 at 4:53 PM, <rave@onticage.com> wrote: > >> First time user/setup. I am using maven (3.0.3) and java (1.6.0_20) but >> getting a build failure on the rave-mongodb component. >> >> [ERROR] >> >> /my/path/rave/trunk/rave-components/rave-mongodb/src/main/java/org/apache/rave/portal/repository/impl/MongoModelTemplate.java:[79,39] >> type parameters of <T>T cannot be determined; no unique maximal instance >> exists for type variable T with upper bounds E,java.lang.Object >> >> I just started following the Getting Started directions here: >> http://rave.apache.org/source.html >> >> 1. svn co >> 2. mvn install >> >> Any insights? I don't really intend to use mongodb for persistence >> anyway >> but didn't want to remove the dependency from the pom if this is >> something >> silly I'm tripping myself over. >> >> It looks like this code was changed a bit in the last few months, not >> sure >> if these are relevant yet... >> >> >> http://stackoverflow.com/questions/11747020/error-type-parameters-of-tt-cannot-be-determined-during-maven-install >> >> >> http://stackoverflow.com/questions/5666027/why-does-the-compiler-state-no-unique-maximal-instance-exists >> >> Thanks. >> >> >
Welcome to Rave and sorry you ran into a problem on your first attempt. I believe this may be caused by a bug in your version of the JDK [1]. You'll notice the affected version is 6u20. This particular issue shows it was fixed in Java 7 but if you look at the related backport links lower in the bug report it looks like it was back ported to 6u22 and above. Is there any chance you can try to upgrade your JDK version and try again? I can confirm it compiles on 6u37. Also, if you are just looking to run the system you can download the demo binaries which are all setup to run from here [2]. Thanks, Chris [1] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6302954 [2] http://rave.apache.org/downloads.html On Tue, Feb 19, 2013 at 4:53 PM, <rave@onticage.com> wrote: > First time user/setup. I am using maven (3.0.3) and java (1.6.0_20) but > getting a build failure on the rave-mongodb component. > > [ERROR] > > /my/path/rave/trunk/rave-components/rave-mongodb/src/main/java/org/apache/rave/portal/repository/impl/MongoModelTemplate.java:[79,39] > type parameters of <T>T cannot be determined; no unique maximal instance > exists for type variable T with upper bounds E,java.lang.Object > > I just started following the Getting Started directions here: > http://rave.apache.org/source.html > > 1. svn co > 2. mvn install > > Any insights? I don't really intend to use mongodb for persistence anyway > but didn't want to remove the dependency from the pom if this is something > silly I'm tripping myself over. > > It looks like this code was changed a bit in the last few months, not sure > if these are relevant yet... > > > http://stackoverflow.com/questions/11747020/error-type-parameters-of-tt-cannot-be-determined-during-maven-install > > > http://stackoverflow.com/questions/5666027/why-does-the-compiler-state-no-unique-maximal-instance-exists > > Thanks. > >
First time user/setup. I am using maven (3.0.3) and java (1.6.0_20) but getting a build failure on the rave-mongodb component. [ERROR] /my/path/rave/trunk/rave-components/rave-mongodb/src/main/java/org/apache/rave/portal/repository/impl/MongoModelTemplate.java:[79,39] type parameters of <T>T cannot be determined; no unique maximal instance exists for type variable T with upper bounds E,java.lang.Object I just started following the Getting Started directions here: http://rave.apache.org/source.html 1. svn co 2. mvn install Any insights? I don't really intend to use mongodb for persistence anyway but didn't want to remove the dependency from the pom if this is something silly I'm tripping myself over. It looks like this code was changed a bit in the last few months, not sure if these are relevant yet... http://stackoverflow.com/questions/11747020/error-type-parameters-of-tt-cannot-be-determined-during-maven-install http://stackoverflow.com/questions/5666027/why-does-the-compiler-state-no-unique-maximal-instance-exists Thanks.
Hi Ate, I will join to the dev list so because I think I can contribute a little bit to the project. Though I'm still analyzing how this project can fit in my requirements. :-) About complexity. You are right. This project can be grow huge. But as you said the difficult part is to ease the life of each group of target users without making life more miserable for the others... This is really difficult but not impossible. I recently checked out Firefox Marketplace project. That is a HUGE project. Aside technology used (truly different). It builds, compiles dependencies, downloads artifacts and runs smoothly. Really! I'm able to work on it after just a few seconds after it finished configuring. Everything seems to be clear. And looks impressive! :-P And while templating system they are using remembers me a lot to velocity (I hate templating, even PHP language switched away this approach). They make clear that this technology is used and how it's used. Let me introduce at least a little doubt about jsp and templating in the dev maillist so we can discuss it. Maybe there is a good point on it. I hope so. :D El vie, 15-02-2013 a las 12:58 +0100, Ate Douma escribió: > Hi Gonzalo, > > Nice to see you here and being interested in Rave. > > First of all, thank you for your serious feedback and suggestions! > And to be clear upfront, I recognize and experience many if not most of the pain > points you report. But I might have a different view on why we have them and how > some can or should be solved, or not :) > > Before trying to respond in more detail below, let me make a general observation > upfront which IMO is important to note. > > A project like Jetspeed, or Rave, is quite different when compared to many other > projects you'll find at Apache. > And that difference comes from the very different and diverse audiences or type > of users: > - core developers, working on base or low level features > - UI/frontend developers, working on end-user experiences or > customization/theming capabilities thereof > - initial or casual reviewers needing a demo or a quick (and dirty) > out-of-the-box starting point to play with and prototype possible use-cases > - product users like integrators, mostly using the project 'as-is', only > slightly customized to their needs or tastes > - downstream developers using the project embedded, as building block or > platform to build a new product on top > > Such a high diversity on *type* of users is not very common, and very unlike > you'll typically find with other projects, like Wicket. > A more fair project comparison (that is: from this perspective) would be against > projects like Liferay, JBoss Portal or within Apache maybe projects like > Geronimo, OFBiz, etc. > > The above is not an excuse but should be taken into account why projects like > Jetspeed, Rave, etc. turn out to be more complex than for instance a casual > developer/user would wish for. But simplifying it for one type of audience, like > (only) for such developers, easily will make life much more miserable for > others. And figuring out an 'easy fix' which takes into account all or most of > the needs and requirements of the difference users, isn't so easy. > > All that said, I do agree building Rave today (again) is probably more > complicated than needed in some areas. Or maybe some technology choices should > be reconsidered (if not already under reconsideration, please subscribe to the > dev@ list as we tend to more discuss these things there). So you're feedback is > very much appreciated and to be considered carefully by the team. > > > On 02/14/2013 05:39 PM, Gonzalo Aguilar Delgado wrote: > > Hello, > > > > I recently switched my attention to this project. Please let me do a short > > introduction so I can explain me better. > > > > I'm triying to build a marketing system from 2 years on. I was looking at most > > advanced arquitectures that can grow with time. One of my elections was > > jetspeed. Now I know it was a big mistake. Let me introduce why. > > > > I found that the system is complex and overbloated. To change just the theme you > > have to go through a nightmare of velocity templates, jsps, and javascript all > > mixed on. No one designer wanted to take it and change it. Belive me. Nor do I. > > [I created a component to render with wicket, it worked and was great to build a > > new gui with it but I then realized that it would be a lot of effort for an > > obsolete system, this is my opinion]. > > > > To make it worse you have to deal with a tailormade build system that only works > > when ran from the command line, if something goes wrong you are out of luck. If > > you want to implement some feature you have to deal with "overlays". Basicly the > > build system copies the original version and then does a unzip of your package > > over it. This is a pain to handle. > > > > So I was thinking to build my own system based on Gadgets, Services, and a > > lightweight interface. This is where *rave* comes in. > > > > Rave is the project I was looking for. > > > > But when I tried to use I found almost the same problems. > > > > [First] The system is based on plan old JSP, and Tiles?: > > > > Please, don't make same mistakes. Use wicket. Let me explain why. > > > > 1.- You can work with talented gui designers, web specialists. Otherway you > > can't. Nobody is going to take JSP and change it, nobody is going to update > > tiles. It will look much better if you can get some talented designers. Will > > sell a lot more :-) > > 2.- You can separate completly the logic form the design. Let's make UI > > attractive. This is a must! > > 3.- Is an apache project. > > 4.- Is well supported. > > 5.- Supports html5 + ajax. This is again a must! > > > > I kind of agree with most reasons and arguments you give above. And I don't like > JSP and/or Tiles either. But replacing it with Wicket isn't the 'golden bullet' > either IMO. > Wicket is a cool project and very feasible for many things. But I wouldn't > choose it here and then force it upon every Rave downstream projects and users. > There already has been several but minor discussions (mainly on the dev@ list) > about front-end and server-side technology choices. I think currently the idea > is more to move in the direction of mostly state-less server-side (REST) > services and leverage them from smart client-side javascript based aggregation > solutions, than picking (again) another, and more state-full, server-side web > framework. > Note: I do like the Wicket component and hierarchical aggregation capabilities, > but IMO it is more fit for dedicated application oriented solutions but less for > generic platform and service orchestration. > > > > > [Second] Keep it simple. > > > > The build system is *again* overcomplex. Why do you do all this kind of stuff? > > > > What's the "com.googlecode.mavenfilesync" stuff? Why it's all required? > Actually, it is or was intended to 'help' Eclipse users. Optionally, not > required. I'm no longer an Eclipse user though, and I don't think many Rave > developers are, so to be honest I have no idea if or how that works today. > > > > > I suppose it's not. Please do not make harder to new developers help. This was > > something it was done in jetspeed that kept a lot of people *out* of the project. > Well, certainly not intentional. Please also realize and recognize the fact that > it helped a lot of *other* people to use that project. > But I fully agree with your general comment. We must strive to keep it as simple > and easy as possible. And backtrack when something doesn't work out, or turns > out no longer to be needed or used. This might be such a case. > > > > > It must be handled/deployed in eclipse/netbeans or whatever ide easily. I found > > that maven cargo:deploy worked but I cannot start the application because > > something failed in the configuration. Since everything was packed into wars I > > had to: > > 1.- Deploy it. > > 2.- Look at it failing bad. > > 3.- Try to fix it over the deployed instance. > > 4.- Copy changed to the main project. > > > > Well I wasn't able to inmediatly track it down. Because of the complexity of the > > build system. When I try deploy it with eclipse, some files are missing. I don't > > know why they appears when I do maven cargo:deploy. Where are they? > This is a very specific question, but without more specific information > impossible to answer. Please raise a separate issue or question if you still > need or want this answered. > > Also please note that the mavenfilesync plugin configuration you mentioned above > was provided exactly because of this use-case (automatically synchronize Eclipse > file changes into the cargo deploy env). > > Concerning the 'whatever' IDE support in general. > While I agree this really is a pain point, other than providing, checking in and > maintaining IDE specific configurations, it is very difficult to generalize and > standardize how to manage and debug a multi-war build/deploy configuration > across IDEs. Single war projects typically are much easier, could use an > embedded servlet engine even, but this is not our 'minimal' setup. We need at > least two, three or even more webapps running concurrently (Shindig, Rave and > optionally Wookie, other gadgets apps). > > > > > Of course I cannot debug because the cargo deployment is outside my eclipse > > config. So I have to move things around to make them run from the vm instance > > it's running inside eclipse. > > > > Having 5 wars deployed for just a demo seems to be a lot. I'm sure there is a > > explanation. But nothing seems to be obvious. > > Well for this it should be obvious. > Our multi-war deployment setup is the logical consequence of a portal platform > where gadget/widget services like Shindig and Wookie are serviced through an > separate (web) application, and necessarily so. They might also be running on a > different host. In practice and in production they most likely are. > So while it *might* be possible to 'merge' (or worse: overlay) multiple of these > wars into one for IDE development/debugging convenience, its a > non-realistic/practical case. And IMO also technically undesirable (dependency > conflict hell). > > Anyway, it doesn't mean it cannot be made easier, but I expect it'll require > more IDE specifics then. And we'll then have to deal with many different > solutions, for Eclipse, Netbeans, IntelliJ IDEA, etc. > And it needs volunteers willing to set this up, and maintain it... > > > > > There is a ROOT context that seems to be the portal, because has a lot of html > > and jps, but it can't be because there is already a portal context, so What's > > this for? > That's Shindig which is deployed by default (because its 'easier') to ROOT. > You'll find the mapping and deployment configuration in the cargo plugin. > > > > > There is also a cargocpc context. That seems todo nothing... Can it be? > The cargocpc is a minimal app injected by cargo to help the plugin to be > notified about the startup/shutdown of the container. Its the lightest possible > app and should really not cause any side-effect or be in the way. So it is used > and needed, but only during development and local cargo deploy. > > > > > Also wookie is deployed. Since it looks good because the project rely on wookie > > for the gadgets, it's not. It seems to have a dependency on the persistence > > libraries deployed with the project that makes it fail on start. [Maybe the > > previous config fault?] > I agree the Wookie integration isn't ideal yet. Which also has been raised > before on the dev@ list, just need some more attention to improve upon. And as > we have several Wookie committers also on the Rave team, further discussing this > and coordinating on it should be not a problem. And further input and proposal > to improve it much appreciated. > > > > > In my opinion if wookie is not tightly integrated it should run completly > > decoupled. If it can't be decoupled then do it right: Embed the system with a > > connector an deploy it with the rest. > I agree we need to 'fix' the Wookie deployment and (database) management issues. > But also note that this concerns the demo and/or development setup only. And for > those purposes I think integrating with Wookie, and demonstrating it, is very > relevant, although using Wookie is optional and should remain so. > > It might be possible maybe to provide some different development 'profiles' to > include/exclude some components like Wookie. But we use Maven primarily, still, > and Maven profiles are typically not recognized or appreciated well by IDEs > either. But if you suggestions how to solve such things, please let us know! > > > > > > > ---------------- > > ---------------- > > So for me it leads to two things: > > > > 1.- Keep things easy and lightweight. [Wicket = +Designers] > > 2.- Let others to get hands dirty in the project without much hassle. [Easy to > > build = More developers] > > > > > > Hope you have this into account. > > I think we will :) > > > > > Looks promising! I will surely fork it to see if I can contribute something. > Great, looking forward to it! > > > > > Thanks a lot! > > > > PS: Just for reference in JIRA I missed the list in first place... ;-) > > https://issues.apache.org/jira/browse/RAVE-892 > > > I think I'll close that issue as it is more appropriate to discuss these things > on the mailing list (and maybe better dev@ in this case). > JIRA really shouldn't be used for open discussions IMO. >