What is the 3rd part JSON library you're using? What is the error your
receiving on deployment?
I assume you're not getting any errors on compile...
Steve
On Tue, Aug 10, 2010 at 7:33 AM, Martin, Ray <armart3_at_tycho.ncsc.mil> wrote:
> Using netbeans 6.8
>
>
>
> Have been working in glassfish v2 yesterday switched to v3 wow. (big
> changes in the JPA.)
>
>
>
> After many hours of work, got all the errors out of the EJBModule project.
>
> It deploys.
>
> It starts when commanded from the SOAP interface.
>
> It crashes as soon as a third party library is called JSON in this case.
> Though the oracle library must have been seen because database connections
> are working. The JSON jar has other dependencies like commons-*.
>
>
>
> All third party jars have been packaged into the EJBModule jar.
>
>
>
> I built the project in SE using JPA and the third party jars runs great.
>
> I built a similar project as a web app where the EJBs, JPA, and third party
> jars are used runs great.
>
>
>
> Wow am I sorry that I changed to v3.
>
>
>
> I have searched and searched I cannot be the only guy who has this
> problem but, I can find no solution.
>
>
>
> Thought maybe it was netbeans fault so, deployed using admin console
> same problem. So, I guess it is a packaging problem??? A manifest
> problem??? wow
>
>
>