| WTP 1.0 No EJB Client Jar Module created [message #154190] |
Thu, 29 December 2005 13:45  |
Eclipse User |
|
|
|
Originally posted by: barrettsontour.yahoo.co.uk
When I create a New EJB Project and the checkbox "Create an EJB Client JAR
Module to hold the client interfaces and classes" is checked no Client
project and/or Client jar is created.
An error is displayed complaining about the ejb-jar.xml, the problem
appears to be as no <enterprise-beans> have yet been defined (which they
wouldn't yet). Maybe this error prevents the creation of the client
project though?
Once I create EJB's in the project the ejb-jar.xml error disappears and I
am able to deploy the EJB to Weblogic Server v8.1 successfully. I still
have no client project or jar however.
In earlier versions I created the EJB project and EJB all in one go and
both projects were created.
Is there a way to specify the generation of the EJB Client Jar after a
project has been created?
Also, is there a way to specify the creation of of serialVersionUID in
XDoclet for the generated EJB?
Thanks.
|
|
|
| Re: WTP 1.0 No EJB Client Jar Module created [message #154299 is a reply to message #154190] |
Fri, 30 December 2005 12:40  |
| Eclipse User |
|
|
|
Originally posted by: wknauf_NO_._INSIDE_hg-online.de
Hi Steve,
for the client jar problem: https://bugs.eclipse.org/bugs/show_bug.cgi?id=122272
You have the create the enterprise app without an ejb project and add the ejb
module later (there you can specify the creation of a client jar).
If you really need client jar projects take a look at this (a bug with client
jar projects and entity beans, which is a real stopper, in my opinion at least):
https://bugs.eclipse.org/bugs/show_bug.cgi?id=122274
Best regards
Wolfgang
Steve Barrett wrote:
> When I create a New EJB Project and the checkbox "Create an EJB Client
> JAR Module to hold the client interfaces and classes" is checked no
> Client project and/or Client jar is created.
>
> An error is displayed complaining about the ejb-jar.xml, the problem
> appears to be as no <enterprise-beans> have yet been defined (which they
> wouldn't yet). Maybe this error prevents the creation of the client
> project though?
>
> Once I create EJB's in the project the ejb-jar.xml error disappears and
> I am able to deploy the EJB to Weblogic Server v8.1 successfully. I
> still have no client project or jar however.
>
> In earlier versions I created the EJB project and EJB all in one go and
> both projects were created.
>
> Is there a way to specify the generation of the EJB Client Jar after a
> project has been created?
>
> Also, is there a way to specify the creation of of serialVersionUID in
> XDoclet for the generated EJB?
>
> Thanks.
>
|
|
|
| Re: WTP 1.0 No EJB Client Jar Module created [message #154307 is a reply to message #154299] |
Fri, 30 December 2005 13:40 |
| Eclipse User |
|
|
|
Originally posted by: barrettsontour.yahoo.co.uk
Hi Wolfgang,
Thanks for the reply.
I also managed to get the Client project created if I specified "Add
project to Ear" when using the New EJB Project Wizard.
Unfortunately I can then no longer deploy to WLS 8.1. as when "Add and
Remove Projects" against the WLS 8.1 server is used and the EAR project is
selected the wizard declares that the "Module type is not compatible". If
you ignore this message and add the project anyway the
NullPointerException below is thrown during the deployment.
If I however use eclipse to export either the EJB Project to an ejb-jar or
the EAR project to an ear archive I can successfully deploy either of
these to WLS 8.1 outside of eclipse.
java.lang.NullPointerException
at
org.eclipse.jst.server.generic.core.internal.ServerTypeDefin itionUtil.getPublisherID(ServerTypeDefinitionUtil.java:85)
at
org.eclipse.jst.server.generic.core.internal.GenericServerBe haviour.removeFromServer(GenericServerBehaviour.java:117)
at
org.eclipse.jst.server.generic.core.internal.GenericServerBe haviour.publishModule(GenericServerBehaviour.java:80)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.pu blishModule(ServerBehaviourDelegate.java:658)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.pu blishModules(ServerBehaviourDelegate.java:738)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.pu blish(ServerBehaviourDelegate.java:596)
at org.eclipse.wst.server.core.internal.Server.doPublish(Server .java:799)
at org.eclipse.wst.server.core.internal.Server.publish(Server.j ava:788)
at
org.eclipse.wst.server.core.internal.PublishServerJob.run(Pu blishServerJob.java:145)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
!SUBENTRY 1 org.eclipse.wst.server.core 4 0 2005-12-30 20:58:13.250
!MESSAGE Could not publish to the server.
!STACK 0
Regards,
Steve
|
|
|
| Re: WTP 1.0 No EJB Client Jar Module created [message #154315 is a reply to message #154307] |
Fri, 30 December 2005 14:19 |
| Eclipse User |
|
|
|
Originally posted by: wknauf_NO_._INSIDE_hg-online.de
Hi Steve,
only a vague guess: do some module versions mismatch ? WLS 8.1 seems to be only
J2EE compliant. Maybe you picked some wrong J2EE version in one of your modules
? Goto to the project properties, the facets tell you what Java/J2EE versions
are used. Or check the J2EE version declarations in your deployment descriptors.
I hope this helps
Wolfgang
Steve Barrett wrote:
> Hi Wolfgang,
>
> Thanks for the reply.
>
> I also managed to get the Client project created if I specified "Add
> project to Ear" when using the New EJB Project Wizard.
>
> Unfortunately I can then no longer deploy to WLS 8.1. as when "Add and
> Remove Projects" against the WLS 8.1 server is used and the EAR project
> is selected the wizard declares that the "Module type is not
> compatible". If you ignore this message and add the project anyway the
> NullPointerException below is thrown during the deployment.
>
> If I however use eclipse to export either the EJB Project to an ejb-jar
> or the EAR project to an ear archive I can successfully deploy either of
> these to WLS 8.1 outside of eclipse.
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.01774 seconds
] 
Search
Help
Register
Login
Home
