"dlmiles" wrote :
| The point I was getting at, is that no deployer should mindlessly attempt
to deploy all files it finds at any nesting depth ending in *-beans.xml.
|
It is not.
Like I said, only those that are in metadata path.
See StructureDeployers for more info.
"dlmiles" wrote :
|
See also http://jira.jboss.org/jira/browse/JBMETA-5 (which I believe to be the
correct channel for updates to jboss-metadata.jar). The XSD validation is
picking up the information contained in that JAR.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133474#4
"alesj" wrote : "dlmiles" wrote :
| | Surely there is some other qualifying requirement too. For example the
*.deployer file name as well as requiring a META-INF/spring-deployers-beans.xml
with outer element ?
| |
| The file has to be in metadata path, recognized by StructureDeploye
"dlmiles" wrote :
| I'm surprised it could find it, none of my containment files are exploded.
|
It's called JBoss VFS. ;-)
"dlmiles" wrote :
| Surely there is some other qualifying requirement too. For example the
*.deployer file name as well as requiring a META-INF/spring-deployers-be
Thank you for your replies again.
Picks up ? Ah I see the error is from the deployer trying to deploy something
as a JBoss service which is actually contained inside my EAR which has a WAR
and in my /WEB-INF/spring.beans.xml. I'm surprised it could find it, none of
my containment files are ex
"dlmiles" wrote :
| Anyway now moving onto my next problem.
|
| Are all the schemes that spring usually has setup (when running as a
web-app in plain Tomcat; not Tomcat under JBoss), are they enabled and
functional with respect to JBoss ? In particular the scheme handler for
"classpath:"
"dlmiles" wrote : Caused by: org.jboss.xb.binding.JBossXBException: Failed to
parse source: Failed to parse schema for nsURI=, baseURI=null,
schemaLocation=http://www.springframework.org/dtd/spring-beans.dtd
I converted all my spring-beans.dtd to XSD (both in the web-app itself and all
its incl
"dlmiles" wrote :
| I can also see that the MANIFEST of jboss-spring.deployer itself does not
include its own version number and would also like to see jboss-spring.jar from
inside the *.deployer file renamed to jboss-spring-3.0.jar (as well as version
in the manifest). Both would be ideal a
That fragment for jboss-log4j.xml was mean to come out like:
|
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133399#4133399
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133399
__
Thank for your prompt reply.
I was able to turn on logging to see SpringParserDeployer and
ApplicationContextDeployer being picked up by editing */conf/jboss-log4j.xml
and adding:
Also for interest with those reading this thread (as of this time) Spring 2.0
is shipped with JBos
"dlmiles" wrote :
| I am correct in thinking the above version is for JBoss AS 4.2.x and older
? But should not be used wit JBoss AS 5 ?
|
Yes, only JBossAS 4.x.
"dlmiles" wrote :
| Should something appear in the JBossAS console log ?
|
If you use trace log for deployers packages, th
11 matches
Mail list logo
