Any ideas on this?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3917704#3917704
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3917704
---
This SF.net email is spons
I have a jboss5alpha that I checked out in Nov the following code works fine.
Latest jbossAlpha5 checkout...
Name Not Found Exception during injection lookup.
(shortened for brevity)
package org.test.ejb;
...
@Stateless
@Local (value=Test.class) // I have also tried @Remote here
public class Tes
Still having the same problem. Is this a bug?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910159#3910159
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910159
--
I am having the same problem.
I am using @FlushMode(FlushModeType.COMMIT) above each method inside of my
Stateless Session Bean.
Inside one of my methods I am trying create a query and get a result set.
@Entity
@Cache(...TRANSACTIONAL)
public class Rock {
@Id..auto
int id;
}
@Stateles
It is also referred to as "instrumentation".
http://docs.jboss.com/jbcache/1.2.4beta/TreeCacheAop/html/instrumentation.html
Note that TreeCacheAop does not support jdk5 annotations as of yet (that I am
aware of) so you have to use an annotation precompiler.
Example:
1. add a marker to the cla
Quote from the TreeCacheAop documentation:
In addition, it (TreeCache) has additional known limitations:
? User will have to manage the cache specifically. E.g., when an object is
updated, a user will need a corresponding
API to update the cache content.
? If the object size is huge, even a singl
I understand that when I make a call to EntityManager, a call is made to
TreeCache. Hibernate will make a field level change but TreeCache replicates
the entire object across a cluster. I want to turn this thing off completely
and set up TreeCacheAop as my cache that will replicate the the obj
Thanks for the reply.
Maybe I just don't understand how it works. I thought that TreeCache was being
used as the second-level cache which updates nodes on a cluster on a per object
basis instead of a per field basis. If you are using a cluster with a large
number of nodes with a large number o
If not, are there any plans for doing this in the future?
TreeCache performance does not appear to be very robust. I need to replicate a
tree that contains roughly 1,000,000 nodes. I need fine grained updating. Any
ideas?
View the original post :
http://www.jboss.com/index.html?module=bb&
