Last commit
Jacopo Murador
applications aren't update to this new version. I hope to complete
asap. If I can go to the next jug meeting, we will talk about it.
My english is bad, I know :-)
Jacopo
Enrico Giurin
Jacopo, the plugin parancoe-plugin-springsecurity was still in
development so there was no reason to modify it.
Could you please better clarify why you have introduced the file
applicationContext-plugin.xml and what is the relationship with the
file parancoe-plugin.xml?
Thanks,
Enrico.
Jacopo Murador
Il giorno 22/set/08, alle ore 16:27, Enrico Giurin ha scritto:
> Jacopo, the plugin parancoe-plugin-springsecurity was still in
> development so there was no reason to modify it.
>
Ok.
> Could you please better clarify why you have introduced the file
> applicationContext-plugin.xml and what is the relationship with the
> file parancoe-plugin.xml?
The previous version of parancoe with only the parancoe-servlet.xml
has some problems in application with a lot of configured classes.
Parancoe needs to read the config file (parancoe-servlet.xml) at the
start of application for some features as the db populate. So the
org.parancoe.web.ContextListner read the parancoe-servlet when you
start the application, but it's done also by the spring framework when
the DispatchServlet is load. This double reading of the xml file
creates strange behaviours, expecially on my project :-)
To eliminate this problem, I choose to divide the parancoe-
servlet.xml into two parts as described on the spring documentation.
I put the configuration of the persistent and business logic related
objects into applicationContext.xml, whereas into parancoe-servlet you
can find the configuration of the controller and view related objects.
The first file is load by the contextListner, instead the second is
read at the load of the dispatch servlet.
The configuration files of plugin work in the same way: the
onfiguration of persistent and business logic related objects is in
the applicationContext-plugin.xml and into parancoe-plugin.xml the
configuration of the controller and view related objects.
If you need another informations, you know my e-mail address :-)
Jacopo
Lucio Benfante
> The configuration files of plugin work in the same way: the
> onfiguration of persistent and business logic related objects is in
> the applicationContext-plugin.xml and into parancoe-plugin.xml the
> configuration of the controller and view related objects.
>
> If you need another informations, you know my e-mail address :-)
>
>
Hi,
I have to add that I was aware of the Jacopo develpment and changes. We
discussed them 1-2 weeks ago, and I agreed with him about his proposals.
Sorry for my fault in communicating it.
Lucio
--
Lucio Benfante
JUG Padova http://www.parancoe.org ...have a look at it!
www.jugpadova.it http://www.jugevents.org
Enrico Giurin
<jacopo....@gmail.com> wrote:
[cut]
> The configuration files of plugin work in the same way: the
> onfiguration of persistent and business logic related objects is in
> the applicationContext-plugin.xml and into parancoe-plugin.xml the
> configuration of the controller and view related objects.
Hi Jacopo,
thanks for the explanation but still it's not clear to me as I have to
split the content of the parancoe-plugin.xml for the plugin security.
I mean, all the specific springsecurity (was acegi)configuration, like
the filters, should be written in the applicationContext-plugin.xml?
That makes sense?
Jacopo Murador
Il giorno 24/set/08, alle ore 13:24, Enrico Giurin ha scritto:
> I mean, all the specific springsecurity (was acegi)configuration, like
> the filters, should be written in the applicationContext-plugin.xml?
No. The filters are contorller and view related objects, therefore you
must put their configuration into parancoe-plugin.xml.
I already split the parancoe-plugin.xml of springsecurity plugin into
two parts in my last commit. You can look these files as example.
Jacopo