Depends how you are doing this stuff. If you are using makefiles that copy
a deploy.properties into the server-name/deploy directory (like our samples
do) every time you deploy, then this is the behavior you'll get.
TIP: I'd recommend avoiding the JMC's deploy tool until SP2 comes out, just
because it's unreliable except for simple tasks. Actually, the JMC may be
the one blowing away your deploy.properties. I don't usually use the JMC
for deploying EJBs.
When you define properties for an EJB in the ejb-jar.xml, those are all
bean-level configurations. Server-level configuration takes place in
deploy.properties. So there's an essential disconnect between the two (they
have different purposes). The ejb-jar.xml should only contain data that's
(more or less) app-server independent so that your EJB jars will be
portable. The deploy.properties file is a vendor-specific (Allaire/JRun)
properties file. So everything configured there is beyond what you can or
would configure for particular beans or for a particular bean app.
Other app server vendors often use a separate, vendor-specific XML file to
configure their server info (often at a container-level rather (or in
addition to) the server-level -- JRun/Ejipt currently combines the
functionality of container and server). We use deploy.properties and, to a
lesser extent for the EJB server, the other local and global properties
files.
There should only be one deploy.properties per server. So if you have
multiple EJB apps per server they have to be configured in the same
deploy.properties. Then that deploy.properties is used to generate
runtime.properties which is generated (and then left sloppily -- this is
another thing that will be fixed) in the deploy directory and then copied to
the runtime directory along with your jar(s) and the generated stubs and EJB
interface implementations.
Scott Stirling
Allaire Corporation
http://www.allaire.com/developer/jrunreferencedesk/
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 13, 2000 3:35 PM
> To: JRun-Talk
> Subject: Overwriting of deploy.properties
>
>
> Has anyone noticed that if you edit the deploy.properties
> directly that it
> will get overwritten, when there is a re-deploy? This is
> what I have
> found to be the case. Do you have to enter all properties for the
> deploy.properties in the JMC?
>
> When you define bean properties in an ejb_jar.xml are these properties
> supposed to show up in the runtime.properties? Currently
> they are not
> showing up in my runtime.properties or deploy.properties.
> They do show
> up if I go through the JMC and look at the beans properties.
> Is this
> normal?
>
> Thanks for any information,
>
> Adam
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
