[JBoss JIRA] Created: (AS7-941) Encountered an exception while porting a Seam application from AS5 to AS7, root cause ZipException
by Sande Gilda (JIRA)
Encountered an exception while porting a Seam application from AS5 to AS7, root cause ZipException
--------------------------------------------------------------------------------------------------
Key: AS7-941
URL: https://issues.jboss.org/browse/AS7-941
Project: Application Server 7
Issue Type: Bug
Affects Versions: No Release
Environment: Fedora 14, porting an EAP5.x application to AS7,
Reporter: Sande Gilda
I am porting the TopicIndex application that was built on EAP5.x to AS7. I have worked around a number of ClassNotFound and other issues. My current build is based on git://github.com/jbossejb3/jboss-as.git which as a fix for AS7-910 and I have coded around AS7-896.
I am now seeing this exception in the log:
09:46:45,570 INFO [javax.servlet.ServletContextListener] (MSC service thread 1-7) Welcome to Seam null
09:46:45,588 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/TopicIndex]] (MSC service thread 1-7) Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener: java.lang.RuntimeException: Error handling file /content/TopicIndex.war/WEB-INF/lib/jboss-seam-remoting.jar
at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:134) [jboss-seam.jar:]
at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:]
at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:]
at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:]
at org.jboss.seam.init.Initialization.create(Initialization.java:130) [jboss-seam.jar:]
at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.0.CR1.jar:7.0.0.Beta4-SNAPSHOT]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3817) [jbossweb-7.0.0.CR1.jar:7.0.0.Beta4-SNAPSHOT]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method) [:1.6.0_25]
at java.util.zip.ZipFile.<init>(ZipFile.java:127) [:1.6.0_25]
at java.util.zip.ZipFile.<init>(ZipFile.java:144) [:1.6.0_25]
at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:]
... 12 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[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
14 years, 10 months
[JBoss JIRA] Created: (AS7-1112) EJB annotation processing DUP fails to find annotations from classes belonging to jars in .ear/lib
by jaikiran pai (JIRA)
EJB annotation processing DUP fails to find annotations from classes belonging to jars in .ear/lib
--------------------------------------------------------------------------------------------------
Key: AS7-1112
URL: https://issues.jboss.org/browse/AS7-1112
Project: Application Server 7
Issue Type: Bug
Components: EJB
Environment: AS7 upstream (June 24 2011)
Reporter: jaikiran pai
Assignee: jaikiran pai
Consider the following deployment:
{code}
.ear
|
|--- lib/lib.jar
|
|--- ejb.jar
{code}
If ejb.jar contains:
{code}
@Stateless
public class MyBean implements SomeInterface {
}
{code}
and the lib/lib.jar contains the interface:
{code}
@Remote
public interface SomeInterface {
...
}
{code}
then the BusinessViewAnnotationProcessor complains about missing index for the SomeInterface class:
{code}
09:05:28,739 WARN [org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor] (MSC service thread 1-2) Could not read annotations on EJB interface blah.blah.SomeInterface
{code}
Please see the referenced forum thread for the details.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (AS7-1146) Source bundle build problems
by Richard Achmatowicz (JIRA)
Source bundle build problems
----------------------------
Key: AS7-1146
URL: https://issues.jboss.org/browse/AS7-1146
Project: Application Server 7
Issue Type: Bug
Components: Build System
Affects Versions: 7.0.0.CR1
Environment: GitHub, Linux
Reporter: Richard Achmatowicz
Assignee: Jason Greene
Fix For: 7.0.0.Final
The source bundle for AS 7.0.0.CR1 tag obtained from GitHub does not build correctly.
Jason indicated that "the problem is that build is configured to include the git hash in the binaries so that we can track down where it came from. If you don't have a git repo though it won't work. So we need to add some kind of workaround for this scenario "
Steps to reproduce:
1. Navigate https://github.com/jbossas/jboss-as/
2. Switch tags to 7.0.0.CR1
3. Download the zip source bundle for 7.0.0.CR1
4. Unzip and build it with maven via .build.sh install -Dmaven.test.skip=true
The build is unsuccessful and I see the following:
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server: Build Configuration ..... SUCCESS [1.188s]
[INFO] JBoss Application Server: Parent Aggregator ....... FAILURE [0.323s]
[INFO] JBoss Application Server: Protocol Utilities ...... SKIPPED
[snip]
[INFO] JBoss Application Server Test Suite: Smoke Tests .. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.832s
[INFO] Finished at: Wed Jun 29 09:57:06 EDT 2011
[INFO] Final Memory: 59M/434M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.codehaus.mojo:buildnumber-maven-plugin:1.0:create (default) on project jboss-as-parent: Cannot get the revision information from the
scm repository :
[ERROR] Exception while executing SCM command. UnsupportedOperationException
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :jboss-as-parent
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months