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

Posted to dev@beehive.apache.org by "Michael Merz (JIRA)" <be...@incubator.apache.org> on 2004/11/02 18:49:35 UTC

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

     [ http://nagoya.apache.org/jira/browse/BEEHIVE-14?page=history ]
     
Michael Merz resolved BEEHIVE-14:
---------------------------------

     Resolution: Fixed
    Fix Version: V1Alpha
                     (was: TBD)

The deployment model has changed. jws-files are now pre-built in an explicit build step -- not on demand at runtime. apt is used in the build files to generate any required artifacts. As a side effect this bug is resolved because apt is no longer called programmatucally.

> apt classpath problem
> ---------------------
>
>          Key: BEEHIVE-14
>          URL: http://nagoya.apache.org/jira/browse/BEEHIVE-14
>      Project: Beehive
>         Type: Bug
>   Components: Web Services (181)
>     Versions: TBD
>     Reporter: Michael Merz
>     Assignee: Michael Merz
>      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://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira