[JBoss JIRA] Created: (JBAS-9266) java.lang.reflect.UndeclaredThrowableException when using @ApplicationException in combination with @InterceptorBinding
by Felix Ullrich (JIRA)
java.lang.reflect.UndeclaredThrowableException when using @ApplicationException in combination with @InterceptorBinding
-----------------------------------------------------------------------------------------------------------------------
Key: JBAS-9266
URL: https://issues.jboss.org/browse/JBAS-9266
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Reporter: Felix Ullrich
Assignee: Carlo de Wolf
If I'm using @InterceptorBinding a thrown Exception out of an EJB marked with @ApplicationException dont reach the client. Instead of the @ApplicationException I get a java.lang.reflect.UndeclaredThrowableException.
I've attached a minimal example.
My client-main-program looks like this:
{code:title=Bar.java|borderStyle=solid}
public static void main(final String[] args) throws NamingException {
final InitialContext context = new InitialContext();
context.lookup("StatefulTestBean/remote");
try {
statefulTest.throwApplicationError();
} catch (final Exception e) {
System.out.println(e);
}
}
{code}
The excepted output would be:
{code}
error.AppError
{code}
but its:
{code}
java.lang.reflect.UndeclaredThrowableException
{code}
If you comment out the annotation @InterceptorAnnotation in the StatefulTestBean.java and redeploy the application then everything is fine - you get the expetced AppError-Exception.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (EJBTHREE-2243) Transaction problems, possible bug in ApplicationExceptionComponentMetaDataLoaderFactory
by Benoit Heinrich (JIRA)
Transaction problems, possible bug in ApplicationExceptionComponentMetaDataLoaderFactory
----------------------------------------------------------------------------------------
Key: EJBTHREE-2243
URL: https://issues.jboss.org/browse/EJBTHREE-2243
Project: EJB 3.0
Issue Type: Bug
Components: transactions
Affects Versions: EJB3_1 1.0.3
Environment: JBoss AS 6.0.0.Final
Reporter: Benoit Heinrich
I think I've found a possible bug with transaction attributes management in jboss 6.0.0 Final.
The problem appears when using the @TransactionAttribute annotation on an EJB bean with the @Interceptors.
When using that it seems that the @TransactionAttribute annotation is ignored.
By removing the @Interceptors annotation it works and the right transaction attribute is used.
More details available in the jboss forum link.
Cheers,
/Benoit
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBRULES-2730) Duplicate rules name errors not being identified across multiple resources in same package
by Michael Pellegrini (JIRA)
Duplicate rules name errors not being identified across multiple resources in same package
------------------------------------------------------------------------------------------
Key: JBRULES-2730
URL: https://jira.jboss.org/browse/JBRULES-2730
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Windows XP, Java 1.6.0_17
Reporter: Michael Pellegrini
Assignee: Mark Proctor
The validateUniqueRuleNamesmethod in the org.drools.compiler.PackageBuilder class currently only checks for duplicate rule names that are defined within the same resource. However, in the case where there are multiple resources added to the knowledge builder that share the same package name then the validateUniqueRuleNames method is not detecting duplicates across the package.
In cases where rules have the same name and are defined in the same package then I would have expected to get a duplicate rule error but I do not as the rules are physically reside in two separate resources.
It seems logical that in addition to checking if any rules are duplicated within the resource that it also checks to see that rule was already defined in the package registry as well. Otherwise the last rule overwrites the first and creates some rather odd behavior.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBAS-9336) password_tool.bat generates java.lang.ClassNotFoundException
by Andrew Murphy (JIRA)
password_tool.bat generates java.lang.ClassNotFoundException
------------------------------------------------------------
Key: JBAS-9336
URL: https://issues.jboss.org/browse/JBAS-9336
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: 6.0.0.Final
Environment: Windows
Reporter: Andrew Murphy
Assignee: Anil Saldhana
The password_tool.bat command found in %JBOSS_HOME%\bin generates a java.lang.ClassNotFoundException
D:\JBoss\jboss-6.0.0.GA\bin>password_tool.bat
**********************************
**** JBoss Password Tool********
**********************************
Keystore is null. Please specify keystore below:
0: Encrypt Keystore Password 1:Specify KeyStore 2:Create Password 3: Remove a domain 4:Enquire Domain 5:Exit
1
Enter Keystore location including the file name
password/password.keystore
Enter Keystore alias
jboss
log4j:WARN No appenders could be found for logger (org.apache.xml.security.Init).
log4j:WARN Please initialize the log4j system properly.
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/xml/utils/URI$MalformedURIException
at org.jboss.security.integration.password.XMLEncryptionUtil.decrypt(XMLEncryptionUtil.java:205)
at org.jboss.security.integration.password.PasswordMaskManagement.load(PasswordMaskManagement.java:200)
at org.jboss.security.integration.password.PasswordTool.load(PasswordTool.java:172)
at org.jboss.security.integration.password.PasswordTool.main(PasswordTool.java:128)
Caused by: java.lang.ClassNotFoundException: org.apache.xml.utils.URI$MalformedURIException
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
... 4 more
org.jboss.security.integration.password.PasswordTool$ShutdownHook run called
Storing domains [
]
Exception in thread "Thread-0" java.lang.NoClassDefFoundError: org/apache/xml/utils/URI$MalformedURIException
at org.jboss.security.integration.password.XMLEncryptionUtil.encrypt(XMLEncryptionUtil.java:136)
at org.jboss.security.integration.password.PasswordMaskManagement.store(PasswordMaskManagement.java:251)
at org.jboss.security.integration.password.PasswordTool$ShutdownHook.run(PasswordTool.java:205)
Caused by: java.lang.ClassNotFoundException: org.apache.xml.utils.URI$MalformedURIException
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
... 3 more
The underlying problem is xalan.jar cannot be found on the classpath. In GA6.0.0 xalan.jar is located in %JBOSS_HOME%\client, not %JBOSS_HOME%\lib\endorsed, so the password_tool.bat classpath declaration needs to reflect this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JASSIST-138) CHECKCAST of javassist.bytecode.analysis.Executor.execute() is broken
by Yu Kobayashi (JIRA)
CHECKCAST of javassist.bytecode.analysis.Executor.execute() is broken
---------------------------------------------------------------------
Key: JASSIST-138
URL: https://issues.jboss.org/browse/JASSIST-138
Project: Javassist
Issue Type: Bug
Affects Versions: 3.12.0.GA
Reporter: Yu Kobayashi
Assignee: Shigeru Chiba
At execute(MethodInfo method, int pos, CodeIterator iter, Frame frame, Subroutine subroutine) of
javassist.bytecode.analysis.Executor, CHECKCAST is this.
case CHECKCAST:
verifyAssignable(Type.OBJECT, simplePop(frame));
frame.push(typeFromDesc(constPool.getClassInfo(iter.u16bitAt(pos + 1))));
break;
However, constPool.getClassInfo() doesn't returns its descriptor.
To fix this, please change it to
frame.push(typeFromDesc(constPool.getClassInfoByDescriptor(iter.u16bitAt(pos + 1))));
and add this to javassist.bytecode.ConstPool.
public String getClassInfoByDescriptor(int index) {
ClassInfo c = (ClassInfo)getItem(index);
if (c == null)
return null;
else {
String className = getUtf8Info(c.name);
if (className.charAt(0) == '[') {
return className;
} else {
return Descriptor.of(className);
}
}
}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years