I am fairly new to XFire and Spring, but I am evaluating them as a new
direction in our develop process. I have built a prototype - proof of
concept that has been tested and is working well. I have a few questions
that I am hoping someone can help out.
I have a service that is being exposed using XFire built on the
SpringFrameworks. The current implementation, which was only a prototype,
looks at the incoming message due to some legacy application needs and
from the payload determines what processing is required. A Spring
ApplicationContext is created and the appropriate object to handle the
call is created from the context and invoked.
Initial thought was to move the spring bean definitions to be imported
within the service.xml and then access it from this ApplicationContext to
create the other objects so that all spring configuration occurs upfront.
After looking through the code I have not found how to access this
ApplicationContext from my service. Is this a recommended approach and
also how do you gain access to this ApplicationContext? Should the
"application" ApplicationContext be kept separate and managed seperatly
from the XFire ApplicationContext? Are there any implications either way?
I have found where I can create a inhandler to determine which service
should be called and then set that in the PRE-DISPATCH phase allowing
XFire to then invoke the appropriate service class. Would this be a more
appropriate location for this processing?
Performance is an utmost critical issue and the application will be going
through a thorough performance lab testing stressing it to its limits for
capacity planning.
Thanks for your help and great job to the XFire developers.
Wes Smoak
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
