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