[JBoss JIRA] Created: (LOGTOOL-11) Refactor into Core Generation and Specific Annotation Processing Modules
by Ken Finnigan (JIRA)
Refactor into Core Generation and Specific Annotation Processing Modules
------------------------------------------------------------------------
Key: LOGTOOL-11
URL: https://issues.jboss.org/browse/LOGTOOL-11
Project: Log Tool
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.Beta3
Reporter: Ken Finnigan
Assignee: David Lloyd
JBoss Solder/Seam would like to use their own annotations for generating message classes instead of those found within JBoss Logging, as recommended by David Lloyd.
At present the Annotation processor in Logging Tools specifically references the JBoss Logging annotations by package and imports them to use in generating the classes.
What we'd like is to create a core processing module that has common functionality that is agnostic of whatever annotations need to be processed, or what methods those annotations may have, and then modules bolted on top of that for specific JBoss Logging annotation processing.
This then allows the creation of a Solder/Seam specific annotation processor module that utilizes the core, without having to fork the entire project to achieve it.
Have discussed this with both James and David, and James is currently working on a prototype.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBJCA-480) Add jmx monitoring to jvm.
by Jeremy Whiting (JIRA)
Add jmx monitoring to jvm.
--------------------------
Key: JBJCA-480
URL: https://jira.jboss.org/browse/JBJCA-480
Project: IronJacamar
Issue Type: Task
Components: Performance
Environment: All environments.
Reporter: Jeremy Whiting
Assignee: Jesper Pedersen
Priority: Minor
This contribution changes the jmeter benchmarking to provide JMX monitoring.
Also the in memory database used is changed to HSQLDB due to it's ability to shutdown a standalone database.
The performance guide documentation has also been updated with instructions to control jvm processes.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBNAME-52) Auto discovery results not cached
by Dennis Reed (JIRA)
Auto discovery results not cached
---------------------------------
Key: JBNAME-52
URL: https://issues.jboss.org/browse/JBNAME-52
Project: JBoss Naming
Issue Type: Bug
Components: jnpserver
Affects Versions: 5.0.3.GA
Reporter: Dennis Reed
When using auto-discovery to find a server, the results are not cached.
Every new InitialContext sends a multicast discovery request and waits for the results.
This can cause a performance problem when lots of contexts are created.
org.jnp.interfaces.NamingContext has the plumbing already implemented for caching the results.
It just needs a call to setHANamingServerForPartition in discoverServer to cache the discovery results,
and calls to removeHANamingServerForPartition to invalidate the cache entry at the appropriate places.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBCL-94) Spaces in URLs returned by getResource() should in vfszip: handler
by Ondrej Medek (JIRA)
Spaces in URLs returned by getResource() should in vfszip: handler
------------------------------------------------------------------
Key: JBCL-94
URL: https://jira.jboss.org/jira/browse/JBCL-94
Project: JBoss ClassLoader
Issue Type: Bug
Components: ClassLoader
Environment: JBoss AS 5.0.1, WinXP, JDK 1.6.0u12
Reporter: Ondrej Medek
Priority: Minor
Hi,
I have an EAR deployed as directory (not as JAR). Inside I have one service bean and a config directory. I have tried to deploy config directory as a plain directory and packed in the JAR. I have spotted different behaviour of handling spaces in the resource URLS returned by org.jboss.classloader.spi.base.BaseClassLoader when accessing the config directory. My service bean reads config direcory by:
this.getClass().getClassLoader().getResource("conf/")
I get the URL: vfsfile:/C:/Program%20Files/JBoss/jboss-5.0.1.GA/server/default/deploy/prinsee-ear.ear/conf/
(Space is '%20')
however, when I put the resource in the JAR and access it by:
this.getClass().getClassLoader().getResource("prinsee-client.jar/conf")
I get the URL: vfszip:/C:/Program Files/JBoss/jboss-5.0.1.GA/server/default/deploy/prinsee-ear.ear/prinsee-client.jar/conf/
(Space is ' ').
I think, the behaviour of vfszip: handler is wrong. The space should be always '%20'.
Cheers
andy
--
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
15 years, 4 months