Hi Kristian,
You are trying to do things I haven't tried yet, so I canot help you
here.
However, I tried something that sounds similar. I have succesfully setup
some projects to build and deploy JBI/CASA applications. Those are
applications that can be deployed on OpenESB/GlassFish ESB. All the
necessary classes and jars are nowhere to be found on the web.
So I dug into the NetBeans ant scripts to figure out which jars are
needed and installed them into our local Maven repository and told
Nexus to make them available. I simply took the ones that ship with
NetBeans :-)
NetBeans also does a lot of checking, xml generation and other stuff to
build the jars that will be deployed and it uses ant for that. So I
included the maven antrun plugin in my poms and used that to copy the
NetBeans behaviour. The hardest part was to figure out how to make the
jars in the Maven repository available to ant through maven but even
that turned out to be not very difficult.
Using this approach we have succesfully been building and deploying our
projects from Hudson to GlassFish ESB version 2. If you need some help
with this, or have specific questions, you'll know where to find me.
HTH, Wouter
On Fri, Feb 04, 2011 at 10:01:51AM +0100, Kristian Rink wrote:
> Hi Wouter;
>
> and thanks a bunch for giving a hand again, much appreciated. ;)
>
> Am Fri, 4 Feb 2011 09:53:08 +0100
> schrieb Wouter van Reeven <wouter_at_van.reeven.nl>:
> > What problem(s) are you facing exactly? Perhaps we can do this off
> > list, unless other people are interested in this as well.
>
> Most of my current findings is outlined in [1]. Bottom line of what I
> want to do is to set up a maven2 based project structure (the project
> should exclusively use maven2 for build) consisting of an ear
> (including a bunch of ejb modules) for deployment to a glassfish v3 and
> an "application client" supposed to be deployed to local workstations,
> to connect to the remote gfv3 server and make proper use of remote EJBs.
>
> So far, I tried following the NetBeans tutorials on these things which
> are pretty straightforward - building an application client project,
> inject/annotate an @EJB in the client, run - fine. However, as soon as
> even considering using maven2 for build, these things don't work.
> Annotated beans (@EJB) in the client class are always null. No
> surprise, I think. :) Manually adding a couple of artifacts off a
> remote repository (which "seemed" right) didn't work but just provide
> me with a couple of different ClassNotFoundExceptions related to
> org.omg.corba or com.sun.* stuff. Same for trying to configure JNDI to
> tell where the remote server lives.
>
> Basically, the information I failed fo find, so far, for this very use
> case is
>
> - which maven2 dependencies are required to build a remote ejb client
> for glassfish v3 and where (repository) to get them, and
>
> - what kind of configuration (code, config files, ...) inside the
> client application is required for glassfishv3 to make proper use of
> remote EJBs.
>
> Not sure if this is of public interest, keeping it on-list for a while,
> what do others think of that? :)
>
> Cheers & thanks, by now,
> Kristian
>
> [1]http://www.java.net/forum/topic/glassfish/glassfish/glassfishv3-ejb-standalone-client-and-ma
>
>
> --
> Dipl.-Ing.(BA) Kristian Rink * Software- und Systemingenieur
> planConnect GmbH * Könneritzstr. 33 * 01067 Dresden
> fon: 0351 215 203 71 * cell: 0176 2447 2771 * mail: rink_at_planconnect.de
> Amtsgericht Dresden HRB: 20 015 * St.-Nr. FA DD I 201 / 116 / 05360
> Geschäftsführer: Stefan Voß, Karl Stierstorfer
--
Home is not where you live but where they understand you.
[Christian Morgenstern]
Skype: wvreeven
Facebook: wvreeven
Twitter: wvreeven