Hi, Vince
Thanks for pointing this out. From what I remember in their ear
directory deployment case, their top level directory is named foo.ear
(instead of foo), so it would be recognized. If we find any problems
there, we could always modify the logic to recognize additional
subdirectories suffixes (.[ewrj]ar).
Thanks,
- Hong
>
> Thanks for the update.
>
> Will the _[ewrj]ar requirement cause problems for directory deployment
> from MyEclipse? Last I heard, they were using directories with
> .[ewrj]ar suffixes when they create an exploded ear.
>
> vbk
>
>
> Hong Zhang wrote:
>
>> Hi, Vince
>> I have checked in the support for the optional application.xml:
>> 1. For archive deployment, the suffix .ear will be used to
>> recognize the archive.
>> 2. For directory deployment, the sub modules are expected to be in
>> subdirectory forms of "_war", "_rar" etc.We had to add this rule as
>> there is just no good way to tell whether it's an ear or not in
>> directory deployment case. We could also add a --type option in the
>> deploy command to remove the ambiguity if desired.
>>
>> Thanks,
>>
>> - Hong
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>