PeterJ,
Thanks for writing. I think this thread is closed now thanks to your
persistence. I've now just to think of how to pass info to the waiting program
to allow it to do its thing.
This isn't a problem for this list, though. I think it is more of a design
thing. You know, a class' name
Why not use the stream classes to do the copying?
Or you could use File.rename() to move the JAR for the deploy directory.
Also, if you are going to do a copy, it is usually best to copy the file to a
temporary location on the same disk partition as the deploy directory, and then
move that
PeterJ,
Thanks for writing.
anonymous wrote : Because your code is running within the server, you can
always look up the name of the deploy directory and then copy the resulting EJB
jar file to that directory and let the hot deployer pick it up on the next scan.
I like this idea, but I think
Two possibilities that I can think of.
1) Because your code is running within the server, you can always look up the
name of the deploy directory and then copy the resulting EJB jar file to that
directory and let the hot deployer pick it up on the next scan. You can
determine the deploy
PeterJ,
Thanks for writing, as always!
anonymous wrote : You are attempting to write a stand-alone Java application
(one not deployed to JBoss AS) that you can use to deploy applications.
Not quite. I'm just looking for ideas as how to do this from within a deployed
app on the same server.
I
Let me see if I understand this correctly. You are attempting to write a
stand-alone Java application (one not deployed to JBoss AS) that you can use to
deploy applications. I assume that this application might not be running on the
same host as the app server. And you want to know how to code
PeterJ,
Firstly, thanks for all your help (to at least me) over the past year. It has
made things easier for me.
I'm still looking for the same thing, even after all these months. I'm still
trying to deploy files in arbitrary locations to the JBoss server. They may be
services or JAR, EAR or
When I pointed you to the DEFAULT_SUFFIX_ORDER I knew that it was no longer
used (though the ordering is still correct). But that is the only place I have
found that lists the various suffixes all in one location.
Also, the *-service.xml file can be used to deploy any MBean, not just
PeterJ,
Thanks for writing. I understand a lot more about the app server as a result.
A more definitive list can be found in the source at
system/src/main/org/jboss/deployment/DeploymentSorter.java, look at
DEFAULT_SUFFIX_ORDER.
Interesting. It is deprecated, but points to
Regarding a list of suffixes. This doc page gives some of that information,
particularly the bullet list of deployers:
http://docs.jboss.com/jbossas/guides/j2eeguide/r2/en/html_single/#ch2.deployers
A more definitive list can be found in the source at
1) You should not modify the configuration files in place while the application
server is running. Instead, copy the one you want to modify to a temporary
location, edit it there, and then copy back to deploy. Note that the filesin
server/xxx/conf are read only on startup. Not sure that you
PeterJ,
Thanks for writing! My answers/reply inline:
1) You should not modify the configuration files in place while the application
server is running. Instead, copy the one you want to modify to a temporary
location, edit it there, and then copy back to deploy. Note that the files in
12 matches
Mail list logo
