[JBoss JIRA] Created: (JBRULES-428) Access Control List - each node to be protected
by Michael Neale (JIRA)
Access Control List - each node to be protected
------------------------------------------------
Key: JBRULES-428
URL: http://jira.jboss.com/jira/browse/JBRULES-428
Project: JBoss Rules
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: drools-brms
Reporter: Michael Neale
Assigned To: Michael Neale
Rule nodes (at least) need to have an ACL: what groups can access it in what capacity. First need to have a structure for ACLs to be stored.
They should be tied to user groups/roles, not individual logins.
JAAS should provide the user name and the users context (group membership) I believe.
When there is an ACL, it must be checked to see if the user (via their group membership) can do one of the following:
Edit, change status, view, delete.
If they can't view, ideally it will not be shown in any "lists", but if that is not feasable, it would be acceptable to list it, but not show the contents.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBAS-8592) quartz annotations + MDB integration not working in JBoss 5.1.10,
by Jason Novotny (JIRA)
quartz annotations + MDB integration not working in JBoss 5.1.10,
------------------------------------------------------------------
Key: JBAS-8592
URL: https://jira.jboss.org/browse/JBAS-8592
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Scheduling/Timers
Affects Versions: JBossAS-5.1.0.GA
Environment: JBossAS-5.1.10, Mac OS X, Java 6
Reporter: Jason Novotny
Assignee: Dimitris Andreadis
This used to work with JBoss 4.2.3GA
@MessageDriven(activationConfig = {
@ActivationConfigProperty(propertyName = "cronTrigger", propertyValue = "0 0 6,10,14 * * ?")
})
@ResourceAdapter("quartz-ra.rar")
public class AutoAlertingWatcherJob implements Job {
....
In Jboss 5.1.10GA it reports an error:
14:31:01,531 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=mach_EJB.jar,name=AutoAlertingWatcherJobMDB,service=EJB3 state=Create
org.jboss.deployers.spi.DeploymentException: MessagingType 'org.quartz.Job' not found in resource deployment jboss.jca:service=RARDeployment,name='jms-ra.rar'
at org.jboss.resource.deployers.RARDeployment.createActivationSpec(RARDeployment.java:311)
at org.jboss.resource.deployers.RARDeployment.internalInvoke(RARDeployment.java:276)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBAS-8591) Race condition in JCA datasource deployments
by Jason Greene (JIRA)
Race condition in JCA datasource deployments
--------------------------------------------
Key: JBAS-8591
URL: https://jira.jboss.org/browse/JBAS-8591
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Jason Greene
Assignee: Jason Greene
Priority: Blocker
Fix For: 7.0.0.Alpha1
13:26:35,678 ERROR [org.jboss.as.connector.deployer.dsdeployer] (pool-1-thread-1) Error during the deployment of java:/H2DS: org.jboss.jca.core.spi.mdr.NotFoundException: jdbc-local isn't registered
at org.jboss.jca.core.mdr.SimpleMetadataRepository.getResourceAdapter(SimpleMetadataRepository.java:144)
at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:247)
at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:163)
at org.jboss.as.connector.deployers.processors.DsDeploymentProcessor$AS7Deployer.doDeploy(DsDeploymentProcessor.java:189)
at org.jboss.as.connector.deployers.processors.DsDeploymentProcessor.processDeployment(DsDeploymentProcessor.java:116)
at org.jboss.as.deployment.chain.DeploymentChainImpl.processDeployment(DeploymentChainImpl.java:60)
at org.jboss.as.model.ServerDeploymentStartStopHandler.activate(ServerDeploymentStartStopHandler.java:201)
at org.jboss.as.model.ServerDeploymentStartStopHandler.deploy(ServerDeploymentStartStopHandler.java:88)
at org.jboss.as.model.ServerDeploymentStartStopHandler.deploy(ServerDeploymentStartStopHandler.java:72)
at org.jboss.as.connector.subsystems.datasources.JDBCRARDeployService.start(JDBCRARDeployService.java:65)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:923)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_22]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months