[
https://jira.jboss.org/browse/WELDX-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557708#action_12557708
]
Pete Muir commented on WELDX-178:
---------------------------------
There is no need for this to be visible to the user, it can simply be an
internal optimization.
> Add isMetadataChanged() accessor to AnnotatedTypeBuilder
> --------------------------------------------------------
>
> Key: WELDX-178
> URL: https://jira.jboss.org/browse/WELDX-178
> Project: Weld Extensions
> Issue Type: Feature Request
> Affects Versions: 1.0.0.Beta1
> Reporter: Dan Allen
> Priority: Minor
> Fix For: 1.0.0.Beta2
>
>
> As an optimization, it makes sense to only create the AnnotatedType and
> assign it to ProcessAnnotatedType if the metadata has changed in anyway.
> Otherwise, you are wrapping the type just for the sake of wrapping it.
> Therefore, I propose that any change to the state of the annotated type be
> tracked by a changed flag that is accessible by calling the
> AnnotatedTypeBuilder#isMetadataChanged() (or similarly named) method. It
> would be used as follows:
> AnnotatedTypeBuilder b =
> AnnotatedTypeBuilder.readFromType(event.getAnnotatedType(), true);
> // do extension logic
> if (b.isMetadataChanged())
> {
> event.setAnnotatedType(b.create());
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
