You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by "Franklin, Matthew B." <mf...@mitre.org> on 2012/05/28 20:27:34 UTC
[PROPOSAL] Revisit Models as Interfaces
I have created a proposal in the wiki [1] to move back to a interfaces for models approach. I will create a branch and start the work. Any comments or modifications are, as always, welcomed and will be integrated into the branch before applying it to trunk.
[1]: http://wiki.apache.org/rave/ArchitectureTopics/Persistence/ModelInterfaces
RE: [PROPOSAL] Revisit Models as Interfaces
Posted by "Mack, Trevor M." <tm...@mitre.org>.
Matt, this is a great thing to jump at and I would be willing to assist you with anything to get this accomplished.
+1 from me.
--
Trevor Mack
Software Systems Engineer (R501), Apache Rave
MITRE K-building, 1K146 | (781) 271-7252 | tmack@mitre.org
-----Original Message-----
From: Raminderjeet Singh [mailto:raminderjsingh@gmail.com]
Sent: Tuesday, May 29, 2012 12:30 PM
To: dev@rave.apache.org
Subject: Re: [PROPOSAL] Revisit Models as Interfaces
+1 from me. I had problems in the past while exposing rave getUser() method as application/xml and application/json. Spring was not giving any useful error and finally by adding @XmlRootElement it worked.
Thanks
Raminder
On May 29, 2012, at 8:44 AM, Carlucci, Tony wrote:
>> -----Original Message-----
>> From: Scott Wilson [mailto:scott.bradley.wilson@gmail.com]
>> Sent: Monday, May 28, 2012 4:37 PM
>> To: dev@rave.apache.org
>> Subject: Re: [PROPOSAL] Revisit Models as Interfaces
>>
>> On 28 May 2012, at 20:52, Ate Douma wrote:
>>
>>> On 05/28/2012 08:27 PM, Franklin, Matthew B. wrote:
>>>> I have created a proposal in the wiki [1] to move back to a interfaces for
>> models approach. I will create a branch and start the work. Any comments or
>> modifications are, as always, welcomed and will be integrated into the branch
>> before applying it to trunk.
>>>>
>>>> [1]:
>> http://wiki.apache.org/rave/ArchitectureTopics/Persistence/ModelInterfaces
>>>
>>> Great you're picking this up Matt!
>>> Big +1 from me and I'd like to help and chime in as much as I can.
>>
>> +1 this is pretty similar to how we ended up doing pluggable persistence in
>> Wookie also - we used an API following the ActiveRecord pattern with two
>> persistence modules (JPA and JCR) but only JPA as the default. Its a bit of a
>> pain when you want to modify models, but I think most of the Rave core
>> model is fairly stable.
>>
>>>
>>> Ate
>
> +1 as well
>
> One big gotcha we'll have to solve is how to handle JAXB and JSON bindings with the interfaces since the binding APIs require classes to bind to/from.
>
> Tony
>
Re: [PROPOSAL] Revisit Models as Interfaces
Posted by Raminderjeet Singh <ra...@gmail.com>.
+1 from me. I had problems in the past while exposing rave getUser() method as application/xml and application/json. Spring was not giving any useful error and finally by adding @XmlRootElement it worked.
Thanks
Raminder
On May 29, 2012, at 8:44 AM, Carlucci, Tony wrote:
>> -----Original Message-----
>> From: Scott Wilson [mailto:scott.bradley.wilson@gmail.com]
>> Sent: Monday, May 28, 2012 4:37 PM
>> To: dev@rave.apache.org
>> Subject: Re: [PROPOSAL] Revisit Models as Interfaces
>>
>> On 28 May 2012, at 20:52, Ate Douma wrote:
>>
>>> On 05/28/2012 08:27 PM, Franklin, Matthew B. wrote:
>>>> I have created a proposal in the wiki [1] to move back to a interfaces for
>> models approach. I will create a branch and start the work. Any comments or
>> modifications are, as always, welcomed and will be integrated into the branch
>> before applying it to trunk.
>>>>
>>>> [1]:
>> http://wiki.apache.org/rave/ArchitectureTopics/Persistence/ModelInterfaces
>>>
>>> Great you're picking this up Matt!
>>> Big +1 from me and I'd like to help and chime in as much as I can.
>>
>> +1 this is pretty similar to how we ended up doing pluggable persistence in
>> Wookie also - we used an API following the ActiveRecord pattern with two
>> persistence modules (JPA and JCR) but only JPA as the default. Its a bit of a
>> pain when you want to modify models, but I think most of the Rave core
>> model is fairly stable.
>>
>>>
>>> Ate
>
> +1 as well
>
> One big gotcha we'll have to solve is how to handle JAXB and JSON bindings with the interfaces since the binding APIs require classes to bind to/from.
>
> Tony
>
RE: [PROPOSAL] Revisit Models as Interfaces
Posted by "Carlucci, Tony" <ac...@mitre.org>.
>-----Original Message-----
>From: Scott Wilson [mailto:scott.bradley.wilson@gmail.com]
>Sent: Monday, May 28, 2012 4:37 PM
>To: dev@rave.apache.org
>Subject: Re: [PROPOSAL] Revisit Models as Interfaces
>
>On 28 May 2012, at 20:52, Ate Douma wrote:
>
>> On 05/28/2012 08:27 PM, Franklin, Matthew B. wrote:
>>> I have created a proposal in the wiki [1] to move back to a interfaces for
>models approach. I will create a branch and start the work. Any comments or
>modifications are, as always, welcomed and will be integrated into the branch
>before applying it to trunk.
>>>
>>> [1]:
>http://wiki.apache.org/rave/ArchitectureTopics/Persistence/ModelInterfaces
>>
>> Great you're picking this up Matt!
>> Big +1 from me and I'd like to help and chime in as much as I can.
>
>+1 this is pretty similar to how we ended up doing pluggable persistence in
>Wookie also - we used an API following the ActiveRecord pattern with two
>persistence modules (JPA and JCR) but only JPA as the default. Its a bit of a
>pain when you want to modify models, but I think most of the Rave core
>model is fairly stable.
>
>>
>> Ate
+1 as well
One big gotcha we'll have to solve is how to handle JAXB and JSON bindings with the interfaces since the binding APIs require classes to bind to/from.
Tony
Re: [PROPOSAL] Revisit Models as Interfaces
Posted by Scott Wilson <sc...@gmail.com>.
On 28 May 2012, at 20:52, Ate Douma wrote:
> On 05/28/2012 08:27 PM, Franklin, Matthew B. wrote:
>> I have created a proposal in the wiki [1] to move back to a interfaces for models approach. I will create a branch and start the work. Any comments or modifications are, as always, welcomed and will be integrated into the branch before applying it to trunk.
>>
>> [1]: http://wiki.apache.org/rave/ArchitectureTopics/Persistence/ModelInterfaces
>
> Great you're picking this up Matt!
> Big +1 from me and I'd like to help and chime in as much as I can.
+1 this is pretty similar to how we ended up doing pluggable persistence in Wookie also - we used an API following the ActiveRecord pattern with two persistence modules (JPA and JCR) but only JPA as the default. Its a bit of a pain when you want to modify models, but I think most of the Rave core model is fairly stable.
>
> Ate
Re: [PROPOSAL] Revisit Models as Interfaces
Posted by Ate Douma <at...@douma.nu>.
On 05/28/2012 08:27 PM, Franklin, Matthew B. wrote:
> I have created a proposal in the wiki [1] to move back to a interfaces for models approach. I will create a branch and start the work. Any comments or modifications are, as always, welcomed and will be integrated into the branch before applying it to trunk.
>
> [1]: http://wiki.apache.org/rave/ArchitectureTopics/Persistence/ModelInterfaces
Great you're picking this up Matt!
Big +1 from me and I'd like to help and chime in as much as I can.
Ate
Re: [PROPOSAL] Revisit Models as Interfaces
Posted by Jasha Joachimsthal <ja...@apache.org>.
On 28 May 2012 20:27, Franklin, Matthew B. <mf...@mitre.org> wrote:
> I have created a proposal in the wiki [1] to move back to a interfaces for
> models approach. I will create a branch and start the work. Any comments
> or modifications are, as always, welcomed and will be integrated into the
> branch before applying it to trunk.
>
> [1]:
> http://wiki.apache.org/rave/ArchitectureTopics/Persistence/ModelInterfaces
>
+1
I assume the 0.12 release will still have the old models approach and this
will be a part of the 0.13 release?
Jasha