I have Rave running on Glassfish now.
Figured out the issue. In shindig web.xml file, Glassfish expects a "/" before
the url-pattern for etagFilter mapping.
<filter-mapping>
<filter-name>etagFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
Steps to run Rave on Glassfish:
1. Add metadata-complete="true" to all the web.xml files which use JPA. (one is
shindig and one is rave-portal-resources).
2. Prefix a / to the url-pattern for the filter mapping etagFilter in shindig
web.xml
Let me know if you have have other issues….
-Venkat
-----Original Message-----
From: Mahadevan, Venkat [mailto:[email protected]]
Sent: Thursday, November 17, 2011 10:02 AM
To: [email protected]
Subject: RE: [jira] [Commented] (RAVE-361) Deploy Rave on Jetty
Here is the error from the admin command line.
asadmin> deploy "C:\Users\venkatm\Desktop\ROOT.war"
remote failure: Error occurred during deployment: Exception while deploying the
app [ROOT] : Invalid URL Pattern: [*]. Please see server.log for more details.
Command deploy failed.
-----Original Message-----
From: Mahadevan, Venkat
Sent: Thursday, November 17, 2011 10:00 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [jira] [Commented] (RAVE-361) Deploy Rave on Jetty
Hi Jasha
I downloaded Glassfish 3.1.1 and tried it. It looks like there is some issue
with the way JPA RESOURCE_LOCAL is handled in Glassfish. This was overcome with
adding metadata-complete="true" to the web.xml files (one is shindig and one is
rave-portal-resources).
I having some issues with running shindig though. Here is the error that I got.
Looks like there is some issue with the URL mapping. Will take a look at it.
[#|2011-11-17T09:17:00.442-0500|SEVERE|glassfish3.1.1|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=18;_ThreadName=admin-thread-pool-48
);|Exception while deploying the app [ROOT] : Invalid URL Pattern: [*]|#]
[#|2011-11-17T09:19:57.397-0500|WARNING|glassfish3.1.1|null|_ThreadID=19;_ThreadName=admin-thread-pool-4848(3);|Error
occurred
java.lang.IllegalArgumentException: Invalid URL Pattern: [*]
at
com.sun.enterprise.deployment.node.web.FilterMappingNode.setElementValue(FilterMappingNode.java:137)
at
com.sun.enterprise.deployment.node.SaxParserHandler.endElement(SaxParserHandler.java:451)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601)
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.endElement(XMLSchemaValidator.java:822)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1782)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2939)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at
com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:306)
at
com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:233)
at
com.sun.enterprise.deployment.archivist.Archivist.readStandardDeploymentDescriptor(Archivist.java:639)
at
com.sun.enterprise.deployment.archivist.ApplicationFactory.createApplicationFromStandardDD(ApplicationFactory.java:216)
at
org.glassfish.javaee.core.deployment.DolProvider.getNameFor(DolProvider.java:234)
at
org.glassfish.internal.deployment.GenericHandler.getDefaultApplicationName(GenericHandler.java:143)
at
org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:222)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1064)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1244)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1232)
at
com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:459)
at
com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:209)
at
com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168)
at
com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:238)
at
com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:828)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:725)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1019)
at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
at
com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at
com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at
com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:662)
|#]
-Venkat
-----Original Message-----
From: Jasha Joachimsthal (Commented) (JIRA)
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Thursday, November 17, 2011 8:41 AM
To: [email protected]<mailto:[email protected]>
Subject: [jira] [Commented] (RAVE-361) Deploy Rave on Jetty
[
https://issues.apache.org/jira/browse/RAVE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152046#comment-13152046
]
Jasha Joachimsthal commented on RAVE-361:
-----------------------------------------
Go ahead. Do you have time to check if Rave runs out of the box in Glassfish?
> Deploy Rave on Jetty
> --------------------
>
> Key: RAVE-361
> URL: https://issues.apache.org/jira/browse/RAVE-361
> Project: Rave
> Issue Type: Improvement
> Reporter: Raminderjeet Singh
> Fix For: 0.6-INCUBATING
>
> Attachments: pom.xml
>
>
> Ioan Kiss reported about Rave not working on Jetty and here are the steps he
> followed
> Here are the steps followed in running Rave on Jetty server 7.5.4
> 1. Download Jetty 7.5.4
> 2.Download rave (apache-rave-0.5-incubating-bin.zip)
> 3. Copied portal.war, root.war and demogadgets.war in Jetty/webapps folder
> 4. start jetty - did not noticed any errors during jetty startup
> 5. open browser and type http://localhost:8080/portal/
> 6. The login page was displayed
> 7. Enter canonical/canonical and hit login button
> 8. Directory view displayed (Directory: /portal/);
> in the jetty console I found the following message (32646
> ravePersistenceUnit WARN [qtp31505416-12 -
> /portal/j_spring_security_check] openjpa.Runtime - Query "select u from User
> u where u.username = :username" is removed from cache excluded permanently.
> Query "select u from User u where u.username = :username" is not cached
> because it generates multiple SQL statements. A query can be cached only
> when it corresponds to a single SQL statement.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
