[JBoss Seam] - Re: No active event context
by SmokingAPipe
Did anyone find a solution to this problem? I'm getting it when I'm trying to use Facelets:
01:43:23,236 INFO [Events] no events.xml file found
| 01:43:23,299 ERROR [PhaseListenerManager] Exception in PhaseListener RESTORE_VIEW(1) afterPhase
| java.lang.IllegalStateException: No phase id bound to current thread (make sure you do not have two SeamPhaseListener instances installed)
| at org.jboss.seam.contexts.PageContext.getPhaseId(PageContext.java:153)
| at org.jboss.seam.contexts.PageContext.isRenderResponsePhase(PageContext.java:165)
| at org.jboss.seam.contexts.PageContext.getCurrentReadableMap(PageContext.java:76)
| at org.jboss.seam.contexts.PageContext.get(PageContext.java:66)
| at org.jboss.seam.Component.getInstance(Component.java:1603)
|
| ................
|
|
|
| 01:43:23,596 ERROR [PhaseListenerManager] Exception in PhaseListener RENDER_RESPONSE(6) afterPhase
| java.lang.IllegalStateException: No active event context
|
Any ideas? I'm quite stuck on this, and I have no idea how to debug where to go.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996262#3996262
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996262
19 years, 7 months
[JBoss Seam] - Re: Any experience with SeamFaceletViewHandler?
by SmokingAPipe
Now I copied the myfaces jars from the facelets distribution, and I get:
00:59:18,186 ERROR [StartupServletContextListener] Error initializing ServletContext
| javax.faces.FacesException: org.jboss.seam.jsf.SeamApplicationFactory
| at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:587)
| at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:460)
| at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256)
| .....
| Caused by: java.lang.InstantiationException: org.jboss.seam.jsf.SeamApplicationFactory
| at java.lang.Class.newInstance0(Class.java:340)
| at java.lang.Class.newInstance(Class.java:308)
| at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:585)
|
which is different, but still the app can't run. Surely when someone was developing these packages, they must have gotten them to run somewhere? These things are on released versions, implying not just that they were built but they have been run?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996258#3996258
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996258
19 years, 7 months
[Security & JAAS/JBoss] - Obtaining SecurityManagerService failed
by awanisz
My collegue developed a programme for security during login..but upon login i get this error...how do i fix it??could u guys help me out...i really am a beginner...
2006-12-26 15:51:36,453 DEBUG [org.jboss.web.tomcat.security.SecurityFlushSessionListener] Obtaining SecurityManagerService failed::
java.lang.ClassCastException: org.jnp.interfaces.NamingContext
at org.jboss.web.tomcat.security.SecurityFlushSessionListener.getSecurityManagerService(SecurityFlushSessionListener.java:193)
at org.jboss.web.tomcat.security.SecurityFlushSessionListener.getSubjectAndSecurityDomain(SecurityFlushSessionListener.java:160)
at org.jboss.web.tomcat.security.SecurityFlushSessionListener.sessionDestroyed(SecurityFlushSessionListener.java:79)
at org.apache.catalina.session.StandardSession.expire(StandardSession.java:687)
at org.apache.catalina.session.StandardSession.expire(StandardSession.java:645)
at org.apache.catalina.session.StandardSession.invalidate(StandardSession.java:1090)
at org.apache.catalina.session.StandardSessionFacade.invalidate(StandardSessionFacade.java:149)
at com.utm.iumis.sadm.struts.action.penyelenggaraansistem.AuthenticationAction.execute(AuthenticationAction.java:106)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
2006-12-26 15:51:36,453 DEBUG [org.jboss.web.tomcat.security.SecurityFlushSessionListener] Unable to obtain SecurityDomain
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996249#3996249
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996249
19 years, 7 months
[JBoss AOP] - Compile Error in org\jboss\aop\Advisor.java
by jagadeeshvn
Hi All,
I am trying to compile the latest AOP source and I am getting a few compilation errors in Advisor.java ( ln:360 ).
[execmodules] E:\JavaSource\JBoss_AOP\aop\src\main\org\jboss\aop\Advisor.java:36
0: hasAnnotation(java.lang.Class) in org.jboss.repository.spi.MetaDataContext ca
nnot be applied to (java.lang.String)
[execmodules] if (metadataContext.hasAnnotation(annotation)) return tru
e;
[execmodules] ^
[execmodules] E:\JavaSource\JBoss_AOP\aop\src\main\org\jboss\aop\Advisor.java:37
8: getAnnotation(java.lang.Class) in org.jboss.repository.spi.MetaDataContext ca
nnot be applied to (java.lang.reflect.Method,java.lang.Class)
[execmodules] Object val = metadataContext.getAnnotation(m, annotation)
;
[execmodules] ^
[execmodules] E:\JavaSource\JBoss_AOP\aop\src\main\org\jboss\aop\Advisor.java:42
3: hasAnnotation(java.lang.Class) in org.jboss.repository.spi.MetaDataContext ca
nnot be applied to (java.lang.reflect.Method,java.lang.String)
[execmodules] if (metadataContext.hasAnnotation(m, annotation)) return
true;
[execmodules] 3 errors
[execmodules] 2 warnings
I understand that the problem is with jboss-container.jar and the version I have downloaded from svn when I executed build.bat is relatively new, but Advisor.java is looking for a previous version. I couldn't find that version anywhere in SVN. I would really appreciate if you can point me to a repository from where I can download that version of jboss-container.jar.
Thanks
Jugs
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996248#3996248
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996248
19 years, 7 months
[JBoss Seam] - Re: Any experience with SeamFaceletViewHandler?
by SmokingAPipe
Ok, I'll try that. I'm now thinking that the problem is I don't have the Facelets Servlet installed in my web.xml. That would make sense; it's a load-on-startup servlet which probably does set up factories, etc.
But then I'm totally confused about URLs. Right now my files are .jsp files, but they are actually served by Seam, so the URLs are all .seam URLs. I notice in the Facelets examples they are all .xhtml files. What is the logic for getting these .xhtml files to be processed by both Seam and Facelets? I'm totally confused.
One good thing about changing them from .jsp to .xhtml is that NetBeans has a good built-in xhtml editor that will spot xhtml syntax errors, so I won't have to worry about that. I just have to worry about getting Seam and Faclets to operate on the same files, right?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996246#3996246
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996246
19 years, 7 months
[JBoss Seam] - Re: Any experience with SeamFaceletViewHandler?
by SmokingAPipe
Ok, I'm running plain vanilla JBoss 4.0.5 with whatever Tomcat it comes with, meaning that I'm using JSP 2.0, so that shouldn't be a problem.
"norman.richards(a)jboss.com" wrote : Oh, and Facelets is trivial to set up. Have a look at the examples. I would NEVER go back to plain JSPs unless forced to.
Here's what I tried:
I put the following in my faces-config.xml:
<application>
| <view-handler>org.jboss.seam.ui.facelet.SeamFaceletViewHandler</view-handler>
| </application>
|
which should just activate the Seam view handler, right? But then I get these exceptions:
Exception sending context initialized event to listener instance of class org.apache.myfaces.webapp.StartupServletContextListener
| java.lang.NoClassDefFoundError: com/sun/facelets/FaceletViewHandler
So I assume that if I put the right jars into my WEB-INF/lib, that would solve that exception, right? Any suggestions on which jars? Do I need to remove any jars from JBoss or do anything like that?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996242#3996242
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996242
19 years, 7 months
[EJB 3.0] - Re: Help on EjB 3 Packaging
by bustanil
Hi ALRubinger,
Currently my project has grown from 3 modules to 7 modules.
And my entity classes that is used by more than one session bean is scattered over the 7 jar file. It makes hot deployment running slow and surely slowing the development process. So I tried your setup.
Here's my first packaging build.xml :
| <?xml version="1.0"?>
|
| <!-- ======================================================================= -->
| <!-- JBoss build file -->
| <!-- ======================================================================= -->
|
| <project name="OLIBSE2-SERVER" default="all" basedir=".">
|
| ......
|
| <!-- =================================================================== -->
| <!-- Pack the CIF Module -->
| <!-- =================================================================== -->
| <target name="olibse2-cif" depends="compile">
| <jar jarfile="build/olibse2-cif.ejb3">
| <fileset dir="${build.classes.dir}">
| <include name="com/cip/olibse2/domain/cif/*.class" />
| <include name="com/cip/olibse2/cif/*.class" />
| </fileset>
| <fileset dir="${src.resources}/">
| <include name="META-INF/persistence.xml" />
| </fileset>
| </jar>
| <copy file="build/olibse2-cif.ejb3" todir="${jboss.home}/server/default/deploy" />
| </target>
|
| <!-- =================================================================== -->
| <!-- Pack the CurrentAccount Module -->
| <!-- =================================================================== -->
| <target name="olibse2-ca" depends="compile">
| <jar jarfile="build/olibse2-current.ejb3">
| <fileset dir="${build.classes.dir}">
| <include name="com/cip/olibse2/serahterimamodal/server/domain/*.class" />
| <include name="com/cip/olibse2/funding/saving/server/domain/*.class" />
| <include name="com/cip/olibse2/config/server/domain/*.class" />
| <include name="com/cip/olibse2/funding/current/server/*.class" />
| <include name="com/cip/olibse2/funding/saving/server/domain/*.class" />
| <include name="com/cip/olibse2/cif/server/domain/*.class" />
| <include name="com/cip/olibse2/cif/server/OperationResult.class" />
| <include name="com/cip/olibse2/funding/current/server/domain/*.class" />
| <include name="com/cip/olibse2/funding/current/server/exceptions/*.class" />
| <include name="com/cip/olibse2/approval/server/AuthSchema.class" />
| <include name="com/cip/olibse2/security/server/User.class" />
| </fileset>
| <fileset dir="${src.resources}/">
| <include name="META-INF/persistence.xml" />
| </fileset>
| </jar>
| <copy file="build/olibse2-current.ejb3" todir="${jboss.home}/server/default/deploy" />
| </target>
|
| <!-- =================================================================== -->
| <!-- Pack the Configuration Module -->
| <!-- =================================================================== -->
| <target name="olibse2-config" depends="compile">
| <jar jarfile="build/olibse2-config.ejb3">
| <fileset dir="${build.classes.dir}">
| <include name="com/cip/olibse2/serahterimamodal/server/domain/*.class" />
| <include name="com/cip/olibse2/cif/server/domain/*.class" />
| <include name="com/cip/olibse2/funding/saving/server/domain/*.class" />
| <include name="com/cip/olibse2/config/server/*.class" />
| <include name="com/cip/olibse2/config/server/domain/*.class" />
| <include name="com/cip/olibse2/cif/server/OperationResult.class" />
| <include name="com/cip/olibse2/approval/server/AuthSchema.class" />
| <include name="com/cip/olibse2/security/server/User.class" />
| </fileset>
| <fileset dir="${src.resources}/">
| <include name="META-INF/persistence.xml" />
| </fileset>
| </jar>
| <copy file="build/olibse2-config.ejb3" todir="${jboss.home}/server/default/deploy" />
| </target>
|
| <!-- =================================================================== -->
| <!-- Pack the Transaction Module -->
| <!-- =================================================================== -->
| <target name="olibse2-tx" depends="compile">
| <jar jarfile="build/olibse2-tx.ejb3">
| <fileset dir="${build.classes.dir}">
| <include name="com/cip/olibse2/serahterimamodal/server/domain/*.class" />
| <include name="com/cip/olibse2/cif/server/domain/*.class" />
| <include name="com/cip/olibse2/funding/saving/server/domain/*.class" />
| <include name="com/cip/olibse2/transaction/server/*.class" />
| <include name="com/cip/olibse2/transaction/server/domain/*.class" />
| <include name="com/cip/olibse2/cif/server/OperationResult.class" />
| <include name="com/cip/olibse2/approval/server/AuthSchema.class" />
| <include name="com/cip/olibse2/security/server/User.class" />
| </fileset>
| <fileset dir="${src.resources}/">
| <include name="META-INF/persistence.xml" />
| </fileset>
| </jar>
| <copy file="build/olibse2-tx.ejb3" todir="${jboss.home}/server/default/deploy" />
| </target>
|
| </project>
As you can see, 20 classes under com/cip/olibse2/cif/server/domain/ is used on every module. So, i changed the configuration as you suggested to speed up the hot deployment:
| <!-- =================================================================== -->
| <!-- Pack the Entity Classes -->
| <!-- =================================================================== -->
| <target name="olibse2-entity" depends="compile">
| <jar jarfile="build/olibse2-entity.jar">
| <fileset dir="${build.classes.dir}">
| <include name="com/cip/olibse2/funding/current/server/domain/*.class" />
| <include name="com/cip/olibse2/funding/saving/server/domain/*.class" />
| <include name="com/cip/olibse2/cif/server/domain/*.class" />
| <include name="com/cip/olibse2/security/server/EcUserMenu.class" />
| <include name="com/cip/olibse2/security/server/EcUserMenuId.class" />
| <include name="com/cip/olibse2/transaction/server/domain/*.class" />
| <include name="com/cip/olibse2/config/server/domain/*.class" />
| <include name="com/cip/olibse2/serahterimamodal/server/domain/*.class" />
| </fileset>
| <fileset dir="${src.resources}/">
| <include name="META-INF/persistence.xml" />
| </fileset>
| </jar>
| <copy file="build/olibse2-entity.jar" todir="${jboss.home}/server/default/deploy" />
| </target>
|
| <target name="olibse2-cif-service" depends="compile">
| <jar jarfile="build/olibse2-cif-service.jar">
| <fileset dir="${build.classes.dir}">
| <include name="com/cip/olibse2/cif/server/*.class" />
| <include name="com/cip/olibse2/cif/server/exceptions/*.class" />
| <include name="com/cip/olibse2/approval/server/AuthSchema.class" />
| </fileset>
| <fileset dir="${src.resources}/">
| <include name="META-INF/persistence.xml" />
| </fileset>
| </jar>
| <copy file="build/olibse2-cif-service.jar" todir="${jboss.home}/server/default/deploy" />
| </target>
|
| .... // other services
|
|
The new configuration really made the hot deployment alot faster :D. But one big problem arose :(. The session bean in olibse2-cif-service.jar cannot found the entities which was packed in olibse2-entity.jar. I'have tried using ear configuration with an application.xml, but it didn't solve the problem. Is there anything I missed? Please help.
Best regards,
Bustanil
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996235#3996235
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996235
19 years, 7 months