[
https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.s...
]
jarkko rantavuori updated AS7-6420:
-----------------------------------
Steps to Reproduce:
Try to deploy attached spring-xml 2.10 component, downloaded from spring enterprise
repository, in the JBoss AS7 snapshot installation (link as a comment). Using web-based
admin console, red message "deployment failed" appears, but no reason is
available in logs, System.out or UI.
Removing spring-ws deployment, again from admin console, makes spring-xml deployment
appear in the admin console UI.
was:Try to deploy attached spring-xml 2.10 component, downloaded from spring enterprise
repository, in the latest JBoss AS7 snapshot. Using web-based admin console, red message
"deployment failed" appears, but no reason is available in logs, System.out or
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/...
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