Hi Hong
> I don't think this is anything specific to the singleton ejb, it just
> happened to be the first application you tried to deploy after you
> installed the new installation which contains a command option change.
Yeah.
>
> The deployment dev tests do not contain any singleton ejb test case
> (these tests focus on testing different mechanisms of deployment but not
> all the different ejb types). The ejb deployment dev tests do contain
> the singleton ejb test cases (in
> appserv-tests/devtests/ejb/ejb31/singleton), and their hudson job
> (http://hudson-sca.us.oracle.com/job/ejb-devtests-trunk/) shows all the
> tests are passing.
Thanks your comments, I see.
>use/cache the new command option signature. I assume the deploy command
>executed successfully despite the message?
Yes, the deploy command can execute and work successfully.
In addition, I agree with Tom's idea.
Thanks
--Tang
>
> Thanks,
>
> - Hong
>
> On 10/15/2012 9:05 AM, lvsongping wrote:
>> Dear Tang:
>>
>> I think there's no test cases exists in dev-tests to test the special cases
>> about singalton.
>>
>> BTW: I have run the dev tests this morning and all of them can be passed.
>>
>> Best regards
>> -Jeremy
>>
>> -----Original Message-----
>> From: Tang Yong [mailto:tangyong_at_cn.fujitsu.com]
>> Sent: Monday, October 15, 2012 9:38 PM
>> To: dev_at_glassfish.java.net; Lv Songping
>> Cc: 'Hong Zhang'; 'Sahoo'
>> Subject: Re: About singleton ejb's deployment
>>
>> Hi Jeremy,
>>
>> Thanks your confirmation and I want to ask whether dev tests contained
>> such a singleton ejb's deployment case or not?
>>
>> From your confirmation, it seemed to have a regression on deployment.
>>
>> Thanks!
>> --Tang
>>
>> lvsongping wrote:
>>> Dear Tang：
>>>
>>> I have tried to reproduce it and found it can be reproduced in the
>>> latest version of GFV4.
>>>
>>> I also tried to reproduce this phenomenon in the gf trunk before
>>> October 9,
>>> 2012 and found
>>> it can't be reproduced. Anyway, I also tried to deploy any other kind
>>> of ejb samples, such as stateless ejb sample. The similar error
>>> messages can't be thrown out.
>>>
>>> According to the phenomenon I have referred above, I think it may be
>>> caused by any changes about the trunk between October 12, 2012 and
>>> October 15, 2012 and it could be a bug about deployment.
>>>
>>> Hong:
>>> What's your opinion about this phenomenon?
>>>
>>> Best regards
>>> -Jeremy
>>>
>>> -----Original Message-----
>>> From: Tang Yong [mailto:tangyong_at_cn.fujitsu.com]
>>> Sent: Monday, October 15, 2012 8:53 PM
>>> To: Hong Zhang; dev_at_glassfish.java.net
>>> Cc: Sahoo
>>> Subject: About singleton ejb's deployment
>>>
>>> Hi Hong
>>> CC: Sahoo,
>>>
>>> While investigating GLASSFISH-19152, there is a problem about
>>> singleton ejb's deployment and want to discuss with you and deployment
>> team.
>>> While I execute the following command using the attachment(14/Oct/12
>>> 's
>>> version) of GLASSFISH-19152, the following result happened.
>>>
>>> asadmin deploy D:\singleton-osgi\target\singleton-osgi-1.0.jar
>>> Command signature of deploy command was changed. Re executing with new
>>> metadata.
>>> Application deployed with name singleton-osgi-1.0.Command deploy
>>> executed successfully.
>>>
>>> asadmin undeploy singleton-osgi-1.0
>>> Command signature of undeploy command was changed. Re executing with
>>> new metadata.
>>> Command undeploy executed successfully.
>>>
>>> I felt suprised to "Command signature of deploy command was changed.
>>> Re executing with new metadata.", so I want to ask you whether
>>> deployment command usage has a change or not?
>>>
>>> BTW: I used my building snapshot based today's gf trunk.
>>>
>>> Thanks!
>>> --Tang
>>>
>>>
>>>
>
>