You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@beehive.apache.org by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org> on 2005/06/03 19:47:54 UTC

[jira] Closed: (BEEHIVE-14) apt classpath problem

     [ http://issues.apache.org/jira/browse/BEEHIVE-14?page=all ]
     
Jeremiah Johnson closed BEEHIVE-14:
-----------------------------------

    Assign To: Jeremiah Johnson  (was: Michael Merz)

Verified in SVN 177983.

The DropInDeploymentHandler went away with SVN 109594 and none of the
other handlers get the object model directly from APT.

The build-webservices macro was added to beehive-tools.xml in SVN
161377; this calls APT during build-time to generate the necessary
artifacts for run-time.

While the bug wasn't resolved by changes to the APT, the changes in WSM
deployment do sufficiently resolve the bug.

> apt classpath problem
> ---------------------
>
>          Key: BEEHIVE-14
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-14
>      Project: Beehive
>         Type: Bug
>   Components: Web Services (181)
>     Versions: TBD
>     Reporter: Michael Merz
>     Assignee: Jeremiah Johnson
>      Fix For: V1Alpha

>
> The object model created by apt is stored in a class that had been loaded with the wrong classloader and is therefore not accessible from the caller (e.g. DropInDeploymentHandler).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira