<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I predict funny bugs from time to time if you use a true hash function :)<div><br><div><div>On 27 mai 2011, at 15:37, Lincoln Baxter, III wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Why can't we just append a short hash to the FQCN?<br><br><div class="gmail_quote">On Fri, May 27, 2011 at 3:51 AM, David Allen <span dir="ltr"><<a href="mailto:drallendc@gmail.com">drallendc@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Stuart,<br><br>We can probably easily identify cases through an initial pattern in the name on deserialization, and then just stick to simply the class name as the rest when that works and use the bean ID only in special cases where needed. Sounds easy enough, but identifying the correct cases on serialization might be more involved. I'll think about it some and might have some time in June to do it, if you don't.<br>
<font color="#888888">
<br>- David</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Fri, May 27, 2011 at 12:53 AM, Stuart Douglas <span dir="ltr"><<a href="mailto:stuart.w.douglas@gmail.com" target="_blank">stuart.w.douglas@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<br>
<font color="#888888">
<br>Stuart<br><br></font><div class="gmail_quote"><div><div></div><div>On Fri, May 27, 2011 at 5:21 AM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com" target="_blank">dan.j.allen@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div><div></div><div>
<div>On Thu, May 26, 2011 at 02:31, Jaikiran Pai <span dir="ltr"><<a href="mailto:jpai@redhat.com" target="_blank">jpai@redhat.com</a>></span> wrote:<br></div><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
I am seeing many forum posts where, within the exception stacktrace, I<br>
see really long classnames for proxies generated by Weld.Here's one<br>
example <a href="http://community.jboss.org/message/604723#604723" target="_blank">http://community.jboss.org/message/604723#604723</a>. Out of<br>
curiosity, is there any reason why those names are so lengthy instead of<br>
just generating the classnames like java.lang.reflect.Proxy does?<br></blockquote><div><br></div></div><div>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.</div>
<div><br></div><div>-Dan</div><div><br></div></div><font color="#888888">-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>
<a href="http://mojavelinux.com/" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>
</font><br></div></div><div>_______________________________________________<br>
weld-dev mailing list<br>
<a href="mailto:weld-dev@lists.jboss.org" target="_blank">weld-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br></div></blockquote></div><br>
<br>_______________________________________________<br>
weld-dev mailing list<br>
<a href="mailto:weld-dev@lists.jboss.org" target="_blank">weld-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br></blockquote></div><br>
</div></div><br>_______________________________________________<br>
weld-dev mailing list<br>
<a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com/">http://ocpsoft.com</a><br>
<a href="http://scrumshark.com/">http://scrumshark.com</a><br>"Keep it Simple"<br>
_______________________________________________<br>weld-dev mailing list<br><a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/weld-dev</blockquote></div><br></div></body></html>