So are you suggesting I modify the main ejb3-interceptors-aop.xml or can I
include a ejb3-interceptors-aop.xml like file in a deployable unit (ie: ear)
that contains information on how to invoke my new aspects relative to the ejb3
standard ones? I have been looking at the aspectdomain test
Ok, I looked at the spec again, and it says it intercepts *business* methods
(which are public, among other things I think). However, if I make the
internal methods public, it still does not intercept them when they are called
internally.
View the original post :
PeterJ wrote : Interceptors only work if you call the method via a bean
reference (i.e., one you got from JNDI). By calling the method via a bean
reference, the server has a chance to determine that an interceptor exists and
can deflect the method call to the interceptor. But, within the
I have read the installation and deployment documentation and deploying an
aspect to JBossAS 4.0.x seems straightforward. However, I want to create an
interceptor that is invoked just *before* the EJB3 transaction interceptors.
Since the EJB3 interceptors are defined in some other scope in
OK, I'll check this out. Thanks for the reply!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3956436#3956436
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3956436
On 4.0.4.GA (w/ EJB RC7), when I get a deadlock, I end up with the following
exception hierarchy:
| javax.ejb.EJBTransactionRolledbackException
| javax.ejb.EJBException
| javax.persistence.PersistenceException
| org.hibernate.exception.LockAcquisitionException: could not insert: ...
|
I am using JBoss 4.0.4.GA (w/ EJB RC7).
When I define interceptors (ie: @Interceptors(MyInterceptor.class)) on a class,
the @AroundInvoke method is only called when a method is called from outside
the bean . If a method is called from within the bean the @AroundInvoke method
is not fired.
I am also looking for a solution to this problem.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3944660#3944660
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3944660
---
After upgrading from 4.0.3SP1 = jboss-4.0.4.GA, I now have the following
problem when deploying:
org.hibernate.AnnotationException: Use of @OneToMany or @ManyToMany targeting
an unmapped class ...
The situation is I have a @OneToMany annotation targeting an @Embeddable class.
This used to
Sorry, this is really a hibernate issue. I have moved this post here:
http://forum.hibernate.org/viewtopic.php?t=959542
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3944084#3944084
Reply to the post :
Consider the following example:
@Entity
@Table
(
name=foobar,
[EMAIL PROTECTED](columnNames={natural_key})}
)
class Foobar
{
@Id(generate = GeneratorType.AUTO)
@Column(name = primary_key)
long primary_key;
@Column(name = natural_key
String natural_key;
public
Consider the following example:
If I have a Shape class which has subclasses called Square, Circle, etc. with
separate data members, I would like to treat this hierarchy as @Embeddable
since I don't care about database identity, just equality. However, it seems
that I cannot embed the Shape
12 matches
Mail list logo
