Paul, I still think we could use the JAXWSDeployer to automatically deploy a jax-ws module (an in-memory constructed one rather than needing a separate .mar) when JAX-WS services are found. Unfortunately I don't have time to work on it right now.... anyone else? If this is a good approach I could raise a JIRA so we pick it up before the next release?
David On Wed, May 28, 2008 at 4:41 PM, Paul Fremantle <[EMAIL PROTECTED]> wrote: > Deepal > > I don't think your scenario with a JAXWS module solves the TCK > problem. The TCK clearly states (as Dims pointed out) that the code > must work "out of the box" with no additional configuration. I also > want this, irrespective of the TCK rules. The fact is that we are > making it complex to use JAXWS when all the alternative toolkits make > it as easy as possible. > > I don't really understand your motivation here. > > Paul > > On Wed, May 28, 2008 at 5:21 AM, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: >> >>> 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] >> >> > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
