Re: Problems running a JSF application on Jetty:Run

2006-11-02 Thread Wayne Fay

You realize this is the Maven Users list, not MyFaces, right? ;-)

Wayne

On 11/2/06, smccrory <[EMAIL PROTECTED]> wrote:


I hope this is a silly question, but does anyone know if ADF Faces/Tobago is
(now) compatable with Tomahawk, in particular its dataTable component?  I
remember reading about how the use of different renderers at least used to
be a problem.  Thanks in advance,
   Scott
--
View this message in context:
http://www.nabble.com/Problems-running-a-JSF-application-on-Jetty%3ARun-tf2515457s177.html#a7145843
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Problems running a JSF application on Jetty:Run

2006-11-02 Thread smccrory

I hope this is a silly question, but does anyone know if ADF Faces/Tobago is
(now) compatable with Tomahawk, in particular its dataTable component?  I
remember reading about how the use of different renderers at least used to
be a problem.  Thanks in advance,
   Scott
-- 
View this message in context: 
http://www.nabble.com/Problems-running-a-JSF-application-on-Jetty%3ARun-tf2515457s177.html#a7145843
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Problems running a JSF application on Jetty:Run

2006-11-01 Thread Craig McClanahan

On 11/1/06, Ronen Naor <[EMAIL PROTECTED]> wrote:


The problem is that the j2ee spec says that the jsf jars need to be as
part
of the container classpath.



Actually, that is only required (in the specs) for Java EE 5.  For EE 1.4,
you can either treat either the JSF RI or MyFaces as a normal dependency for
webapps and have it loaded in WEB-INF/lib, or do what you did and load it
into the container classpath.

Craig


Re: Problems running a JSF application on Jetty:Run

2006-11-01 Thread Ronen Naor

The problem is that the j2ee spec says that the jsf jars need to be as part
of the container classpath.
try:

   org.mortbay.jetty
   maven-jetty-plugin
.
   
   
   org.apache.myfaces.core
   myfaces-api
   1.1.3
   
   
   org.apache.myfaces.core
   myfaces-impl
   1.1.3
   
 ...

It worked for me



On 10/26/06, Dudu <[EMAIL PROTECTED]> wrote:


I can't discover the problem in this strack trace...
I'm running RI JSF implementation + tomahawk + ADF Faces:



this is the pom.xml


junit
junit
4.0
test


hibernate
hibernate
3.0
compile


log4j
log4j
1.2.12
compile


ojdbc
ojdbc
14
compile


oracle.adf
adf-faces-impl
10.1.3.0.4
compile


oracle.adf
adf-faces-api
10.1.3.0.4
compile


oracle.adf
adf-facelets
1.0
compile


javax.faces
jsf-impl
1.1
compile


javax.faces
jsf-api
1.1
compile


org.apache.shale
shale-test
1.0.3
test


myfaces
tomahawk
1.1.2
compile


commons-configuration
commons-configuration
1.3
compile


javax.mail
mail
1.4
compile


javax.servlet
servlet-api
2.5
compile


javax.servlet
jstl
1.1.2
compile


commons-validator
commons-validator
1.1.4
compile


oro
oro
2.0.8
compile


jaybird
jaybird-full
2.0.1
compile



commons-el
commons-el
1.0
compile



sagweb


maven-compiler-plugin

1.5
1.5



org.mortbay.jetty
maven-jetty-plugin



8081










And this is the error:
(But I look to the error and it seems to me the application is using the
myfaces implementation)

2006-10-26 15:29:44.015::WARN:  /sagweb/faces/accesscontrol/login.jspx
java.lang.IllegalStateException: STREAM
at org.mortbay.jetty.Response.getWriter(Response.java:470)
at
org.apache.myfaces.renderkit.html.util.DefaultAddResource.writeRespon
se(DefaultAddResource.java:807)
at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter
(Extensions
Filter.java:162)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
(Servlet
Handler.java:1041)
at org.mortbay.jetty.servlet.ServletHandler.handle(
ServletHandler.java:3
54)
at org.mortbay.jetty.servlet.SessionHandler.handle(
SessionHandler.java:2
26)
at org.mortbay.jetty.handler.ContextHandler.handle(
ContextHandler.java:6
15)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle
(ContextHand
lerCollection.java:149)
at org.mortbay.jetty.handler.HandlerCollection.handle
(HandlerCollection.
java:123)
at org.mortbay.jetty.handler.HandlerWrapper.handle(
HandlerWrapper.java:1
41)
at org.mortbay.jetty.Server.handle(Server.java:269)
at org.mortbay.jetty.HttpConnection.handleRequest(
HttpConnection.java:43
0)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete
(HttpCo
nnection.java:678)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:492)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java
:199)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java
:339)
at org.mortbay.jetty.nio.HttpChannelEndPoint.run(
HttpChannelEndPoint.jav
a:270)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run
(BoundedThreadPool
.java:475)




Re: Problems running a JSF application on Jetty:Run

2006-10-27 Thread Fabricio Lemos

You could get confused because the stacktrace shows DefaultAddResource
and ExtensionsFilter that belongs to org.apache.myfaces package. But
these classes are part of myfaces tomahawk api, not myfaces core api.

On 10/26/06, Dudu <[EMAIL PROTECTED]> wrote:

I can't discover the problem in this strack trace...
I'm running RI JSF implementation + tomahawk + ADF Faces:



this is the pom.xml


junit
junit
4.0
test


hibernate
hibernate
3.0
compile


log4j
log4j
1.2.12
compile


ojdbc
ojdbc
14
compile


oracle.adf
adf-faces-impl
10.1.3.0.4
compile


oracle.adf
adf-faces-api
10.1.3.0.4
compile


oracle.adf
adf-facelets
1.0
compile


javax.faces
jsf-impl
1.1
compile


javax.faces
jsf-api
1.1
compile


org.apache.shale
shale-test
1.0.3
test


myfaces
tomahawk
1.1.2
compile


commons-configuration
commons-configuration
1.3
compile


javax.mail
mail
1.4
compile


javax.servlet
servlet-api
2.5
compile


javax.servlet
jstl
1.1.2
compile


commons-validator
commons-validator
1.1.4
compile


oro
oro
2.0.8
compile


jaybird
jaybird-full
2.0.1
compile



commons-el
commons-el
1.0
compile



sagweb


maven-compiler-plugin

1.5
1.5



org.mortbay.jetty
maven-jetty-plugin



8081










And this is the error:
(But I look to the error and it seems to me the application is using the
myfaces implementation)

2006-10-26 15:29:44.015::WARN:  /sagweb/faces/accesscontrol/login.jspx
java.lang.IllegalStateException: STREAM
at org.mortbay.jetty.Response.getWriter(Response.java:470)
at
org.apache.myfaces.renderkit.html.util.DefaultAddResource.writeRespon
se(DefaultAddResource.java:807)
at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter
(Extensions
Filter.java:162)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
(Servlet
Handler.java:1041)
at org.mortbay.jetty.servlet.ServletHandler.handle(
ServletHandler.java:3
54)
at org.mortbay.jetty.servlet.SessionHandler.handle(
SessionHandler.java:2
26)
at org.mortbay.jetty.handler.ContextHandler.handle(
ContextHandler.java:6
15)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle
(ContextHand
lerCollection.java:149)
at org.mortbay.jetty.handler.HandlerCollection.handle
(HandlerCollection.
java:123)
at org.mortbay.jetty.handler.HandlerWrapper.handle(
HandlerWrapper.java:1
41)
at org.mortbay.jetty.Server.handle(Server.java:269)
at org.mortbay.jetty.HttpConnection.handleRequest(
HttpConnection.java:43
0)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete
(HttpCo
nnection.java:678)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:492)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:199)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:339)
at org.mortbay.jetty.nio.HttpChannelEndPoint.run(
HttpChannelEndPoint.jav
a:270)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run
(BoundedThreadPool
.java:475)




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Problems running a JSF application on Jetty:Run

2006-10-26 Thread Dudu

I can't discover the problem in this strack trace...
I'm running RI JSF implementation + tomahawk + ADF Faces:



this is the pom.xml
   
   
   junit
   junit
   4.0
   test
   
   
   hibernate
   hibernate
   3.0
   compile
   
   
   log4j
   log4j
   1.2.12
   compile
   
   
   ojdbc
   ojdbc
   14
   compile
   
   
   oracle.adf
   adf-faces-impl
   10.1.3.0.4
   compile
   
   
   oracle.adf
   adf-faces-api
   10.1.3.0.4
   compile
   
   
   oracle.adf
   adf-facelets
   1.0
   compile
   
   
   javax.faces
   jsf-impl
   1.1
   compile
   
   
   javax.faces
   jsf-api
   1.1
   compile
   
   
   org.apache.shale
   shale-test
   1.0.3
   test
   
   
   myfaces
   tomahawk
   1.1.2
   compile
   
   
   commons-configuration
   commons-configuration
   1.3
   compile
   
   
   javax.mail
   mail
   1.4
   compile
   
   
   javax.servlet
   servlet-api
   2.5
   compile
   
   
   javax.servlet
   jstl
   1.1.2
   compile
   
   
   commons-validator
   commons-validator
   1.1.4
   compile
   
   
   oro
   oro
   2.0.8
   compile
   
   
   jaybird
   jaybird-full
   2.0.1
   compile
   

   
   commons-el
   commons-el
   1.0
   compile
   
   
   
   sagweb
   
   
   maven-compiler-plugin
   
   1.5
   1.5
   
   
   
   org.mortbay.jetty
   maven-jetty-plugin
   
   
   
   8081
   
   
   

   
   
   



And this is the error:
(But I look to the error and it seems to me the application is using the
myfaces implementation)

2006-10-26 15:29:44.015::WARN:  /sagweb/faces/accesscontrol/login.jspx
java.lang.IllegalStateException: STREAM
   at org.mortbay.jetty.Response.getWriter(Response.java:470)
   at
org.apache.myfaces.renderkit.html.util.DefaultAddResource.writeRespon
se(DefaultAddResource.java:807)
   at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter
(Extensions
Filter.java:162)
   at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
(Servlet
Handler.java:1041)
   at org.mortbay.jetty.servlet.ServletHandler.handle(
ServletHandler.java:3
54)
   at org.mortbay.jetty.servlet.SessionHandler.handle(
SessionHandler.java:2
26)
   at org.mortbay.jetty.handler.ContextHandler.handle(
ContextHandler.java:6
15)
   at org.mortbay.jetty.handler.ContextHandlerCollection.handle
(ContextHand
lerCollection.java:149)
   at org.mortbay.jetty.handler.HandlerCollection.handle
(HandlerCollection.
java:123)
   at org.mortbay.jetty.handler.HandlerWrapper.handle(
HandlerWrapper.java:1
41)
   at org.mortbay.jetty.Server.handle(Server.java:269)
   at org.mortbay.jetty.HttpConnection.handleRequest(
HttpConnection.java:43
0)
   at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete
(HttpCo
nnection.java:678)
   at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:492)
   at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:199)
   at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:339)
   at org.mortbay.jetty.nio.HttpChannelEndPoint.run(
HttpChannelEndPoint.jav
a:270)
   at org.mortbay.thread.BoundedThreadPool$PoolThread.run
(BoundedThreadPool
.java:475)