[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:
-------------------------------------
[~sannegrinovero] yes, but [see discussion above|https://issues.jboss.org/browse/WFLY-10520?focusedCommentId=1359785...] asking if we should move the transformer to Hibernate ORM core, since it is generic. I suppose one reason to not move it, is that we removed the ORM dependency on ASM, years ago (when we dropped cglib as a bytecode provider).
> 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] (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 commented on DROOLS-2659:
-------------------------------------
Thanks [~mstevens1]! Going to reassign this to you, glad I asked. :)
> 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] (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 reassigned DROOLS-2659:
-----------------------------------
Assignee: Matthew Stevens (was: Liz Clayton)
> 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: Matthew Stevens
> 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] (DROOLS-2659) UX: Design of Stunner Designers Zoom
by Matthew Stevens (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2659?page=com.atlassian.jira.plugi... ]
Matthew Stevens commented on DROOLS-2659:
-----------------------------------------
Hello [~uxdlc] [~jomarko] [~roger600] I think the zoom controls would be the same across all modelers. The recommendations from last year in BAPL-989 still apply (below). As for location, either on the canvas or toolbar would be best. I would recommend against the property panel.
_Copied comment from BAPL-989_
1) A dropdown menu with quick zoom levels is standard. I would use values like Michael mentions above: 25, 50, 75, 100, 125, 150, 200, 300, 400. Then maybe: Fit Window (everything is visible) and Fit Page Width (everything fits horizontally, can scroll vertically).
2) In addition to that control, you often see an additional control for quick, granular zooms. These could be +/- buttons or a slider. It looks like one of the asset types already uses +/- buttons. I would prefer a slider but either is fine.
3) Finally, keyboard zoom is a nice bonus. The comment above mentions the Control key. That is fine. That key and the mouse wheel together should zoom.
> 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-10520) Add Hibernate ORM 5.3 compatibility transformer
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ]
Sanne Grinovero commented on WFLY-10520:
----------------------------------------
In ORM we can document which APIs changed but the transformations rules aren't shipped by ORM so having such documentation in ORM would get ouf of synch. It's also not relevant to the users who're not on a specific WildFly version.
> 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] (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 commented on DROOLS-2659:
-------------------------------------
[~jomarko] [~roger.martinez] Is this for Stunner or DMN modeler, or both (all designers?). [~mstevens1] If this is for all designers, is this something that you're already working on or planning to work on? Glad to work on it, just don't want confuse things... Thanks!
> 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 eagerly
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10647?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-10647:
----------------------------------
Affects Version/s: 13.0.0.Final
> Custom jgroups classes should be registered eagerly
> ---------------------------------------------------
>
> Key: WFLY-10647
> URL: https://issues.jboss.org/browse/WFLY-10647
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 13.0.0.Final
> 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] (WFLY-10647) Custom jgroups classes should be registered eagerly
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10647?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-10647:
----------------------------------
Summary: Custom jgroups classes should be registered eagerly (was: Custom jgroups classes should be registered registered eagerly)
> Custom jgroups classes should be 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