[
https://issues.apache.org/jira/browse/TRINIDAD-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603922#action_12603922
]
Scott O'Bryan commented on TRINIDAD-1089:
-----------------------------------------
While I'm not so keen to provide top-level pre-built support for non-j2ee
container, it seems that the current demo will work (as-is) in neither a
standard J2EE environment OR in tomcat. The reason for this is that MyFaces is
packaged, by default, with the demos. So if we have a standard J2EE container,
MyFaces will interfere with the built-in implementation. Jetty has JSTL and
NOT faces, and Tomcat has neither. Furthermore, the Trinidad POMS are hard to
manage and it has been a while since they've been updated. Therefore, here is
my proposal to solve this issue:
* By default the demo's will include neither JSF nor JSTL libraries. These
will no longer be present in the distribution.
* Add two profiles which may be used from maven to support adding these to a
custom build of the demo projects: includeJSF and includeJSTL
* Continue to support the jettyConfig parameter which will include JSF and not
JSTL by default
* Continue to support the jsf=ri property to select which version of JSF gets
packaged with the demo or used with Jetty
My enhancements also include much better versioning support (thorough
properties) for Trinidad's dependent libraries and a "release" profile which is
automatically activated when a mvn release:perform is done instead of having to
do a mvn release:perform -Prelease like we have to do today. It also includes
an includeBridge profile which will include the bridge jars for testing the
demo in a portlet environment.
I've also cleaned up the -DprepareRelease profile activation to work much
cleaner with the assembly projects.
If these changes look good, I'll check this in along with some documentation
which outlines these build options so it should be possible to generate a war
file for use in just about any container.
> trinidad-demo.war does not run in non-J2EE container as distributed.
> --------------------------------------------------------------------
>
> Key: TRINIDAD-1089
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1089
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 1.0.8-core, 1.2.8-core
> Reporter: Paul Spencer
> Assignee: Scott O'Bryan
>
> The trinidad-demo.war does not run in a non-J2EE container, like Tomcat, as
> distributed in examples.zip/tar.gz. This is due to a missing JSTL jar which
> is provided by a J2EE container. This improvement is simplify the process of
> installing the demo in a non-J2EE container. Changes should include
> documentation included in the distribution and available on demo project's
> web site. Additional change may be required in the POM.
> Their is a related thread titled "Trinidad] Should a non-J2EE demo war be
> added to the distribution" in the myfaces-dev mailing list. [1]
> ***
> * The procedure I used to run trinidad-demo.war in Tomcat 6.0.16
> ***
> 1) Download the examples distribution
> 2) Copy the trinidad-demo.war from the distribution to Tomcat's webapps
> directory
> 3) After Tomcat exploded the war, I copied jstl-1.2.jar into the WEB-INF/lib
> directory of the exploded war.
> 4) Restart tomcat.
> [1] http://markmail.org/message/7ah2zedr57ppzfx6
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
