3:29 p.m.
resolve potential LinkageError
------------------------------
Key: WBRI-193
URL: https://jira.jboss.org/jira/browse/WBRI-193
Project: Web Beans
Issue Type: Patch
Affects Versions: 1.0.0.BETA1
Reporter: Takeshi Kondo
Priority: Trivial
Some time age, LinkageError is caused by Seam's Javassist ProxyFactory usage.
It same applies to WebBeans.
if possible, make a modification
from
---
ProxyFactory proxyFactory = new ProxyFactory();
proxyFactory.setSuperclass(getSuperClass();
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
to
---
ProxyFactory proxyFactory = new ProxyFactory();
Class<?> superClass = getSuperClass();
if(superClass != Object.class)
{
proxyFactory.setSuperclass(superClass);
}
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
---
Apply to this patch,
If proxy target class is interface, generated proxy class name changes
form "org.javassist.tmp.java.lang.Object_$$_javassist_0"
to "org.javassist.tmp.java.util.List_$$_javassist_0".
All interface generated proxy class name is
"org.javassist.tmp.java.lang.Object_$$_javassist_(number)"
Because proxy class name pattern is monotone,
duplicate proxy class name, then it causes LinkageError.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:31 p.m.
New subject: [webbeans-issues] [JBoss JIRA] Updated: (WBRI-193) resolve potential LinkageError
[
https://jira.jboss.org/jira/browse/WBRI-193?page=com.atlassian.jira.plugi...
]
Takeshi Kondo updated WBRI-193:
-------------------------------
Attachment: Proxies.java.patch
resolve potential LinkageError
------------------------------
Key: WBRI-193
URL: https://jira.jboss.org/jira/browse/WBRI-193
Project: Web Beans
Issue Type: Patch
Affects Versions: 1.0.0.BETA1
Reporter: Takeshi Kondo
Priority: Trivial
Attachments: Proxies.java.patch
Some time age, LinkageError is caused by Seam's Javassist ProxyFactory usage.
It same applies to WebBeans.
if possible, make a modification
from
---
ProxyFactory proxyFactory = new ProxyFactory();
proxyFactory.setSuperclass(getSuperClass();
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
to
---
ProxyFactory proxyFactory = new ProxyFactory();
Class<?> superClass = getSuperClass();
if(superClass != Object.class)
{
proxyFactory.setSuperclass(superClass);
}
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
---
Apply to this patch,
If proxy target class is interface, generated proxy class name changes
form "org.javassist.tmp.java.lang.Object_$$_javassist_0"
to "org.javassist.tmp.java.util.List_$$_javassist_0".
All interface generated proxy class name is
"org.javassist.tmp.java.lang.Object_$$_javassist_(number)"
Because proxy class name pattern is monotone,
duplicate proxy class name, then it causes LinkageError.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:37 a.m.
New subject: [webbeans-issues] [JBoss JIRA] Updated: (WBRI-193) resolve potential LinkageError
[
https://jira.jboss.org/jira/browse/WBRI-193?page=com.atlassian.jira.plugi...
]
Pete Muir updated WBRI-193:
---------------------------
Fix Version/s: 1.1.0.BETA1
Assignee: Nicklas Karlsson
resolve potential LinkageError
------------------------------
Key: WBRI-193
URL: https://jira.jboss.org/jira/browse/WBRI-193
Project: Web Beans
Issue Type: Patch
Affects Versions: 1.0.0.BETA1
Reporter: Takeshi Kondo
Assignee: Nicklas Karlsson
Priority: Trivial
Fix For: 1.1.0.BETA1
Attachments: Proxies.java.patch
Some time age, LinkageError is caused by Seam's Javassist ProxyFactory usage.
It same applies to WebBeans.
if possible, make a modification
from
---
ProxyFactory proxyFactory = new ProxyFactory();
proxyFactory.setSuperclass(getSuperClass();
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
to
---
ProxyFactory proxyFactory = new ProxyFactory();
Class<?> superClass = getSuperClass();
if(superClass != Object.class)
{
proxyFactory.setSuperclass(superClass);
}
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
---
Apply to this patch,
If proxy target class is interface, generated proxy class name changes
form "org.javassist.tmp.java.lang.Object_$$_javassist_0"
to "org.javassist.tmp.java.util.List_$$_javassist_0".
All interface generated proxy class name is
"org.javassist.tmp.java.lang.Object_$$_javassist_(number)"
Because proxy class name pattern is monotone,
duplicate proxy class name, then it causes LinkageError.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:13 a.m.
New subject: [webbeans-issues] [JBoss JIRA] Commented: (WBRI-193) resolve potential LinkageError
[
https://jira.jboss.org/jira/browse/WBRI-193?page=com.atlassian.jira.plugi...
]
Pete Muir commented on WBRI-193:
--------------------------------
Basically, if the only superclass is Object.class (e.g. for session beans) void setting it
explicitly (it is added implicitly to all objects anyway). This tidies up the naming a bit
- though I don't understand where the LinkageError comes from.
resolve potential LinkageError
------------------------------
Key: WBRI-193
URL: https://jira.jboss.org/jira/browse/WBRI-193
Project: Web Beans
Issue Type: Patch
Affects Versions: 1.0.0.BETA1
Reporter: Takeshi Kondo
Assignee: Nicklas Karlsson
Priority: Trivial
Fix For: 1.1.0.BETA1
Attachments: Proxies.java.patch
Some time age, LinkageError is caused by Seam's Javassist ProxyFactory usage.
It same applies to WebBeans.
if possible, make a modification
from
---
ProxyFactory proxyFactory = new ProxyFactory();
proxyFactory.setSuperclass(getSuperClass();
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
to
---
ProxyFactory proxyFactory = new ProxyFactory();
Class<?> superClass = getSuperClass();
if(superClass != Object.class)
{
proxyFactory.setSuperclass(superClass);
}
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
---
Apply to this patch,
If proxy target class is interface, generated proxy class name changes
form "org.javassist.tmp.java.lang.Object_$$_javassist_0"
to "org.javassist.tmp.java.util.List_$$_javassist_0".
All interface generated proxy class name is
"org.javassist.tmp.java.lang.Object_$$_javassist_(number)"
Because proxy class name pattern is monotone,
duplicate proxy class name, then it causes LinkageError.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 p.m.
New subject: [webbeans-issues] [JBoss JIRA] Commented: (WBRI-193) resolve potential LinkageError
[
https://jira.jboss.org/jira/browse/WBRI-193?page=com.atlassian.jira.plugi...
]
Takeshi Kondo commented on WBRI-193:
------------------------------------
though I don't understand where the LinkageError comes from.
ProxyFactory don't cause LinkageError, because ProxyFactory ensure generated
class naming uniqueness.
But, Seam have ProxyFactory coped from
Javassist(http://docs.jboss.org/seam/2.0.2.SP1/api/org/jboss/seam/util/Pr...
,so ProxyFactory's generated class naming uniqueness is lost.
Using Seam's ProxyFactory and Javassist's ProxyFactory , monotone class naming
rule cause dumplicate class name.
LinkageError comes from it.
resolve potential LinkageError
------------------------------
Key: WBRI-193
URL: https://jira.jboss.org/jira/browse/WBRI-193
Project: Web Beans
Issue Type: Patch
Affects Versions: 1.0.0.BETA1
Reporter: Takeshi Kondo
Assignee: Nicklas Karlsson
Priority: Trivial
Fix For: 1.1.0.BETA1
Attachments: Proxies.java.patch
Some time age, LinkageError is caused by Seam's Javassist ProxyFactory usage.
It same applies to WebBeans.
if possible, make a modification
from
---
ProxyFactory proxyFactory = new ProxyFactory();
proxyFactory.setSuperclass(getSuperClass();
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
to
---
ProxyFactory proxyFactory = new ProxyFactory();
Class<?> superClass = getSuperClass();
if(superClass != Object.class)
{
proxyFactory.setSuperclass(superClass);
}
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
---
Apply to this patch,
If proxy target class is interface, generated proxy class name changes
form "org.javassist.tmp.java.lang.Object_$$_javassist_0"
to "org.javassist.tmp.java.util.List_$$_javassist_0".
All interface generated proxy class name is
"org.javassist.tmp.java.lang.Object_$$_javassist_(number)"
Because proxy class name pattern is monotone,
duplicate proxy class name, then it causes LinkageError.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 p.m.
New subject: [webbeans-issues] [JBoss JIRA] Updated: (WBRI-193) resolve potential LinkageError
[
https://jira.jboss.org/jira/browse/WBRI-193?page=com.atlassian.jira.plugi...
]
Pete Muir updated WBRI-193:
---------------------------
Fix Version/s: 1.0.0.PREVIEW
(was: 1.1.0.BETA1)
Wrong fix version ;-)
resolve potential LinkageError
------------------------------
Key: WBRI-193
URL: https://jira.jboss.org/jira/browse/WBRI-193
Project: Web Beans
Issue Type: Patch
Affects Versions: 1.0.0.BETA1
Reporter: Takeshi Kondo
Assignee: Nicklas Karlsson
Priority: Trivial
Fix For: 1.0.0.PREVIEW
Attachments: Proxies.java.patch
Some time age, LinkageError is caused by Seam's Javassist ProxyFactory usage.
It same applies to WebBeans.
if possible, make a modification
from
---
ProxyFactory proxyFactory = new ProxyFactory();
proxyFactory.setSuperclass(getSuperClass();
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
to
---
ProxyFactory proxyFactory = new ProxyFactory();
Class<?> superClass = getSuperClass();
if(superClass != Object.class)
{
proxyFactory.setSuperclass(superClass);
}
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
---
Apply to this patch,
If proxy target class is interface, generated proxy class name changes
form "org.javassist.tmp.java.lang.Object_$$_javassist_0"
to "org.javassist.tmp.java.util.List_$$_javassist_0".
All interface generated proxy class name is
"org.javassist.tmp.java.lang.Object_$$_javassist_(number)"
Because proxy class name pattern is monotone,
duplicate proxy class name, then it causes LinkageError.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:52 p.m.
New subject: [webbeans-issues] [JBoss JIRA] Commented: (WBRI-193) resolve potential LinkageError
[
https://jira.jboss.org/jira/browse/WBRI-193?page=com.atlassian.jira.plugi...
]
Pete Muir commented on WBRI-193:
--------------------------------
Takeshi, Web Beans uses the ProxyFactory from Javassist, so I don't think this
LinkageError is a problem...
But I agree with the naming - it would be better to make the names nice.
resolve potential LinkageError
------------------------------
Key: WBRI-193
URL: https://jira.jboss.org/jira/browse/WBRI-193
Project: Web Beans
Issue Type: Patch
Affects Versions: 1.0.0.BETA1
Reporter: Takeshi Kondo
Assignee: Nicklas Karlsson
Priority: Trivial
Fix For: 1.0.0.PREVIEW
Attachments: Proxies.java.patch
Some time age, LinkageError is caused by Seam's Javassist ProxyFactory usage.
It same applies to WebBeans.
if possible, make a modification
from
---
ProxyFactory proxyFactory = new ProxyFactory();
proxyFactory.setSuperclass(getSuperClass();
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
to
---
ProxyFactory proxyFactory = new ProxyFactory();
Class<?> superClass = getSuperClass();
if(superClass != Object.class)
{
proxyFactory.setSuperclass(superClass);
}
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
---
Apply to this patch,
If proxy target class is interface, generated proxy class name changes
form "org.javassist.tmp.java.lang.Object_$$_javassist_0"
to "org.javassist.tmp.java.util.List_$$_javassist_0".
All interface generated proxy class name is
"org.javassist.tmp.java.lang.Object_$$_javassist_(number)"
Because proxy class name pattern is monotone,
duplicate proxy class name, then it causes LinkageError.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:54 p.m.
New subject: [webbeans-issues] [JBoss JIRA] Assigned: (WBRI-193) resolve potential LinkageError
[
https://jira.jboss.org/jira/browse/WBRI-193?page=com.atlassian.jira.plugi...
]
Pete Muir reassigned WBRI-193:
------------------------------
Assignee: Pete Muir (was: Nicklas Karlsson)
resolve potential LinkageError
------------------------------
Key: WBRI-193
URL: https://jira.jboss.org/jira/browse/WBRI-193
Project: Web Beans
Issue Type: Patch
Affects Versions: 1.0.0.BETA1
Reporter: Takeshi Kondo
Assignee: Pete Muir
Priority: Trivial
Fix For: 1.0.0.PREVIEW
Attachments: Proxies.java.patch
Some time age, LinkageError is caused by Seam's Javassist ProxyFactory usage.
It same applies to WebBeans.
if possible, make a modification
from
---
ProxyFactory proxyFactory = new ProxyFactory();
proxyFactory.setSuperclass(getSuperClass();
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
to
---
ProxyFactory proxyFactory = new ProxyFactory();
Class<?> superClass = getSuperClass();
if(superClass != Object.class)
{
proxyFactory.setSuperclass(superClass);
}
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
---
Apply to this patch,
If proxy target class is interface, generated proxy class name changes
form "org.javassist.tmp.java.lang.Object_$$_javassist_0"
to "org.javassist.tmp.java.util.List_$$_javassist_0".
All interface generated proxy class name is
"org.javassist.tmp.java.lang.Object_$$_javassist_(number)"
Because proxy class name pattern is monotone,
duplicate proxy class name, then it causes LinkageError.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:36 p.m.
New subject: [webbeans-issues] [JBoss JIRA] Closed: (WBRI-193) resolve potential LinkageError
[
https://jira.jboss.org/jira/browse/WBRI-193?page=com.atlassian.jira.plugi...
]
Pete Muir closed WBRI-193.
--------------------------
Resolution: Done
resolve potential LinkageError
------------------------------
Key: WBRI-193
URL: https://jira.jboss.org/jira/browse/WBRI-193
Project: Web Beans
Issue Type: Patch
Affects Versions: 1.0.0.BETA1
Reporter: Takeshi Kondo
Assignee: Pete Muir
Priority: Trivial
Fix For: 1.0.0.PREVIEW
Attachments: Proxies.java.patch
Some time age, LinkageError is caused by Seam's Javassist ProxyFactory usage.
It same applies to WebBeans.
if possible, make a modification
from
---
ProxyFactory proxyFactory = new ProxyFactory();
proxyFactory.setSuperclass(getSuperClass();
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
to
---
ProxyFactory proxyFactory = new ProxyFactory();
Class<?> superClass = getSuperClass();
if(superClass != Object.class)
{
proxyFactory.setSuperclass(superClass);
}
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
---
Apply to this patch,
If proxy target class is interface, generated proxy class name changes
form "org.javassist.tmp.java.lang.Object_$$_javassist_0"
to "org.javassist.tmp.java.util.List_$$_javassist_0".
All interface generated proxy class name is
"org.javassist.tmp.java.lang.Object_$$_javassist_(number)"
Because proxy class name pattern is monotone,
duplicate proxy class name, then it causes LinkageError.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:24 a.m.
New subject: [webbeans-issues] [JBoss JIRA] Commented: (WBRI-193) resolve potential LinkageError
[
https://jira.jboss.org/jira/browse/WBRI-193?page=com.atlassian.jira.plugi...
]
Takeshi Kondo commented on WBRI-193:
------------------------------------
Pete, thanks for your acceptance.
Recently, this LinkageError have afflicted me, so I am grateful for it.
resolve potential LinkageError
------------------------------
Key: WBRI-193
URL: https://jira.jboss.org/jira/browse/WBRI-193
Project: Web Beans
Issue Type: Patch
Affects Versions: 1.0.0.BETA1
Reporter: Takeshi Kondo
Assignee: Pete Muir
Priority: Trivial
Fix For: 1.0.0.PREVIEW
Attachments: Proxies.java.patch
Some time age, LinkageError is caused by Seam's Javassist ProxyFactory usage.
It same applies to WebBeans.
if possible, make a modification
from
---
ProxyFactory proxyFactory = new ProxyFactory();
proxyFactory.setSuperclass(getSuperClass();
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
to
---
ProxyFactory proxyFactory = new ProxyFactory();
Class<?> superClass = getSuperClass();
if(superClass != Object.class)
{
proxyFactory.setSuperclass(superClass);
}
proxyFactory.setInterfaces(getInterfaces());
return proxyFactory;
---
Apply to this patch,
If proxy target class is interface, generated proxy class name changes
form "org.javassist.tmp.java.lang.Object_$$_javassist_0"
to "org.javassist.tmp.java.util.List_$$_javassist_0".
All interface generated proxy class name is
"org.javassist.tmp.java.lang.Object_$$_javassist_(number)"
Because proxy class name pattern is monotone,
duplicate proxy class name, then it causes LinkageError.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5751
days inactive
5757
days old
9 comments
2 participants
participants (2)
-
Pete Muir (JIRA) -
Takeshi Kondo (JIRA)