[JBoss JIRA] (WFLY-5427) If used journal object store (AMQ Artemis journal) directory is named HornetqObjectStore
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5427?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5427:
-------------------------------
Fix Version/s: 12.0.0.Final
(was: 12.0.0.CR1)
> If used journal object store (AMQ Artemis journal) directory is named HornetqObjectStore
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-5427
> URL: https://issues.jboss.org/browse/WFLY-5427
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 10.0.0.CR2
> Reporter: Ondra Chaloupka
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 12.0.0.Final
>
>
> Directory of transaction object store is named {{standalone/data/tx-object-store/HornetqObjectStore}}. The WFLY 10 does not use HornetQ object store but it uses ActiveMQ Artemis object store. That's same for the Transaction subsystem.
> The journal dirctory should be renamed to {{JournalObjectStore}} or something similar.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-5265) Use WildFly Common for null param checks
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5265?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5265:
-------------------------------
Fix Version/s: 12.0.0.Final
(was: 12.0.0.CR1)
> Use WildFly Common for null param checks
> ----------------------------------------
>
> Key: WFLY-5265
> URL: https://issues.jboss.org/browse/WFLY-5265
> Project: WildFly
> Issue Type: Task
> Reporter: David Lloyd
> Assignee: David Lloyd
> Priority: Minor
> Fix For: 12.0.0.Final
>
>
> For each module, do the following:
> * Locate any/all null param check methods in the log msg
> * Replace them with calls to org.wildfly.common.Assert#checkNotNullParam or related method as needed
> * Replace the old null param check method with a comment that reserves the ID and shows that it was previously used for that purpose
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-5141) Custom operation for setting of process-id-*
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5141?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5141:
-------------------------------
Fix Version/s: 12.0.0.Final
(was: 12.0.0.CR1)
> Custom operation for setting of process-id-*
> --------------------------------------------
>
> Key: WFLY-5141
> URL: https://issues.jboss.org/browse/WFLY-5141
> Project: WildFly
> Issue Type: Feature Request
> Components: Transactions
> Affects Versions: 10.0.0.Beta1
> Reporter: Ondra Chaloupka
> Assignee: Amos Feng
> Priority: Minor
> Labels: ux
> Fix For: 12.0.0.Final
>
>
> When you want to set generation of process-id-* - either as uuid or as socket id the way to set it and set it back is inconsistent. In one direction you need to use composite operation in other direction you can't use it.
> All this is discussed in jiras WFLY-2623 and WFLY-5126
> As result of discussion https://issues.jboss.org/browse/WFLY-2623#comment-13100037 this issue is raised.
> It would be much better for user to have single way how to do this switching and custom operation could solve this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-6365) Update permissions to use Elytron permission helper API
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-6365?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-6365:
-------------------------------
Fix Version/s: 12.0.0.Final
(was: 12.0.0.CR1)
> Update permissions to use Elytron permission helper API
> -------------------------------------------------------
>
> Key: WFLY-6365
> URL: https://issues.jboss.org/browse/WFLY-6365
> Project: WildFly
> Issue Type: Sub-task
> Reporter: David Lloyd
> Fix For: 12.0.0.Final
>
>
> The Elytron permission base classes ensure spec compliance including serialization guarantees while also drastically reducing the amount of code required to implement permission classes correctly and improving performance and memory overhead, especially when a security manager is engaged. Use these classes as base classes for all WildFly permission classes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months