[idea] Application .info directory

[Dain Sundstrom <da...@iq80.com>]

I think I'm finally over my Titan Quest: Immortal Throne bender, and  
was thinking about a problem David mentioned to me the other day...

When we deploy an application we create a meta-data complete ejb- 
jar.xml file amongst other artifacts in memory.  This data is very  
useful for debugging applications but takes up a lot of memory (and  
is generally just a pain to track).  My idea at the time was to just  
dump the file to the temp directory and keep around a pointer to the  
location, but that is problematic because systems normally have  
scripts that clean the temp dir and to be friendly, you want to  
delete the file on shutdown.  So here is my improved idea:

For each application we deploy we create a .info directory beside  
it.  For example, if we deploy foo.ear, we create a foo.ear.info (or  
foo.info) directory.  This directory would contain the meta-data  
complete ejb-jar.xml file in addition to the cmp to jpa mappings file  
and any other information we think might be helpful to debug/admin  
the application.

WDYT?

-dain

Re: [idea] Application .info directory

[Mohammad Nour El-Din <no...@gmail.com>]

+1 on the logger.info idea

On 8/9/07, Karan Malhi <ka...@gmail.com> wrote:
>
> I wanted to comment on this earlier, but did not understand the
> difference between a "meta-data complete ejb-jar.xml" and a regular
> "ejb-jar.xml". So , I dont know what extra information is going to be
> in the "meta-data complete ejb-jar.xml" , but since it is going to
> help admins, I think it is a really neat idea to create the .info
> files . I like the file name as "foo.ear.info", instead of "foo.info".
> We could also then use WebAdmin to show these files.
>
> I like Mohammad's idea of creating our own temp and putting the .info
> files under that. This way, I can also put a logger.info under temp,
> which will help admins troubleshoot any logging issues.
>
>
>
> On 8/9/07, Mohammad Nour El-Din <no...@gmail.com> wrote:
> > Sounds good, but I suggest to have our own temp dir created under the
> base
> > dir of OEJB, just like what JBoss and Tomcat do. WDYT?
> >
> > On 8/9/07, Manu George <ma...@gmail.com> wrote:
> > >
> > > Sounds good. Will certainly be useful for debugging
> > >
> > > Regards
> > > Manu
> > >
> > > On 8/9/07, Dain Sundstrom <da...@iq80.com> wrote:
> > > > I think I'm finally over my Titan Quest: Immortal Throne bender, and
> > > > was thinking about a problem David mentioned to me the other day...
> > > >
> > > > When we deploy an application we create a meta-data complete ejb-
> > > > jar.xml file amongst other artifacts in memory.  This data is very
> > > > useful for debugging applications but takes up a lot of memory (and
> > > > is generally just a pain to track).  My idea at the time was to just
> > > > dump the file to the temp directory and keep around a pointer to the
> > > > location, but that is problematic because systems normally have
> > > > scripts that clean the temp dir and to be friendly, you want to
> > > > delete the file on shutdown.  So here is my improved idea:
> > > >
> > > > For each application we deploy we create a .info directory beside
> > > > it.  For example, if we deploy foo.ear, we create a foo.ear.info (or
> > > > foo.info) directory.  This directory would contain the meta-data
> > > > complete ejb-jar.xml file in addition to the cmp to jpa mappings
> file
> > > > and any other information we think might be helpful to debug/admin
> > > > the application.
> > > >
> > > > WDYT?
> > > >
> > > > -dain
> > > >
> > >
> >
> >
> >
> > --
> > Thanks
> > - Mohammad Nour
> >
>
>
> --
> Karan Singh Malhi
>



-- 
Thanks
- Mohammad Nour

Re: [idea] Application .info directory

[Karan Malhi <ka...@gmail.com>]

I wanted to comment on this earlier, but did not understand the
difference between a "meta-data complete ejb-jar.xml" and a regular
"ejb-jar.xml". So , I dont know what extra information is going to be
in the "meta-data complete ejb-jar.xml" , but since it is going to
help admins, I think it is a really neat idea to create the .info
files . I like the file name as "foo.ear.info", instead of "foo.info".
We could also then use WebAdmin to show these files.

I like Mohammad's idea of creating our own temp and putting the .info
files under that. This way, I can also put a logger.info under temp,
which will help admins troubleshoot any logging issues.



On 8/9/07, Mohammad Nour El-Din <no...@gmail.com> wrote:
> Sounds good, but I suggest to have our own temp dir created under the base
> dir of OEJB, just like what JBoss and Tomcat do. WDYT?
>
> On 8/9/07, Manu George <ma...@gmail.com> wrote:
> >
> > Sounds good. Will certainly be useful for debugging
> >
> > Regards
> > Manu
> >
> > On 8/9/07, Dain Sundstrom <da...@iq80.com> wrote:
> > > I think I'm finally over my Titan Quest: Immortal Throne bender, and
> > > was thinking about a problem David mentioned to me the other day...
> > >
> > > When we deploy an application we create a meta-data complete ejb-
> > > jar.xml file amongst other artifacts in memory.  This data is very
> > > useful for debugging applications but takes up a lot of memory (and
> > > is generally just a pain to track).  My idea at the time was to just
> > > dump the file to the temp directory and keep around a pointer to the
> > > location, but that is problematic because systems normally have
> > > scripts that clean the temp dir and to be friendly, you want to
> > > delete the file on shutdown.  So here is my improved idea:
> > >
> > > For each application we deploy we create a .info directory beside
> > > it.  For example, if we deploy foo.ear, we create a foo.ear.info (or
> > > foo.info) directory.  This directory would contain the meta-data
> > > complete ejb-jar.xml file in addition to the cmp to jpa mappings file
> > > and any other information we think might be helpful to debug/admin
> > > the application.
> > >
> > > WDYT?
> > >
> > > -dain
> > >
> >
>
>
>
> --
> Thanks
> - Mohammad Nour
>


-- 
Karan Singh Malhi

Re: [idea] Application .info directory

[Mohammad Nour El-Din <no...@gmail.com>]

Sounds good, but I suggest to have our own temp dir created under the base
dir of OEJB, just like what JBoss and Tomcat do. WDYT?

On 8/9/07, Manu George <ma...@gmail.com> wrote:
>
> Sounds good. Will certainly be useful for debugging
>
> Regards
> Manu
>
> On 8/9/07, Dain Sundstrom <da...@iq80.com> wrote:
> > I think I'm finally over my Titan Quest: Immortal Throne bender, and
> > was thinking about a problem David mentioned to me the other day...
> >
> > When we deploy an application we create a meta-data complete ejb-
> > jar.xml file amongst other artifacts in memory.  This data is very
> > useful for debugging applications but takes up a lot of memory (and
> > is generally just a pain to track).  My idea at the time was to just
> > dump the file to the temp directory and keep around a pointer to the
> > location, but that is problematic because systems normally have
> > scripts that clean the temp dir and to be friendly, you want to
> > delete the file on shutdown.  So here is my improved idea:
> >
> > For each application we deploy we create a .info directory beside
> > it.  For example, if we deploy foo.ear, we create a foo.ear.info (or
> > foo.info) directory.  This directory would contain the meta-data
> > complete ejb-jar.xml file in addition to the cmp to jpa mappings file
> > and any other information we think might be helpful to debug/admin
> > the application.
> >
> > WDYT?
> >
> > -dain
> >
>



-- 
Thanks
- Mohammad Nour

Re: [idea] Application .info directory

[Manu George <ma...@gmail.com>]

Sounds good. Will certainly be useful for debugging

Regards
Manu

On 8/9/07, Dain Sundstrom <da...@iq80.com> wrote:
> I think I'm finally over my Titan Quest: Immortal Throne bender, and
> was thinking about a problem David mentioned to me the other day...
>
> When we deploy an application we create a meta-data complete ejb-
> jar.xml file amongst other artifacts in memory.  This data is very
> useful for debugging applications but takes up a lot of memory (and
> is generally just a pain to track).  My idea at the time was to just
> dump the file to the temp directory and keep around a pointer to the
> location, but that is problematic because systems normally have
> scripts that clean the temp dir and to be friendly, you want to
> delete the file on shutdown.  So here is my improved idea:
>
> For each application we deploy we create a .info directory beside
> it.  For example, if we deploy foo.ear, we create a foo.ear.info (or
> foo.info) directory.  This directory would contain the meta-data
> complete ejb-jar.xml file in addition to the cmp to jpa mappings file
> and any other information we think might be helpful to debug/admin
> the application.
>
> WDYT?
>
> -dain
>

Re: [idea] Application .info directory

[Karan Malhi <ka...@gmail.com>]

> For each application we deploy we create a .info directory beside
> it.  For example, if we deploy foo.ear, we create a foo.ear.info (or
> foo.info) directory.  This directory would contain the meta-data
> complete ejb-jar.xml file in addition to the cmp to jpa mappings file
> and any other information we think might be helpful to debug/admin
> the application.
>
> WDYT?
>
> -dain
>
Dain,

Are you going to implement this? I really liked the idea

-- 
Karan Singh Malhi