Thanks for all the comments and possible reasons.
http://jetbrains.net/jira/browse/JEEAS-180 has been already filed.
I added a pointer to this thread as well.
Thanks,
-Arun
Tim Quinn wrote:
> Hi, Arun.
>
> The deploy operation (in v2 and v3) has allowed the user to specify
> whether to "force" the deployment of an app if that app name is already
> deployed. In v3 currently the default is "force=false" which means you
> want the server to reject attempts to redeploy an app. (The thinking is
> that this is safer - that the user has to take explicit action to
> replace a previously-deployed app of the same name.)
>
> In v2 the default (in the CLI at least) was force=true. You might have
> them check this aspect of their plug-in explicitly, although the problem
> could be something else entirely.
>
> - Tim
>
> Arun Gupta wrote:
>> Ok, thanks for the confirmation.
>>
>> I'll file a bug on their JIRA once it comes back live, it's painfully
>> slow right now.
>>
>> -Arun
>>
>> Kedar Mhaswade wrote:
>>> I believe this to be an Intellij plugin bug. It's not calling
>>> redeploy sequence,
>>> apparently.
>>>
>>> -Kedar
>>>
>>> Arun Gupta wrote:
>>>> Deploying a Web application from IntelliJ on GlassFish works fine.
>>>> But re-deploying always gives the following error:
>>>>
>>>> [#|2008-07-09T12:15:56.499-0700|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=18;_ThreadName=httpWorkerThread-4848-1;_RequestID=0d06f54e-b551-45e6-be37-4ec7b65a9136;|ADM1082:Creating
>>>> the application reference failed - Detailed Message:
>>>> com.sun.enterprise.deployment.backend.IASDeploymentException:
>>>> Application reference GlassFishWSWeb already exists in server
>>>> instance server.
>>>> at
>>>> com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.getAndValidateDeploymentTarget(DeploymentServiceUtils.java:1212)
>>>>
>>>> at
>>>> com.sun.enterprise.deployment.phasing.PEDeploymentService.associate(PEDeploymentService.java:452)
>>>>
>>>> at
>>>> com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.createApplicationReference(ApplicationsConfigMBean.java:693)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>> com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:375)
>>>>
>>>> at
>>>> com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358)
>>>>
>>>> at
>>>> com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464)
>>>>
>>>>
>>>> If the application is explicitly undeployed and deployed, then
>>>> everything works.
>>>>
>>>> Any clues before I file an issue in IntelliJ's JIRA ?
>>>>
>>>> -Arun
>>>
>>> ---------------------------------------------------------------------
>>> 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
>
--
Application Platform, Sun Microsystems, Inc.
Blog: http://blogs.sun.com/arungupta