On 7/25/07, Mike Miller <[EMAIL PROTECTED]> wrote:
>
> I need to expose a single method from one of our EJBs. I have already read
> thru the article at http://www.tsolak.com/?p=15 and exchanged a comment
> with the author, but we don't use Spring in our application.
>
> It seems like the easiest way to expose my method would be to follow the
> example from
> http://www.javaworld.com/javaworld/jw-05-2006/jw-0501-xfire.html?page=2
> and use the EJBInvoker that is in the documentation - but it brings up some
> questions:
>
> 1) Do I use the <method> parm in services.xml if I only want to expose a
> subset of methods from my implementation class? If I don't provide a method
> parm, does xfire expose all public methods?
Yes,all public method will be exposed.
> 2) Based on some of the reading I have done so far, it appears that the
> process (maybe the old process) generates the wsdl and mapping files and
> packages them for deployment, but in some of the examples for xfire, I don't
> see the WSDL?
WSDL is generated on the fly based on java classes and config files.
> 3) Does XFire automatically generate (on-the-fly) the WSDL and mappings
> configuration files - rather than using some type of ant task to
> pre-generate the wsdl for deployment?
Yep, it generate WSDL on the fly. But only WSDL, mappings files must
be created by hand ( if needed, but in most cases you don't need them
)
> 4) Can use this approach with the current version of XFire if we run under
> the java 1.4.x version?
Sure
> Thanks in advance!
>
> ________________________________
> See what you're getting into…before you go there. Check it out!
--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
