myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Heinz Striebeck (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Commented] (EXTCDI-301) JEE Deployment error if CODI is outside of WAR
Date Fri, 26 Oct 2012 19:25:12 GMT

    [ https://issues.apache.org/jira/browse/EXTCDI-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485134#comment-13485134
] 

Heinz Striebeck commented on EXTCDI-301:
----------------------------------------

"it shouldn't be an issue, since you just see it in the log-file (but there is no other impact)."

Unfortunately this is not true. The application is not working when this error appears (managed
beans cannot be resolved).

                
> JEE Deployment error if CODI is outside of WAR
> ----------------------------------------------
>
>                 Key: EXTCDI-301
>                 URL: https://issues.apache.org/jira/browse/EXTCDI-301
>             Project: MyFaces CODI
>          Issue Type: Bug
>          Components: JEE-JSF20-Module
>    Affects Versions: 1.0.5
>         Environment: WebSphere 8.0 FP 2, Windows
>            Reporter: Heinz Striebeck
>            Priority: Minor
>
> When deploying an EAR with a WAR inside which has CODI inside the WEB-INF/lib of the
WAR, everything works fine.
> But if CODI is placed outside the WAR (e.g. in the root of the EAR) deployment fails
with this exception:
> [23.10.12 10:24:32:075 CEST]     FFDC 
> Exception:javax.naming.ConfigurationException 
> SourceId:com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS

> ProbeId:537 Reporter:java.lang.Class@784d5d
> javax.naming.ConfigurationException: A JNDI operation on a "java:" name cannot 
> be completed because the server runtime is not able to associate the operation's 
> thread with any J2EE application component.  This condition can occur when the 
> JNDI client using the "java:" name is not executed on the thread of a server 
> application request.  Make sure that a J2EE application does not execute JNDI 
> operations on "java:" names within static code blocks or in threads created by 
> that J2EE application.  Such code does not necessarily run on the thread of a 
> server application request and therefore is not supported by JNDI operations on 
> "java:" names. [Root exception is javax.naming.NameNotFoundException: Name 
> comp/env/myfaces-codi not found in context "java:".]
>          at 
> com.ibm.ws.naming.java.javaURLContextImpl.throwExceptionIfDefaultJavaNS(javaURLContextImpl.java:522)

>          at 
> com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS(javaURLContextImpl.java:552)

>          at 
> com.ibm.ws.naming.java.javaURLContextImpl.lookupExt(javaURLContextImpl.java:481)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message