This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 102412 - Can't deploy 1.4 app server project -- lifecycle error
Summary: Can't deploy 1.4 app server project -- lifecycle error
Status: VERIFIED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: _ potingwu
URL:
Keywords:
Depends on:
Blocks: 100628
  Show dependency tree
 
Reported: 2007-04-25 00:55 UTC by _ krystyna
Modified: 2007-04-26 03:50 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ krystyna 2007-04-25 00:55:57 UTC 
NB full installer 0704241200
XP
jdk1.6_01

Reproducible. 

1. Clean userdir, Create a 1.4 SunAppserver9 project
2. drop button, listbox (any) components and deploy
>get http status 404 - requested service not available

from server.log

WebModule[/WebApplication290]PWC1396: Servlet /WebApplication290 threw load()
exception
java.lang.IllegalArgumentException: Cant create Lifecycle for id:
com.sun.faces.lifecycle.PARTIAL.
        at
com.sun.faces.lifecycle.LifecycleFactoryImpl.getLifecycle(LifecycleFactoryImpl.java:226)
        at javax.faces.webapp.FacesServlet.init(FacesServlet.java:170)
        at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1165)
        at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:994)
        at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4778)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:5162)
        at com.sun.enterprise.web.WebModule.start(WebModule.java:308)
        at com.sun.enterprise.web.LifecycleStarter.doRun(LifecycleStarter.java:45)
        at
com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:283)
        at
com.sun.appserv.management.util.misc.RunnableBase._submit(RunnableBase.java:155)
        at
com.sun.appserv.management.util.misc.RunnableBase.submit(RunnableBase.java:171)
        at
com.sun.enterprise.web.VirtualServer.startChildren(VirtualServer.java:1566)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1218)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:938)
        at com.sun.enterprise.web.LifecycleStarter.doRun(LifecycleStarter.java:45)
        at
com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:283)
        at
com.sun.appserv.management.util.misc.RunnableBase.run(RunnableBase.java:317)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
        at java.lang.Thread.run(Thread.java:619)
WEB0190: Error starting virtual server
StandardEngine[com.sun.appserv].StandardHost[server]
java.util.MissingResourceException: Can't find resource for bundle
java.util.PropertyResourceBundle, key virtualServer.startContextError
        at java.util.ResourceBundle.getObject(ResourceBundle.java:386)
        at java.util.ResourceBundle.getString(ResourceBundle.java:346)
        at
com.sun.enterprise.web.VirtualServer.startChildren(VirtualServer.java:1575)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1218)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:938)
        at com.sun.enterprise.web.LifecycleStarter.doRun(LifecycleStarter.java:45)
        at
com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:283)
        at
com.sun.appserv.management.util.misc.RunnableBase.run(RunnableBase.java:317)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
        at java.lang.Thread.run(Thread.java:619)
Comment 1 Yousuf Haider 2007-04-25 01:32:47 UTC 
I can't seem to reproduce this issue on my machine. I am using:

NB build 200704240830 (zipped version)
jdk 1.6.0
WinXp

I tried it on both Glassfish b33 and b41c.
Comment 2 _ krystyna 2007-04-25 01:42:16 UTC 
Yours is an ealier build than the one I used.
See the timestamps. Can you please update to 04241200 and retry?
I actually think the error was introduced in 
a recent putback.
Comment 3 _ potingwu 2007-04-25 02:03:12 UTC 
I can reproduce it by the current trunk (build from source). Looks like it is
caused by recent web.xml change. Matthew adds the following into web.xml:

   <servlet>
       <servlet-name>Faces Servlet</servlet-name>
       <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
       <init-param>
           <param-name>javax.faces.LIFECYCLE_ID</param-name>
           <param-value>com.sun.faces.lifecycle.PARTIAL</param-value>
       </init-param>
       <load-on-startup>1</load-on-startup>
   </servlet>
Comment 4 Yousuf Haider 2007-04-25 02:20:13 UTC 
I can reproduce it with the NBI build 200704241200 as well.
Comment 5 _ potingwu 2007-04-25 02:23:16 UTC 
I just integrated the fix for Matthew.
Comment 6 _ potingwu 2007-04-25 03:48:12 UTC 
I fixed it by, add this descriptor iff it's a Java EE 5 project.

Matthew, if that's not you intend to add, then please speak up. At least now it
works for both J2EE 1.4 and Java 5 projects.
Comment 7 _ krystyna 2007-04-25 21:44:30 UTC 
Verified fixed in 0704251200.
By the way, this fix means that for dynafaces for 1.4 will
require manually entering lifecycle_id parameters. It is
auto-set for 1.5 projects.
Comment 8 _ krystyna 2007-04-26 03:50:15 UTC 
*** Issue 102567 has been marked as a duplicate of this issue. ***