R: R: [Phrame-devel] Phrame and Log4php

[Sergio S. <se...@as...>]

>> Yes, "your" Phrame work well with Log4php 0.7 after
>> replacing
>> LoggerFactory::getLogger with LogFactory::getLog
>They changed the method names since version 0.2!

No change, simple additions: 0.2 is a partial porting, instead 0.7 is a full
porting.

>> I am working on two others things:
>> - application configuration (with a web.xml file),
>> used instead of modification of the WEB-INF/options.php file.

> we should consider building one config file for it as well.

In struts I see 5 files (struts-config, tiles-config, validation,
validation-rules and web-app), plus log4php: seems to be too much :-)

Well, we must work in integration, but heach package must work also alone
(as is now for log4php, adodb and smarty) and integrated by phrame.  I think
the goal is to use a config file driven setter, instead of webapp
options.php

Now you use XML config in XMLMappingBuilder::get(), which load data with
private methods, then discard the loaded xml tree.

My proposal is to build a PhrameCreator object:
1) the contructor read phrame-config.xml and set all define using specific
context-param
2) method for creating a logger (call LogFactory::getLog() )
3) method for creating an adodbconnection (using a specific context-param
for dsn)
4) method for creating a mapping using a modified XMLMappingBuilder which
receive the xml tree as parameter
5) create a controller (using an ActionController::create()); the logic for
caching should be transferred here, because the creator must decide if
create a mapping to be passed to the controller creator.

>> - authentication & authorization (like jaas), to be
>> integrated in HttpServletRequest: I am registering a new sf
>> project for this.
>I implemented some of the user and role code already.

I seen your examples.  But should be "pluggable" with the desired strategy
(specified in configuration file): so I'll write pass.