You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Thiago H de Paula Figueiredo <th...@gmail.com> on 2014/10/08 17:14:19 UTC
BeanModel classes as a separate project and/or JAR?
Hi!
Taking a look at a problem I'm having at my day job right now, I noticed
the BeanModel classes (including PropertyModel, PropertyConduit,
BeanModelSource, etc) could be hugely useful for projects and code that
need to deal with class properties: discovery, reading and writing
properties. Tapestry does that and in a very fast manner, as it doesn't
use reflection at all for reading and writing properties. Our scenario
here is a homegrown XML mapper that cannot be replaced due to backward
compatibility and we'd also need some lazy-loading of mapped properties,
as most of the time most properties aren't needed
BeanModel et al is inside tapestry-core, so anything using it would need
to depend on an (awesome) Tapestry framework. I believe with a little bit
of work, including a sprinkle of Gradle magic, we could generate a
BeanModel JAR separate from tapestry-core.
What do you guys think?
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: BeanModel classes as a separate project and/or JAR?
Posted by Lance Java <la...@googlemail.com>.
On the other hand, the alternative of needing a "tapestry-commons" project
isn't great either.
On 9 Oct 2014 14:42, "Lance Java" <la...@googlemail.com> wrote:
> For a BeanModel framework to come packaged with tapestry-ioc feels like
> bloatware to me.
>
Re: BeanModel classes as a separate project and/or JAR?
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Fri, 10 Oct 2014 11:57:55 -0300, Kalle Korhonen
<ka...@gmail.com> wrote:
> No reason to vote yet as we don't know how the end result would look
> like. I think it'd be far better to create a remote branch for all to
> see, and
> once you know how it's gonna turn out, we can vote on merging it in.
You nailed it, Kalle. I'm creating a beanmodel-split branch and I'll push
it to Apache's Git as soon as I have enough work.
Lance, you mentioned the possibility of having a tapestry-commons project,
and the work I've done so far does indicate that it should exist. There's
a lot of stuff the beanmodel project will need that doesn't make sense any
sense to be inside it: ObjectLocator, AnnotationProvider,
MessageFormatter, Messages, TypeCoercer, Coercion, CoercionTuple, and
that's just the ones I've uncovered so far. I'm creating a 'commons'
subproject for them.
>
> Kalle
>
>>
>>
>>
>>> -----Original Message-----
>>> From: "Thiago H de Paula Figueiredo" <th...@gmail.com>
>>> Sent: 10/10/2014 16:20
>>> To: "Tapestry development" <de...@tapestry.apache.org>
>>> Subject: Re: BeanModel classes as a separate project and/or JAR?
>>>
>>> On Fri, 10 Oct 2014 03:28:52 -0300, Lance Java
>>> <lance.java@googlemail.com
>>> >
>>> wrote:
>>>
>>> Yes... It would be a dependency rather than the same package. Either
>>> way
>>>> it's the same net result (tapestry-ioc on the classpath when all you
>>>> wanted was a bean mapper). That's the bloatware I was speaking of.
>>>>
>>>
>>> I see. I agree this is far from ideal, but it may not be possible to
>>> do it
>>> in another way. I don't know yet.
>>>
>>> Regarding Git, is there any way of copying files from one folder to
>>> another without losing its history?
>>>
>>> On 9 Oct 2014 22:19, "Thiago H de Paula Figueiredo"
>>> <thiagohp@gmail.com
>>>> >
>>>> wrote:
>>>>
>>>> On Thu, 09 Oct 2014 10:42:48 -0300, Lance Java
>>>>> <la...@googlemail.com>
>>>>> wrote:
>>>>>
>>>>> For a BeanModel framework to come packaged with tapestry-ioc feels
>>>>> like
>>>>>
>>>>>> bloatware to me.
>>>>>>
>>>>>>
>>>>> I suggested a BeanModel JAR with a dependency on Tapestry-IoC, not
>>>>> including Tapestry-IoC, in case we cannot really make a standalone
>>>>> BeanModel JAR.
>>>>>
>>>>> --
>>>>> Thiago H. de Paula Figueiredo
>>>>> Tapestry, Java and Hibernate consultant and developer
>>>>> http://machina.com.br
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>>
>>>>>
>>>
>>>
>>
>> --
>> Thiago H. de Paula Figueiredo
>> Tapestry, Java and Hibernate consultant and developer
>> http://machina.com.br
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: BeanModel classes as a separate project and/or JAR?
Posted by Kalle Korhonen <ka...@gmail.com>.
On Fri, Oct 10, 2014 at 6:58 AM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Fri, 10 Oct 2014 10:21:34 -0300, Dimitris Zenios <
> dimitris.zenios@gmail.com> wrote:
>
>> Git mv
>>
> Thanks!
> Do you guys think this change should have a vote before it's done?
No reason to vote yet as we don't know how the end result would look like.
I think it'd be far better to create a remote branch for all to see, and
once you know how it's gonna turn out, we can vote on merging it in.
Kalle
>
>
>
>> -----Original Message-----
>> From: "Thiago H de Paula Figueiredo" <th...@gmail.com>
>> Sent: 10/10/2014 16:20
>> To: "Tapestry development" <de...@tapestry.apache.org>
>> Subject: Re: BeanModel classes as a separate project and/or JAR?
>>
>> On Fri, 10 Oct 2014 03:28:52 -0300, Lance Java <lance.java@googlemail.com
>> >
>> wrote:
>>
>> Yes... It would be a dependency rather than the same package. Either way
>>> it's the same net result (tapestry-ioc on the classpath when all you
>>> wanted was a bean mapper). That's the bloatware I was speaking of.
>>>
>>
>> I see. I agree this is far from ideal, but it may not be possible to do it
>> in another way. I don't know yet.
>>
>> Regarding Git, is there any way of copying files from one folder to
>> another without losing its history?
>>
>> On 9 Oct 2014 22:19, "Thiago H de Paula Figueiredo" <thiagohp@gmail.com
>>> >
>>> wrote:
>>>
>>> On Thu, 09 Oct 2014 10:42:48 -0300, Lance Java
>>>> <la...@googlemail.com>
>>>> wrote:
>>>>
>>>> For a BeanModel framework to come packaged with tapestry-ioc feels like
>>>>
>>>>> bloatware to me.
>>>>>
>>>>>
>>>> I suggested a BeanModel JAR with a dependency on Tapestry-IoC, not
>>>> including Tapestry-IoC, in case we cannot really make a standalone
>>>> BeanModel JAR.
>>>>
>>>> --
>>>> Thiago H. de Paula Figueiredo
>>>> Tapestry, Java and Hibernate consultant and developer
>>>> http://machina.com.br
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>>
>>
>>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: BeanModel classes as a separate project and/or JAR?
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Fri, 10 Oct 2014 10:21:34 -0300, Dimitris Zenios
<di...@gmail.com> wrote:
> Git mv
Thanks!
Do you guys think this change should have a vote before it's done?
>
> -----Original Message-----
> From: "Thiago H de Paula Figueiredo" <th...@gmail.com>
> Sent: 10/10/2014 16:20
> To: "Tapestry development" <de...@tapestry.apache.org>
> Subject: Re: BeanModel classes as a separate project and/or JAR?
>
> On Fri, 10 Oct 2014 03:28:52 -0300, Lance Java
> <la...@googlemail.com>
> wrote:
>
>> Yes... It would be a dependency rather than the same package. Either way
>> it's the same net result (tapestry-ioc on the classpath when all you
>> wanted was a bean mapper). That's the bloatware I was speaking of.
>
> I see. I agree this is far from ideal, but it may not be possible to do
> it
> in another way. I don't know yet.
>
> Regarding Git, is there any way of copying files from one folder to
> another without losing its history?
>
>> On 9 Oct 2014 22:19, "Thiago H de Paula Figueiredo"
>> <th...@gmail.com>
>> wrote:
>>
>>> On Thu, 09 Oct 2014 10:42:48 -0300, Lance Java
>>> <la...@googlemail.com>
>>> wrote:
>>>
>>> For a BeanModel framework to come packaged with tapestry-ioc feels
>>> like
>>>> bloatware to me.
>>>>
>>>
>>> I suggested a BeanModel JAR with a dependency on Tapestry-IoC, not
>>> including Tapestry-IoC, in case we cannot really make a standalone
>>> BeanModel JAR.
>>>
>>> --
>>> Thiago H. de Paula Figueiredo
>>> Tapestry, Java and Hibernate consultant and developer
>>> http://machina.com.br
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>
>
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
RE: BeanModel classes as a separate project and/or JAR?
Posted by Dimitris Zenios <di...@gmail.com>.
Git mv
-----Original Message-----
From: "Thiago H de Paula Figueiredo" <th...@gmail.com>
Sent: 10/10/2014 16:20
To: "Tapestry development" <de...@tapestry.apache.org>
Subject: Re: BeanModel classes as a separate project and/or JAR?
On Fri, 10 Oct 2014 03:28:52 -0300, Lance Java <la...@googlemail.com>
wrote:
> Yes... It would be a dependency rather than the same package. Either way
> it's the same net result (tapestry-ioc on the classpath when all you
> wanted was a bean mapper). That's the bloatware I was speaking of.
I see. I agree this is far from ideal, but it may not be possible to do it
in another way. I don't know yet.
Regarding Git, is there any way of copying files from one folder to
another without losing its history?
> On 9 Oct 2014 22:19, "Thiago H de Paula Figueiredo" <th...@gmail.com>
> wrote:
>
>> On Thu, 09 Oct 2014 10:42:48 -0300, Lance Java
>> <la...@googlemail.com>
>> wrote:
>>
>> For a BeanModel framework to come packaged with tapestry-ioc feels like
>>> bloatware to me.
>>>
>>
>> I suggested a BeanModel JAR with a dependency on Tapestry-IoC, not
>> including Tapestry-IoC, in case we cannot really make a standalone
>> BeanModel JAR.
>>
>> --
>> Thiago H. de Paula Figueiredo
>> Tapestry, Java and Hibernate consultant and developer
>> http://machina.com.br
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: BeanModel classes as a separate project and/or JAR?
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Fri, 10 Oct 2014 03:28:52 -0300, Lance Java <la...@googlemail.com>
wrote:
> Yes... It would be a dependency rather than the same package. Either way
> it's the same net result (tapestry-ioc on the classpath when all you
> wanted was a bean mapper). That's the bloatware I was speaking of.
I see. I agree this is far from ideal, but it may not be possible to do it
in another way. I don't know yet.
Regarding Git, is there any way of copying files from one folder to
another without losing its history?
> On 9 Oct 2014 22:19, "Thiago H de Paula Figueiredo" <th...@gmail.com>
> wrote:
>
>> On Thu, 09 Oct 2014 10:42:48 -0300, Lance Java
>> <la...@googlemail.com>
>> wrote:
>>
>> For a BeanModel framework to come packaged with tapestry-ioc feels like
>>> bloatware to me.
>>>
>>
>> I suggested a BeanModel JAR with a dependency on Tapestry-IoC, not
>> including Tapestry-IoC, in case we cannot really make a standalone
>> BeanModel JAR.
>>
>> --
>> Thiago H. de Paula Figueiredo
>> Tapestry, Java and Hibernate consultant and developer
>> http://machina.com.br
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: BeanModel classes as a separate project and/or JAR?
Posted by Lance Java <la...@googlemail.com>.
Yes... It would be a dependency rather than the same package. Either way
it's the same net result (tapestry-ioc on the classpath when all you wanted
was a bean mapper). That's the bloatware I was speaking of.
On 9 Oct 2014 22:19, "Thiago H de Paula Figueiredo" <th...@gmail.com>
wrote:
> On Thu, 09 Oct 2014 10:42:48 -0300, Lance Java <la...@googlemail.com>
> wrote:
>
> For a BeanModel framework to come packaged with tapestry-ioc feels like
>> bloatware to me.
>>
>
> I suggested a BeanModel JAR with a dependency on Tapestry-IoC, not
> including Tapestry-IoC, in case we cannot really make a standalone
> BeanModel JAR.
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: BeanModel classes as a separate project and/or JAR?
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Thu, 09 Oct 2014 10:42:48 -0300, Lance Java <la...@googlemail.com>
wrote:
> For a BeanModel framework to come packaged with tapestry-ioc feels like
> bloatware to me.
I suggested a BeanModel JAR with a dependency on Tapestry-IoC, not
including Tapestry-IoC, in case we cannot really make a standalone
BeanModel JAR.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: BeanModel classes as a separate project and/or JAR?
Posted by Lance Java <la...@googlemail.com>.
For a BeanModel framework to come packaged with tapestry-ioc feels like
bloatware to me.
Re: BeanModel classes as a separate project and/or JAR?
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Wed, 08 Oct 2014 13:40:48 -0300, Lance Java <la...@googlemail.com>
wrote:
> Sounds useful. I'm assuming plastic would need to be on the classpath but
> tapestry-ioc would not?
I haven't investigated much yet, but it would need a dependency on Plastic
for sure and probably Tapestry-IoC too due to TypeCoercer, ObjectLocator,
DataTypeAnalyzer, AnnotationProvider. I think the new JAR could get
DataTypeAnalyzer and AnnotationProvider, ObjectLocator is only used for
object instantiation, so its direct use is easily replaceable. TypeCoercer
would be difficult to replace, but I haven't dived in this specific part
yet.
Having a Tapestry-IoC dependency wouldn't be a problem, I think.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: BeanModel classes as a separate project and/or JAR?
Posted by Lance Java <la...@googlemail.com>.
Sounds useful. I'm assuming plastic would need to be on the classpath but
tapestry-ioc would not?