CDI Extensions not discovered in EAR structure
----------------------------------------------
Key: JBAS-8683
URL: https://jira.jboss.org/browse/JBAS-8683
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.CR1
Reporter: Heiko Braun
Assignee: Marius Bogoevici
A web application contains a CDI extension shipped within WEB-INF/lib. If this web application is packaged in an EAR, the extension will not be discovered and executed.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add utility to generate a virtual jar/zip file input stream from a VFS directory
--------------------------------------------------------------------------------
Key: JBVFS-155
URL: https://jira.jboss.org/jira/browse/JBVFS-155
Project: JBoss VFS
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0.CR5
Reporter: John Bailey
Assignee: John Bailey
Fix For: 3.0.0.CR6
This should allow someone with a VFS directory to get an InputStream that will produce a stream of bytes according to the zip specification. This should only be used by 3rd party frameworks that require an actual input stream to an archive for integration.
--
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
Cannot read from vfs: protocol URL
----------------------------------
Key: JBVFS-147
URL: https://jira.jboss.org/jira/browse/JBVFS-147
Project: JBoss VFS
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0.CR3
Reporter: Thomas Diesler
Assignee: John Bailey
Fix For: 3.0.0.CR4
Cannot read bytes from vfs: protocol URL
URL url = new URL("vfs:/home/tdiesler/svn/jboss-osgi/projects/testing/trunk/target/test-libs/example-simple.jar/");
URLConnection con = (URLConnection)url.openConnection();
InputStream inputStream = con.getInputStream();
int read = inputStream.read();
read is -1
--
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
performance report include profiler data
----------------------------------------
Key: JBJCA-424
URL: https://jira.jboss.org/browse/JBJCA-424
Project: IronJacamar
Issue Type: Task
Components: Performance
Reporter: Jeff Zhang
Assignee: Jeff Zhang
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Performance report with different connection manager strategies
---------------------------------------------------------------
Key: JBJCA-423
URL: https://jira.jboss.org/browse/JBJCA-423
Project: IronJacamar
Issue Type: Task
Components: Performance
Reporter: Jeff Zhang
Assignee: Jeff Zhang
Fix For: 1.0.0.CR1
Ddoing a run with the connection tests with the
-Dironjacamar.mcp=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool
system property then one with
-Dironjacamar.mcp=org.jboss.jca.core.connectionmanager.pool.mcp.ArrayBlockingQueueManagedConnectionPool
so we can see if the numbers are different.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Verify OSGi information in all manifests
----------------------------------------
Key: JBJCA-77
URL: https://jira.jboss.org/jira/browse/JBJCA-77
Project: JBoss JCA
Issue Type: Task
Components: Common, Core, Deployer
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Priority: Blocker
Fix For: 1.0.0.Beta1
Verify that the OSGi information in all the MANIFEST.MF files are correct.
This information needs to be kept in sync from this point on.
--
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
Make it easier to configure boot logging file
---------------------------------------------
Key: JBAS-8044
URL: https://jira.jboss.org/browse/JBAS-8044
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Logging
Affects Versions: 6.0.0.M3
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 6.0.0.M4
As explained in the referenced forum thread, it would be a lot easier to configure JBoss AS boot logging, if the logging.properties file is placed outside the run.jar.
Please refer to the referenced forum thread for more details.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
JBoss MBeans in JConsole no longer works
-----------------------------------------
Key: JBAS-6185
URL: https://jira.jboss.org/jira/browse/JBAS-6185
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX
Affects Versions: JBossAS-5.0.0.CR2
Environment: JBossAS-5 CR2, Sun Java 1.5, Windows 2003
Reporter: jaikiran pai
Assignee: Dimitris Andreadis
Displaying of JBoss MBeans in JConsole as explained here http://www.jboss.org/community/docs/DOC-10521 , no longer works because of the classpath issue. Maybe related to the refactoring of org\jboss\system\server\jmx\* classes into jboss-system-jmx.jar in JBoss-5.
More details about this issue can be found in the linked forum thread.
--
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
BRMS: Cannot easily remove data when creating a test scenario
-------------------------------------------------------------
Key: JBRULES-1699
URL: https://jira.jboss.org/jira/browse/JBRULES-1699
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.0.0.M1
Reporter: Jaroslaw Kijanowski
Assignee: Michael Neale
Fix For: 5.0.0.M2
I create a test scenario and add a fact in the Given section. If I want to remove it, I have to add a field. Then two "minus" signs appear, on for the field and one for the whole fact.
Same for the Expect section and globals.
--
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
Investigate moving AnnotatedElementMetaDataLoader to use jboss-reflect instead of plain reflection
--------------------------------------------------------------------------------------------------
Key: JBMDR-71
URL: https://jira.jboss.org/browse/JBMDR-71
Project: JBoss MetaData Repository
Issue Type: Feature Request
Components: Loader
Reporter: Kabir Khan
Assignee: Kabir Khan
Fix For: JBossMDR-2.2.0.Beta1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira