Yeah unfortunately it's not just the RemoteFactoryBean. To get this to work meant changes to the DefaultXMLBeanFactory, the RemoteProxyBean, the AOPProxyBean, the ProxyFactoryBean, the utility CFCs, and some of the AOP components. This is to support injecting the custom metadata into your Advices (which avoids what Chris was having to do with adding extra attributes directly to his Service CFCs to tell his Logging Advice what to log for example). What this does goes far beyond just handling AJAX for CF8. And it is fully usable by anyone that can use ColdSpring, not just CF8 users. Basically it lets you define custom metadata in the ColdSpring XML that will:
1. let you alter the API for methods generated in a remote proxy bean and 2. let you inject custom metadata about a method or it's arguments into your AOP Advices without having to modify the component being wrapped Does that make it more clear what I'm doing? The CF8 AJAX stuff was only the first use case, but either of these could be used by anyone. Thanks, Brian On 7/12/07, Barney Boisvert <[EMAIL PROTECTED]> wrote:
Yep, that's the gist of it. You don't want to go muck with RemoteFactoryBean, you want to extend it with some bits of useful functionality. CustomMetadataRemoteFactoryBean might seem to be what you want, but I think you really want CF8AjaxRemoteFactoryBean, and in order to implement it you happen to create a CMRFB type that is an abstract superclass also suitable for other customizations. My core point was that the deliverable should be CF8ARFB, not CMRFB. The latter is only useful to people who want to write peers of CF8ARFB (e.g. MooToolsRemoteFactoryBean), while the former is useful to ColdSpring users in general. I definitely agree that CMRFB is a good idea, but the important item is CF8ARFB. That make sense? cheers, barneyb On 7/12/07, Brian Kotek <[EMAIL PROTECTED]> wrote: > Just to be sure we are both on the same page Barney, the tweaks to the > remote factory bean don't have anything to do with AJAX specifically, but > rather with the ability to add "extra" metadata that will be used when the > remote proxy is generated. That metadata could be for anything, it just > happens that the use case I am running into initially is calling the remote > proxy from an AJAX grid. > > Aside from the code that acutally has to loop over the "extra" and "real" > metadata and merge them together, which is fairly complex, the other > modifications are only a few lines of code. Still, maybe what you'd say in > reply to this is extend the RemoteFactoryBean with a > CustomMetadataRemoteFactoryBean? I just want to be sure the > difference between us is just semantic and not that I'm missing something > crucial that you're saying. > > Thanks! > > Brian > -- Barney Boisvert [EMAIL PROTECTED] http://www.barneyb.com/ Got Gmail? I have 100 invites.
