On 30 Nov 2009, at 21:49, Brian Stansberry wrote:
> Be cautious about exposing cache contents (even just keys) via JMX. If
> you do, make it something that people can turn off, without turning off
> the basic JMX interface. Reason is the same as in recent discussions
> about providing access t
Hey,
Doing a svn update of the Hibernate trunk, I realized I probably had
changed the project to be Java5 manually as it reverted to 1.4
(because of some pom.xml change) in IntelliJ.
Talking to Max and Emmanuel at Devoxx I thought trunk was now to be
Java 5? Is this not the case after all, or are p
Guys,
As I know there are some Infinispan guys on this list, I'm sending it
here. It seems that Infinispan maven repo used to contain some
"-tests.jar" artifacts, but they weren't published on Nov 30, causing
Hibernate trunk build to fail (look at cache-infinispan/pom.xml).
Question is: should
I have issues reloading Maven-based projects in IntelliJ as well. I
simply try to minimize the number of times I reload.
Hibernate is *built* with JDK 1.5, but not all the modules are 1.5
compatible.
What "statistics work" discussion? I must have missed that. But for
sure the hibernate-core
We've been doing some improvement to the Hibernate statistics at
Terracotta, when we realized how much the synchronization on it was
impacting throughput in our tests.
That is work we wanted to contribute back to you guys, should
Hibernate Core be target at 1.5. As it seems that's not yet the case,
I guess I have just been waiting until we can actually leverage 1.5
features (ala utilize enums or expose generics/typing). That will not
happen for 3.5.
Now statistics are encapsulated behind a set of interfaces (Statistics
and StatisticsImplementor). We could make this alterable like I did fo
+1
The only big company still using Java 1.4 I know of is planning a
migration right now, skipping directly to 6 (it's an italian bank).
Any new development starting now is using 1.6.
2009/12/1 Steve Ebersole :
> I guess I have just been waiting until we can actually leverage 1.5
> features (ala u
I'm forwarding this to the infinispan-dev list so the Infinispan guys
can fix it. Pinging them on IM as well.
On 12/01/2009 05:55 AM, Juraci Paixao Krohling wrote:
> Guys,
>
> As I know there are some Infinispan guys on this list, I'm sending it
> here. It seems that Infinispan maven repo used to
+1 for java5 and +1 for concurrency improvements that can happen as a
result.
On 12/01/2009 09:59 AM, Steve Ebersole wrote:
> I guess I have just been waiting until we can actually leverage 1.5
> features (ala utilize enums or expose generics/typing). That will not
> happen for 3.5.
>
> Now stat
Well the interfaces themselves depend on other classes that are not
encapsulated behind interfaces: EntityStatistics,
CollectionStatistics, SecondLevelCacheStatistics and QueryStatistics.
These classes are also modified to use JDK 5 java.util.concurrent
constructs... Choosing what impl. to use at r
10 matches
Mail list logo
