Not having looked at the actual implementation for injection, I'd guess that
| @EJB
| private SameEJB same;
|
I would expect that it doesn't give you a self referencing proxy.
It probably at best give an error that it's not legal
At worst give you infinite recursion as it would be creatin
Sorry to be bumping my post here, but I am really curious if this is even
supposed to work.
We can't seem to figure out a way to select the parent without also selecting
the children. Which works fine until the tables get really big.
View the original post :
http://www.jboss.com/index.html?mo
I didn't even realize you could get the proxy object from the context, might
have been a better solution.
The @Tx stuff works, and I've been using the JBoss AOP stuff for a few years in
production, so I don't really worry about that (aside from the 1/3 increase in
deploy time, but that's no b
we found that the TransactionAttribute annotation gets ignored when calling
other methods in from a session bean.
ie:
| public void doSomething() { // this is the method called from the client
| doSomethingInNewTx();
| }
|
| @TransactionAttribute(TransactionAttributeType.REQUIRES
Is it possible to get OneToOne relationships to be lazy initialized?
Our "main" entity has 12 or so OneToOne relationships that seem to get selected
every time.
We're doing a simbol "from MainClass" query on the entity manager, but when I
enable hibernate sql tracing, i see all the related tabl
not sure how to *really* fix it, but at a minimum you can get around this by
putting your code in a directory that doesn't contain spaces
I'd guess, given the stack, that the RMI class loader is having "issues" with a
path containing spaces.
View the original post :
http://www.jboss.com/ind
Just dawned on me, is this supposed to actually work with vanilla EJB3
persistence?
We've been using the workaround so long that I forgot we used hibernate
specific annotations.
Also, is there a test case / example out there that does this? Just thought I
could stop pestering everyone if ther
Thanks for the quick reply. It still doesn't seem to work though.
Now the problem is on the other side of the relationship
It seems as though the @OneToOne marked parent field is not considered when
looking up the @OneToOne(mappedBy="") on the child
I've looked over your response several times
Small followup:
In case it didn't make sense for what I was trying to do.
I want child table's primary key to be a foreign key to the parent, and use
entity accessors rather than having the child only have "Id".
meaning:
parent == parent.getChild().getParent()
Rather than the 'normal'(per the
Hi Folks,
First off, I'm using JBoss 4.0.4-GA (upgrading from 4.0.3SP1 + EJB3 RC5)
It appears that the GenericGenerator / PrimaryKeyJoinColumn workaround no
longer works.
This was a work around I found on these message boards (and has been working
for us in production for a while).
Basic ide
I'd be interested to know if there's a fancy way as well, but what we have to
do is:
em.createQuery("from Pets p where p.type = 'dog'")
or whatever is equivilent (selecing on the descriminator specifically in your
case I'd expect)
View the original post :
http://www.jboss.com/index.html?mod
Our workaround is to switch to LockModeType.READ
which translates to LockMode.UPGRADE (which works)
I suppose the LockModeType.WRITE -> LockMode.FORCE thing is just a plain old
bug? (since hibernate 3.1 AND 3.2CR1 both don't actually support FORCE, same
issue in the static map)
View the origi
Looking at fisheye (current rev, not sure which rev was RC6):
Looks like AbstractEntityManager::lock(entity,LockModeType)
calls getLockMode, which translates LockModeType.WRITE -> LockMode.FORCE
But AbstractEntityPersister, who takes the Hib LockMode instance, has a static
map of registered type
We just upgraded to EJB3 RC6 and are now getting NPEs in
org.hibernate.persister.entity.AbstractEntityPersister.lock(AbstractEntityPersister.java:1282)
This occurs while calling em.lock(obj)
adding debugging to our code, we have verified that "obj" is not null, so we're
not sure whats going on
You could also just download the src distro and compile yourself.
EJB3 gets included in the build/output/jboss-xxx directory.
Just zip that up and you are good to go.
We actually check in the result of the build so we can upgrade EJB3 engines
easily and just check out / update the jboss deploymen
Thanks for the reply guys,
I hadn't realized that SLSB was single threaded. So, more instances get
created with concurrent requests? Or all requests get processed serially?
I ask because I made the (apprearantly incorrect) assumption that SLSB was
accessed concurrently and implemented our sit
Hi folks,
Just wondering, if I use EntityManager injection via:
@PersistenceContext(unitName="blah')
protected EntityManager em;
Is it safe to do from SLSBs or MDBs?
It appears that MDBs are 1 instance per concurrent message processor, so I'd
guess those are safe.
SLSB on the other hand, wasn
tpedone, could you possibly post the relevant tags you put on your classes to
get this to work?
Spent the last 5 hours spinning my wheels on getting true OneToOnes working
(where child pk = fk to parent pk).
After trying combinations of @GenericGenerator(foreign) placed all around ( I
can't f
Thanks for the info Kabir.
Are you sure on the 1.3.5 in RC4 thing? Many class names are different in the
Annotation jar.
Difference looks like there were a ton of anonymous inners that got changed to
named (maybe static) inners.
That and many of the files have different sizes, but I suppose
Hi Folks,
I'm kind of stumped on why I'm getting a cartesian product in my query.
The query is:
from Order o where trunc(o.activity.activityDate) = trunc(sysdate) order by id
In effect, I'm trying to get:
select o.* from ORDER o where o.ORDER_ID in ( select a.ORDER_ID from ACTIVITY a
where trun
In case anyone was wondering.
I stold pluggable-instrumentor.jar from the JBAOP 1.3.5 release and used it on
my JBAS 4.0.3sp1 + EJB3-PFD 4 installation and it works like a charm
my mbeans with
@Tx
public void doStuff(){ }
Now participate in transactions
View the original post :
http://www.j
Hi folks,
When I upgraded to the EJB3 PFD release on my JB 4.0.3sp1 installation it
required replacement of the JBossAOP deployer/libraries
I'd like to turn on load time weaving to get transaction injection in to
ServiceMBean objects we have (@Service type services wont work because we need
to
I have two tables
User (pkcol user_id(Long))
UserDetail (pkcol user_id(Long), also foreign key to User)
I read in the Hibernate Annotation Reference section 2.2.5.1 (OneToOne)
section a piece saying that the slave table should have the id itself mapped as
the raw value (ie: mapped as Long, rather
I don't suppose you've ever solved this?
I posted a message (probably in the wrong forum) on the ejb3 forum about my
messages seeming to be rolled back on undeploy.
Closer look seems to indicate that the sonic xa connection is never actually
enrolled with the TX. the TM mbean shows that transa
24 matches
Mail list logo