I would expect that if the file name varies due to a timestamp or the
name of a target, etc., then the files for that function would go in a
subdirectory. If the generated file always has the same name, then a
subdirectory would not be needed.
Thoughts?
Tom
On 9/30/2010 9:36 AM, Jennifer Chou wrote:
> On 9/30/2010 3:26 PM, Tom Mueller wrote:
>> I haven't seen any response to this other than from Kshitiz.
>>
>> Chris, Jennifer, do you think it would be more appropriate to
>> generate backup and sync-bundles into the generated directory by
>> default since that is where other GlassFish generated files go?
> This sounds good to me.
>>
>> It seems inconsistent to me to look in generated for one type of file
>> and then in special purpose directories for the other files.
>>
>> There are also subdirectories under generated (ejb, jsp, policy,
>> xml). Maybe sync and backups should be subdirectories under generated?
> Either is fine with me - with or without the subdirectory.
>
> Thanks,
> Jennifer
>>
>> Tom
>>
>>
>> On 9/27/2010 11:00 AM, Kshitiz Saxena wrote:
>>> I have used /*generated*/ directory as same was used in GlassFish
>>> 2.1.1. In many cases, user will provide absolute path specifying the
>>> directory where load-balancer xml file need to be created.
>>>
>>> Since generated directory is used for files generated/exploded by
>>> GlassFish, it is best to use the same for load-balancer as well.
>>>
>>> Thanks,
>>> Kshitiz
>>>
>>> On Monday 27 September 2010 07:24 PM, Tom Mueller wrote:
>>>> We have several commands that save files on the DAS within the
>>>> domain directory tree. Here is a (partial?) list and where the
>>>> files are written:
>>>>
>>>> Command
>>>> Output file location
>>>> backup-domain <domaindir>/backups
>>>> export-http-lb-config
>>>> <domaindir>/generated
>>>> collect-log-files
>>>> no default - --outputfilepath is required param - file is saved on
>>>> DAS, param is absolute pathname, no option to save locally (--retrieve)
>>>> export-sync-bundle
>>>> <domaindir>/sync
>>>>
>>>>
>>>> I'm just checking to make sure this is ok when looking at this
>>>> across all of the commands.
>>>>
>>>> backup-domain and export-sync-bundle are creating their own
>>>> directory for this, while export-http-lb-config is reusing a
>>>> directory that is already there. Should the former commands use the
>>>> generated directory too? Should export-http-lb-config create its
>>>> own directory? Should collect-log-files have a default place within
>>>> the domain tree to put the files?
>>>>
>>>> Thoughts?
>>>> Tom
>>>>
>