-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mitesh,
thanks. I plan to reuse as much as possible. Jerome has emailed me and
has suggest that I should use get getIncompatibleSnifferTypes() to
invalidate the existing sniffer.
This is the correct approach right?
Regards
Chuk
On 06/01/11 09:03, Mitesh Meswani wrote:
> Hi Lee,
>
> You should be able to use a sniffer/deployer pair to wire up new
> deployer that can handle stuff from new archive. You should aim to
> reuse code from PersistenceUnitLoade and to do that you will need to
> construct PersistenceUnitDescriptor for your pu and provide and impl of
> ProviderContainerContractInfo.
>
> HTH,
> Mitesh
>
> On 1/5/2011 5:16 AM, Lee Chuk Munn wrote:
>> Hi
>>
>> I would like to get JPA support in my custom container. My container
>> deploys XAR file, which is basically a JAR file with a renamed suffix.
>>
>> What I would like to do is to get JPA supported in the XAR. I've been
>> looking at the JPA container source. The JPADeployer.java seem to only
>> recognize JavaEE application types.
>>
>> My question is that can I write another JPA sniffer (that looks for
>> META-INF/persistance.xml) for my application type?
>>
>> If I do this, will it clash with the existing JPASniffer? How do I
>> resolve this?
>>
>> Thanks
>>
>> Regards
>> Chuk
>>
>
- --
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/
iQEcBAEBAgAGBQJNJRbVAAoJEAnxPH9ZReNjy4EH/21Jm8pEadT3chOKAKcXgf5+
9eaSi/kkCKaHiEPujS1oIGjpfjupm8T4zGIj2lbXIjewHxoUtMPtXHOK7pzBVrOj
XtSVNeqN5C34vhfGsbac/YlxIosYZcHgR6tkcy3H1T2Fj8HKLxpx5Oy4cQ1bkNKq
yiZw1MyHc3gW3mjdeuBgf7diM7DUEDEUcRjY5Xd6to77PgNmYvo9E332XT0/H2rh
IlOiMyMQVf5H0ORGHY7WEAvfRsqLjJu6ubtszMZKUojmav7TXF1smxXEIztHX43h
hHCZfPtAECdrBSjqjYYS8SKwqnOmrhgWChQ5Ajq0CgjMgouzNpcu3SvHzW2BpzM=
=2Qz/
-----END PGP SIGNATURE-----