Hello Andreas,

 I don't think this has been discussed for MINA3 yet but it should be
sometime in the future. For Mina 2.0 I guess your best option  would
be to write wrapper classes - and you can provide patches for these,
of course.




2010/4/7 Andreas Sahlbach <andr...@sahlbach.com>:
> Well, that depends on my coding style, I guess. :-)
>
> But the reason for my question is, that there is no simple right or
> wrong answer. It's possible to extend the class to provide support for
> spring or to write a wrapper class to decouple the spring support from
> the core classes. So I just want to know the overall strategy
> regarding spring. And then it's no problem to provide patches.
>
> On Wed, Apr 7, 2010 at 10:50 AM, Norman Maurer
> <norman.mau...@googlemail.com> wrote:
>> Hi Andreas,
>>
>> I'm not a mina dev but I'm sure they love patches which make the code
>> more usable ;)
>>
>> Bye,
>> Norman
>>
>>
>> 2010/4/7 Andreas Sahlbach <andreas.sahlb...@gmail.com>:
>>> Hi guys!
>>>
>>> I am a new user of your framework (great stuff!) and I have a short
>>> question regarding the spring framework. I am using mina 2.x and
>>> noticed that you removed a lot of special spring stuff in favor of a
>>> more general support for injection frameworks.
>>>
>>> Still there are a number of classes in the framework that are pretty
>>> spring-unfriendly and cannot be used from within spring without user
>>> modifications (like extending them or wrapping them). So my question
>>> is:
>>>
>>> What is your midterm plans regarding spring integration?
>>> Are you going to modify your classes so that they can be easily from
>>> within spring?
>>> If so, should I file a bug (with patch) for classes that don't work 
>>> currently?
>>> Or are you going to implement more helper classes in the xbean package?
>>>
>>> I am referring for example to DemuxingProtocolCodecFactory or
>>> DemuxingIoHandler, which can't be initialized easily from within
>>> spring.
>>>
>>> Best regards,
>>>
>>> Andreas
>>>
>>> --
>>> Andreas Sahlbach
>>>
>>
>
>
>
> --
> Andreas Sahlbach
>

Reply via email to