Update build.xml to use Maven deploy plugin 2.6
-----------------------------------------------
Key: JBJCA-571
URL: https://issues.jboss.org/browse/JBJCA-571
Project: IronJacamar
Issue Type: Task
Reporter: Paul Gier
Assignee: Jesper Pedersen
The maven-deploy-plugin version 2.6 will have new options to include the sources and javadoc jars in the "deploy-file" goal. Using these will allow the ironjacamar snapshot deployments to use the normal Maven timestamped snapshots and simplify the upload script.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Improve prepared statement cache
--------------------------------
Key: JBJCA-574
URL: https://issues.jboss.org/browse/JBJCA-574
Project: IronJacamar
Issue Type: Task
Components: JDBC
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Fix For: 1.0.0.Beta7
Create a prepared statement cache implementation based on BoundedConcurrentHashMap.
Set default eviction policy to LIRS.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Support non JTA datasources
---------------------------
Key: JBJCA-588
URL: https://issues.jboss.org/browse/JBJCA-588
Project: IronJacamar
Issue Type: Task
Components: Common, Deployer
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Fix For: 1.0.0.Beta7
Add support for non JTA datasources through <datasource ... jta="false" ...>
--
This message is automatically generated by JIRA.
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
Change dependencies on org.jboss.javaee APIs to org.jboss.spec
---------------------------------------------------------------
Key: JBJCA-564
URL: https://issues.jboss.org/browse/JBJCA-564
Project: IronJacamar
Issue Type: Bug
Reporter: Shelly McGowan
Assignee: Jesper Pedersen
The JBoss Java EE API Specs project has revised the naming convention of the APIs to identify the version of the specification that the APIs align with. IronJacamar has dependencies on the older API project.
<dependency org="org.jboss.javaee" name="jboss-jaspi-api" rev="${version.jboss.jaspi.api}" conf="common,ironjacamar-core-impl,ironjacamar-depchain"/>
<dependency org="org.jboss.javaee" name="jboss-transaction-api" rev="${version.transaction.api}" conf="common,ironjacamar-core-api,ironjacamar-core-impl,ironjacamar-depchain,ironjacamar-deployers-fungal,ironjacamar-spec-api"/>
I'd recommend updating these dependencies to the newer versions being maintained:
https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j...https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j...
--
This message is automatically generated by JIRA.
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
resource-adapters from standalone.xml loose metadata in detyped model
---------------------------------------------------------------------
Key: AS7-958
URL: https://issues.jboss.org/browse/AS7-958
Project: Application Server 7
Issue Type: Bug
Reporter: Stefano Maestri
Assignee: Stefano Maestri
--
This message is automatically generated by JIRA.
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