Hi, Felipe
I am not sure about the admin console part, but the autodeployment of
the ear should work. How did you package your ear file, is there an
application.xml (this is optional), are sub modules ended with the
expected suffix? If you can share your ear file or provide a simple test
case, I can try from my end. Our QL tests contain ear test cases, so the
basic support of the ear should still function properly.
Thanks,
- Hong
Felipe Gaúcho wrote:
>how can I deploy an EAR file to V3 ?
>
>in the admin console ther eis only a web application option, and if I
>copy the EAR to the autodeploy folder:
>
>#|2009-06-13T22:47:25.072+0200|INFO|glassfish|javax.enterprise.system.tools.deployment|_ThreadID=18;_ThreadName=Thread-3;|[AutoDeploy]
>Selecting file /home/fgaucho/dev/glassfishv3-prelude/glassfish/domains/domain1/autodeploy/footprint-service-ear-1.0-SNAPSHOT.ear
>for autodeployment.|#]
>
>[#|2009-06-13T22:47:25.094+0200|FINE|glassfish|javax.enterprise.system.util|_ThreadID=18;_ThreadName=Thread-3;ClassName=null;MethodName=null;/home/fgaucho/dev/glassfishv3-prelude/glassfish/domains/domain1/applications/footprint-service-ear-1.0-SNAPSHOT;|UTIL6049:
>Attempt to delete
>/home/fgaucho/dev/glassfishv3-prelude/glassfish/domains/domain1/applications/footprint-service-ear-1.0-SNAPSHOT
>failed; the file is reported as non-existent|#]
>
>[#|2009-06-13T22:47:25.165+0200|FINE|glassfish|javax.enterprise.system.util|_ThreadID=18;_ThreadName=Thread-3;ClassName=null;MethodName=null;|No
>local string for deploy.unknownmoduletpe|#]
>
>[#|2009-06-13T22:47:25.165+0200|SEVERE|glassfish|javax.enterprise.system.core|_ThreadID=18;_ThreadName=Thread-3;|Module
>type not recognized|#]
>
>[#|2009-06-13T22:47:25.168+0200|WARNING|glassfish|javax.enterprise.system.tools.deployment|_ThreadID=18;_ThreadName=Thread-3;|[AutoDeploy]
>Autodeploy failed :
>/home/fgaucho/dev/glassfishv3-prelude/glassfish/domains/domain1/autodeploy/footprint-service-ear-1.0-SNAPSHOT.ear.|#]
>
>
>
>