Comments on Architecture 2.0

Last modified by Vincent Massol on 2024/02/26 17:54

  • machac
    machac, 2007/03/01 16:05

    Halo,

    what about 

    1) using standard JPA storage instead of Hibernate (Hibernate implements JPA specification too). Pros: possibility to change implementation (Hibernate, OpenJPA, Toplink, ...) - with their pros and cons. Cons: changing from HQL to JPQL in scripts (solution is using independent QL and translate to JPQL)

    2) installation creating script (building *.war) - selecting DB type, DB connection, encoding of input and output, ... 

  • VincentMassol
    VincentMassol, 2007/03/02 08:29

    Hi there,

    For 1) we want to do even better (if possible this needs to be validated) by using JCR which is a superset of JPA, etc. For 2) I assume you're talking about the build. I've been working on this but it's not finished yet.

    Thanks -Vincent

  • kristian
    kristian, 2007/04/24 13:57

    hi, for the future i'd suggest Tapestry 5 as web framework. furthermore i'd suggest tapestry IoC for configuration because it allows OSGI like components (jar files with manifest) to be deployed that get discovered and configured automatically... of course it does not offer all OSGI features emoticon_smile

Get Connected