[jboss-jira] [JBoss JIRA] (AS7-6420) spring-xml deployment fails without any error message given in latest snapshot
jarkko rantavuori (JIRA)
jira-events at lists.jboss.org
Wed Jan 30 09:51:51 EST 2013
[ https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751364#comment-12751364 ]
jarkko rantavuori edited comment on AS7-6420 at 1/30/13 9:50 AM:
-----------------------------------------------------------------
I've now uploaded my whole JBoss into http://slsh.kapsi.fi/misc/jboss-as-7.2.0.Alpha1-SNAPSHOT.zip (~124M, user/pass admin/jboss). Using that, spring-xml deployment doesn't appear in the admin panel at all, nor does it let you deploy that package, showing just the red message in admin UI. However, if spring-ws deployment is removed, spring-xml deployment appears in admin UI.
was (Author: jrantav):
I've now uploaded my whole JBoss into http://slsh.kapsi.fi/misc/jboss-as-7.2.0.Alpha1-SNAPSHOT.zip (~124M). Using that, spring-xml deployment doesn't appear in the admin panel at all, nor does it let you deploy that package, showing just the red message in admin UI. However, if spring-ws deployment is removed, spring-xml deployment appears in admin UI.
> spring-xml deployment fails without any error message given in latest snapshot
> ------------------------------------------------------------------------------
>
> Key: AS7-6420
> URL: https://issues.jboss.org/browse/AS7-6420
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, Server
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: org.springframework.xml-2.1.0.RELEASE.jar
>
>
> Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/artifact/build/target/jboss-as-7.x.zip and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
> I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
> Jar is from Spring enterprise repository, containing OSGi metadata, so this might be OSGi related.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list