can anyone help me here, i am using the basic jsf archetype, the
following
command worked once and i was able to see the app running but the
second
and
subsequest times i get the following ...
:-((
D:\Emmett\sandbox\gbe>mvn -P hsqldb jetty:run-war
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'jetty'.
[INFO]
--------------------------------------------------------------------
--------
[INFO] Building AppFuse JSF Application
[INFO] task-segment: [jetty:run-war]
[INFO]
--------------------------------------------------------------------
--------
[INFO] Preparing jetty:run-war
[INFO] [warpath:add-classes {execution: default}]
[INFO] [aspectj:compile {execution: default}]
[INFO] [native2ascii:native2ascii {execution: native2ascii-utf8}]
[INFO] [native2ascii:native2ascii {execution: native2ascii-8859_1}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] Preparing hibernate3:hbm2ddl
[WARNING] Removing: hbm2ddl from forked lifecycle, to prevent
recursive
invocation.
[INFO] [warpath:add-classes {execution: default}]
[INFO] [aspectj:compile {execution: default}]
[INFO] [native2ascii:native2ascii {execution: native2ascii-utf8}]
[INFO] [native2ascii:native2ascii {execution: native2ascii-8859_1}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'org.hibernate:jtidy:pom:r8-20060801:runtime' is
invalid.
It will be ignored for artifact resolution. Reason: Parse error
reading
PO
M. Reason: TEXT must be immediately followed by END_TAG and not
START_TAG
(position: START_TAG seen ...<licenses>\n\t\t\t<license>...
@12:13) for
pro
ject org.hibernate:jtidy at C:\Documents and
Settings\c_walsh_e\.m2\repository\org\hibernate\jtidy\r8-20060801
\jtidy-r8-20060801.pom
[WARNING] POM for 'org.hibernate:jtidy:pom:r8-20060801:runtime' is
invalid.
It will be ignored for artifact resolution. Reason: Parse error
reading
PO
M. Reason: TEXT must be immediately followed by END_TAG and not
START_TAG
(position: START_TAG seen ...<licenses>\n\t\t\t<license>...
@12:13) for
pro
ject org.hibernate:jtidy at C:\Documents and
Settings\c_walsh_e\.m2\repository\org\hibernate\jtidy\r8-20060801
\jtidy-r8-20060801.pom
[INFO] [hibernate3:hbm2ddl {execution: default}]
[INFO] Configuration XML file loaded:
D:\Emmett\sandbox\gbe\src\main\resources\hibernate.cfg.xml
[INFO] Configuration XML file loaded:
D:\Emmett\sandbox\gbe\src\main\resources\hibernate.cfg.xml
[INFO] Configuration Properties file loaded:
D:\Emmett\sandbox\gbe\target\classes\jdbc.properties
alter table user_role drop constraint FK143BF46AF503D155;
alter table user_role drop constraint FK143BF46A4FD90D75;
drop table app_user if exists;
drop table role if exists;
drop table user_role if exists;
create table app_user (id bigint generated by default as identity
(start
with 1), username varchar(50) not null, email varchar(255) not null,
password
_hint varchar(255), first_name varchar(50) not null, last_name
varchar(50)
not null, phone_number varchar(255), website varchar(255),
account_expired
bit not null, account_locked bit not null, credentials_expired
bit not
null,
city varchar(50) not null, province varchar(100), postal_code
varchar(15)
not null, address varchar(150), country varchar(100),
account_enabled
bit,
version integer, password varchar(255) not null, primary key
(id), unique
(email), unique (username));
create table role (id bigint generated by default as identity
(start with
1), name varchar(20), description varchar(64), primary key (id));
create table user_role (user_id bigint not null, role_id bigint
not null,
primary key (user_id, role_id));
alter table user_role add constraint FK143BF46AF503D155 foreign key
(user_id) references app_user;
alter table user_role add constraint FK143BF46A4FD90D75 foreign key
(role_id) references role;
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [dbunit:operation {execution: test-compile}]
[INFO] [surefire:test]
[INFO] Surefire report directory:
D:\Emmett\sandbox\gbe\target\surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running com.sodamodena.AppTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
0.078 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO] [dbunit:operation {execution: test}]
[INFO] [war:war]
[INFO] Exploding webapp...
[INFO] Assembling webapp gbe in
D:\Emmett\sandbox\gbe\target\gbe-1.0-SNAPSHOT
[INFO] Copy webapp webResources to
D:\Emmett\sandbox\gbe\target\gbe-1.0-SNAPSHOT
[INFO] Overlaying 2 war(s).
[INFO] Generating war D:\Emmett\sandbox\gbe\target\gbe-1.0-
SNAPSHOT.war
[INFO] Building war: D:\Emmett\sandbox\gbe\target\gbe-1.0-
SNAPSHOT.war
[INFO] [jetty:run-war]
[INFO] Configuring Jetty for project: AppFuse JSF Application
2007-12-20 16:37:09.545::INFO: Logging to STDERR via
org.mortbay.log.StdErrLog
[INFO] Context path = /
[INFO] Tmp directory = determined at runtime
[INFO] Web defaults = org/mortbay/jetty/webapp/webdefault.xml
[INFO] Web overrides = none
[INFO] Starting jetty 6.1.6 ...
2007-12-20 16:37:09.732::INFO: jetty-6.1.6
2007-12-20 16:37:10.795::INFO: Extract
jar:file:/D:/Emmett/sandbox/gbe/target/gbe-1.0-SNAPSHOT.war!/ to
D:\Emmett\sandbox\gbe\target\work\webapp
2007-12-20 16:37:44.106::INFO: No Transaction manager found - if
your
webapp requires one, please configure one.
[gbe] ERROR [main] DefaultFacesInitializer.initFaces(126) | Error
initializing MyFaces: java.net.ConnectException: Connection timed
out:
connect
javax.faces.FacesException: java.net.ConnectException: Connection
timed
out:
connect
at
org.apache.myfaces.config.FacesConfigurator.feedClassloaderConfigura
tions(FacesConfigurator.java:425)
at
org.apache.myfaces.config.FacesConfigurator.configure
(FacesConfigurator.java:171)
at
org.apache.myfaces.webapp.DefaultFacesInitializer.initFaces
(DefaultFacesInitializer.java:112)
at
org.apache.myfaces.webapp.StartupServletContextListener.contextIniti
alized(StartupServletContextListener.java:57)
at
org.mortbay.jetty.handler.ContextHandler.startContext
(ContextHandler.java:539)
at
org.mortbay.jetty.servlet.Context.startContext(Context.java:135)
at
org.mortbay.jetty.webapp.WebAppContext.startContext
(WebAppContext.java:1216)
at
org.mortbay.jetty.handler.ContextHandler.doStart
(ContextHandler.java:509)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
447)
at
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart
(Jetty6PluginWebAppContext.java:110)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart
(HandlerCollection.java:147)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart
(ContextHandlerCollection.java:156)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart
(HandlerCollection.java:147)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart
(HandlerWrapper.java:117)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.plugin.Jetty6PluginServer.start
(Jetty6PluginServer.java:132)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty
(AbstractJettyMojo.java:337)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute
(AbstractJettyMojo.java:279)
at
org.mortbay.jetty.plugin.Jetty6RunWar.execute(Jetty6RunWar.java:67)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalon
eGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa
ndleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme
nts(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute
(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute
(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:
255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect
(PlainSocketImpl.java:333)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:
182)
at java.net.Socket.connect(Socket.java:520)
at java.net.Socket.connect(Socket.java:470)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:
388)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:
523)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
at sun.net.www.http.HttpClient.New(HttpClient.java:304)
at sun.net.www.http.HttpClient.New(HttpClient.java:321)
at
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient
(HttpURLConnection.java:813)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect
(HttpURLConnection.java:765)
at
sun.net.www.protocol.http.HttpURLConnection.connect
(HttpURLConnection.java:690)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream
(HttpURLConnection.java:934)
at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurren
tEntity(XMLEntityManager.java:973)
at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity
(XMLEntityManager.java:905)
at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEnt
ity(XMLEntityManager.java:872)
at
com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSo
urce(XMLDTDScannerImpl.java:282)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl
$DTDDispatcher.dispatch(XMLDocumentScannerImpl.java:1021)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerIm
pl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
XML11Configuration.java:834)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
XML11Configuration.java:764)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse
(XMLParser.java:148)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse
(AbstractSAXParser.java:1242)
at org.apache.commons.digester.Digester.parse
(Digester.java:1647)
at
org.apache.myfaces.config.impl.digester.DigesterFacesConfigUnmarshal
lerImpl.getFacesConfig(DigesterFacesConfigUnmarshallerImpl.java:194)
at
org.apache.myfaces.config.impl.digester.DigesterFacesConfigUnmarshal
lerImpl.getFacesConfig(DigesterFacesConfigUnmarshallerImpl.java:34)
at
org.apache.myfaces.config.FacesConfigurator.feedClassloaderConfigura
tions(FacesConfigurator.java:419)
... 40 more
2007-12-20 16:38:06.405:/:INFO: Initializing Spring root
WebApplicationContext
2007-12-20 16:38:15.979::WARN: failed faces
javax.servlet.ServletException: java.lang.IllegalStateException: No
Factories configured for this Application. This happens if the
faces-initializatio
n does not work at all - make sure that you properly include all
configuration settings necessary for a basic faces application
and that
all
the neces
sary libs are included. Also check the logging output of your web
application and your container for any exceptions!
If you did that and find nothing, the mistake might be due to the
fact
that
you use some special web-containers which do not support registering
conte
xt-listeners via TLD files and a context listener is not setup in
your
web.xml.
A typical config looks like this;
<listener>
<listener-
class>org.apache.myfaces.webapp.StartupServletContextListener</
listener-class>
</listener>
at
org.mortbay.jetty.servlet.ServletHolder.initServlet
(ServletHolder.java:437)
at
org.mortbay.jetty.servlet.ServletHolder.doStart
(ServletHolder.java:256)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.servlet.ServletHandler.initialize
(ServletHandler.java:612)
at
org.mortbay.jetty.servlet.Context.startContext(Context.java:139)
at
org.mortbay.jetty.webapp.WebAppContext.startContext
(WebAppContext.java:1216)
at
org.mortbay.jetty.handler.ContextHandler.doStart
(ContextHandler.java:509)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
447)
at
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart
(Jetty6PluginWebAppContext.java:110)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart
(HandlerCollection.java:147)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart
(ContextHandlerCollection.java:156)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart
(HandlerCollection.java:147)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart
(HandlerWrapper.java:117)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.plugin.Jetty6PluginServer.start
(Jetty6PluginServer.java:132)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty
(AbstractJettyMojo.java:337)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute
(AbstractJettyMojo.java:279)
at
org.mortbay.jetty.plugin.Jetty6RunWar.execute(Jetty6RunWar.java:67)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalon
eGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa
ndleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme
nts(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute
(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute
(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:
255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.lang.IllegalStateException: No Factories
configured for
this
Application. This happens if the faces-initialization does not
work at al
l - make sure that you properly include all configuration settings
necessary
for a basic faces application and that all the necessary libs are
include
d. Also check the logging output of your web application and your
container
for any exceptions!
If you did that and find nothing, the mistake might be due to the
fact
that
you use some special web-containers which do not support registering
conte
xt-listeners via TLD files and a context listener is not setup in
your
web.xml.
A typical config looks like this;
<listener>
<listener-
class>org.apache.myfaces.webapp.StartupServletContextListener</
listener-class>
</listener>
at javax.faces.FactoryFinder.getFactory
(FactoryFinder.java:90)
at javax.faces.webapp.FacesServlet.init(FacesServlet.java:
88)
at
org.mortbay.jetty.servlet.ServletHolder.initServlet
(ServletHolder.java:433)
... 39 more
2007-12-20 16:38:57.800::WARN: Nested in
javax.servlet.ServletException:
java.lang.IllegalStateException: No Factories configured for this
Applicatio
n. This happens if the faces-initialization does not work at all
- make
sure
that you properly include all configuration settings necessary
for a basi
c faces application and that all the necessary libs are included.
Also
check
the logging output of your web application and your container for
any exc
eptions!
If you did that and find nothing, the mistake might be due to the
fact
that
you use some special web-containers which do not support registering
conte
xt-listeners via TLD files and a context listener is not setup in
your
web.xml.
A typical config looks like this;
<listener>
<listener-
class>org.apache.myfaces.webapp.StartupServletContextListener</
listener-class>
</listener>
:
java.lang.IllegalStateException: No Factories configured for this
Application. This happens if the faces-initialization does not
work at
all -
make su
re that you properly include all configuration settings necessary
for a
basic faces application and that all the necessary libs are
included.
Also
che
ck the logging output of your web application and your container
for any
exceptions!
If you did that and find nothing, the mistake might be due to the
fact
that
you use some special web-containers which do not support registering
conte
xt-listeners via TLD files and a context listener is not setup in
your
web.xml.
A typical config looks like this;
<listener>
<listener-
class>org.apache.myfaces.webapp.StartupServletContextListener</
listener-class>
</listener>
at javax.faces.FactoryFinder.getFactory
(FactoryFinder.java:90)
at javax.faces.webapp.FacesServlet.init(FacesServlet.java:
88)
at
org.mortbay.jetty.servlet.ServletHolder.initServlet
(ServletHolder.java:433)
at
org.mortbay.jetty.servlet.ServletHolder.doStart
(ServletHolder.java:256)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.servlet.ServletHandler.initialize
(ServletHandler.java:612)
at
org.mortbay.jetty.servlet.Context.startContext(Context.java:139)
at
org.mortbay.jetty.webapp.WebAppContext.startContext
(WebAppContext.java:1216)
at
org.mortbay.jetty.handler.ContextHandler.doStart
(ContextHandler.java:509)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
447)
at
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart
(Jetty6PluginWebAppContext.java:110)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart
(HandlerCollection.java:147)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart
(ContextHandlerCollection.java:156)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart
(HandlerCollection.java:147)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart
(HandlerWrapper.java:117)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.plugin.Jetty6PluginServer.start
(Jetty6PluginServer.java:132)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty
(AbstractJettyMojo.java:337)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute
(AbstractJettyMojo.java:279)
at
org.mortbay.jetty.plugin.Jetty6RunWar.execute(Jetty6RunWar.java:67)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalon
eGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa
ndleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme
nts(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute
(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute
(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:
255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
2007-12-20 16:38:57.972::WARN: Failed startup of context
[EMAIL PROTECTED]
{/,jar:file:/D:/Emmett/sandbox/gbe/
target/gbe-1.0-SNAPSHOT.war!/}
javax.servlet.ServletException: java.lang.IllegalStateException: No
Factories configured for this Application. This happens if the
faces-initializatio
n does not work at all - make sure that you properly include all
configuration settings necessary for a basic faces application
and that
all
the neces
sary libs are included. Also check the logging output of your web
application and your container for any exceptions!
If you did that and find nothing, the mistake might be due to the
fact
that
you use some special web-containers which do not support registering
conte
xt-listeners via TLD files and a context listener is not setup in
your
web.xml.
A typical config looks like this;
<listener>
<listener-
class>org.apache.myfaces.webapp.StartupServletContextListener</
listener-class>
</listener>
at
org.mortbay.jetty.servlet.ServletHolder.initServlet
(ServletHolder.java:437)
at
org.mortbay.jetty.servlet.ServletHolder.doStart
(ServletHolder.java:256)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.servlet.ServletHandler.initialize
(ServletHandler.java:612)
at
org.mortbay.jetty.servlet.Context.startContext(Context.java:139)
at
org.mortbay.jetty.webapp.WebAppContext.startContext
(WebAppContext.java:1216)
at
org.mortbay.jetty.handler.ContextHandler.doStart
(ContextHandler.java:509)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
447)
at
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart
(Jetty6PluginWebAppContext.java:110)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart
(HandlerCollection.java:147)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart
(ContextHandlerCollection.java:156)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart
(HandlerCollection.java:147)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart
(HandlerWrapper.java:117)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.plugin.Jetty6PluginServer.start
(Jetty6PluginServer.java:132)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty
(AbstractJettyMojo.java:337)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute
(AbstractJettyMojo.java:279)
at
org.mortbay.jetty.plugin.Jetty6RunWar.execute(Jetty6RunWar.java:67)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalon
eGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa
ndleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme
nts(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute
(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute
(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:
255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.lang.IllegalStateException: No Factories
configured for
this
Application. This happens if the faces-initialization does not
work at al
l - make sure that you properly include all configuration settings
necessary
for a basic faces application and that all the necessary libs are
include
d. Also check the logging output of your web application and your
container
for any exceptions!
If you did that and find nothing, the mistake might be due to the
fact
that
you use some special web-containers which do not support registering
conte
xt-listeners via TLD files and a context listener is not setup in
your
web.xml.
A typical config looks like this;
<listener>
<listener-
class>org.apache.myfaces.webapp.StartupServletContextListener</
listener-class>
</listener>
at javax.faces.FactoryFinder.getFactory
(FactoryFinder.java:90)
at javax.faces.webapp.FacesServlet.init(FacesServlet.java:
88)
at
org.mortbay.jetty.servlet.ServletHolder.initServlet
(ServletHolder.java:433)
... 39 more
2007-12-20 16:38:57.160::WARN: Nested in
javax.servlet.ServletException:
java.lang.IllegalStateException: No Factories configured for this
Applicatio
n. This happens if the faces-initialization does not work at all
- make
sure
that you properly include all configuration settings necessary
for a basi
c faces application and that all the necessary libs are included.
Also
check
the logging output of your web application and your container for
any exc
eptions!
If you did that and find nothing, the mistake might be due to the
fact
that
you use some special web-containers which do not support registering
conte
xt-listeners via TLD files and a context listener is not setup in
your
web.xml.
A typical config looks like this;
<listener>
<listener-
class>org.apache.myfaces.webapp.StartupServletContextListener</
listener-class>
</listener>
:
java.lang.IllegalStateException: No Factories configured for this
Application. This happens if the faces-initialization does not
work at
all -
make su
re that you properly include all configuration settings necessary
for a
basic faces application and that all the necessary libs are
included.
Also
che
ck the logging output of your web application and your container
for any
exceptions!
If you did that and find nothing, the mistake might be due to the
fact
that
you use some special web-containers which do not support registering
conte
xt-listeners via TLD files and a context listener is not setup in
your
web.xml.
A typical config looks like this;
<listener>
<listener-
class>org.apache.myfaces.webapp.StartupServletContextListener</
listener-class>
</listener>
at javax.faces.FactoryFinder.getFactory
(FactoryFinder.java:90)
at javax.faces.webapp.FacesServlet.init(FacesServlet.java:
88)
at
org.mortbay.jetty.servlet.ServletHolder.initServlet
(ServletHolder.java:433)
at
org.mortbay.jetty.servlet.ServletHolder.doStart
(ServletHolder.java:256)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.servlet.ServletHandler.initialize
(ServletHandler.java:612)
at
org.mortbay.jetty.servlet.Context.startContext(Context.java:139)
at
org.mortbay.jetty.webapp.WebAppContext.startContext
(WebAppContext.java:1216)
at
org.mortbay.jetty.handler.ContextHandler.doStart
(ContextHandler.java:509)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
447)
at
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart
(Jetty6PluginWebAppContext.java:110)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart
(HandlerCollection.java:147)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart
(ContextHandlerCollection.java:156)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart
(HandlerCollection.java:147)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart
(HandlerWrapper.java:117)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at
org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.plugin.Jetty6PluginServer.start
(Jetty6PluginServer.java:132)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty
(AbstractJettyMojo.java:337)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute
(AbstractJettyMojo.java:279)
at
org.mortbay.jetty.plugin.Jetty6RunWar.execute(Jetty6RunWar.java:67)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalon
eGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa
ndleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme
nts(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute
(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute
(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:
255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
--
View this message in context:
http://www.nabble.com/Error-initializing-MyFaces%3A-
java.net.ConnectException%3A-tp14439989s2369p14439989.html
Sent from the AppFuse - User mailing list archive at Nabble.com.
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]