On Jun 24, 2008, at 7:32 AM, Jaime Geovane Marcondes wrote:
We have to ignore the @WebService annotation in
LocalInitialContextFactory. Our legacy project contains more than
100 EJB's
with these annotations, and can't be changed. The legacy libraries are
currently running on an OC4j/IAS environment.
To solve this problem, we made an adjustment on the
AnnotationDeployer
class, at line 1021:
"if (sessionBean.getServiceEndpoint() != null)", but that's not
recommended
as at least 50 developers will use this tool.
I think that creating that kind of "fork" over your GA is not the
best
way to deal with the problem.
With that particular adjustment you're still going to get hit with the
"real" deployment code in o.a.openejb.config.WsDeployer and the code
that constructs the related CXF gadgetry. We'll probably want to cut
that out for you along with service-refs and webservice.xmls in the app.
I've put together an alternate would should eliminate all webservice
related assets from an app, including the removal of any session beans
that are only webservices (i.e. have no other business interfaces) as
well as any transaction and security constraints associated with those
beans. You can enable it with setting the property
"openejb.webservices.enabled" to "false" (default is true obviously).
I've uploaded a snapshot binary here:
people.apache.org/repo/m2-snapshot-repository/org/apache/openejb/
openejb-standalone/3.1-SNAPSHOT/openejb-
standalone-3.1-20080625.051933-3.zip
As well if you're doing testing with maven2, you can simply update
your openejb version to 3.1-SNAPSHOT.
Let me know if this works for you and if you see any kind of
performance boost in test time.
-David
David Blevins wrote:
On Jun 23, 2008, at 6:29 AM, Jaime Geovane Marcondes wrote:
I have a project that is annotated with @WebService, but i don't use
these in Local mode (LocalInitialContextFactory).
It's possible to ignore the annotation of type WebService on start
of
server ?
We don't have the functionality to ignore the @WebService annotation,
but on the same side supporting the testing of components as
@WebService requires you to enable some "heavier" functionality that
is off by default; essentially a lightweight http server.
If you could share some of the motivation behind wanting to ignore
the
@WebService annotation, we could probably add something that could do
the trick. I.e. is there something in particular about the
processing
or support of @WebService that you'd really like to avoid?
Sounds like there might some neat ideas.
-David
--
View this message in context:
http://www.nabble.com/%40WebService---LocalInitialContextFactory-tp18068108p18092375.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
