-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
HI Hong,
thanks for the reply.
I'll try to work around it by faking a servlet.
Thanks
Regards
Chuk
On 17/04/11 08:55, Hong Zhang wrote:
> Hi, Chuk
> No, there is no ordering of the deployers. What happened in the
> stack trace (DolProvider) is that the GlassFish tried to process the
> JavaEE related metadata in the application and found none. Even though
> the GlassFish allows the plug in of extension container, we do assume
> the application still contains certain JavaEE components in addition to
> the extension components (except for special case like OSGI module). The
> GlassFish currently does not support deployment of pure extension module.
> - Hong
>
> On 4/16/2011 2:57 AM, Lee Chuk Munn wrote:
>> Hi
>>
>> I'm in the process of implementing JPA for my container (XARContainer)
>> which is not a JavaEE application. I've got XARContainer running, viz
>> this is the container that runs the actual component.
>>
>> I have a separate JPA container XJPAContainer, can't reuse existing
>> cause the app is not JavaEE, which handles JPA.
>>
>> I have indicated in my both my XJPASniffer and XARSniffer that its not
>> compatible with 'org.glassfish.persistence.jpa.JPASniffer'
>> (getIncompatibleSnifferTypes()).
>>
>> When I deploy my app, XJAPSniffer.handles() returns true. I've also
>> added some log statement which shows that XJPAContainer and XJPADeployer
>> have been instantiated by Glassfish. But for some reason,
>> XJPADeployer.prepare() was never called. Instead Glassfish is treating
>> my app as a JavaEE application so I'm getting an exception (see end of
>> this mail).
>>
>> My question is is there some sort of ordering for Deployers? Or is there
>> a way to get GF to give preferences to my deployer?
>>
>> Thanks
>>
>> Regards
>> Chuk
>>
>>
>>
>> [#|2011-04-16T14:23:20.482+0800|SEVERE|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=54;_ThreadName=Thread-1;|Archive
>>
>> [jpatest] was deployed as a Java EE archive while it does not contain
>> any valid Java EE components. Please check the packaging of the archive.
>> java.lang.RuntimeException: Archive [jpatest] was deployed as a Java EE
>> archive while it does not contain any valid Java EE components. Please
>> check the packaging of the archive.
>> at
>> org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:143)
>>
>> at
>> org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:93)
>>
>> at
>> com.sun.enterprise.v3.server.ApplicationLifecycle.loadDeployer(ApplicationLifecycle.java:826)
>>
>> at
>> com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:768)
>>
>> at
>> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:368)
>>
>> at
>> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
>>
>> at
>> org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:370)
>>
>> at
>> com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355)
>>
>>
- --
In software systems, it is often the early bird that makes the worm.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNqm1mAAoJEAnxPH9ZReNjeyIH/2HEsaE8SxZ9t0/LN4TPR55E
iX2AT0aXPHilOu3WsGO006lI8X36ZODgPfWZat4sv4p26iIuWx9RXbKmmx7AVkI/
bLCExce7o7B+0NWT4XiJ3DjPDbuHLTzWPsU7xenZWb7SOj1GAhGSwboPMAZbyTC1
xTVf/NteZtShk6E9IP/nTqSEcHwLWut0vNYTTHxrMpZ7SIDkX2mNZqqtM9ZFCwWo
5JfBoRBqO1jntD9/pX7WZlk1vTqUOHN096nwNjf4EPaBYcYwW64mbdPprLjg8QgG
dUsUWy7rpNcwNG7iReNxnNAy48dXvq0BR23lLBWS9rVircbuwZHQ94mRBgin7jI=
=JJwb
-----END PGP SIGNATURE-----