anonymous wrote :
| I think it should work as they described
|
In fact it does. But I needed some times before to get it: the key words are "current request". The viewId is the one of the request, i.e. of the required view, not of the requiring view.
You can switch from the current request to a new one and then come back to this request, but not to the point which raised this request.
Login in seam-gen is a good example to get it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082535#4082535
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082535
@In(required=false)
| TblReviews tr=new TblReviews();
|
| @In(required=false)
| TblComments tblcomm;
| @Out(required=false)
| @RequestParameter
| Long rid4comm; (review entry id value)
|
| public void writeComment() {
| tr.setReviewEntryId(rid4comm);
| tblcomm.setReviewEntryId(tr);
| em.persist(tblcomm);
| }
if we use tr.setReviewEntryId(rid4comm); it giving error
without that it inserting
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082533#4082533
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082533
Hi,
Is there any way to secure JNDI? I have been doing research on google, but couldn't find a way to secure JNDI. Basically, anyone can connect to JNDI via port 1099 and access to DataSource, JMS Queue, etc...
I am porting the application from Weblogic to JBoss. Weblogic can use "java.naming.security.principal" and "java.naming.security.credentials" to do a simple authentication to access JNDI, but I couldn't find a way to do in JBoss to make the authentication mandatory. Btw, there are clients from outside need to connect to JNDI to access EJB, so I cannot block port 1099 also.
Any suggestion on this matter? Thanks!
Cheers,
Deep Blue
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082528#4082528
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082528