Done and done.
https://jira.jboss.org/jira/browse/JBMESSAGING-1460
Thanks!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192253#4192253
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192253
JBoss 4.2.3 and JBM 1.4.0.SP3
If I have a number of messages scheduled in the future and then call
removeAllMessages() from the JMX Console on that queue, the messages are
correctly removed. Both MessageCount and ScheduledMessageCount are set to
zero. The messages are not sent at their schedu
I've got an h:commandLink as follows:
|
| Go
|
|
|
|
|
|
The problem I'm having is that when the request is submitted, the call to
EntityQuery.getResultList() is performed before something.doAction(entity).
Since something.doAction() affects EntityQuery.getR
JIRA Issue created:
http://jira.jboss.com/jira/browse/JBSEAM-1902
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083084#4083084
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083084
If you have your logging level set to INFO you should see the following log
message printed out:
| 14:39:48,750 INFO [RuleBase] parsing rules: /META-INF/security.drl
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081026#4081026
Reply to the post :
I started hacking around with the source and I came up with the following
solution:
Change Identity.isSecurityEnabled():
|public static boolean isSecurityEnabled()
|{
| return securityEnabled &&
| Contexts.isSessionContextActive()&&
| Identity.i
I've just recently started using Seam's JBoss Rules support for securing
entities and I've run into an issue. When one of my MDBs tries to write to the
database, I get the following exception:
| java.lang.IllegalStateException: No active session context
| at org.jboss.seam.security.Ide
More of a EJB3 question, but I think you need to change:
| @OneToMany(mappedBy="workout", cascade=CascadeType.REMOVE)
| private List workouts = new ArrayList();
|
to
| @OneToMany(mappedBy="athlete", cascade=CascadeType.REMOVE)
| private List workouts = new ArrayList();
|
Looking at the @Restrict annotation I see that any objects in the Seam Context
can be referenced (such as 'selectedAccount' below):
@Name("account")
| public class AccountAction {
| @In Account selectedAccount;
| @Restrict("#{s:hasPermission('account','modify',selectedAccount)}")
