Thanks Jeremy. I applied the patches and there are some more errors
down the line. I am looking into resolving them and will submit a
patch once I get to that point. Hopefully this weekend.


On Mon, May 17, 2010 at 11:49 PM, Jeremy Thomerson
<> wrote:
> I'm not a maintainer on those projects so I defer on applying the following
> patches.  However, I think that it is a bug.  If it is a bug, it will also
> require a change in the annotations project in WicketStuff.  I have created
> a patch for each.  Could you test it and see if it works?  If so, I'll go
> ahead and commit it (unless one of the maintainers objects here first).
> Patch for annotations:
> Patch for merged-resources:
> File attachments to the list will be stripped.
> --
> Jeremy Thomerson
> On Mon, May 17, 2010 at 9:43 PM, Ryan Crumley <> wrote:
>> All,
>> [If there is a wicketstuff specific mailing list please let me know
>> and I will be happy to post there ( is down so its
>> difficult to find information).]
>> I am using wicketstuff-merged-resources (3.1-SNAPSHOT) with
>> wicketstuff-annotation (1.1) and I have found a potential issue with
>> annotation detection. My page hierarchy looks something like this:
>> public abstract class BasePage extends WebPage { ... }
>> public class HomePage extends BasePage { ... }
>> I would like to add @JsContribution to BasePage however the resources
>> are only included if the concrete page (in this example: 'HomePage')
>> also has resource annotations. Removing @JsContribution from HomePage
>> results in all resources from BasePage also disappearing. Is this a
>> known bug? Am I using the framework incorrectly?
>> Thanks in advance for any guidance.
>> Ryan
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to