Thanks :-) On 8/11/07, James M Snell <[EMAIL PROTECTED]> wrote: > > Since I changed my mind after you had already gone through the trouble > of merging it into the server module I'll take care of the ant stuff :-) > > - James > > Dan Diephouse (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/ABDERA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] > > > > Dan Diephouse updated ABDERA-56: > > -------------------------------- > > > > Attachment: spring-module.patch > > > > This is the spring stuff I wrote included as a separate module. I didn't > have time to do the ant stuff today, so someone else may have to do that or > I'll revisit sometime soon. > > > >> Spring Integration > >> ------------------ > >> > >> Key: ABDERA-56 > >> URL: https://issues.apache.org/jira/browse/ABDERA-56 > >> Project: Abdera > >> Issue Type: New Feature > >> Reporter: Dan Diephouse > >> Fix For: 0.3.0 > >> > >> Attachments: spring-module.patch, spring-server.patch, > spring.patch > >> > >> > >> I've written a spring module for Abdera which providers an > AbderaServlet which works with Spring as well as some XML parsers. With this > creating an Abdera Provider becomes as simple as this: > >> <a:serviceContext> > >> > >> <a:provider> > >> <ref bean="provider"/> > >> </a:provider> > >> > >> <a:targetResolver> > >> <a:regexTargetResolver> > >> <a:collection>/atom/feed(\\?[^#]*)?</a:collection> > >> <a:entry>/atom/feed/([^/#?]+)(\\?[^#]*)?</a:entry> > >> <a:service>/atom(\\?[^#]*)?</a:service> > >> </a:regexTargetResolver> > >> </a:targetResolver> > >> > >> </a:serviceContext> > >> <bean id="provider" class="org.apache.abdera.spring.TestProvider"> > >> </bean> > >> The only code you need to write then is the TestProvider class. > >> This patch does make two other changes. > >> 1. It modifies the Resolver interface to add a > initializeContextPath(String context) method. This makes it so you can > create target resolvers and not have to worry about the context path when > you initialize it - Abdera will just initialize it later. I'm not sure that > what I came up with is the best way to do that though. Any other > suggestions? Maybe Resolver.resolve should take contextPath as a > parameter? Maybe the request URI should come without the context path in it? > >> 2. Uses the correct groupId for Woodstox in MAven > > >
-- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
