> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Bill > Burke > Sent: Wednesday, March 26, 2003 11:37 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] AOP versioned ACID objects 1st iteration > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Jeff > > Haynie > > Sent: Wednesday, March 26, 2003 11:07 PM > > To: [EMAIL PROTECTED] > > Subject: RE: [JBoss-dev] AOP versioned ACID objects 1st iteration > > > > > > Bill, > > > > This is fabulous stuff. Good job. > > > > JBoss Remoting is much more fabulous. We need to get the word > out on it... > > > Is there a way we might be able to use the AOP xml to dynamically do > > your example below (as well as the clustered and remoting) for POJOs > > during construction time? In other words, could you not have an > > interceptor on a constructor pointcut that would do this for you and > > dynamically make the class Versionable, Clusterable, Remotable, etc. so > > that the actual instance you receive back has these capabilities > > transparently w/o having to programatically do this? > > > > The advantages of this would be that you could dynamically modify the > > POJO from the XML file without having to do it programmatically (of > > course, you could if you wanted to). That way, we can truly separate > > the business logic (as an example, no flames here) from the > > cross-cutting of concerns such as transactibility, security, remoteness, > > etc. > > > > Looking at the jboss-aop.xml in the testsuite - it looks like you're > > doing this with the Tx Interceptor on the VersionedPOJO - why not just > > create the VersionedPOJO in the same way and insert the Versioned > > Interceptor the same way? Is this possible? > > > > > I totally agree. And yes, a constructor pointcut is the way to go. The > only downside of constructor pointcuts is that reflection bypasses the > interception! Same thing with field interception. The problem is that > unlike methods, you have to modify the bytecode of the calling logic. > > I will write some testcases that put the whole stack together with > constructor pointcuts. >
One more thing...I don't think the constructor pointcut approach makes sense most of the time for Remoting and Clustering. The point being that you don't want to hardcode your remotable object to a specific protocol. Bill ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
