« Return to Thread: Services in Spring.NET with AOP Proxies failing after upgrading from 1.0.0.13 to 1.0.0.15

Services in Spring.NET with AOP Proxies failing after upgrading from 1.0.0.13 to 1.0.0.15

by Vinnie Luther :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View in Thread

Some parts of this message have been removed. Learn more about Nabble's security policy.

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


_______________________________________________
fluorine mailing list
fluorine@...
http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine.thesilentgroup.com

 « Return to Thread: Services in Spring.NET with AOP Proxies failing after upgrading from 1.0.0.13 to 1.0.0.15