I've the following problem: my Web Application reads and writes text files from within the Application. This files have to be accessible over the internet.
The problem is: when i create a file, it's created in the jboss/bin directory... but it has to be created in the web application (otherwise it wouldn't be accessible though the browser)... but every time i deploy the application, the random number increments, making it impossible to set a path or something like that...
How can I get the current deployment location from within the code? or, if that's not possible, how can i set one fixed location for the deployment of the Application, making it possible to hardcode the path?
Thanks in advance!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133404#4133404
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133404
I'm running JBoss 4.2.2. I have an MDB that I want to control programmatically. Specifically I do not want the MDB to start automatically when the application server starts up, but instead start it programmatically.
I can think of a few different strategies by which this might be accomplished, but I'm not sure if these are possible or how to do about it.
1) Do not deploy the MDB via annotations or xml descriptor, but rather through some programmatic API.
2) Allow the MDBContainer to be created but prevent it from starting, it can then be started via the MBean.
3) Set the pool size to 0 and then increase it programmatically.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133401#4133401
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133401
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 JBoss Spring Deployer 3.0. This saves you from downloading every version of Spring framework and comparing JARs until you find a match.
I disagree you are not modifying the file by changing the filename by appending the version number like spring-core-2.0.8.jar but would support you stance if I was asking for the content to be modified (which I am not).
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 and would save you documenting a README file about which version you built with this week.
My next problem is that one or more Spring bean descriptors does not use XSD/Namespaces but DTD, is that allowed ?
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
Now my remaining concern: I have a WAR in my EAR which currently has spring*.jar's inside (/WEB-INF/lib/*.jar) what is the correct way the package those ?
If the JBoss deployer version (of Spring Framework) and the WAR version (of Spring Framework) were different, would there ever be a problem, I am thinking that the WAR container encapsulaltion will still work fine, since I would need to go to JNDI to obtain access to an ApplicationContext for any components deployed via JBoss Spring Deployer. Is my understanding correct on this ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133398#4133398
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133398