You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@shale.apache.org by sc...@apache.org on 2006/07/31 21:30:47 UTC
svn commit: r427223 - /shale/sandbox/shale-petstore/pom.xml
Author: schof
Date: Mon Jul 31 12:30:46 2006
New Revision: 427223
URL: http://svn.apache.org/viewvc?rev=427223&view=rev
Log:
changed JSF dep to RI; added jsp-2.1 api dp (still need to get the EL dependency added)
Modified:
shale/sandbox/shale-petstore/pom.xml
Modified: shale/sandbox/shale-petstore/pom.xml
URL: http://svn.apache.org/viewvc/shale/sandbox/shale-petstore/pom.xml?rev=427223&r1=427222&r2=427223&view=diff
==============================================================================
--- shale/sandbox/shale-petstore/pom.xml (original)
+++ shale/sandbox/shale-petstore/pom.xml Mon Jul 31 12:30:46 2006
@@ -72,7 +72,6 @@
</plugin>
</plugins>
</build>
-
<dependencies>
<dependency>
<groupId>commons-lang</groupId>
@@ -80,14 +79,14 @@
<version>2.1</version>
</dependency>
<dependency>
- <groupId>org.apache.myfaces.core</groupId>
- <artifactId>myfaces-api</artifactId>
- <version>1.1.5-SNAPSHOT</version>
+ <groupId>javax.faces</groupId>
+ <artifactId>jsf-api</artifactId>
+ <version>1.2-b19</version>
</dependency>
<dependency>
- <groupId>org.apache.myfaces.core</groupId>
- <artifactId>myfaces-impl</artifactId>
- <version>1.1.5-SNAPSHOT</version>
+ <groupId>javax.faces</groupId>
+ <artifactId>jsf-impl</artifactId>
+ <version>1.2-b19</version>
</dependency>
<dependency>
<groupId>org.apache.myfaces.tomahawk</groupId>
@@ -163,7 +162,12 @@
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.13</version>
- </dependency>
+ </dependency>
+ <dependency>
+ <groupId>javax.servlet.jsp</groupId>
+ <artifactId>jsp-api</artifactId>
+ <version>2.1</version>
+ </dependency>
<!-- provided deps -->
<dependency>
<groupId>javax.servlet</groupId>
Re: svn commit: r427223 - /shale/sandbox/shale-petstore/pom.xml
Posted by Sean Schofield <se...@gmail.com>.
This list is for discussing the development of the Apache Shale
project. Try posting your question on the facelets user list instead.
They should be able to help you there.
Sean
On 8/29/06, Varun <va...@gmail.com> wrote:
>
> Hi I am planning to add facelet support to an already existing project of
> mine. I addded the follwing three libs jsf-facelets.jar, el-api.jar and
> el-ri.jar and the other jars in my lib are the commons (4) jars,
> jsf-api,jsf-impl, jstl, standard and tl-common.jar. I added a very simple
> facelet page (the number guess example) and tried to run it but got the very
> same error :
> Error Rendering View[/facelet1.jsp] Could not instantiate
> feature[compiler.ExpressionFactory]: com.sun.el.ExpressionFactoryImpl
> at com.sun.facelets.compiler.Compiler.featureInstance(Compiler.java:153)
> at
> com.sun.facelets.compiler.Compiler.createExpressionFactory(Compiler.java:142)
> at
> com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:193)
> at
> com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:141)......
>
> According to this post this should have been resolved if we had the el-api
> and el-ri jars in my lib folder. These libs have been added to the class
> path and btw i downloaded the jars from the java.net site.
>
> What else can be the problem. For facelets I have added a single entry in
> the faces-config.xml file for the view-handler. Do I need to make more
> changes in this file or any other file. Thanks for the help.
>
>
> Mike Kienenberger wrote:
> >
> > Yes, el-api.jar and el-ri.jar are required.
> >
> > These are available from the glassfish project (facelets uses ant
> > tasks to download them from there, or at least that's how they used to
> > get fetched during the facelets build process).
> >
> > On 7/31/06, Sean Schofield <se...@gmail.com> wrote:
> >> According to the facelets site (section 1.2) the EL RI is also needed
> >> for facelets[1]. That's probably why I am getting the following stack
> >> trace:
> >>
> >> SEVERE: Error Rendering View[/welcome.xhtml]
> >> com.sun.facelets.FaceletException: Could not instantiate
> >> feature[compiler.ExpressionFactory]: com.sun.el.ExpressionFactoryImpl
> >> at
> >> com.sun.facelets.compiler.Compiler.featureInstance(Compiler.java:153)
> >> at
> >> com.sun.facelets.compiler.Compiler.createExpressionFactory(Compiler.java:127)
> >> at
> >> com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:193)
> >> ...
> >>
> >> I must have hard-copied that dep into the project and now that I'm
> >> using maven its not working.
> >>
> >> Sean
> >>
> >> [1] https://facelets.dev.java.net/nonav/docs/dev/docbook.html
> >>
> >> On 7/31/06, Craig McClanahan <cr...@apache.org> wrote:
> >> > On 7/31/06, schof@apache.org <sc...@apache.org> wrote:
> >> > >
> >> > > Author: schof
> >> > > Date: Mon Jul 31 12:30:46 2006
> >> > > New Revision: 427223
> >> > >
> >> > > URL: http://svn.apache.org/viewvc?rev=427223&view=rev
> >> > > Log:
> >> > > changed JSF dep to RI; added jsp-2.1 api dp (still need to get the EL
> >> > > dependency added)
> >> >
> >> >
> >> > I asked about this issue internally, and here's the answer I got: as
> >> of JSP
> >> > 2.1, the new unified EL APIs are still part of the JSP specification,
> >> so the
> >> > classes themselves are supposed to be in the jsp-api jar that your new
> >> > dependency references. If/when the unified EL classes are separated
> >> into
> >> > their own JSR (probably in some future maintenance rev of the JSP spec)
> >> they
> >> > will be split out into their own JAR and published separately.
> >> >
> >> > Craig
> >> >
> >> >
> >>
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Re%3A-svn-commit%3A-r427223----shale-sandbox-shale-petstore-pom.xml-tf2029610.html#a6039579
> Sent from the Shale - Dev forum at Nabble.com.
>
>
Re: svn commit: r427223 - /shale/sandbox/shale-petstore/pom.xml
Posted by Varun <va...@gmail.com>.
Hi I am planning to add facelet support to an already existing project of
mine. I addded the follwing three libs jsf-facelets.jar, el-api.jar and
el-ri.jar and the other jars in my lib are the commons (4) jars,
jsf-api,jsf-impl, jstl, standard and tl-common.jar. I added a very simple
facelet page (the number guess example) and tried to run it but got the very
same error :
Error Rendering View[/facelet1.jsp] Could not instantiate
feature[compiler.ExpressionFactory]: com.sun.el.ExpressionFactoryImpl
at com.sun.facelets.compiler.Compiler.featureInstance(Compiler.java:153)
at
com.sun.facelets.compiler.Compiler.createExpressionFactory(Compiler.java:142)
at
com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:193)
at
com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:141)......
According to this post this should have been resolved if we had the el-api
and el-ri jars in my lib folder. These libs have been added to the class
path and btw i downloaded the jars from the java.net site.
What else can be the problem. For facelets I have added a single entry in
the faces-config.xml file for the view-handler. Do I need to make more
changes in this file or any other file. Thanks for the help.
Mike Kienenberger wrote:
>
> Yes, el-api.jar and el-ri.jar are required.
>
> These are available from the glassfish project (facelets uses ant
> tasks to download them from there, or at least that's how they used to
> get fetched during the facelets build process).
>
> On 7/31/06, Sean Schofield <se...@gmail.com> wrote:
>> According to the facelets site (section 1.2) the EL RI is also needed
>> for facelets[1]. That's probably why I am getting the following stack
>> trace:
>>
>> SEVERE: Error Rendering View[/welcome.xhtml]
>> com.sun.facelets.FaceletException: Could not instantiate
>> feature[compiler.ExpressionFactory]: com.sun.el.ExpressionFactoryImpl
>> at
>> com.sun.facelets.compiler.Compiler.featureInstance(Compiler.java:153)
>> at
>> com.sun.facelets.compiler.Compiler.createExpressionFactory(Compiler.java:127)
>> at
>> com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:193)
>> ...
>>
>> I must have hard-copied that dep into the project and now that I'm
>> using maven its not working.
>>
>> Sean
>>
>> [1] https://facelets.dev.java.net/nonav/docs/dev/docbook.html
>>
>> On 7/31/06, Craig McClanahan <cr...@apache.org> wrote:
>> > On 7/31/06, schof@apache.org <sc...@apache.org> wrote:
>> > >
>> > > Author: schof
>> > > Date: Mon Jul 31 12:30:46 2006
>> > > New Revision: 427223
>> > >
>> > > URL: http://svn.apache.org/viewvc?rev=427223&view=rev
>> > > Log:
>> > > changed JSF dep to RI; added jsp-2.1 api dp (still need to get the EL
>> > > dependency added)
>> >
>> >
>> > I asked about this issue internally, and here's the answer I got: as
>> of JSP
>> > 2.1, the new unified EL APIs are still part of the JSP specification,
>> so the
>> > classes themselves are supposed to be in the jsp-api jar that your new
>> > dependency references. If/when the unified EL classes are separated
>> into
>> > their own JSR (probably in some future maintenance rev of the JSP spec)
>> they
>> > will be split out into their own JAR and published separately.
>> >
>> > Craig
>> >
>> >
>>
>
>
--
View this message in context: http://www.nabble.com/Re%3A-svn-commit%3A-r427223----shale-sandbox-shale-petstore-pom.xml-tf2029610.html#a6039579
Sent from the Shale - Dev forum at Nabble.com.
Re: svn commit: r427223 - /shale/sandbox/shale-petstore/pom.xml
Posted by Mike Kienenberger <mk...@gmail.com>.
Yes, el-api.jar and el-ri.jar are required.
These are available from the glassfish project (facelets uses ant
tasks to download them from there, or at least that's how they used to
get fetched during the facelets build process).
On 7/31/06, Sean Schofield <se...@gmail.com> wrote:
> According to the facelets site (section 1.2) the EL RI is also needed
> for facelets[1]. That's probably why I am getting the following stack
> trace:
>
> SEVERE: Error Rendering View[/welcome.xhtml]
> com.sun.facelets.FaceletException: Could not instantiate
> feature[compiler.ExpressionFactory]: com.sun.el.ExpressionFactoryImpl
> at com.sun.facelets.compiler.Compiler.featureInstance(Compiler.java:153)
> at com.sun.facelets.compiler.Compiler.createExpressionFactory(Compiler.java:127)
> at com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:193)
> ...
>
> I must have hard-copied that dep into the project and now that I'm
> using maven its not working.
>
> Sean
>
> [1] https://facelets.dev.java.net/nonav/docs/dev/docbook.html
>
> On 7/31/06, Craig McClanahan <cr...@apache.org> wrote:
> > On 7/31/06, schof@apache.org <sc...@apache.org> wrote:
> > >
> > > Author: schof
> > > Date: Mon Jul 31 12:30:46 2006
> > > New Revision: 427223
> > >
> > > URL: http://svn.apache.org/viewvc?rev=427223&view=rev
> > > Log:
> > > changed JSF dep to RI; added jsp-2.1 api dp (still need to get the EL
> > > dependency added)
> >
> >
> > I asked about this issue internally, and here's the answer I got: as of JSP
> > 2.1, the new unified EL APIs are still part of the JSP specification, so the
> > classes themselves are supposed to be in the jsp-api jar that your new
> > dependency references. If/when the unified EL classes are separated into
> > their own JSR (probably in some future maintenance rev of the JSP spec) they
> > will be split out into their own JAR and published separately.
> >
> > Craig
> >
> >
>
Re: svn commit: r427223 - /shale/sandbox/shale-petstore/pom.xml
Posted by Matthias Wessendorf <ma...@apache.org>.
Means, they use it for TC6
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/javax/el/
not on ibiblio though.
On 7/31/06, Sean Schofield <se...@gmail.com> wrote:
> I remember that discussion. But donated means what exactly? Is it
> checked in? Is it being built? Earlier today I looked for it under
> tomcat in ibiblio but I could not find it.
>
> Sean
>
> On 7/31/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > I posted this to facelets mailing list before I realized Sean switched
> > mailing lists on me :-)
> >
> > ================================
> >
> > Ok. Here's what a quick search of my mailbox turned up: it's donated
> > to Tomcat according to Jacob.
> >
> > ---------- Forwarded message ----------
> > From: jacob@hookom.net <ja...@hookom.net>
> > Date: May 5, 2006 1:25 PM
> > Subject: Re: el-ri.jar and commons-el
> > To: users@facelets.dev.java.net
> >
> > [...non-relevent text...]
> >
> > - I wrote the EL implementation for the RI and donated to Tomcat.
> > There is some debate as to whether the org.apache.el code should stay
> > with Jasper or if it should be migrated out to replace commons-el.
> > But that's for MyFaces-Dev and Tomcat-Dev to sort out.
> >
>
--
Matthias Wessendorf
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: svn commit: r427223 - /shale/sandbox/shale-petstore/pom.xml
Posted by Sean Schofield <se...@gmail.com>.
I remember that discussion. But donated means what exactly? Is it
checked in? Is it being built? Earlier today I looked for it under
tomcat in ibiblio but I could not find it.
Sean
On 7/31/06, Mike Kienenberger <mk...@gmail.com> wrote:
> I posted this to facelets mailing list before I realized Sean switched
> mailing lists on me :-)
>
> ================================
>
> Ok. Here's what a quick search of my mailbox turned up: it's donated
> to Tomcat according to Jacob.
>
> ---------- Forwarded message ----------
> From: jacob@hookom.net <ja...@hookom.net>
> Date: May 5, 2006 1:25 PM
> Subject: Re: el-ri.jar and commons-el
> To: users@facelets.dev.java.net
>
> [...non-relevent text...]
>
> - I wrote the EL implementation for the RI and donated to Tomcat.
> There is some debate as to whether the org.apache.el code should stay
> with Jasper or if it should be migrated out to replace commons-el.
> But that's for MyFaces-Dev and Tomcat-Dev to sort out.
>
Re: svn commit: r427223 - /shale/sandbox/shale-petstore/pom.xml
Posted by Mike Kienenberger <mk...@gmail.com>.
I posted this to facelets mailing list before I realized Sean switched
mailing lists on me :-)
================================
Ok. Here's what a quick search of my mailbox turned up: it's donated
to Tomcat according to Jacob.
---------- Forwarded message ----------
From: jacob@hookom.net <ja...@hookom.net>
Date: May 5, 2006 1:25 PM
Subject: Re: el-ri.jar and commons-el
To: users@facelets.dev.java.net
[...non-relevent text...]
- I wrote the EL implementation for the RI and donated to Tomcat.
There is some debate as to whether the org.apache.el code should stay
with Jasper or if it should be migrated out to replace commons-el.
But that's for MyFaces-Dev and Tomcat-Dev to sort out.
Re: svn commit: r427223 - /shale/sandbox/shale-petstore/pom.xml
Posted by Sean Schofield <se...@gmail.com>.
Well the api seems to be solved by including the jsp 2.1 dependency.
Unfortunately the EL-RI needs to be grabbed from the glassfish project
and installed manually. Perhaps we can get Sun to make that available
in ibiblio?
Sean
On 7/31/06, Greg Reddin <gr...@apache.org> wrote:
>
> On Jul 31, 2006, at 3:16 PM, Sean Schofield wrote:
>
> > According to the facelets site (section 1.2) the EL RI is also needed
> > for facelets[1]. That's probably why I am getting the following stack
> > trace:
>
> I was able to find the el-api JAR on a java.net maven repo, but I
> couldn't find the ri JAR anywhere. For our project we set up an
> internal maven repo that contains those JAR files until they put them
> in a public place.
>
> Greg
>
>
>
>
Re: svn commit: r427223 - /shale/sandbox/shale-petstore/pom.xml
Posted by Greg Reddin <gr...@apache.org>.
On Jul 31, 2006, at 3:16 PM, Sean Schofield wrote:
> According to the facelets site (section 1.2) the EL RI is also needed
> for facelets[1]. That's probably why I am getting the following stack
> trace:
I was able to find the el-api JAR on a java.net maven repo, but I
couldn't find the ri JAR anywhere. For our project we set up an
internal maven repo that contains those JAR files until they put them
in a public place.
Greg
Re: svn commit: r427223 - /shale/sandbox/shale-petstore/pom.xml
Posted by Sean Schofield <se...@gmail.com>.
According to the facelets site (section 1.2) the EL RI is also needed
for facelets[1]. That's probably why I am getting the following stack
trace:
SEVERE: Error Rendering View[/welcome.xhtml]
com.sun.facelets.FaceletException: Could not instantiate
feature[compiler.ExpressionFactory]: com.sun.el.ExpressionFactoryImpl
at com.sun.facelets.compiler.Compiler.featureInstance(Compiler.java:153)
at com.sun.facelets.compiler.Compiler.createExpressionFactory(Compiler.java:127)
at com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:193)
...
I must have hard-copied that dep into the project and now that I'm
using maven its not working.
Sean
[1] https://facelets.dev.java.net/nonav/docs/dev/docbook.html
On 7/31/06, Craig McClanahan <cr...@apache.org> wrote:
> On 7/31/06, schof@apache.org <sc...@apache.org> wrote:
> >
> > Author: schof
> > Date: Mon Jul 31 12:30:46 2006
> > New Revision: 427223
> >
> > URL: http://svn.apache.org/viewvc?rev=427223&view=rev
> > Log:
> > changed JSF dep to RI; added jsp-2.1 api dp (still need to get the EL
> > dependency added)
>
>
> I asked about this issue internally, and here's the answer I got: as of JSP
> 2.1, the new unified EL APIs are still part of the JSP specification, so the
> classes themselves are supposed to be in the jsp-api jar that your new
> dependency references. If/when the unified EL classes are separated into
> their own JSR (probably in some future maintenance rev of the JSP spec) they
> will be split out into their own JAR and published separately.
>
> Craig
>
>
Re: svn commit: r427223 - /shale/sandbox/shale-petstore/pom.xml
Posted by Craig McClanahan <cr...@apache.org>.
On 7/31/06, schof@apache.org <sc...@apache.org> wrote:
>
> Author: schof
> Date: Mon Jul 31 12:30:46 2006
> New Revision: 427223
>
> URL: http://svn.apache.org/viewvc?rev=427223&view=rev
> Log:
> changed JSF dep to RI; added jsp-2.1 api dp (still need to get the EL
> dependency added)
I asked about this issue internally, and here's the answer I got: as of JSP
2.1, the new unified EL APIs are still part of the JSP specification, so the
classes themselves are supposed to be in the jsp-api jar that your new
dependency references. If/when the unified EL classes are separated into
their own JSR (probably in some future maintenance rev of the JSP spec) they
will be split out into their own JAR and published separately.
Craig