[
https://issues.apache.org/jira/browse/BEEHIVE-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlin Rogers resolved BEEHIVE-1210.
------------------------------------
Resolution: Fixed
Change submitted with SVN revision 603377.
> Add an option to the Beehive AptTask to allow a user to define an AP factory
> or factory path to override the usual discovery process
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-1210
> URL: https://issues.apache.org/jira/browse/BEEHIVE-1210
> Project: Beehive
> Issue Type: Improvement
> Components: Controls, NetUI
> Affects Versions: 1.0, 1.0.1, 1.0.2
> Reporter: Carlin Rogers
> Assignee: Carlin Rogers
> Fix For: V.Next
>
>
> Extend the AptTask to allow a user to define apt specific options for the
> name of an annotation processor (AP) factory to use or the factory path for
> finding the AP factories. This allows apt to bypass the default discovery
> process or specify where to find AP factories.
> This can help resolve build issues users may experience when multiple
> annotation processors conflict. For example,...
> A project may contain Beehive annotations as well as JAX-RPC 1.1 Web Services
> annotations.
> However, starting with JDK1.6, JDK bundles the JAX-WS 2.0 AP in its tool jar.
> JAX-RPC and JAX-WS use the same JSR 181 annotations but the JAX-WS 2.0 AP
> doesn't support the earlier JAX-RPC use of the RPC/ENCODED soapbinding
> annotation on an endpoint. A user running the build through the Beehive
> AptTask and using Java 6, would see APT fail on JAX-RPC 1.1 services thinking
> they are invalid JAX-WS services.
> This improvement would allow a user to define the AP factory to use.
> Note that for the above scenario, unfortunately, using the -factorypath
> option would not disable the built-in annotation processor because tools.jar
> is always in APT's class path. In this case, exposing the option to use a
> specific factory
> solves the problem. There can only be one factory name when invoking APT, so
> a user of this task and the factory name option may need to pass a wrapper
> factory that is an aggregated annotation processor factory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
