Re[2]: Looking for Tapestry+Hibernate examples...

["Dmitry I. Zubarovsky" <au...@rambler.ru>]

Hello Karel!

HISPACTA is really cool!
I wonder, why do not u use spring classes for obtaining localized
messages.

I wrote this in app context:
        <!--
                Message source for this context, loaded from localized "messages_xx" files 
        -->
        <bean id="messageSource" 
                class="org.springframework.context.support.ResourceBundleMessageSource">
                <property name="basename">
                        <value>globalmessages</value>
                </property>
        </bean>

and obtain that bean from Appcontext in engine implementation
        
Regards,
Dima

KM> Hi,

KM> I have just created and published another example application called HISPACTA (Hibernate + Spring + Acegi security + Tapestry):
KM> http://sourceforge.net/projects/hispacta

KM> It is a simple intranet application including user details and possibility to publish news.

KM> It is in its early stage, the application is completely working, but there is no readme nor documentation created yet.

KM> To point out a few points how it differs from the better petshop:
KM> * complete security (authentication and authorization) is done using Acegi Security System for Spring
KM> * there is quite a lot of tests (unit + integration tests) using JUnit, DbUnit, easymock and JWebUnit, so it is also an example of some testing possibilities
KM> * it is "CRUDL oriented" - there are abstract classes with MethodTemplates for Create / Read / Update / Delete (detail page) and Listing pages

KM> Any comments welcome,
KM> Karel


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: Re[2]: Looking for Tapestry+Hibernate examples...

[Karel Miarka <ka...@issa.cz>]

Hi Dima,

> HISPACTA is really cool!

Thanks! It is nice to hear some nice feedback. :-)


> I wonder, why do not u use spring classes for obtaining localized
> messages.
>
> I wrote this in app context:
>         <!--
>                 Message source for this context, loaded from localized
"messages_xx" files
>         -->
>         <bean id="messageSource"
>
class="org.springframework.context.support.ResourceBundleMessageSource">
>                 <property name="basename">
>                         <value>globalmessages</value>
>                 </property>
>         </bean>
>
> and obtain that bean from Appcontext in engine implementation

Looks interesting. I have created my custom global message source before I
have started to use Spring, so that's why it is used in Hispacta now. But I
will try the approach you suggested and change it in Hispacta. I also plan
to rename the package hispacta.bo (business objects) to hispacta.model ,
because it will be probably less confusing with business services.

Regards,
Karel



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org