[weld-dev] Why the lengthy classnames for proxies generated by Weld?

[Stuart Douglas]

It is something I have been planing to do something about for a while now,
but never quite got around to it. The original reason is that we needed a
deterministic way of determining proxy names that will be the same accross
JVM's, and using the class name will not always work, so we used bean ID's.
It should be possible to simplify this for most cases.

Stuart

On Fri, May 27, 2011 at 5:21 AM, Dan Allen <dan.j.allen at gmail.com> wrote:

> On Thu, May 26, 2011 at 02:31, Jaikiran Pai <jpai at redhat.com> wrote:
>
>> I am seeing many forum posts where, within the exception stacktrace, I
>> see really long classnames for proxies generated by Weld.Here's one
>> example http://community.jboss.org/message/604723#604723. Out of
>> curiosity, is there any reason why those names are so lengthy instead of
>> just generating the classnames like java.lang.reflect.Proxy does?
>>
>
> On top of the length annoyance, I think this is one of the reasons Weld
> doesn't work on the IBM JDK (or I'm mistaken an it's a Solder issue). But
> from my brief testing, it had something to do with generated class names.
> Just a heads up.
>
> -Dan
>
> --
> Dan Allen
> Principal Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://www.google.com/profiles/dan.j.allen#about
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20110527/6ea260c1/attachment.html