[JBoss JIRA] Created: (JBRULES-976) ShadowProxyUtils.cloneObject() spews noise to stdout
by Dirk Bergstrom (JIRA)
ShadowProxyUtils.cloneObject() spews noise to stdout
----------------------------------------------------
Key: JBRULES-976
URL: http://jira.jboss.com/jira/browse/JBRULES-976
Project: JBoss Rules
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: Reteoo
Affects Versions: 4.0.0.MR4
Reporter: Dirk Bergstrom
Assigned To: Mark Proctor
Attachments: diff.txt
With this new code, I get about 75 megs worth of the following errors
when I initialize my application (stacktraces abbreviated):
java.lang.IllegalAccessException: Class org.drools.util.ShadowProxyUtils can not access a member of class java.util.Collections$EmptySet with modifiers "private"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
at java.lang.Class.newInstance0(Class.java:344)
at java.lang.Class.newInstance(Class.java:303)
at org.drools.util.ShadowProxyUtils.cloneObject(ShadowProxyUtils.java:54)
java.lang.InstantiationException: java.util.Collections$UnmodifiableSet
at java.lang.Class.newInstance0(Class.java:335)
at java.lang.Class.newInstance(Class.java:303)
at org.drools.util.ShadowProxyUtils.cloneObject(ShadowProxyUtils.java:54)
The attached patch takes care of these two errors, and removes the
printStackTrace() call from the catch block, since it's noise to
everyone except the Drools developers. If there's a debug or
developer flag of some kind in the codebase, it would be reasonable to
use that to control the output.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 3 months
[JBoss JIRA] Created: (JBMICROCONT-140) Configurator should check that fields/methods exist before trying to use them
by Adrian Brock (JIRA)
Configurator should check that fields/methods exist before trying to use them
-----------------------------------------------------------------------------
Key: JBMICROCONT-140
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-140
Project: JBoss MicroContainer
Issue Type: Bug
Components: Configurator
Affects Versions: JBossMC_2_0_0 Beta
Reporter: Adrian Brock
Assigned To: Ales Justin
Fix For: JBossMC_2_0_0_CR1
Make sure the configurator is throwing reasonable error messages (not NPE)
when things are null.
e.g. the following method needs to check for null method info meaning there is no getter
public static TargettedJoinpoint getPropertyGetterJoinPoint(boolean trace, PropertyInfo info) throws Throwable
{
if (trace)
log.trace("Get property setter join point info=" + info);
if (info == null)
throw new IllegalArgumentException("Null property info");
JoinpointFactory jpf = info.getBeanInfo().getJoinpointFactory();
MethodInfo minfo = info.getGetter();
+ if (minfo == null)
+ throw new IllegalArgumentException("Property is write only");
return getMethodJoinpoint(null, jpf, minfo.getName(), null, null);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 3 months
[JBoss JIRA] Closed: (JBMICROCONT-40) Add a warning for ambigous signatures.
by Ales Justin (JIRA)
[ http://jira.jboss.com/jira/browse/JBMICROCONT-40?page=all ]
Ales Justin closed JBMICROCONT-40.
----------------------------------
Resolution: Done
We added isAssignable and isProgression which should make this more flexible.
> Add a warning for ambigous signatures.
> --------------------------------------
>
> Key: JBMICROCONT-40
> URL: http://jira.jboss.com/jira/browse/JBMICROCONT-40
> Project: JBoss MicroContainer
> Issue Type: Task
> Components: BeanInfo
> Affects Versions: JBossMC_1_0_0M1
> Reporter: Adrian Brock
> Assigned To: Ales Justin
> Priority: Minor
> Fix For: JBossMC_2_0_0_CR1
>
>
> It should at least WARN the user when a method or constructor is overridden
> and the positional format of the parameters is ambigous before choosing the first one.
> e.g.
> public class MyBean
> {
> public MyBean(String);
> public MyBean(Integer);
> }
> <constructor>
> <parameter>Some value</parameter>
> </constructor>
> should warn the user, which they can resolve with:
> <constructor>
> <parameter class="java.lang.String">Some value</parameter>
> </constructor>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 3 months