Re: Services in Spring.NET with AOP Proxies failingafterupgrading from 1.0.0.13 to 1.0.0.15

Zoli,

I found the issue.  I am using subclassed AOP proxies, so my [RemoteService] attributes were on a superclass of the AOP proxy class.  I found a solution by changing

line 496 in TypeHelper.cs to use true on the GetAttribute call.

                Attribute attribute = ReflectionUtils.GetAttribute(typeof(RemotingServiceAttribute), type, true);

That may not be secure for other people, I don’t know, but it solved my problem.

Thanks,

Vinnie

Hi Vinnie,

can you send to support@ some details about your setup so I can try to reproduce the problem?

thanks,

Zoli

From: fluorine-bounces@... [mailto:fluorine-bounces@...] On Behalf Of Vinnie Luther
Sent: Thursday, April 16, 2009 8:07 PM
To: fluorine@...
Subject: [Fluorine] Services in Spring.NET with AOP Proxies failing afterupgrading from 1.0.0.13 to 1.0.0.15

Hey,

I’d like to upgrade to FluorineFx 1.0.0.15 or .16 in SVN, but it seems there has been a change that prevents it from calling services using the spring.net factory that have AOP proxies.

I’m getting this error in .15, but it works fine if I replace the .dll with .13:

2009-04-16 13:02:42,250 [4] ERROR FluorineFx.Messaging.MessageBroker - Failed to locate the requested  type DecoratorAopProxy_aa88094b4de5491aa2c600ea741135cd

FluorineFx.Messaging.MessageException: Failed to locate the requested  type DecoratorAopProxy_aa88094b4de5491aa2c600ea741135cd ---> System.TypeLoadException: Failed to locate the requested  type DecoratorAopProxy_aa88094b4de5491aa2c600ea741135cd

   --- End of inner exception stack trace ---

   at FluorineFx.Remoting.RemotingAdapter.Invoke(IMessage message)

   at FluorineFx.Messaging.Services.RemotingService.ServiceMessage(IMessage message)

   at FluorineFx.Messaging.MessageBroker.RouteMessage(IMessage message, IEndpoint endpoint)

Vinnie