[ https://jira.jboss.org/jira/browse/JBPORTAL-2101?page=com.atlassian.jira.... ]
Viliam Rockai commented on JBPORTAL-2101:
-----------------------------------------
i'm wondering about strenght of the test. i hope it is a good thing to test during the user creation process
whether the defaultly assigned group is "Users"
in confirmation window, assert all accesible data about newly created user
and actually for sure assert "User created" at the end
but i'm not quite sure about defaultly assigned groups
> identity admin ui testing
> -------------------------
>
> Key: JBPORTAL-2101
> URL: https://jira.jboss.org/jira/browse/JBPORTAL-2101
> Project: JBoss Portal
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Prabhat Jha
> Assignee: Viliam Rockai
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Deleting and readding node in tx causes modification event
----------------------------------------------------------
Key: JBCACHE-1396
URL: https://jira.jboss.org/jira/browse/JBCACHE-1396
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Replication
Affects Versions: 2.1.1.GA
Reporter: Krzysztof Sobolewski
Assignee: Manik Surtani
When a node is being added, then removed and added again, all in the same transaction, for the last operation a NODE_MODIFIED event is sent, instead of (I think) expected NODE_CREATED.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Specify the adapter on the class being adapted
----------------------------------------------
Key: JBXB-125
URL: http://jira.jboss.com/jira/browse/JBXB-125
Project: JBoss XML Binding (JBossXB)
Issue Type: Feature Request
Affects Versions: JBossXB-2.0.0.CR6
Reporter: Ales Justin
Assigned To: Alexey Loubyansky
Fix For: JBossXB-2.0.0.CR7
We should really be able to specify the adapter on the class being adapted
rather than having to repeat it on every top level package.
e.g.
@JBossXMLAdapter(ConstrollerStateXMLAdapter.class)
public class ControllerState {}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Element values should be trimmed
--------------------------------
Key: JBMETA-76
URL: http://jira.jboss.com/jira/browse/JBMETA-76
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.Beta28
Reporter: Remy Maucherat
Assigned To: Alexey Loubyansky
Priority: Critical
At least for web.xml parsing of web metadata, element values are apparently not trimmed.
Something like:
<servlet-class>
org.apache.catalina.servlets.DefaultServlet
</servlet-class>
causes a classloading failure, while <servlet-class>org.apache.catalina.servlets.DefaultServlet</servlet-class> works.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Investigate whether create() and destroy() public lifecycle methods are needed or whether start() and stop() alone will be sufficient.
--------------------------------------------------------------------------------------------------------------------------------------
Key: JBCACHE-1369
URL: http://jira.jboss.com/jira/browse/JBCACHE-1369
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Manik Surtani
Assigned To: Manik Surtani
Fix For: 3.0.0
See forum thread
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/jira/browse/JBMICROCONT-323?page=com.atlassian.jir... ]
Ales Justin resolved JBMICROCONT-323.
-------------------------------------
Resolution: Done
Adding JDK's Executor to AbstractController.
ScopedController uses its own if exists, else delegates to parent.
> Add ExecutionEnvironmet interface to Controller
> -----------------------------------------------
>
> Key: JBMICROCONT-323
> URL: https://jira.jboss.org/jira/browse/JBMICROCONT-323
> Project: JBoss MicroContainer
> Issue Type: Task
> Components: Dependency
> Affects Versions: JBossMC.2.0.0.Beta16
> Reporter: Ales Justin
> Assignee: Ales Justin
> Fix For: JBossMC.2.0.0.CR1
>
>
> With concurrency deployment issue JBMICROCONT-265,
> users should be able to use their own execution environment
> to trigger/start new threads when deployment should be dealt in parallel.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Annotation processors need to merge injection targets
-----------------------------------------------------
Key: JBMETA-88
URL: https://jira.jboss.org/jira/browse/JBMETA-88
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.Beta34
Reporter: Emanuel Muckenhuber
Assignee: Emanuel Muckenhuber
Fix For: 1.0.0.CR1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/jira/browse/JBAS-3207?page=com.atlassian.jira.plug... ]
Jesper Pedersen updated JBAS-3207:
----------------------------------
Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)])
Priority: Major (was: Critical)
> Unification of Timer implementation for JBossAS
> -----------------------------------------------
>
> Key: JBAS-3207
> URL: https://jira.jboss.org/jira/browse/JBAS-3207
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JCA service
> Affects Versions: No Release
> Reporter: Weston Price
> Assignee: Jesper Pedersen
> Fix For: JBossAS-5.1.0.CR1
>
>
> * Unification of timers into a Quartz based implementation. Timer uses to unify include:
> ** jPBM timers
> ** EJB/EJB3 timers
> ** jmx timers
> ** jmx timer service
> ** org.jboss.util.* custom timers
> * Have a Quartz rar providing a message inflow adaptor that delivers a Quartz event.
> * Expose the Quartz APIs as Seam components
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira