[
https://jira.jboss.org/browse/JBAS-8102?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on JBAS-8102:
---------------------------------
Currently we see
15:27:05,382 INFO [Version] WELD-000900 1.0.1 (Final)
15:27:05,457 INFO [SessionSpecContainer] Starting
jboss.j2ee:jar=seam-booking-simplified.war,name=AuthenticatorBean,service=EJB3
15:27:05,471 INFO [EJBContainer] STARTED EJB:
org.jboss.seam.examples.booking.security.AuthenticatorBean ejbName: AuthenticatorBean
15:27:05,822 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global
JNDI:
AuthenticatorBean/local - EJB3.x Default Local Business Interface
AuthenticatorBean/local-org.jboss.seam.examples.booking.security.Authenticator - EJB3.x
Local Business Interface
15:27:11,237 INFO [TomcatDeployment] deploy, ctxPath=/seam-booking-simplified
15:27:11,350 WARN [Servlet] WELD-000700 Not starting Weld/Servlet integration as Weld
failed to initialize
- the WARN from Weld indicates that the Weld container is being booted too late.
NB there may be other deployment errors, but if we can get rid of the message, then this
issue is done.
jbossweb is starting before Weld when an war with ejbs in it is
deployed
------------------------------------------------------------------------
Key: JBAS-8102
URL:
https://jira.jboss.org/browse/JBAS-8102
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M3
Reporter: Pete Muir
Assignee: Ales Justin
Priority: Critical
Fix For: 6.0.0.M4
Attachments: seam-booking-simplified.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira