[JBoss Seam] - multiple @Remove, EJB3 incompatible?
by sannegrinovero
Hello everyone, I was thinking about Seam's use of the @Remove and @Destroy annotations,
I am wondering if Seam is imposing me some limitations on respect to EJB3 specs, or if I'm missing something.
from the Seam docs:
@Destroy
anonymous wrote : The @Destroy method is called when the context that the Seam component is bound to ends. Components may define only one @Destroy method...[...]
| ...Destroy methods should be used only for cleanup.
@Remove
anonymous wrote : The EJB standard @Remove annotation specifies that a stateful session bean should be removed and its state destroyed after invocation of the annotated method. In Seam, all stateful session beans must define a method with no parameters marked @Remove. This method will be called when Seam destroys the session context.
Our application has some Stateful Beans with 1 single @Destroy and multiple @Remove; toying since some days JBoss Tools i get this error:
Duplicate @Remove method "methodname".
The applications actually looks-like working and I cant't tell if something bad is happening behind the scenes, but:
The warning from the tool makes sense as "This method will be called when Seam destroys the session context".. How could Seam know which method to call?
EJB3 uses the single @Destroy as a callback to cleanup, and is triggered by one of the @Remove; I think Seam is abusing this to call a @Remove (expecting it to be single) to trigger the EJB destroy.. is that right? couldn't seam directly ask EJB to trigger destruction? or have another annotation, an extension to @Remove, single on a bean, so to know which one to call?
I know I could avoid the need of multiple @Remove s with another design, but that's not the point.
Do I really need to remove the multiple "@Remove" from my beans? Does it really cause some trouble? I wouldn't like Seam spontaneously to call some of my annotated actions.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118216#4118216
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118216
18 years, 3 months
[Security & JAAS/JBoss] - HTTP Status 403 - logging with another role causes error
by neglli＠gmx.de
hi evereybody!
we are using different roles in our project: child and parent. for the parents site only parents should have access to the secured pages.
we are using form-based authentication.
when i log in with a user, that is not registered in our db, everything works fine and I am redirected to the login-error-page. when i log in as parent, also everything works fine and i am getting access to the secured page.
but when i log in as child (which is a proper defined role), i a not redirected to the login-error-page..
why? what do i have to change?
the relating passage of web.xml looks like this:
<!-- security -->
<security-constraint>
<display-name>SaferWebSecurity</display-name>
<web-resource-collection>
<web-resource-name>
SecureResource
</web-resource-name>
<url-pattern>/forwardPage.iface</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>P</role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<form-login-config>
<form-login-page>/login.html</form-login-page>
<form-error-page>/loginError.html</form-error-page>
</form-login-config>
</login-config>
<security-role>
Parent
<role-name>P</role-name>
</security-role>
<security-role>
Child
<role-name>C</role-name>
</security-role>
i'm looking forward for your answers.
cheers stefan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118198#4118198
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118198
18 years, 3 months