Hi On Wed, Aug 18, 2010 at 9:23 PM, ymikhel <[email protected]> wrote:
> > Hi, > > I have a webapp that contains web service implementing Provider API, and it > fails to deploy unless "implements Provider<T>" added to the service class, > in addition to being present in the abstract class that the service class > extends, as suggested here: https://issues.apache.org/jira/browse/CXF-1852 > . > > It says that this issue was resolved 2.2.3, we run 2.2.9 (as part of > jbossws-cxf-3.3.1.GA), but it doesn't work without "implements" statement. > > I have added a test the other day addressing a similar issue raised at one of the JBoss forums, please see http://svn.apache.org/repos/asf/cxf/trunk/systests/jaxws/src/test/java/org/apache/cxf/systest/provider/AbstractSourcePayloadProvider.java http://svn.apache.org/repos/asf/cxf/trunk/systests/jaxws/src/test/java/org/apache/cxf/systest/provider/SourceProvider.java http://svn.apache.org/repos/asf/cxf/trunk/systests/jaxws/src/test/java/org/apache/cxf/systest/provider/HWSourcePayloadProvider.java AbstractSourcePayloadProvider is an abstract class which implements ServiceProvider interface extending Provider<Source>. HWSourcePayloadProvider extends AbstractSourcePayloadProvider. I just quickly rerun the test by having AbstractSourcePayloadProvider implement Provider<Source> directly and adding Serializable to the list of interfaces (1st position), just to check if implementing multiple interfaces can affect it, and the test still works, what is different in your case ? cheers, Sergey > Thanks, > Yuri > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/ArrayIndexOutOfBoundsException-with-Provider-services-on-CXF-tp2640049p2640049.html > Sent from the cxf-user mailing list archive at Nabble.com. >
