Lucene Directory
by Sanne Grinovero
Hi,
I'm polishing some stuff for Lucene Directory, it should be ready this
WE; I've heard about a release soon, should I wait for committing
this, or do I have to hurry up?
Sanne
16 years
multiple cloud persistence
by Adrian Cole
Hi, guys.
Currently, the s3 cachestore does what it says it does: persist to S3 ;)
That said, the next beta of jclouds supports 5+ storage clouds:
s3, rackspace, cloudlayer, nirvanix, microsoft azure, and anyone running
mezeo v2.
Is we interested in adding multi-cloud support instead of or in addition to
s3?
What do you think?
-Adrian
jclouds
16 years
[ISPN-134] Creating @Jopr* annotations or extending @Managed* ones?
by Galder Zamarreno
Hi,
Heiko, this is FYI too:
Re: https://jira.jboss.org/jira/browse/ISPN-134
I see different ways of doing this. Let's take the DefaultCacheManager
as example. It has 4 @ManagedAttribute methods:
getDefinedCacheCount()
getCreatedCacheCount()
getVersion()
getDefinedCacheNames()
Now, at the jopr level, even these 4 would be treated differently. First
two are measurement metrics, the two below are trait metrics. So, on top
of jopr adding new fields, there's the issue that not all
@ManagedAttribute map to the same thing on the jopr side.
So, my suggestion would be to have some jopr specific annotations that
allow us to differentiate between different jopr types (i.e.
@JoprMetric(dataType="measurement"), @JoprMetric(dataType="trait")) and
where we can add any extra information required by jopr, i.e.
displayName...etc.
I think using this annotations would be cleaner than extending @Managed*
ones. Also, such @Jopr* or annotations would need to live in core/
Heiko, does Jopr have annotations like this already?
Thoughts?
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
16 years
