[JBoss JIRA] (WFLY-10352) Update singleton service API to MSC 1.4.x
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-10352?page=com.atlassian.jira.plugin... ]
Paul Ferraro updated WFLY-10352:
--------------------------------
Description:
The singleton service API uses MSC API that was deprecated in 1.4.x.
We need to update the singleton service API to support building services using the new MSC API while maintaining API compatibility.
was:
The singleton service API uses MSC API that was deprecated in 1.4.x.
We need to update the singleton service API while maintain API compatibility.
> Update singleton service API to MSC 1.4.x
> -----------------------------------------
>
> Key: WFLY-10352
> URL: https://issues.jboss.org/browse/WFLY-10352
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Affects Versions: 13.0.0.Beta1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
>
> The singleton service API uses MSC API that was deprecated in 1.4.x.
> We need to update the singleton service API to support building services using the new MSC API while maintaining API compatibility.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10329) Have JipiJapa enable Hibernate Search backward compatibility properties
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/WFLY-10329?page=com.atlassian.jira.plugin... ]
Sanne Grinovero commented on WFLY-10329:
----------------------------------------
ok thanks Scott. Hibernate Search already has such tests of course, I just wondered if you felt if Wildfly was needing a test to verify the property is being set... but that's probably excessive :)
> Have JipiJapa enable Hibernate Search backward compatibility properties
> -----------------------------------------------------------------------
>
> Key: WFLY-10329
> URL: https://issues.jboss.org/browse/WFLY-10329
> Project: WildFly
> Issue Type: Task
> Reporter: Sanne Grinovero
> Assignee: Scott Marlow
> Fix For: 13.0.0.Beta1
>
>
> For Hibernate Search 5.10.x to be fully backwards compatible with the previous versions included in WildFly, we need the following property to be set by default among the Hibernate ORM configuration properties:
> {code}
> hibernate.search.index_uninverting_allowed=true
> {code}
> When set to true and the mapping actually makes use of this feature, a warning will be logged.
> We probably will want to document this as well: recommend users to set it to "false" explicitly, as relying on this feature has a performance penalty, yet no relying on it requires mapping changes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10025) Use new org.jboss.modules.ClassTransformer interface instead of j.l.i.ClassFileTransformer
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-10025?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-10025:
-------------------------------------
Looks like we are clear to proceed on this, as Modules 1.8.5.Final (or newer) appears to be in wildfly-core now.
> Use new org.jboss.modules.ClassTransformer interface instead of j.l.i.ClassFileTransformer
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-10025
> URL: https://issues.jboss.org/browse/WFLY-10025
> Project: WildFly
> Issue Type: Enhancement
> Components: JPA / Hibernate
> Reporter: David Lloyd
> Assignee: Scott Marlow
> Priority: Minor
>
> The JPA classes use {{java.lang.instrument.ClassFileTransformer}} for class transformation, however this style of transformer incurs an extra whole-byte-array copy when loading memory-mapped classes or using other resource loaders which operate on byte buffers.
> After the Modules 1.8.0.Final upgrade, switch to using {{org.jboss.modules.ClassTransformer}} instead.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-8736) Add jms destination browse functionality provided by Artemis
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8736?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-8736:
-----------------------------------
Component/s: JMS
(was: CLI)
(was: JMX)
I've changed the component on this to JMS, which is the one we use for tracking the messaging subsystems. The proposed change here is just to the management API of the subsystem. The CLI and JConsole automatically support whatever the subsystem exposes so there's no CLI/JMX change involved here.
> Add jms destination browse functionality provided by Artemis
> -------------------------------------------------------------
>
> Key: WFLY-8736
> URL: https://issues.jboss.org/browse/WFLY-8736
> Project: WildFly
> Issue Type: Enhancement
> Components: JMS
> Affects Versions: 10.1.0.CR1, 11.0.0.Alpha1
> Reporter: varsha Kamble
> Labels: cli, jms, jmx-console
>
> Artemis 1.5.x provides browse functionality via jconsole. However Wildfly 11 and below versions which includes Artemis 1.5.x as default JMS broker does not provide/implement this functionality.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months