[EJB 3.0] - <exclude-list> in ejb-jar.xml doesnt work
by sanjeeth
hello All,
I am using the <exclude-list> in the ejb-jar.xml to restrict a method call from the client. My deployment succede but from the client invoking that method succedes without any exception.
ejb-jar.xml
<ejb-jar>
<enterprise-beans>
<ejb-name>ejb1</ejb-name>
test.CurrencyHome
test.Currency
<ejb-class>test.CurrencyBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</enterprise-beans>
<assembly-descriptor>
<exclude-list>
<ejb-name>ejb1</ejb-name>
<method-name>test</method-name>
</exclude-list>
</assembly-descriptor>
</ejb-jar>
jboss.xml
<enterprise-beans>
<ejb-name>ejb1</ejb-name>
<jndi-name>cc</jndi-name>
<local-jndi-name>cclocal</local-jndi-name>
</enterprise-beans>
In the above xmls i have specified the method name "test" to restrict. The Method "test" is declared in the remote interface. From the client when i call method "test" it succedes. Is there any other configuration needs to be done for this to work. Could anybody please help me out regarding this issue.
thanks in advance
sanjeeth S
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987217#3987217
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987217
19Â years, 7Â months
[JBoss Seam] - prevent access to page
by dan.j.allen
One of the troubles I come across when working with JSF applications is the inability to verify that a user should even be on the page that is requested. I am wondering if Seam helps out in this area in any way.
Let me give an example scenario.
In the hotel booking application, a request for /hotel.seam or /book.seam without a conversation id renders a partially broken page (empty hotel data). Some of the logic in the backing bean could assume that a valid hotel is available, but in this case it is not. While the booking application doesn't trip on this, it is very likely that another application could (depending on what is going on in those backing bean getter methods). From the standpoint of a user, I would expect the application to redirect me to a start page if I attempt to access the application somewhere in the middle of a flow.
Is there any place I can perform validation logic before PhaseId.RENDER_VIEW? If the conversation is not valid or a certain variable is not present, I would like to redirect the user somewhere else.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987216#3987216
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987216
19Â years, 7Â months