Hi Folks,
I wanted to ask whether it was generally agreed & accepted that all ejb3
deployments out there that use ejb3 proprietary annotations (e.g
@RemoteBinding) will not work in AS50-Beta3?
If not, this issue would need to get looked at again.
cheers
-thomas
Thomas Diesler wrote:
Carlo de Wolf wrote:
> We just wanted to see how you liked it. :-)
>
> Because we want a clear namespace we've moved everything that's ours to
> org.jboss.ejb3.
>
> You can put both RemoteBinding annotations in the class.
org.jboss.annotation.ejb.RemoteBinding, which is used in AS4x does not
seem to exist in any AS5 jar
[tdiesler@tddell jboss-5.0.0.Beta3]$ find server/default -name *.jar |
xargs grep org/jboss/ejb3/annotation/RemoteBinding
Binary file server/default/lib/jboss-ejb3-ext-api.jar matches
[tdiesler@tddell jboss-5.0.0.Beta3]$ find server/default -name *.jar |
xargs grep org/jboss/annotation/ejb/RemoteBinding
[tdiesler@tddell jboss-5.0.0.Beta3]$
>
> Carlo
>
> On Wed, 2007-12-05 at 15:39 +0100, Thomas Diesler wrote:
>> Folks/Carlo,
>>
>> recently @RemoteBinding has changed package in AS5. As a result of
>> which EJBs that use that annotation from the old package cannot be
>> deployed in AS5 any more. This breaks our cross container test suite
>> and potentially every customer EJB out there that uses jboss
>> proprietary annotations.
>>
>> Is this intentional and if so how do I define the remote binding such
>> that it works both in AS42 and AS5?
>>
>> cheers
>> -thomas
>>
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx