[JBoss JIRA] (DROOLS-14) When using the combination of drools-guvnor and jBPM-designer on JBoss in IE 9 new diagrams are not loaded after creation
by Nils Miehe (JIRA)
Nils Miehe created DROOLS-14:
--------------------------------
Summary: When using the combination of drools-guvnor and jBPM-designer on JBoss in IE 9 new diagrams are not loaded after creation
Key: DROOLS-14
URL: https://issues.jboss.org/browse/DROOLS-14
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Windows 7, IE9, JBoss AS 7.1.1.Final, jBPM Designer 2.4.0.Final, Drools Guvnor 5.5.0.Final
Reporter: Nils Miehe
Assignee: Mark Proctor
I want to use the jBPM Designer to create a BPMN2 process. It is in fact created (It is listed in the according package afterwards.) but when the new process should be opened and it's diagram be shown the screen remains stuck on showing the message "jBPM Web Designer loading. Please wait...". The same is true when I try to load existing BPMN2 processes from the repository (which I created using Firefox).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JGRP-1562) With fluent configuration, not all managed attributes are exposed anymore
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1562?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-1562.
----------------------------
Resolution: Done
- Fluent methods are now supported
- All attributes are exposed as they are written, e.g. mcast_addr is not McastAddr, but mcast_addr
> With fluent configuration, not all managed attributes are exposed anymore
> -------------------------------------------------------------------------
>
> Key: JGRP-1562
> URL: https://issues.jboss.org/browse/JGRP-1562
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.3
>
>
> When we have an attribute 'name' and a getter getName() and setter setName(), the @ManagedAttribute annotation can expose name via JMX. However, if we rename the getter name() and the setter name(String n), then 'name' won't be exposed.
> SOLUTION:
> Change the algorithm to also take getters and setters into account which don't start with "get" or "set"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (DROOLS-13) OTN id generation doesn't take count of inheritance
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-13:
---------------------------------
Summary: OTN id generation doesn't take count of inheritance
Key: DROOLS-13
URL: https://issues.jboss.org/browse/DROOLS-13
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Mario Fusco
Assignee: Mark Proctor
The following set of rules reproduces this issue:
{code}
declare Parent
active : boolean
end
declare Child extends Parent
end
rule "Init"
when
then
insert( new Child( false ) );
end
rule "Print"
when
$g : Child( active == true )
then
System.out.println("Rule B " + $g );
end
rule "Switch"
when
$item : Parent( active == false )
then
System.out.println("Rule C " + $item );
modify ( $item ) {
setActive( true );
}
end
{code}
Here when rule "Switch" modifies the object, it correctly triggers the rule "Print", only, when it tries to create an activation for "Print", it reuses the existing activation for "Switch".
The problem is in LeftTupleSource.doModifyLeftTuple where it ends up comparing otnIds that can potentially be generated by different OTNs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (SECURITY-722) SPNEGO-fallback-to-FORM authentication does not work with httpd+JBossEAP6 if SPNEGO not available
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/SECURITY-722?page=com.atlassian.jira.plug... ]
Darran Lofthouse commented on SECURITY-722:
-------------------------------------------
I am not really following the description here - if you have configured a proxy server that is sending it's own HTTP 401 responses to the client then yes it would be expected that the JBoss Negotiation fall back to FORM authentication will not be possible.
> SPNEGO-fallback-to-FORM authentication does not work with httpd+JBossEAP6 if SPNEGO not available
> -------------------------------------------------------------------------------------------------
>
> Key: SECURITY-722
> URL: https://issues.jboss.org/browse/SECURITY-722
> Project: PicketBox
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Negotiation
> Affects Versions: Negotiation_2_2_1
> Environment: RHEL6, JBoss EAP 6
> Reporter: flame liu
> Assignee: Darran Lofthouse
>
> I configured SPNEGO in EAP6. It works well both with EAP only and EAP6 + Apache httpd(mod_proxy). Users just run kinit and will be able to be successfully authenticated.
> After that, I added the fallback-to-form files/configurations both in the web app and standalone-full.xml. The fallback-to-form works only if httpd stops. If httpd starts, 401 error will always be thrown out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (HIBERNATE-134) Infinispan custom cache command factory not installed error during app deployment
by Anthony O. (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-134?page=com.atlassian.jira.plu... ]
Anthony O. commented on HIBERNATE-134:
--------------------------------------
We have the exact same problem as Miguel Coxo.
> Infinispan custom cache command factory not installed error during app deployment
> ---------------------------------------------------------------------------------
>
> Key: HIBERNATE-134
> URL: https://issues.jboss.org/browse/HIBERNATE-134
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: Ubuntu 12.04, JBoss AS 7.1.2, Hibernate 4.1.2, Infinispan 5.1.4
> Reporter: Dmitry Chuiko
> Assignee: Steve Ebersole
>
> We use Infinispan as 2LC for Hibernate in a clustered configuration under JBoss 7. So {{persistence.xml}} contains the following line: {code:xml}<property name="hibernate.cache.region.factory_class" value="org.hibernate.cache.infinispan.InfinispanRegionFactory"/>{code}. The following error occurs during app deployment:
> {noformat}12:04:52,859 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-14) MSC00001: Failed to start service jboss.persistenceunit."MOYsklad.ear/sklad-base.jar#MOYsklad": org.jboss.msc.service.StartException in service jboss.persistenceunit."MOYsklad.ear/sklad-base.jar#MOYsklad": Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
> Caused by: javax.persistence.PersistenceException: [PersistenceUnit: MOYsklad] Unable to build EntityManagerFactory
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:915)
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:890)
> at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74)
> at org.hibernate.ejb.HibernatePersistenceLognex.createContainerEntityManagerFactory(HibernatePersistenceLognex.java:16)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> Caused by: org.hibernate.cache.CacheException: Infinispan custom cache command factory not installed (possibly because the classloader where Infinispan lives couldn't find the Hibernate Infinispan cache provider)
> at org.hibernate.cache.infinispan.InfinispanRegionFactory.getCacheCommandFactory(InfinispanRegionFactory.java:500)
> at org.hibernate.cache.infinispan.InfinispanRegionFactory.startRegion(InfinispanRegionFactory.java:379)
> at org.hibernate.cache.infinispan.InfinispanRegionFactory.buildEntityRegion(InfinispanRegionFactory.java:212)
> at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:347)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1741)
> at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:93)
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:905)
> ... 10 more
> {noformat}
> This issue takes place because context {{ClassLoader}} is substituted in {{org.hibernate.ejb.Ejb3Configuration#configure}}. So Infinispan can not find {{org.infinispan.commands.module.ModuleCommandExtensions}} realization from {{hibernate-infinispan}} module in {{org.infinispan.util.ModuleProperties#loadModuleCommandHandlers}} method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBLOGGING-89) Log files cleanup for periodic-rotating-file-handler
by Razvan Popa (JIRA)
Razvan Popa created JBLOGGING-89:
------------------------------------
Summary: Log files cleanup for periodic-rotating-file-handler
Key: JBLOGGING-89
URL: https://issues.jboss.org/browse/JBLOGGING-89
Project: JBoss Logging
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Razvan Popa
Assignee: David Lloyd
Priority: Minor
Hi,
It would be useful for the periodic-rotating-file-handler to have a "max-backup-index" attribute to allow the removal of older files like in the size-rotating-file-handler.
It would also be nice to have something like "archive-older-than" and "delete-older-than" to also keep some older files archived for a while.
Regards,
Razvan
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (SECURITY-722) SPNEGO-fallback-to-FORM authentication does not work with httpd+JBossEAP6 if SPNEGO not available
by flame liu (JIRA)
flame liu created SECURITY-722:
----------------------------------
Summary: SPNEGO-fallback-to-FORM authentication does not work with httpd+JBossEAP6 if SPNEGO not available
Key: SECURITY-722
URL: https://issues.jboss.org/browse/SECURITY-722
Project: PicketBox
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Negotiation
Affects Versions: Negotiation_2_2_1
Environment: RHEL6, JBoss EAP 6
Reporter: flame liu
Assignee: Darran Lofthouse
I configured SPNEGO in EAP6. It works well both with EAP only and EAP6 + Apache httpd(mod_proxy). Users just run kinit and will be able to be successfully authenticated.
After that, I added the fallback-to-form files/configurations both in the web app and standalone-full.xml. The fallback-to-form works only if httpd stops. If httpd starts, 401 error will always be thrown out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months