[JBoss JIRA] (DROOLS-2659) UX: Design of Stunner Designers Zoom
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2659?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2659:
--------------------------------
Labels: UX UXTeam (was: Drools UX UXTeam)
> UX: Design of Stunner Designers Zoom
> ------------------------------------
>
> Key: DROOLS-2659
> URL: https://issues.jboss.org/browse/DROOLS-2659
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Liz Clayton
> Labels: UX, UXTeam
>
> Please provide design of the zoom +/- buttons and slider and their positioning. Suggest if the zoom buttons and slider should be:
> - directly in the canvas, similar to google maps
> - in the properties panel on the right side, shown user clicks to empty space in the diagram, i.e. no node is selected
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (WFLY-10647) Custom jgroups classes should be registered registered eagerly
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-10647:
-------------------------------------
Summary: Custom jgroups classes should be registered registered eagerly
Key: WFLY-10647
URL: https://issues.jboss.org/browse/WFLY-10647
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Radoslav Husar
Assignee: Radoslav Husar
If a message is received with configured custom classes (e.g. AUTH) but the receiving stack does not have the protocol, rather than handling and later discarding it, it floods the server log with CNFE.
{noformat}
18:55:49,152 ERROR [org.jgroups.protocols.UDP] (ucast-receiver-5,ejb,node2) JGRP000030: node2: failed handling incoming message: java.lang.ClassNotFoundException: Class for magic number 1100 cannot be found
at org.jgroups.conf.ClassConfigurator.create(ClassConfigurator.java:118)
at org.jgroups.protocols.AuthHeader.readAuthToken(AuthHeader.java:70)
at org.jgroups.protocols.AuthHeader.readFrom(AuthHeader.java:41)
at org.jgroups.Message.readHeader(Message.java:870)
at org.jgroups.Message.readFrom(Message.java:742)
at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1346)
at org.jgroups.protocols.TP.receive(TP.java:1304)
at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:709)
at org.jboss.as.clustering.jgroups.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:52)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (DROOLS-2659) UX: Design of Stunner Designers Zoom
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2659?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2659:
--------------------------------
Labels: Drools UX UXTeam (was: )
> UX: Design of Stunner Designers Zoom
> ------------------------------------
>
> Key: DROOLS-2659
> URL: https://issues.jboss.org/browse/DROOLS-2659
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Liz Clayton
> Labels: Drools, UX, UXTeam
>
> Please provide design of the zoom +/- buttons and slider and their positioning. Suggest if the zoom buttons and slider should be:
> - directly in the canvas, similar to google maps
> - in the properties panel on the right side, shown user clicks to empty space in the diagram, i.e. no node is selected
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-10520:
-------------------------------------
We definitely need some WF doc, about how to enable the transformer, but IMO, the detailed documentation, about which transformations are made, should be in ORM doc.
> Add Hibernate ORM 5.3 compatibility transformer
> -----------------------------------------------
>
> Key: WFLY-10520
> URL: https://issues.jboss.org/browse/WFLY-10520
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate
> Reporter: Gail Badner
> Assignee: Scott Marlow
> Fix For: 14.0.0.CR1
>
>
> A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1.
> From https://docs.google.com/document/d/1cAVBdeQXQfpTwH0f_GKSahh_gRd7bKI6kII-w...
> # Change call to org.hibernate.BasicQueryContract.getFlushMode() to instead call BasicQueryContract.getHibernateFlushMode().
> # Change call to org.hibernate.Session.getFlushMode, to instead call Session.getHibernateFlushMode()
> # App References to Enum org.hibernate.FlushMode.NEVER (0) should be transformed to reference FlushMode.MANUAL (0) instead.
> # For call to org.hibernate.Query.getMaxResults() returning Integer, instead call org.hibernate.Query.getHibernateMaxResults() (returning Integer).
> # For call to org.hibernate.Query.setMaxResults(int), instead call org.hibernate.Query.setHibernateMaxResults(int).
> # For call to org.hibernate.Query.getFirstResult(int) returning Integer, instead call org.hibernate.Query.getHibernateFirstResult() (returning Integer).
> # For call to org.hibernate.Query.setFirstResult(int), instead call org.hibernate.Query.setHibernateFirstResult(int).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer
by Gail Badner (JIRA)
[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ]
Gail Badner commented on WFLY-10520:
------------------------------------
[~smarlow], moving the transformer to the ORM core module makes sense.
I'm not sure about documentation though. [~sgilda], should the transformer be documented in WF as well as Hibernate ORM?
> Add Hibernate ORM 5.3 compatibility transformer
> -----------------------------------------------
>
> Key: WFLY-10520
> URL: https://issues.jboss.org/browse/WFLY-10520
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate
> Reporter: Gail Badner
> Assignee: Scott Marlow
> Fix For: 14.0.0.CR1
>
>
> A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1.
> From https://docs.google.com/document/d/1cAVBdeQXQfpTwH0f_GKSahh_gRd7bKI6kII-w...
> # Change call to org.hibernate.BasicQueryContract.getFlushMode() to instead call BasicQueryContract.getHibernateFlushMode().
> # Change call to org.hibernate.Session.getFlushMode, to instead call Session.getHibernateFlushMode()
> # App References to Enum org.hibernate.FlushMode.NEVER (0) should be transformed to reference FlushMode.MANUAL (0) instead.
> # For call to org.hibernate.Query.getMaxResults() returning Integer, instead call org.hibernate.Query.getHibernateMaxResults() (returning Integer).
> # For call to org.hibernate.Query.setMaxResults(int), instead call org.hibernate.Query.setHibernateMaxResults(int).
> # For call to org.hibernate.Query.getFirstResult(int) returning Integer, instead call org.hibernate.Query.getHibernateFirstResult() (returning Integer).
> # For call to org.hibernate.Query.setFirstResult(int), instead call org.hibernate.Query.setHibernateFirstResult(int).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer
by Gail Badner (JIRA)
[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ]
Gail Badner updated WFLY-10520:
-------------------------------
Description:
A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1.
>From https://docs.google.com/document/d/1cAVBdeQXQfpTwH0f_GKSahh_gRd7bKI6kII-w...
# Change call to org.hibernate.BasicQueryContract.getFlushMode() to instead call BasicQueryContract.getHibernateFlushMode().
# Change call to org.hibernate.Session.getFlushMode, to instead call Session.getHibernateFlushMode()
# App References to Enum org.hibernate.FlushMode.NEVER (0) should be transformed to reference FlushMode.MANUAL (0) instead.
# For call to org.hibernate.Query.getMaxResults() returning Integer, instead call org.hibernate.Query.getHibernateMaxResults() (returning Integer).
# For call to org.hibernate.Query.setMaxResults(int), instead call org.hibernate.Query.setHibernateMaxResults(int).
# For call to org.hibernate.Query.getFirstResult(int) returning Integer, instead call org.hibernate.Query.getHibernateFirstResult() (returning Integer).
# For call to org.hibernate.Query.setFirstResult(int), instead call org.hibernate.Query.setHibernateFirstResult(int).
was:
A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1.
>From https://docs.google.com/document/d/1cAVBdeQXQfpTwH0f_GKSahh_gRd7bKI6kII-w...
# Change call to org.hibernate.BasicQueryContract.getFlushMode() to instead call BasicQueryContract.getHibernateFlushMode().
# Change call to org.hibernate.Session.getFlushMode, to instead call Session.getHibernateFlushMode()
# Modify calls to org.hibernate.Query.getFirstResult() to convert returned int, to Integer result.
# Modify calls to org.hibernate.Query.getMaxResults() to convert returned int, to Integer result.
# App References to Enum org.hibernate.FlushMode.NEVER (0) should be transformed to reference FlushMode.MANUAL (0) instead.
# For call to org.hibernate.Query.setMaxResults(int), instead call org.hibernate.Query.setHibernateMaxResults(int).
# For call to org.hibernate.Query.setFirstResult(int), instead call org.hibernate.Query.setHibernateFirstResult(int).
> Add Hibernate ORM 5.3 compatibility transformer
> -----------------------------------------------
>
> Key: WFLY-10520
> URL: https://issues.jboss.org/browse/WFLY-10520
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate
> Reporter: Gail Badner
> Assignee: Scott Marlow
> Fix For: 14.0.0.CR1
>
>
> A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1.
> From https://docs.google.com/document/d/1cAVBdeQXQfpTwH0f_GKSahh_gRd7bKI6kII-w...
> # Change call to org.hibernate.BasicQueryContract.getFlushMode() to instead call BasicQueryContract.getHibernateFlushMode().
> # Change call to org.hibernate.Session.getFlushMode, to instead call Session.getHibernateFlushMode()
> # App References to Enum org.hibernate.FlushMode.NEVER (0) should be transformed to reference FlushMode.MANUAL (0) instead.
> # For call to org.hibernate.Query.getMaxResults() returning Integer, instead call org.hibernate.Query.getHibernateMaxResults() (returning Integer).
> # For call to org.hibernate.Query.setMaxResults(int), instead call org.hibernate.Query.setHibernateMaxResults(int).
> # For call to org.hibernate.Query.getFirstResult(int) returning Integer, instead call org.hibernate.Query.getHibernateFirstResult() (returning Integer).
> # For call to org.hibernate.Query.setFirstResult(int), instead call org.hibernate.Query.setHibernateFirstResult(int).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (WFLY-10638) Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-10638?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-10638:
-------------------------------------
[~pferraro] what is the best way for us to disable the warning that comes from Infinispan-Hibernate 5.3 integration code? Create a ISPN jira for removing the warning?
> Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-10638
> URL: https://issues.jboss.org/browse/WFLY-10638
> Project: WildFly
> Issue Type: Task
> Components: Clustering, JPA / Hibernate
> Affects Versions: 13.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 14.0.0.CR1
>
>
> Currently, during deployment of ORM 5.3.* applications, the following warning is logged in the server console, four times per persistence unit. It should not appear at all.
> {quote}
> HHH025030: Transactional caches are not supported. The configuration option will be ignored; please unset.
> {quote}
> The warning comes from ORM 5.3 integration code org.infinispan.hibernate.cache.v53.InfinispanRegionFactory#unsetTransactions.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-10520:
-------------------------------------
[~gbadner] now that we are closer to completion, should we move the transformer to the ORM core module, so it could be used by other environments?
I'm also curious where the transformer documentation should be? In ORM or WF or both?
> Add Hibernate ORM 5.3 compatibility transformer
> -----------------------------------------------
>
> Key: WFLY-10520
> URL: https://issues.jboss.org/browse/WFLY-10520
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate
> Reporter: Gail Badner
> Assignee: Scott Marlow
> Fix For: 14.0.0.CR1
>
>
> A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1.
> From https://docs.google.com/document/d/1cAVBdeQXQfpTwH0f_GKSahh_gRd7bKI6kII-w...
> # Change call to org.hibernate.BasicQueryContract.getFlushMode() to instead call BasicQueryContract.getHibernateFlushMode().
> # Change call to org.hibernate.Session.getFlushMode, to instead call Session.getHibernateFlushMode()
> # Modify calls to org.hibernate.Query.getFirstResult() to convert returned int, to Integer result.
> # Modify calls to org.hibernate.Query.getMaxResults() to convert returned int, to Integer result.
> # App References to Enum org.hibernate.FlushMode.NEVER (0) should be transformed to reference FlushMode.MANUAL (0) instead.
> # For call to org.hibernate.Query.setMaxResults(int), instead call org.hibernate.Query.setHibernateMaxResults(int).
> # For call to org.hibernate.Query.setFirstResult(int), instead call org.hibernate.Query.setHibernateFirstResult(int).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (WFLY-10288) Remove ee8.preview.mode support
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-10288?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-10288:
---------------------------------
Description:
Once Java EE 8 compliant we need to remove the support for the {{ee8.preview.mode}} system property.
The following modules will need to be updated:
* -{{javax.enterprise.api}}-
* {{javax.validation.api}}
* -{{javax.json.bind.api}}-
* -{{javax.json.api}}-
* {{javax.annotation.api}}
* -{{javax.servlet.api}}-
* -{{org.wildfly.bridge.servlet-api-bridge}} (needs to be removed)-
* -{{org.eclipse.yasson}}-
* -{{org.glassfish.javax.json}}-
* {{javax.persistence.api}}
* {{javax.ws.rs.api}}
* {{javax.faces.api}}
* {{javax.mail.api}}
* {{javax.xml.bind.api}}
* -{{org.wildfly.cdi-api-bridge}}-
* {{org.jboss.resteasy.resteasy-json-binding-provider}}
* {{org.jboss.resteasy.resteasy-jaxrs}}
* {{org.hibernate.validator}}
* {{org.hibernate.validator.cdi}}
* {{org.hibernate}}
* {{com.sun.jsf-impl}}
The following configuration needs to be removed:
* {{./feature-pack/src/main/resources/configuration/standalone/template-ee8.xml}}
The Hibernate Search modules are currently duplicated:
* {{org.hibernate.search.*}} using "main" slot should be removed
* {{org.hibernate.search.*}} using "5.10" slot should be promoted to main
* Update usage of constants {{org.jboss.as.jpa.config.Configuration#PROVIDER_MODULE_HIBERNATE_SEARCH_EE8}}, PROVIDER_MODULE_HIBERNATE_SEARCH_EE7
The following source files should be updated:
* -{{org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.java}}-
* -{{org.wildfly.extension.undertow.deployment.WarMetaDataProcessor.java}}-
Any solution for WFLY-10289 should be reverted.
The following documentation needs to be updated:
* {{./docs/src/main/asciidoc/Getting_Started_Guide.adoc}}
was:
Once Java EE 8 compliant we need to remove the support for the {{ee8.preview.mode}} system property.
The following modules will need to be updated:
* {{javax.enterprise.api}}
* {{javax.validation.api}}
* -{{javax.json.bind.api}}-
* -{{javax.json.api}}-
* {{javax.annotation.api}}
* -{{javax.servlet.api}}-
* -{{org.wildfly.bridge.servlet-api-bridge}} (needs to be removed)-
* -{{org.eclipse.yasson}}-
* -{{org.glassfish.javax.json}}-
* {{javax.persistence.api}}
* {{javax.ws.rs.api}}
* {{javax.faces.api}}
* {{javax.mail.api}}
* {{javax.xml.bind.api}}
* {{org.wildfly.cdi-api-bridge}}
* {{org.jboss.resteasy.resteasy-json-binding-provider}}
* {{org.jboss.resteasy.resteasy-jaxrs}}
* {{org.hibernate.validator}}
* {{org.hibernate.validator.cdi}}
* {{org.hibernate}}
* {{com.sun.jsf-impl}}
The following configuration needs to be removed:
* {{./feature-pack/src/main/resources/configuration/standalone/template-ee8.xml}}
The Hibernate Search modules are currently duplicated:
* {{org.hibernate.search.*}} using "main" slot should be removed
* {{org.hibernate.search.*}} using "5.10" slot should be promoted to main
* Update usage of constants {{org.jboss.as.jpa.config.Configuration#PROVIDER_MODULE_HIBERNATE_SEARCH_EE8}}, PROVIDER_MODULE_HIBERNATE_SEARCH_EE7
The following source files should be updated:
* -{{org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.java}}-
* -{{org.wildfly.extension.undertow.deployment.WarMetaDataProcessor.java}}-
Any solution for WFLY-10289 should be reverted.
The following documentation needs to be updated:
* {{./docs/src/main/asciidoc/Getting_Started_Guide.adoc}}
> Remove ee8.preview.mode support
> -------------------------------
>
> Key: WFLY-10288
> URL: https://issues.jboss.org/browse/WFLY-10288
> Project: WildFly
> Issue Type: Sub-task
> Components: EE
> Reporter: James Perkins
> Assignee: James Perkins
> Fix For: 14.0.0.CR1
>
>
> Once Java EE 8 compliant we need to remove the support for the {{ee8.preview.mode}} system property.
> The following modules will need to be updated:
> * -{{javax.enterprise.api}}-
> * {{javax.validation.api}}
> * -{{javax.json.bind.api}}-
> * -{{javax.json.api}}-
> * {{javax.annotation.api}}
> * -{{javax.servlet.api}}-
> * -{{org.wildfly.bridge.servlet-api-bridge}} (needs to be removed)-
> * -{{org.eclipse.yasson}}-
> * -{{org.glassfish.javax.json}}-
> * {{javax.persistence.api}}
> * {{javax.ws.rs.api}}
> * {{javax.faces.api}}
> * {{javax.mail.api}}
> * {{javax.xml.bind.api}}
> * -{{org.wildfly.cdi-api-bridge}}-
> * {{org.jboss.resteasy.resteasy-json-binding-provider}}
> * {{org.jboss.resteasy.resteasy-jaxrs}}
> * {{org.hibernate.validator}}
> * {{org.hibernate.validator.cdi}}
> * {{org.hibernate}}
> * {{com.sun.jsf-impl}}
> The following configuration needs to be removed:
> * {{./feature-pack/src/main/resources/configuration/standalone/template-ee8.xml}}
> The Hibernate Search modules are currently duplicated:
> * {{org.hibernate.search.*}} using "main" slot should be removed
> * {{org.hibernate.search.*}} using "5.10" slot should be promoted to main
> * Update usage of constants {{org.jboss.as.jpa.config.Configuration#PROVIDER_MODULE_HIBERNATE_SEARCH_EE8}}, PROVIDER_MODULE_HIBERNATE_SEARCH_EE7
> The following source files should be updated:
> * -{{org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.java}}-
> * -{{org.wildfly.extension.undertow.deployment.WarMetaDataProcessor.java}}-
> Any solution for WFLY-10289 should be reverted.
> The following documentation needs to be updated:
> * {{./docs/src/main/asciidoc/Getting_Started_Guide.adoc}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 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 commented on DROOLS-2532:
-------------------------------------
Thanks [~aglass]!
> UX design for scenario simulation
> ---------------------------------
>
> Key: DROOLS-2532
> URL: https://issues.jboss.org/browse/DROOLS-2532
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: Appformer, ScenarioSimulation, UX, UXTeam
> Attachments: RoundG2.pdf
>
>
> As Aimee or Cameron I want to:
> * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision.
> * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT.
> * Run a test scenario simulation so that I can verify the expected results against test simulation results.
> Verification conditions:
> Provide wireframe design and click-thru prototype which includes the following views:
> * Overview (properties)
> * Scenario Template
> * Scenarios Input Screen
> * Results
> * Code View
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months