Hi Deepal, Paul:
Deepal Jayasinghe wrote:
Is there a way of making it more dynamic? If its there it works, if
not then its still ok?
But now we get Class not found exception , if we try to use Axis2
without having jaxws around :)
Paul was asking if there's a way *around* that kind of problem,
Deepal... and I think there is.
For much of our configuration, components (handlers in particular) are
non-optional - failing to find a configured class means a fatal error.
We could pretty easily change that to allow for optional components in
several ways:
* We could leave everything as-is and create an "OptionalDispatcher"
which uses reflection to load a target class. It's a noop if it can't
find the target class, and it delegates if it can.
I can not agree here. then we are making some assumptions on unwanted
thing.
<handler name="GenericProviderDispatcher"
class="org.apache.axis2.dispatchers.Optional">
<parameter name="targetClass">
[...]dispatchers.GenericProviderDispatcher
</parameter>
</handler>
* We could add an "optional" flag to our handler configuration which
would allow trapping ClassNotFoundExceptions and simply skipping the
handler if one is thrown.
Well , what we are discussing here is some major changes. But we can
easily solve this problem by having jaxws module with those handlers (I
mean a mar file). If we do so we can remove those handlers from
axis2.xml and move them to jaxws.mar so if someone want jaxws support
then what he has to do is
- first drop all the jaxws related jar into class path
- second engage jaxws module.
Thank you!
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
