[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2963) Booking example on tomcat6 with JBoss Embedded throws NameNotFoundException

Jay Balunas (JIRA) jira-events at lists.jboss.org
Tue May 6 14:38:20 EDT 2008


     [ http://jira.jboss.com/jira/browse/JBSEAM-2963?page=all ]

Jay Balunas updated JBSEAM-2963:
--------------------------------

    Attachment: tomcat-booking-error.txt

> Booking example on tomcat6 with JBoss Embedded throws NameNotFoundException
> ---------------------------------------------------------------------------
>
>                 Key: JBSEAM-2963
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2963
>             Project: Seam
>          Issue Type: Bug
>          Components: Examples, Platform interoperability
>    Affects Versions: 2.0.2.CR2
>            Reporter: Jay Balunas
>         Attachments: tomcat-booking-error.txt
>
>
> Deploy booking example to tomcat6 with JBoss embedded as it seems to deploy fine.  When accessed get the exception below (see attachment for full stack).  Note all other embedded examples work fine.
> Caused by: javax.naming.NameNotFoundException: Name jboss-seam-booking is not bound in this Context
> 	at org.apache.naming.NamingContext.lookup(NamingContext.java:770)
> 	at org.apache.naming.NamingContext.lookup(NamingContext.java:153)
> 	at org.apache.naming.SelectorContext.lookup(SelectorContext.java:137)
> 	at sun.reflect.GeneratedMethodAccessor71.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.embedded.jndi.BridgeContext.invoke(BridgeContext.java:77)
> 	at $Proxy100.lookup(Unknown Source)
> 	at javax.naming.InitialContext.lookup(InitialContext.java:351)
> 	at org.jboss.seam.Component.instantiateSessionBean(Component.java:1287)
> 	at org.jboss.seam.Component.instantiate(Component.java:1273)
> 	at org.jboss.seam.Component.newInstance(Component.java:1967)
> 	... 42 more

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list