NetBeans Platform as enterprise application deployed from glassfish

[MailingLists-22]

Hy all of you,

I'm looking for resources that could help me to deploy a netbeans platform and its modules from a GF3.1.1 server.
I found some resources and the entry of all of them could be found here I think : http://netbeans-org.1045718.n5.nabble.com/Netbeans-Platform-on-top-of-GFv3-enterprise-application-client-no-way-td2970680.html

My problem is all those resources looks very old and I'm wondering if somebody succeed in doing this with the recent release?

Thanks for your help

[MailingLists-22]

Hy,

Thank you for answering so fast.
What I would like to is to have both benefits :
- Benefits from the NB platform for GUI and RCP
- Benefits from EJB
- Benfits from the deployment from a GF server

So, if my french level of english let me understand well, I agree with your proposal.
To be sure I'll formulate it in another way.

I would like to have a NetBeans RCP app in a EA project instead of the usual JavaSwing App Client.
Am I explaining well my needs?

regards


 make me

Le 20/02/2012 19:01, Sahoo a écrit :

So you want to build an RCP app and embed GlassFish ACC there?

On Monday 20 February 2012 10:56 PM, Florent THOMAS wrote:

Hy all of you,

I'm looking for resources that could help me to deploy a netbeans platform and its modules from a GF3.1.1 server.
I found some resources and the entry of all of them could be found here I think : http://netbeans-org.1045718.n5.nabble.com/Netbeans-Platform-on-top-of-GFv3-enterprise-application-client-no-way-td2970680.html

My problem is all those resources looks very old and I'm wondering if somebody succeed in doing this with the recent release?

Thanks for your help

[MailingLists-22]

Hy timon,

Thanks for answering. Below my answers.

Le 20/02/2012 22:48, Timon Veenstra a écrit :
>> What I would like to is to have both benefits :
>> - Benefits from the NB platform for GUI and RCP
>> - Benefits from EJB
>> - Benfits from the deployment from a GF server
>>
> You can distribute your application through webstart which could be
> served by your GlassFish application server.
> You can also use your GlassFish server as central backend for your
> rich client frontend.
Wonderful
> Using EE functionality like EJB will probably require some tricks but
> is probably possible.
Ouch, I don't really like "tricks" that lowering the benefits of the
solutions
> I have successfully used this kind of setup in the past (with spring
> instead of ejb and on oracle application server) .
Ok,
>> I would like to have a NetBeans RCP app in a EA project instead of the usual
>> JavaSwing App Client.
>> Am I explaining well my needs?
> If you mean to say you want to use a netbeans rcp application as
> frontend for your glassfish backend, yes :)
> Though your netbeans app will not be "in" another project.
> You can develop the frontend in a different project from the backend
> and use a shared set of code to communicate.
Here, I don't understand well. You say that netbeans app will not be IN
but you also said that the frontend (Netbeans RCP) will be in a
different project.

Another question, when you're talking about a shered set of code to
communicate, do you means for example that it won't be possible to
inject EJB by annotations in the nbm modules?

Thanks for sharing your expertise.
> Cheers,
> Timon
Regards,

Florent

[MailingLists-22]

Hy Timon

Thanks for your prcise worklow. We will try to get in production thanks to that.
I'll let you know.

regards

Le 21/02/2012 13:13, Timon Veenstra a écrit :

Using EE functionality like EJB will probably require some tricks but
is probably possible.

Ouch, I don't really like "tricks" that lowering the benefits of the
solutions

Tricks as in you might need to do some trial and error configuration
http://wiki.netbeans.org/DevFaqCallEjbFromNbm

If you mean to say you want to use a netbeans rcp application as
frontend for your glassfish backend, yes :)
Though your netbeans app will not be "in" another project.
You can develop the frontend in a different project from the backend
and use a shared set of code to communicate.

Here, I don't understand well. You say that netbeans app will not be IN but
you also said that the frontend (Netbeans RCP) will be in a different
project.

There are projects as in I want to develop software with a certain purpose and
there are netbeans project which could also be seen as modules within
a software development project.
Generally in Netbeans projects are the latter and usually grouped by
technology (rcp module project, php project, JEE web project, etc)

myProject-model -> plain java project containing beans (with ejb annotations )
myProject-backend -> java ee application (war/ear) to be deployed on
GlassFish, has model as dependency
myProject-frontend -> netbeans RCP application, has model as dependency

Another question, when you're talking about a shered set of code to
communicate, do you means for example that it won't be possible to inject
EJB by annotations in the nbm modules?

To use a bean in your code, you need to know its definition. This is
the shared piece of code, model definitions.
You can get instances of those model definitions by EJB injection.