> For the complete documentation index, see [llms.txt](https://wirebox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wirebox.ortusbooks.com/5/aspect-oriented-programming/aop-intro/create-your-aspect/methodinvocation-useful-methods.md).

# MethodInvocation Useful Methods

Here are a list of the most useful methods in this CFC

* `getMethod()` : Get the name of the method (join point) that we are proxying and is being executed
* `getMethodMetadata()` : Get the metadata structure of the current executing method. A great way to check for annotations on the method (join point)
* `getArgs()` : Get the argument collection of the method call
* `setArgs()` : Override the argument collection of the method call
* `getTarget()` : Get the object reference to the target object
* `getTargetName()` : Get the name of the target object
* `getTargetMapping()` : Get the object mapping of the proxied object. Great for getting metadata information about the object, extra attributes, etc.
* `proceed()` : This is where the magic happens, this method tells WireBox AOP to continue to execute the target method. If you do not call this in your aspect, then the proxyied method will NOT be executed.

The last method is the most important one as it tells WireBox AOP to continue executing either more aspects, the proxyed method or nothing at all.

![](https://3919558135-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LA-UVvsc-e1GVkiaPQ-%2F-LA-Ud03e_n2SeqLC9Ls%2F-LA-Upf6yduaTrjYycIj%2FWireBoxAOP-MethodProceed.jpg?generation=1523647997667863\&alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wirebox.ortusbooks.com/5/aspect-oriented-programming/aop-intro/create-your-aspect/methodinvocation-useful-methods.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.