Sahoo,
Thanks. Also, a few more questions.
1. Web Component Assertions
(
http://java.sun.com/j2ee/avk/5.0/assertions/web_assertions.html )
contains a list of assertions that being with "runtime." (e.g.
runtime.ASCache ).
Are all of these assertions verified by deploy --verify ?
2. Each of the runtime.* assertions are marked as "Not yet mapped".
What does
that mean ?
Sekhar
Sahoo wrote:
> Sekhar,
>
> I have to look at exactly what the test does, but in general, the
> difference between --deploy mode (a.k.a. backend verifier) and
> standalone invocation of verifier is that the latter one does not have
> full access to the server runtime unlike the former one. So, there are
> certain extra resources that can be visible to backend verifier which
> can affect the test result.
>
> Thanks,
> Sahoo
>
> Sekhar Vajjhala wrote:
>
>> I am seeing different results on the same ear file.
>> - verifier.bat ear-file fails verification
>> on AS-WEB property.
>> see attachment - simplejsp.ear.txt
>>
>> - deploy --verify ear-file passes verification
>> and can be deployed successfully.
>> see attachment - simplejsp20080611021044.txt
>>
>> Why is there a difference between the two
>> verification methods ?
>>
>> Sekhar
>>
>> ------------------------------------------------------------------------
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>