AccessException is a checked exception, but it was thrown from the method that doesn’t declare it in its throws clause (actually – from the aspect intercepting that method). It’s an abnormal condition in Java, so your exception is wrapped with UndeclaredThrowableException, which is unchecked. To get your exception as is, you can either declare it … Read more
I haven’t tried this, so I don’t know if the JVM would restrict something like this, but maybe you could compile code which throws ChuckNorrisException, but at runtime provide a class definition of ChuckNorrisException which does not extend Throwable. UPDATE: It doesn’t work. It generates a verifier error: Exception in thread “main” java.lang.VerifyError: (class: TestThrow, … Read more
For performance, AOP approach certainly has a little overhead against the traditional one. One of the many strengths of AOP is that it allows you to separate your non-business concerns from your business logic. It also helps you in mundane tasks such putting a logging logic in each of your method or place a try-catch … Read more
I don’t think there is built in attribute for ajax, but you can create your own AjaxOnly filter like this: public class AjaxOnlyAttribute : ActionMethodSelectorAttribute { public override bool IsValidForRequest(ControllerContext controllerContext, System.Reflection.MethodInfo methodInfo) { return controllerContext.RequestContext.HttpContext.Request.IsAjaxRequest(); } } And decorate your action methods like this: [AjaxOnly] public ActionResult AjaxMethod() { } See Also: ASP.NET MVC … Read more
Andy Brown is right, it is by design. The reason is that according to the AspectJ manual pointcut designators such as @args, @this, @target, @within, @withincode, and @annotation (or the subset of those available in Spring AOP) are used to match based on the presence of an annotation at runtime. This is why in the … Read more
Acutally the explanation is quite simple if you understand the basic difference between call() and execution() pointcuts: While the former intercepts all callers (i.e. the sources of method calls), the latter intercepts the calls themselves no matter where they originate from. So how can the number of interceptions triggered by both pointcuts differ? If you … Read more
Just to get your head around it: It is the ability to hook events such as: creation of objects, setting of properties, etc, and attach general functions to them, that will be populated with relevant context. Because C# doesn’t have an inbuilt facility for this, you need a framework, like PostSharp, to do ‘bytecode weaving’ … Read more
Yes, it is possible to encapsulate this kind of logging, using the extensibility points built into WCF. There are actually multiple possible approaches. The one I’m describing here adds an IServiceBehavior, which uses a custom IOperationInvoker, and does not require any web.config modifications. There are three parts to this. Create an implementation of IOperationInvoker, which … Read more
Before understanding the Crosscutting Concern, we have to understand the Concern. A Concern is a term that refers to a part of the system divided on the basis of the functionality. There are two types of concerns: The concerns representing single and specific functionality for primary requirements are known as core concerns. OR Primary functionality … Read more
See http://www.sharpcrafters.com/blog/post/PostSharp-Principals-Day-12-e28093-Aspect-Providers-e28093-Part-1.aspx Here is a working example. Applying this aspect to a class will apply the XmlIgnore attribute to any public property that does not already have XmlElement or XmlAttribute applied to it. the trick is using the CustomAttributeIntroductioinAspect that is built in to Postsharp. You just need to instantiate an instance specifying the attribute … Read more