This one time, at band camp, Harkness, David said:
HD>Yes, I believe that if you fully-qualify the classes *where they are
HD>used* you will avoid the problem. Clearly, when importing a class you
HD>must FQ it, but this allows you to leave off the package when using it
HD>in code. Try putting in t
Bruce Snyder wrote:
> This one time, at band camp, Harkness, David said:
>
>> Bruce Snyder wrote:
>>> I've been compiling some SLSBs that contain XDoclet tags without
>>> error for a while now. Just the other day, someone added two MDBs
>>> to the build that contain XDoclet tags and suddenly the b
This one time, at band camp, Harkness, David said:
HD>[EMAIL PROTECTED] wrote:
HD>> I've been compiling some SLSBs that contain XDoclet tags
HD>> without error for a while now. Just the other day, someone
HD>> added two MDBs to the build that contain XDoclet tags and
HD>> suddenly the build is rep
[EMAIL PROTECTED] wrote:
> I've been compiling some SLSBs that contain XDoclet tags
> without error for a while now. Just the other day, someone
> added two MDBs to the build that contain XDoclet tags and
> suddenly the build is reporting the following error:
>
> [ejbdoclet] INFO:Some classes
I've been compiling some SLSBs that contain XDoclet tags without error
for a while now. Just the other day, someone added two MDBs to the
build that contain XDoclet tags and suddenly the build is reporting the
following error:
[ejbdoclet] Running
[ejbdoclet] Generating Remote interface for ...
[e
