[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2532:
--------------------------------
Parent: (was: DROOLS-2531)
Issue Type: Enhancement (was: Sub-task)
> UX design for scenario simulation
> ---------------------------------
>
> Key: DROOLS-2532
> URL: https://issues.jboss.org/browse/DROOLS-2532
> Project: Drools
> Issue Type: Enhancement
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam
>
> As Aimee or Cameron I want to:
> * Easily create test scenarios through the application UI, rather than needing to rely on using text files, spreadsheets, etc.
> * Get started with basic task scenario creation, with minimal engagement from IT.
> * Better understand the business ecosystem as it related to scenario simulation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2532:
--------------------------------
Sprint: RHDM7-Iteration13
> UX design for scenario simulation
> ---------------------------------
>
> Key: DROOLS-2532
> URL: https://issues.jboss.org/browse/DROOLS-2532
> Project: Drools
> Issue Type: Enhancement
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam
>
> As Aimee or Cameron I want to:
> * Easily create test scenarios through the application UI, rather than needing to rely on using text files, spreadsheets, etc.
> * Get started with basic task scenario creation, with minimal engagement from IT.
> * Better understand the business ecosystem as it related to scenario simulation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2532:
--------------------------------
Labels: UX UXTeam (was: UXTeam ux)
> UX design for scenario simulation
> ---------------------------------
>
> Key: DROOLS-2532
> URL: https://issues.jboss.org/browse/DROOLS-2532
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam
>
> As Aimee or Cameron I want to:
> * Easily create test scenarios through the application UI, rather than needing to rely on using text files, spreadsheets, etc.
> * Get started with basic task scenario creation, with minimal engagement from IT.
> * Better understand the business ecosystem as it related to scenario simulation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation
by Liz Clayton (JIRA)
Liz Clayton created DROOLS-2532:
-----------------------------------
Summary: UX design for scenario simulation
Key: DROOLS-2532
URL: https://issues.jboss.org/browse/DROOLS-2532
Project: Drools
Issue Type: Sub-task
Reporter: Liz Clayton
Assignee: Liz Clayton
As Aimee or Cameron I want to:
* Easily create test scenarios through the application UI, rather than needing to rely on using text files, spreadsheets, etc.
* Get started with basic task scenario creation, with minimal engagement from IT.
* Better understand the business ecosystem as it related to scenario simulation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3810) The core galleon pack zip is misnamed
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-3810:
----------------------------------------
Summary: The core galleon pack zip is misnamed
Key: WFCORE-3810
URL: https://issues.jboss.org/browse/WFCORE-3810
Project: WildFly Core
Issue Type: Bug
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
The galleon pack zip should be called wildfly-core-galleon-pack-${project.version}.zip. Now it is wildfly-core-feature-pack-${project.version}.zip
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10345) Clean up clustering subsystem tests to leverage more test conditions
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-10345:
-----------------------------------
Summary: Clean up clustering subsystem tests to leverage more test conditions
Key: WFLY-10345
URL: https://issues.jboss.org/browse/WFLY-10345
Project: WildFly
Issue Type: Task
Components: Clustering
Affects Versions: 12.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Currently the clustering subsystem tests don't validate:
* Test xml against a specific xsd
* subsystem-templates against current xsd
They also contain a redundant parsing test - validating the generated operation count - which doesn't really add any value. Removing this eliminates the need to enumerate schema versions.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10020) Custom Hibernate slot and second level cache with Wildfly 12 causes NullPointer Exception
by Jan-Willem Gmelig Meyling (JIRA)
[ https://issues.jboss.org/browse/WFLY-10020?page=com.atlassian.jira.plugin... ]
Jan-Willem Gmelig Meyling commented on WFLY-10020:
--------------------------------------------------
Thanks for your response! But with HH5.3 still in CR, will it make Wildfly 13? Or will this be WF14? I think for WF13 Hibernate 5.2.x can still be interesting. HH5.1 is getting rather old, workarounds to get HH5.2 dont work properly for WF12 anymore, and with the new Infinispan we seem about ready for it.
> Custom Hibernate slot and second level cache with Wildfly 12 causes NullPointer Exception
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-10020
> URL: https://issues.jboss.org/browse/WFLY-10020
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 12.0.0.Final
> Reporter: Alessandro Moscatelli
> Assignee: Scott Marlow
>
> Migrating to 12 with Hibernate Custom slot causes NullPointer Exception.
> https://mvnrepository.com/artifact/org.hibernate/hibernate-orm-modules
> <property name="jboss.as.jpa.providerModule" value="org.hibernate:5.2.13.Final" />
> 16:12:28,868 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Read persistence.xml for optoplus
> 16:12:29,142 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."optoplus-services-ear-1.0.18-SNAPSHOT.ear".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."optoplus-services-ear-1.0.18-SNAPSHOT.ear".FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "optoplus-services-ear-1.0.18-SNAPSHOT.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.jpa.processor.secondLevelCache.InfinispanCacheDeploymentListener.addCacheDependencies(InfinispanCacheDeploymentListener.java:129)
> at org.jboss.as.jpa.processor.secondLevelCache.CacheDeploymentListener.addCacheDependencies(CacheDeploymentListener.java:111)
> at org.jipijapa.event.impl.internal.Notification.addCacheDependencies(Notification.java:95)
> at org.jboss.as.jpa.hibernate5.HibernateSecondLevelCache.addSecondLevelCacheDependencies(HibernateSecondLevelCache.java:125)
> at org.jboss.as.jpa.hibernate5.HibernatePersistenceProviderAdaptor.addProviderDependencies(HibernatePersistenceProviderAdaptor.java:107)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnitPhaseOne(PersistenceUnitServiceHandler.java:538)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:273)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleEarDeployment(PersistenceUnitServiceHandler.java:228)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:135)
> at org.jboss.as.jpa.processor.PersistenceBeginInstallProcessor.deploy(PersistenceBeginInstallProcessor.java:52)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> ... 8 more
> 16:12:29,155 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"optoplus-services-ear-1.0.18-SNAPSHOT.ear\".FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"optoplus-services-ear-1.0.18-SNAPSHOT.ear\"
> Caused by: java.lang.NullPointerException"}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10020) Custom Hibernate slot and second level cache with Wildfly 12 causes NullPointer Exception
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-10020?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-10020:
-------------------------------------
[~jwgmeligmeyling] we recently upgraded to Infinispan 9.2.2 (see [https://github.com/wildfly/wildfly/commit/a753a58515ada9ce7a054c78caf6c4c...]), which contains initial support for the Hibernate ORM 5.3.0. As well as is working with the Hibernate 5.1.x series. We are jumping ahead to Hibernate ORM 5.3.0, which will be the latest + greatest.
The official jira for upgrading WildFly to use Hibernate is now [https://issues.jboss.org/browse/WFLY-10327], which also includes upgrading Hibernate Search.
> Custom Hibernate slot and second level cache with Wildfly 12 causes NullPointer Exception
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-10020
> URL: https://issues.jboss.org/browse/WFLY-10020
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 12.0.0.Final
> Reporter: Alessandro Moscatelli
> Assignee: Scott Marlow
>
> Migrating to 12 with Hibernate Custom slot causes NullPointer Exception.
> https://mvnrepository.com/artifact/org.hibernate/hibernate-orm-modules
> <property name="jboss.as.jpa.providerModule" value="org.hibernate:5.2.13.Final" />
> 16:12:28,868 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Read persistence.xml for optoplus
> 16:12:29,142 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."optoplus-services-ear-1.0.18-SNAPSHOT.ear".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."optoplus-services-ear-1.0.18-SNAPSHOT.ear".FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "optoplus-services-ear-1.0.18-SNAPSHOT.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.jpa.processor.secondLevelCache.InfinispanCacheDeploymentListener.addCacheDependencies(InfinispanCacheDeploymentListener.java:129)
> at org.jboss.as.jpa.processor.secondLevelCache.CacheDeploymentListener.addCacheDependencies(CacheDeploymentListener.java:111)
> at org.jipijapa.event.impl.internal.Notification.addCacheDependencies(Notification.java:95)
> at org.jboss.as.jpa.hibernate5.HibernateSecondLevelCache.addSecondLevelCacheDependencies(HibernateSecondLevelCache.java:125)
> at org.jboss.as.jpa.hibernate5.HibernatePersistenceProviderAdaptor.addProviderDependencies(HibernatePersistenceProviderAdaptor.java:107)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnitPhaseOne(PersistenceUnitServiceHandler.java:538)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:273)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleEarDeployment(PersistenceUnitServiceHandler.java:228)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:135)
> at org.jboss.as.jpa.processor.PersistenceBeginInstallProcessor.deploy(PersistenceBeginInstallProcessor.java:52)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> ... 8 more
> 16:12:29,155 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"optoplus-services-ear-1.0.18-SNAPSHOT.ear\".FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"optoplus-services-ear-1.0.18-SNAPSHOT.ear\"
> Caused by: java.lang.NullPointerException"}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months