I have a design question in the fight about domain driven design, the anemic
domain model, and the way EJB/JPA force us to do things.
Consider a web-mail application which is built using JPA for persistence and
EJB for the services layer. Let's say we have a service method in our EJB like
this:
Don't read too much into my specific example. I'm trying to illustrate a point.
My point is that EJB and JPA force us into a model where our domain objects
cannot rely on any container provided services. I fully understand the
reasoning behind it.
However, I'm asking for ideas on elegant ways
I have a three-part question:
1) Is there a way to propogate an identity other than the username that was
specified during login? For example, using the DatabaseServerLoginModule, I
want to authenticate the user with a username/password but return the user's
id, and not username, when ejbContex
Hello,
I am having trouble making JBoss AOP (standalone) use my custom class loader.
To keep the example simple, let's say I have a ClassLoader called
CustomClassLoader which loads classes from a source other than the class path.
Now, assume we have these two classes
class A {
B someVaria
Turns out this is actually a Javassist "feature". This fixed my problem:
import javassist.ClassPool;
import javassist.LoaderClassPath;
ClassPool cp = ClassPool.getDefault();
cp.insertClassPath(new LoaderClassPath(getClassLoader()));
Where getClassLoader() returns an instance of your own custom
Kabir,
Did you get an updated version released with this fix? I don't see it anywhere.
Thanks,
Tolga
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002484#4002484
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002484
