You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@abdera.apache.org by "James M Snell (JIRA)" <ji...@apache.org> on 2007/08/21 00:19:30 UTC

[jira] Resolved: (ABDERA-56) Spring Integration

     [ https://issues.apache.org/jira/browse/ABDERA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James M Snell resolved ABDERA-56.
---------------------------------

    Resolution: Fixed

checked in

> 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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.