Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6870413
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T03:40:51+00:00 2026-05-27T03:40:51+00:00

I have a working AspectJ Weaver pattern for matching all the setters inside a

  • 0

I have a “working” AspectJ Weaver pattern for matching all the setters inside a certain type (Item):

public pointcut setter(Item item) :
    target(item)
    && execution(void Item+.set*(*));

It works just swell for all the potential setters, but it also matches methods with names like “setup” that takes one argument.

So my solution right now is to check in the method that intercepts all setters if the 4th character is lowercase or not (based on thisJoinPoint.getSignature().getName()), and based on that not continue with the code.

But is there a better way to exclude all methods that have a lowercase character after “set”? As far as I know regular expressions are not part of AspectJ patterns, right?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T03:40:52+00:00Added an answer on May 27, 2026 at 3:40 am

    I don’t know if this is less ugly, but you could introduce an annotation @NoSetter and use this in another pointcut noSetterto exclude the methods like setup(...) where you do not want the aspect applied:

    public pointcut noSetter(Item item) :
    target(item)
    && execution(void @NoSetter Item+.*(..));
    

    Modify the pointcut setter as follows:

    public pointcut setter(Item item) :
    target(item)
    && execution(void Item+.set*(*))
    && !noSetter();
    

    I’ve used this approach in a situation where setter methods needed to fire a certain event. We could not generate the code and doing this by hand was too tedious and error-prone. Also, on some setters the event was to be explicitly not fired at all.

    [The above syntax is untested, don’t have an IDE right now to verify this]

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have been working on a web services related project for about the last
I have been working with Visual Studio (WinForm and ASP.NET applications using mostly C#)
I have been working with a string[] array in C# that gets returned from
We have been working with CVS for years, and frequently find it useful to
I have been working on some legacy C++ code that uses variable length structures
I have a working copy of my project, checked out using Subversion 1.5.1. When
I have a working LINQ to SQL model. I want to be able to
I have this working definition: IDENTIFIER [a-zA-Z][a-zA-Z0-9]* I don't want to keep repeating the
I have been working with relational databases for sometime, but it only recently occurred
I have been working as a native C++ programmer for last few years. Now

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.