-
15. Re: Must call associate() before calling activate()
jaikiran May 9, 2011 3:52 AM (in response to lior.galanti)Lior Galanti wrote:
Is this scheduled to be working on 6.1.0?
Yes, it's scheduled to be fixed for 6.1.0.
-
16. Must call associate() before calling activate()
iabughosh May 9, 2011 5:56 AM (in response to lior.galanti)welcome to the forum Lior, you can use FORM based authentication, try your form-login/form-error pages with pure HTML tags instead of JSP/JSF tags.
-
17. Must call associate() before calling activate()
lior.galanti May 9, 2011 7:06 AM (in response to jaikiran)Is this fixed upstream in the 6.1.0 snapshots already?
-
18. Re: Must call associate() before calling activate()
lior.galanti Jun 22, 2011 10:53 AM (in response to icordoba)guys,
am i correct to assume this is still not fixed in the daily 6.1.x snapshots?
Should i start looking at alternatives or is something likely to happen soon?
-
19. Re: Must call associate() before calling activate()
paul_da_programmer Aug 22, 2011 9:08 AM (in response to lior.galanti)Lior (or anyone),
Can someone confirm this has been fixed in 6.1.0?
-
20. Re: Must call associate() before calling activate()
lior.galanti Aug 22, 2011 9:39 AM (in response to paul_da_programmer)Not really sure what the status on 6.1.x branch is, i sort of gave up on it. I switched the project to JBoss 7, which seems to be gertting all the attention. and although its very poorly documented for some reasone, if you look athis post http://stackoverflow.com/questions/2206911/best-way-for-user-authentication-on-javaee-6-using-jsf-2-0 the rigth way to go about web authentication is through a new feature on servelt 3.0
-
21. Re: Must call associate() before calling activate()
jaikiran Aug 24, 2011 12:39 AM (in response to lior.galanti)Lior Galanti wrote:
Not really sure what the status on 6.1.x branch is, i sort of gave up on it.
6.1.0 has already been released http://planet.jboss.org/view/post.seam?post=jboss_as_6_1_0_released
-
22. Re: Must call associate() before calling activate()
paul_da_programmer Oct 26, 2011 7:18 PM (in response to jaikiran)Ok, finally circled back to this and it appears that it has NOT been fixed for 6.1.0. I may be doing something wrong, but here's the behavior:
In my web.xml if I put:
<error-page>
<exception-type>javax.faces.application.ViewExpiredException</exception-type>
<location>/faces/timeout.xhtml</location>
</error-page>
The application does NOT work.
Instead if I put
<error-page>
<exception-type>javax.faces.application.ViewExpiredException</exception-type>
<location>/timeout.html</location>
</error-page>
The application WILL forward to the correct page when the session times out.
Obviously not being able to forward to a JSF page upon timeout has many problem (can't include templated header/footer) and other issues ...
If my gripe is legitimate I would assume this means you can't use a JSF page as a login form either for JAAS as the servlet container seems unable to forward you to a JSF page - you must have to use html only for login / bad login / timeout / generic error pages / etc .... anything that JAAS would normally forward you to.
If I'm wrong, please correct me
-
23. Re: Must call associate() before calling activate()
jaikiran Oct 28, 2011 12:19 AM (in response to paul_da_programmer)When you say "it's not working" what exactly do you mean? Are you seeing the same exception stacktrace that's reported in this thread? If not, please create a different thread with all the relevant details including the exception stacktrace.
-
24. Re: Must call associate() before calling activate()
paul_da_programmer Oct 28, 2011 6:49 PM (in response to jaikiran)Just to clarify - when I try to have a JSF page (xhtml - matched by the JSF servlet rules) I get the same errors as in the original thread (must call associate() before ...)
-
25. Re: Must call associate() before calling activate()
ildsarria Jun 27, 2012 11:08 AM (in response to paul_da_programmer)I Had the same issue on JBoss7.1.1.Final. The way I got it to work was to remove everything from the beans.xml file in my EJB project ( in the OtherSources: src/main/resourse/META-INF folder) , save it and rebuild the project ( Maven project)
Not a neat resolution but it was the only way it would work
-
26. Re: Must call associate() before calling activate()
paulkossler Apr 29, 2013 5:45 PM (in response to icordoba)FYI I ran into this problem with SEAM 2.3 on Jboss AS7
It is tied to the parsing of the beans.xml file.
I use annotations so my deployment does not need it. I removed it and it works fine.
This is a common issue in complex systems Basically multiple components from different spaces in a temporal graphs can/will run into conflicts as the components come from different spaces in their own temporal paths on the topography of the graphs. The main issue is in a lack of a special subset of integration tests called component dependency tests.
Basically the scope/tier of concern for components has to ensure their actual dependencies and warn the developer/deployer of the actual concern.
Regardless, the CDI in seam and JEE have developed on two overlapping temporal/time graphs. So when a part like seam 2.3 creates its own CDI implementation with things like @In and @Named these are handled in a similar but NOT the same path as JEE5/6 CDI @Inject and @Name. Then when the newer file beans.xml is introduced it changes the assertion path for the application (leading to an error in assumptions and an exception is thrown.)
ANSWER: the inclusion of the beans.xml changes the way the application is loaded in JBoss.
Solution: use annotations for beans and remove the beans.xml from your deployment.
Alternate issues: There may be other JEE configuration files that also cause this issue.
Good luck.
--Paul Kossler OCJP SSA SSE