[ https://issues.jboss.org/browse/WFLY-1877?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-1877:
-------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> Make KeepAliveTimeAttributeDefinition deal with both a simple long and a complex attribute
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-1877
> URL: https://issues.jboss.org/browse/WFLY-1877
> Project: WildFly
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: ehsavoie Hugonnet
> Fix For: 9.0.0.CR1
>
>
> This attribute should support either a simple value or a complex one.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
[ https://issues.jboss.org/browse/WFLY-1984?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-1984:
-------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> MBeanAttributeInfo#isReadable and MBeanAttributeInfo#isWrittable return always true
> -----------------------------------------------------------------------------------
>
> Key: WFLY-1984
> URL: https://issues.jboss.org/browse/WFLY-1984
> Project: WildFly
> Issue Type: Feature Request
> Components: Domain Management, Security
> Reporter: Jakub Cechacek
> Assignee: Kabir Khan
> Labels: rbac-filed-by-qa
> Fix For: 9.0.0.CR1
>
>
> According to javadoc [1] these methods should return boolean value based on whether this attribute can be read / written. However currently true is returned even though authenticated user can't perform read / write operation.
> Note: As I am familiar with JMX spec only very briefly, it is possible that these methods are intended for something bit different.
> [1] http://docs.oracle.com/javase/7/docs/api/javax/management/MBeanAttributeI...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
[ https://issues.jboss.org/browse/WFLY-1878?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-1878:
-------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> Make concurrency items in ee subsystem use KeepAliveTimeAttributeDefinition
> ---------------------------------------------------------------------------
>
> Key: WFLY-1878
> URL: https://issues.jboss.org/browse/WFLY-1878
> Project: WildFly
> Issue Type: Sub-task
> Components: Domain Management, EE
> Reporter: Brian Stansberry
> Assignee: ehsavoie Hugonnet
> Fix For: 9.0.0.CR1
>
>
> Have the time-period attributes in ee use KeepAliveAD (or a renamed, slightly more generic version thereof.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
[ https://issues.jboss.org/browse/WFLY-2031?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-2031:
-------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> container managed persistence context calls that return a StoredProcedureQuery, should return a wrapper if a jta transaction is not active
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-2031
> URL: https://issues.jboss.org/browse/WFLY-2031
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 9.0.0.CR1
>
>
> look at existing use of AbstractEntityManager.detachTypedQueryNonTxInvocation() and also catch queries that need this. For example, createQuery(CriteriaUpdate criteriaUpdate) is in need of this.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)