Dogan Atay wrote:
I have realized registering the JMSExtensions can be accomplished with one line of code
WSIFServiceImpl.addExtensionRegistry(new JMSExtensionRegistry());
Dogan,
this is executed when provider is initialized (check org.apache.wsif.providers.jms.WSIFDynamicProvider_Jms)
However, my question still stands as why the JMSExtensions are not registered like Java, EJB and Format as default.
they are: JMS (and other providers) should be picked up automatically from WSIF jar from CLASSPATH. for description see org.apache.wsif.util.WSIFPluggableProviders but in nutshell it reads text from jar:META-INF/services/org.apache.wsif.spi.WSIFProvider (which is text file). unpack wsif.jar and you can see it contains:
# EJB provider org.apache.wsif.providers.ejb.WSIFDynamicProvider_EJB
# Java provider org.apache.wsif.providers.java.WSIFDynamicProvider_Java
# SOAP Apache Axis provider org.apache.wsif.providers.soap.apacheaxis.WSIFDynamicProvider_ApacheAxis
# SOAP Apache SOAP provider org.apache.wsif.providers.soap.apachesoap.WSIFDynamicProvider_ApacheSOAP
# Native JMS provider org.apache.wsif.providers.jms.WSIFDynamicProvider_Jms
HTH,
alek
-- The best way to predict the future is to invent it - Alan Kay
