A wise old hermit known only as Ara Abrahamian <[EMAIL PROTECTED]> once said:
> May I release v1.1.1 next week? ... > Andrew, is the HP app server stuff ready? Almost, there's just a couple of things left to do. First, I've got to go through all the @bluestone:foo tags I used and change various ones to bluestone-foo parameters on the standard @ejb: tags where appropriate. Second, I've got to sort out this colocated/distributed ejb refs stuff. The person that originally asked about it on the forums (and the only one to send me any feedback) only uses colocated anyway, so I may just ignore the distributed option for now so I can get it checked in sooner. However, I'm a bit puzzled by what's going on with the existing ejb-ref/ejb-external-ref stuff (if I'm going to add the bluestone bits as parameters to those, I figure it's a good idea to know what they're doing to start with!) What exactly is the difference between those two anyway? And what's going on in that <ejb-ref> stuff in the DD (in ejb-body.j)? Part of the ejb-external-ref bit looks for parameters on ejb-ref tags!!?, and why are the ejb-ref bits split either side of the ejb-external-ref bit, depending on whether there's a view-type? Wouldn't it be easier to follow if it did all the ejb-ref stuff, then all the ejb-external-ref, checking for no view-type, view-type="remote" & view-type="local" in turn, in either case? Or is there something subtle going on that needs it to be this way round? If someone could explain what's going on in there, it would help me get it done quicker (since I assume the Bluestone refs bits are going to have to work in much the same way). Oh yeah, and thirdly, I've got to finish off the documentation (and maybe add a few extra tags into the samples source). I'd possibly have had it done by now, but while I was waiting for some answers about it I got distracted by some other stuff I've been adding, which is also nearly done. Probably too late for 1.1.1 now, especially if we want to leave time to check it (which is why I was asking about when the new branch for migrating to xjavadoc was going to be created, I thought it might be less hassle if I'd got it checked in first). Andrew. _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
