On Sep 10, 2008, at 7:00 PM, Kory Markevich wrote:
It wasn't in active use, but it is what I was using for the code for
a custom
application-scoped login module. I had assumed that this was the
correct
type of project to use for such a beast, as none of the other types
seemed
correct (it's not an ejb, nor connector, etc.) Is there a preferred
way to
do this using Geronimo and WTP, or do I have to do some kind of manual
project-reference work?
I don't know how eclipse assists with this but you can include
configuration for gbeans in any kind of geronimo plan, including that
for ears (geronimo-application.xml or external plan), ejb modules
(openejb-jar.xml), or web modules (geronimo-web.xml). META-INF/
geronimo-service.xml would only get detected if you were deploying a
jar directly not as a javaee application.
Generally gbean config is at the end of the plan after all the javaee
stuff.
thanks
david jencks
Thanks for the help.
Tim McConnell-2 wrote:
Hi Kory, Now I understand. It didn't occur to me that you were
generating
a
geronimo-service.xml file. We removed support for that geronimo
deployment
plan
since the GEP didn't do anything with it once it was generated.
Were you
actually
using the geronimo-service.xml file for something or just
generating it ??
I
suspect you were just generating it and then not using it, in which
case
you can
just delete that project without impacting the other projects in your
workspace.
Can you please verify that ??
--
View this message in context:
http://www.nabble.com/Eclipse-Utility-Projects-with-2.1.2-tp19402144s134p19424830.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
