On 3/27/06 8:12 PM, "Nicola Piccinini"
<pic superfluo.org> wrote:
> Hi,
>
> I'm trying the blojsom-3.0 module:
> my mysql installation is case sensitive and so I had to
modify
> blojsom-full-initial-data-mysql.sql and some .hbm.xml
files to put every
> table name initial in lowercase (afterwards I realized
that changing to
> uppercase necessitated less modifications).
> Finally I succeed in viewing the default blog start
page
Awesome, the database support madness begins
>
> A more dbms independent approach may be (inspired by
> https://appfuse.dev.jav
a.net/):
> hibernate tools for creating db schema (so it's not
necessary to keep
> the hibernate configuration files synchronized with the
dump file) +
> dbunit for importing initial data. It should be
possible to do both
> tasks programmatically in the DatabaseLoader. What do
you think?
Well, for people downloading and installing blojsom that may
not have a Java
development environment setup, I'd rather them just change
a configuration
file to specify the database creation script and the
database login details
and be done with it.
The database loader is pretty simple and straightforward.
I'd like to keep
that going forward.
>
> Other question about the dbms management:
> why the database access information are repeated in 3
configuration
> files? Both blojsom.xml, blojsom-xmlrpc.xml and
blojsom-commentapi.xml
> have a definition of the mysqlDataSource bean. Is it
not possible to
> share an unique definition of such bean?
Good point. Then people just need to change
blojsom-helper-beans-include.xml
to edit the database details. Fixed in CVS.
>
>> Sincerely, a hats off to the Spring developers.
>
> I'm not a blojsom developer but I like to play with
its code. Often this
> is the best source of information about how to make
work some stuffs.
> So, please, let me speak about the development process
.
>
> One of the thing I like most of blojsom is its agility
in development.
> The Spring value is unquestionable but I fear that it
could have
> negative impact on the startup time and (I saw some
applications using
> spring that starts very, very slowly) and that it could
be of impediment
> to the live configuration. Imho, these are concerns for
development.
> Luckily, it seems not to be the case: blojsom 3.0
starts as quick as
> usual and every change in configuration files is
reloaded after few
> seconds (at least, I've done some successful tests
changing the dbms
> user password). Hat off David Czarnecki (and thank you
for teaching me
> this new English expression , you are
showing me how to use spring in
> an effective way.
Startup time is mostly a reflection of the initialization
code. The only
thing in the new technology stack that makes startup slower
is the database
pool initialization.
And it was hella worse before I added these to
log4j.properties:
# For running under Tomcat 5.0.xx installations
log4j.logger.org.springframework=ERROR
# For running under Tomcat 5.0.xx installations
log4j.logger.org.hibernate=ERROR
>
> A think that doesn't convince me is maintaining the
configuration files
> far from their natural place. They are in /properties
and the "prepare"
> ant target moves them to /war/WEB-INF/classes. This
means that one has
> to maintain synchronized the two copies, this is
uncomfortable.
>
>> Hibernate
>
> I agree with who appreciates the file system approach
but I agree more
> with David Czarnecki: a dbms will be able to manage in
an easier way the
> relations between data.
>
>> The templates and themes are still stored on
>> the filesystem, but Iąd envision also storing the
template data within
>> the database as well.
>
> anyway, I think that is more convinient editing
templates as files than
> as db fields, even if through html forms. In truth this
is valid for the
> configuration too .
Well, for now the templates are on the filesystem. I've got
some code to
load templates from the database with Velocity, but I
haven't switched over
yet.
I've tried to keep configuration files at a minimum. In
fact, in blojsom 3.0
there are none aside from the Spring configuration files. I
think as long as
the interface is intuitive for people to change options
through the web
console, it'll be A-OK.
>
> As we are talking about a new major release, I believe
it's also time to
> make some proposals:
> - having a database it would be possible to have
permalinks like:
> common-URL?id-permalink=id-of-the-entry. These are less
readable than
> actual permalinks but have the merit to be independent
of category
> alteration (and maybe other merits). What do you think
about? Would it
> be possible to support both permalink types and let the
user choose
> which one to use in his templates?
I'm actually calling it entry_id which is the integer ID of
the entry. Not
sure what I want to do about precedence of entry_id over
permalink in 3.0,
say if both were specified.
Right now the fetchEntries(...) code looks only for
permalink. When you add
an entry, blojsom creates a post slug using the title of the
post and
creates a unique human-friendly ID for the post.
So, the following point to the same entry in 3.0.
http:/
/localhost:8080/blojsom/blog/default/Foo
http://localhost:8080/blojsom/blog/default/uncategor
ized/Foo
http://localhost:8080/blojsom/blog/defaul
t/uncategorized/2006/03/27/Foo
I sort of envisioned in the migration strategy that the
filenames for
entries would just populate the post slug field in the
database. This way
people could still keep the .html extensions.
> - I know that one can subscribe for new comments on a
specific post but
> I believe that an email notification system would fit
better the needs
> of most users. Wouldn't be a good idea to predispose
blojsom 3.0 for
> this feature?
Or maybe I'll just do a plugin contest when 3.0 is released
and someone can
write a plugin to do this functionality. Seems like the
plugin could use a
table in the database, "EntrySubscriptions" with
fields, "ENTRY_ID",
"EMAIL_ADDRESS". And then the plugin subclasses
from the
StandaloneVelocityPlugin so that you can use a Velocity
template for the
e-mail body. And the plugin also implements the Listener
interface to listen
for EntryAdded and EntryUpdated events.
It is left as an exercise for the reader to implement ;)
>
> I hope that my comments may be of some utility. If I'm
able (and have
> time) I'd happy to help in someway (for example in
writing English
> documentation :-D
> Best regards.
--
David Czarnecki
http://www.blojsom.com/b
log/ | http://blojsom.sf.net
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking
scripting language
that extends applications into web and mobile media. Attend
the live webcast
and join the prime developer group breaking into this new
coding territory!
http:
//sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$
1720&dat1642
_______________________________________________
Blojsom-developers mailing list
Blojsom-developers lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bloj
som-developers
|