smartweb-devel — Dedicated to framework developers

Re: [smartweb-devel] Smartweb Auth and problem with XDoclet/ Hibernate union subclass

[Roberto Lo G. <rlo...@sm...>]

+1 to switch back to joined-subclass inheritance mapping if this
solves our portability problems.

2007/11/6, svetrini <st...@gm...>:
>
> At this time smartweb auth  has a little problem... Actually union subclass
> has.
> hbm generation fails due to a bug on xdoclet union subclass.
> We have just sended patches to xdoclet team but none new version was
> released.
> I recently found another minor problem on auth module. It doesn't create
> schema on dbs different from PostgreSQL ( I tried on MySQL and HSQL ) this
> is not our bug but a knowed hibernate  problem.
>
> So...
>
> What do you think about change from union subclass to another subclass type?
>
> I'm waiting to your answers... :-)
> --
> View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13615761
> Sent from the SmartWeb Developers mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> smartweb-devel mailing list
> sma...@li...
> https://lists.sourceforge.net/lists/listinfo/smartweb-devel
>

Re: [smartweb-devel] Hibernate hql,sql query slow pagination

[Roberto Lo G. <rlo...@sm...>]

Again, and for the sake of honesty, neither you are allowed to vote on
the SmartWeb Project (you are allowed to vote on the auth module but
not on the core), but we'll take in account your opinion.

May be we need to be more precise on membership roles on the site.

Anyway I'll take the opportunity to express my vote:
  +1 to the count method
  +1 to the alien package into smartweb.jar

Obviously the premise is to switch to default Hibernate if and when
thay decide to provide such feature through their official API.

2007/11/6, svetrini <st...@gm...>:
>
> I vote for the  solution with the count method and to  adding packages to
> smartweb (waiting for hibernate patch, obviously!)
>
> good work
>
>
> Gaetano Perrone wrote:
> >
> > Until hibernate group answer to our patch request I suggest a vote for one
> > of the following solution :
> > I remember all that the problem is to modify a given hibernate query(hql
> > or sql query) to count the results without extracting it.
> > The problem that requires the hibernate patch is the retrieving of the
> > query parameters for a given hibernate query, because of the protected
> > visibility of the getNamedParams(), getTypes(),getValues() (positional
> > parameters). To solve the problem there are two approch:
> >
> > 1. Make the protected  methods getNamedParams(), getTypes(),getValues() on
> > the AbstractQueryImpl hibernate class public.
> >
> > 2. Adding on the hibernate QueryImpl SqlQueryImpl final class a public
> > count() method in addition to list(), uniqueResult() methods.
> >
> > For each approch there was anothere choice to do until hibernate group
> > approves the patch:
> >
> > a) adding an org.hibernate(needed only by the second solution with the
> > patched Query class ) and org.hibernate.impl (with the patched
> > AbstractQueryImpl class for the first solution and the QueryImpl and
> > SQLQueryImpl for second solution)package to smartweb framework
> >
> > b) Provide for smartweb user's that would use fast hql/sql pagination an
> > zip file with the patch to apply to hibernate jar as an external resource.
> >
> > I suggest a vote for the 2 choices. I hope u answer soon...
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Hibernate-hql%2Csql-query-slow-pagination-tf4751460s17546.html#a13614378
> Sent from the SmartWeb Developers mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> smartweb-devel mailing list
> sma...@li...
> https://lists.sourceforge.net/lists/listinfo/smartweb-devel
>

Re: [smartweb-devel] Smartweb Auth and problem with XDoclet/ Hibernate union subclass

[Pino C. <gco...@gm...>]

I think the choice of a subclass different from the union is excellent. The
important thing in this context where you are to release a stable version of
auth. Consider a person like me who has always used the old auth and was
well to integrate it within their applications to use a version that does
not support MySQL. I'll be gonig to use the old version.
	
		

svetrini wrote:
> 
> At this time smartweb auth  has a little problem... Actually union
> subclass has.
> hbm generation fails due to a bug on xdoclet union subclass.
> We have just sended patches to xdoclet team but none new version was
> released.
> I recently found another minor problem on auth module. It doesn't create
> schema on dbs different from PostgreSQL ( I tried on MySQL and HSQL ) this
> is not our bug but a knowed hibernate  problem.
> 
> So...
> 
> What do you think about change from union subclass to another subclass
> type?
> 
> I'm waiting to your answers... :-)
> 

-- 
View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13617096
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] Time... JODA

[Pino C. <gco...@gm...>]

Hi ..
Interesting .. as a library could be useful in the implementation of
applications in which the dates are at the root of everything .. Like the
calculation of the delay of a goal in a really difficult context.. But I
think it is not necessarily helpful in your case, you could use the good old
Calendar without importing it.
	
	

svetrini wrote:
> 
> I found a nice lib to manage java time and date in the opensource
> comunity.
> This is JODA ( http://joda-time.sourceforge.net/ )
> I think it is usefuller than standard JDK class.
> I tried to use it in Some example Handler inside the auth method.
> exactly i used Period and Inteval to manage Time interval during which an
> user is allowed to execute a login.
> 
> Maybe an entire lib is too much, to use only this feature...
> 
> What do you think about?
> 

-- 
View this message in context: http://www.nabble.com/Time...-JODA-tf4760551s17546.html#a13616779
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

[smartweb-devel] Smartweb Auth and problem with XDoclet/ Hibernate union subclass

[svetrini <st...@gm...>]

At this time smartweb auth  has a little problem... Actually union subclass
has.
hbm generation fails due to a bug on xdoclet union subclass.
We have just sended patches to xdoclet team but none new version was
released.
I recently found another minor problem on auth module. It doesn't create
schema on dbs different from PostgreSQL ( I tried on MySQL and HSQL ) this
is not our bug but a knowed hibernate  problem.

So...

What do you think about change from union subclass to another subclass type?

I'm waiting to your answers... :-)
-- 
View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13615761
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

[smartweb-devel] Time... JODA

[svetrini <st...@gm...>]

I found a nice lib to manage java time and date in the opensource comunity.
This is JODA ( http://joda-time.sourceforge.net/ )
I think it is usefuller than standard JDK class.
I tried to use it in Some example Handler inside the auth method.
exactly i used Period and Inteval to manage Time interval during which an
user is allowed to execute a login.

Maybe an entire lib is too much, to use only this feature...

What do you think about?
-- 
View this message in context: http://www.nabble.com/Time...-JODA-tf4760551s17546.html#a13614454
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] Hibernate hql,sql query slow pagination

[svetrini <st...@gm...>]

I vote for the  solution with the count method and to  adding packages to
smartweb (waiting for hibernate patch, obviously!)

good work


Gaetano Perrone wrote:
> 
> Until hibernate group answer to our patch request I suggest a vote for one
> of the following solution :
> I remember all that the problem is to modify a given hibernate query(hql
> or sql query) to count the results without extracting it.
> The problem that requires the hibernate patch is the retrieving of the
> query parameters for a given hibernate query, because of the protected
> visibility of the getNamedParams(), getTypes(),getValues() (positional
> parameters). To solve the problem there are two approch:
> 
> 1. Make the protected  methods getNamedParams(), getTypes(),getValues() on
> the AbstractQueryImpl hibernate class public.
> 
> 2. Adding on the hibernate QueryImpl SqlQueryImpl final class a public
> count() method in addition to list(), uniqueResult() methods.
> 
> For each approch there was anothere choice to do until hibernate group
> approves the patch:
> 
> a) adding an org.hibernate(needed only by the second solution with the
> patched Query class ) and org.hibernate.impl (with the patched
> AbstractQueryImpl class for the first solution and the QueryImpl and
> SQLQueryImpl for second solution)package to smartweb framework
> 
> b) Provide for smartweb user's that would use fast hql/sql pagination an
> zip file with the patch to apply to hibernate jar as an external resource.
> 
> I suggest a vote for the 2 choices. I hope u answer soon...
> 
> 

-- 
View this message in context: http://www.nabble.com/Hibernate-hql%2Csql-query-slow-pagination-tf4751460s17546.html#a13614378
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] Hibernate hql,sql query slow pagination

[rlogiacco <rlo...@us...>]

Pino Contartese wrote:
> 
> I vote for first choice adding  the new package..waiting for an hibernate
> group answer.
> 

Hi Pino,
we welcome your opinion and contribution about the topic, but you are not
allowed to vote as you are not (yet?) a voting developer on the SmartWeb
Project Community.

If you are interested in becoming a voting developer please refer to our
Contributor Guide (http://smartweb.sourceforge.net/contrib-guide.html) for
more informations.

I wish to assure you your opinion (as the other ones we could receive in the
meantime) is taken in great consideration by the Project Committee as our
decision is mainly focused to your satisfaction :-)

Thank you,
  Roberto Lo Giacco

-- 
View this message in context: http://www.nabble.com/Hibernate-hql%2Csql-query-slow-pagination-tf4751460s17546.html#a13588547
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] Hibernate hql,sql query slow pagination

[Pino C. <gco...@gm...>]

I vote for first choice adding  the new package..waiting for an hibernate
group answer.



Gaetano Perrone wrote:
> 
> Until hibernate group answer to our patch request I suggest a vote for one
> of the following solution :
> I remember all that the problem is to modify a given hibernate query(hql
> or sql query) to count the results without extracting it.
> The problem that requires the hibernate patch is the retrieving of the
> query parameters for a given hibernate query, because of the protected
> visibility of the getNamedParams(), getTypes(),getValues() (positional
> parameters). To solve the problem there are two approch:
> 
> 1. Make the protected  methods getNamedParams(), getTypes(),getValues() on
> the AbstractQueryImpl hibernate class public.
> 
> 2. Adding on the hibernate QueryImpl SqlQueryImpl final class a public
> count() method in addition to list(), uniqueResult() methods.
> 
> For each approch there was anothere choice to do until hibernate group
> approves the patch:
> 
> a) adding an org.hibernate(needed only by the second solution with the
> patched Query class ) and org.hibernate.impl (with the patched
> AbstractQueryImpl class for the first solution and the QueryImpl and
> SQLQueryImpl for second solution)package to smartweb framework
> 
> b) Provide for smartweb user's that would use fast hql/sql pagination an
> zip file with the patch to apply to hibernate jar as an external resource.
> 
> I suggest a vote for the 2 choices. I hope u answer soon...
> 
> 

-- 
View this message in context: http://www.nabble.com/Hibernate-hql%2Csql-query-slow-pagination-tf4751460s17546.html#a13587401
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

[smartweb-devel] Hibernate hql,sql query slow pagination

[Gaetano P. <gpe...@sm...>]

Until hibernate group answer to our patch request I suggest a vote for one
of the following solution :
I remember all that the problem is to modify a given hibernate query(hql
or sql query) to count the results without extracting it.
The problem that requires the hibernate patch is the retrieving of the
query parameters for a given hibernate query, because of the protected
visibility of the getNamedParams(), getTypes(),getValues() (positional
parameters). To solve the problem there are two approch:

1. Make the protected  methods getNamedParams(), getTypes(),getValues() on
the AbstractQueryImpl hibernate class public.

2. Adding on the hibernate QueryImpl SqlQueryImpl final class a public
count() method in addition to list(), uniqueResult() methods.

For each approch there was anothere choice to do until hibernate group
approves the patch:

a) adding an org.hibernate(needed only by the second solution with the
patched Query class ) and org.hibernate.impl (with the patched
AbstractQueryImpl class for the first solution and the QueryImpl and
SQLQueryImpl for second solution)package to smartweb framework

b) Provide for smartweb user's that would use fast hql/sql pagination an
zip file with the patch to apply to hibernate jar as an external resource.

I suggest a vote for the 2 choices. I hope u answer soon...

-- 
View this message in context: http://www.nabble.com/Hibernate-hql%2Csql-query-slow-pagination-tf4751460s17546.html#a13586351
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

[smartweb-devel] Pagination made easier... pheraps!

[rlogiacco <rlo...@us...>]

While correcting some typos on the registry module I found a method which
performs a resource intensive operation (a LIKE clause was used) named
listBySomething.

As per best-practices documentation that method should be named
searchBySomething then I started the refactoring deprecating the previous
method and moving the code inside the newer one... but I suddenly encounter
a naming problem: how should be named the corresponding pageBySomething
method?

If I leave it with the page prefix it will be not obvious the method is
resource intensive... but which other prefix could I use?

I ended up with the following proposal: why don't we use a single method
prefixed with list or search to indicate the complexity and add an optional
parameter to specify the pagination parameters?

For example the preceeding list/search will became

public Collection searchBySomething(Something something, PaginationInfo
info)

where PaginationInfo is an optional value object used to pass the page
number, shown elements and such stuff.

I'll wait for your opinions as this could be a destructive change for many
integrations... obviously we will proceed with deprecation to preserve code
already built.
-- 
View this message in context: http://www.nabble.com/Pagination-made-easier...-pheraps%21-tf4718633s17546.html#a13489223
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] How to organize the Smartweb User's Guide

[rlogiacco <rlo...@us...>]

Gaetano Perrone wrote:
> 
> <p><strong>Following the struts / hibernate approch to the user's guide i
> think about something of there:</strong><br />
> </p>
>   (omissis)
> 

I think the structure is almost ok, I suggest not to mention every module in
here but delegate modules user-guides to modules themselves, I would mention
explicitly here only the auth and i18n modules which are actually more
architectural than the others which are more functional.

Another suggestion I can post is about the examples, which must not be
something like a tutorial (we have another section for that).
-- 
View this message in context: http://www.nabble.com/How-to-organize-the-Smartweb-User%27s-Guide-tf4697476s17546.html#a13489207
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] How to organize the Smartweb User's Guide

[amarini <ann...@gm...>]

>From the key it seems to be a lot of things, I would like to see the
contents, as they turn out, if they are simple, clear and comprehensible, i=
f
they are not wasteful =E2=80=A6 are they yet ready?=20
As they are listed, they seem self-supporting one from one another, it is
therefore? I want to say can I watch for example n=C2=B0 7 without having s=
een n=C2=B0
4 and understand it? Otherwise they would go nested=E2=80=A6 according to t=
heir
possible use, also even repeated inside the different coherent arguments=E2=
=80=A6


Gaetano Perrone wrote:
>=20
> <p><strong>Following the struts / hibernate approch to the user's guide i
> think about something of there:</strong><br />
> </p>
> 1. Introducing Smartweb framework
> <br /><br />
> 2. Architecture<br /><br />
> 3. Setup and configuration<br /><br />
>=20
>   4. Building Model Component
>     <ul>
> =09<li>4.1. Overview</li>
>     <li>4.2. Java Beans and scope</li>
>     <li>4.3. Business Logic domains</li>
> =09</ul>
> </blockquote>
> 5. Building persistence layer with hibernate=20
> <ul>
> =09<li>5.1. Overview</li>
>   <li>5.2. Mapping persistence class wih hibernate and xdoclet</li>
>   <li>5.3. Getting started with BusinessObjectFactory</li>
> </ul>
>   6. Building view components with struts
>   <ul>
>   <li>6.1. Overview</li>
>   <li>6.2. Forms and FormBeans interactionsv
>   <li>6.3. Internationalization and presentation tag library inherited
> from Struts</li>
>   <li>6.4. Query results paging</li>
>   <li>6.5. Forms validation</li>
>   </ul>
>   7. Building controller components
>   <ul>
>   <li>7.1. Overview</li>
>    <li>7.2. Writing action mapping</li>
>    <li>7.3. Getting started with AbstractArchiveAction </li>
>   </ul>
>   8. Getting started with samples<br />
>   //TODO
>   <br /><br />
> 9. Handle application access privilege with auth module
>   <ul>
>   <li>9.1. Overview</li>
>   <li>9.2. Setup and configuration</li>
>   <li>9.3. The auth domain</li>
>  <li>9.4. Administration pages</li>
>   <li>9.5. Getting started with auth samples</li>
>   </ul>
>   10. Registry module=20
>   <ul>
>   <li>10.1. Overview</li>
>   <li>10.2. Setup and configuration</li>
>   <li>10.3. The registry domain</li>
>   <li>10.4. Getting started with auth samples </li>
>   </ul>
>   11. Best practice
>   <ul>
>   <li>11.1 Handle transaction</li>
>   <li>11.2 Where place business rule?</li>
>   <li>11.3 Using criteria, hql or sql queries</li>
>   <li>11.4 Wrapping domains with stateless session bean</li>
>   </ul>
>=20

--=20
View this message in context: http://www.nabble.com/How-to-organize-the-Sma=
rtweb-User%27s-Guide-tf4697476s17546.html#a13489201
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] How to organize the Smartweb User's Guide

[Pino C. <gco...@gm...>]

I fully agree on the structure of documentation.
I was wondering how you would set the example chapter .
Have you in mind to implement a  guide project step by step or something
like that?
In any event you can count on my help ..say what I've to do and I'll do it


Gaetano Perrone wrote:
> 
> <p><strong>Following the struts / hibernate approch to the user's guide i
> think about something of there:</strong><br />
> </p>
> 1. Introducing Smartweb framework
> <br /><br />
> 2. Architecture<br /><br />
> 3. Setup and configuration<br /><br />
> 
>   4. Building Model Component
>     <ul>
> 	<li>4.1. Overview</li>
>     <li>4.2. Java Beans and scope</li>
>     <li>4.3. Business Logic domains</li>
> 	</ul>
> </blockquote>
> 5. Building persistence layer with hibernate 
> <ul>
> 	<li>5.1. Overview</li>
>   <li>5.2. Mapping persistence class wih hibernate and xdoclet</li>
>   <li>5.3. Getting started with BusinessObjectFactory</li>
> </ul>
>   6. Building view components with struts
>   <ul>
>   <li>6.1. Overview</li>
>   <li>6.2. Forms and FormBeans interactionsv
>   <li>6.3. Internationalization and presentation tag library inherited
> from Struts</li>
>   <li>6.4. Query results paging</li>
>   <li>6.5. Forms validation</li>
>   </ul>
>   7. Building controller components
>   <ul>
>   <li>7.1. Overview</li>
>    <li>7.2. Writing action mapping</li>
>    <li>7.3. Getting started with AbstractArchiveAction </li>
>   </ul>
>   8. Getting started with samples<br />
>   //TODO
>   <br /><br />
> 9. Handle application access privilege with auth module
>   <ul>
>   <li>9.1. Overview</li>
>   <li>9.2. Setup and configuration</li>
>   <li>9.3. The auth domain</li>
>  <li>9.4. Administration pages</li>
>   <li>9.5. Getting started with auth samples</li>
>   </ul>
>   10. Registry module 
>   <ul>
>   <li>10.1. Overview</li>
>   <li>10.2. Setup and configuration</li>
>   <li>10.3. The registry domain</li>
>   <li>10.4. Getting started with auth samples </li>
>   </ul>
>   11. Best practice
>   <ul>
>   <li>11.1 Handle transaction</li>
>   <li>11.2 Where place business rule?</li>
>   <li>11.3 Using criteria, hql or sql queries</li>
>   <li>11.4 Wrapping domains with stateless session bean</li>
>   </ul>
> 

-- 
View this message in context: http://www.nabble.com/How-to-organize-the-Smartweb-User%27s-Guide-tf4697476s17546.html#a13489161
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] Configuration file extension misleading

[Pino C. <gco...@gm...>]

I'm not agree about it !!. Maybe the only one missing thing is a really good
devel-guide to explain the fastest and simplest way to configure properly
the configuraton file.:jumping:
Alternatively we can give them, as you say , the possibility to choice..



Pino Contartese wrote:
> 
> 
> 
> rlogiacco wrote:
>> 
>> I started to think the .hcf extension modification was not a so brillant
>> idea for al least two reasons:
>> 
>> 1. it confuses developers which tendo to have difficulties to understand
>> it's just an hibernate.cfg.xml file with a differente name;
>> 2. it confuses programs which need to be configured properly to
>> understand it's an XML file.
>> 
>> May be it would be better to switch back to the standard naming to solve
>> this problems, but we still need to allow custom additional files to be
>> deployed in a shared area. May be a hibernate[-modulename].cfg.xml schema
>> is what we need.
>> 
>> The impact on the file naming is strong as will be the impact on users
>> knowledge: those who already understood the .hcf extension will be
>> confused, but the new ones should find this simpler. We can also allow
>> for both naming for a while...
>> 
>> Waiting for comments and ideas.
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Configuration-file-extension-misleading-tf3192869s17546.html#a13442400
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] Configuration file extension misleading

[Pino C. <gco...@gm...>]

rlogiacco wrote:
> 
> I started to think the .hcf extension modification was not a so brillant
> idea for al least two reasons:
> 
> 1. it confuses developers which tendo to have difficulties to understand
> it's just an hibernate.cfg.xml file with a differente name;
> 2. it confuses programs which need to be configured properly to understand
> it's an XML file.
> 
> May be it would be better to switch back to the standard naming to solve
> this problems, but we still need to allow custom additional files to be
> deployed in a shared area. May be a hibernate[-modulename].cfg.xml schema
> is what we need.
> 
> The impact on the file naming is strong as will be the impact on users
> knowledge: those who already understood the .hcf extension will be
> confused, but the new ones should find this simpler. We can also allow for
> both naming for a while...
> 
> Waiting for comments and ideas.
> 

-- 
View this message in context: http://www.nabble.com/Configuration-file-extension-misleading-tf3192869s17546.html#a13442397
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

[smartweb-devel] How to organize the Smartweb User's Guide

[Gaetano P. <gpe...@sm...>]

Following the struts / hibernate approch to the user's guide i think about
something of there:


1. Introducing Smartweb framework

2. Architecture

3. Setup and configuration


  4. Building Model Component
    

	
4.1. Overview
    
4.2. Java Beans and scope
    
4.3. Business Logic domains
	


5. Building persistence layer with hibernate 

	
5.1. Overview
  
5.2. Mapping persistence class wih hibernate and xdoclet
  
5.3. Getting started with BusinessObjectFactory

  6. Building view components with struts
  

  
6.1. Overview
  
6.2. Forms and FormBeans interactionsv
  
6.3. Internationalization and presentation tag library inherited from Struts
  
6.4. Query results paging
  
6.5. Forms validation
  

  7. Building controller components
  

  
7.1. Overview
   
7.2. Writing action mapping
   
7.3. Getting started with AbstractArchiveAction 
  

  8. Getting started with samples

  //TODO
  

9. Handle application access privilege with auth module
  

  
9.1. Overview
  
9.2. Setup and configuration
  
9.3. The auth domain
 
9.4. Administration pages
  
9.5. Getting started with auth samples
  

  10. Registry module 
  

  
10.1. Overview
  
10.2. Setup and configuration
  
10.3. The registry domain
  
10.4. Getting started with auth samples 
  

  11. Best practice
  

  
11.1 Handle transaction
  
11.2 Where place business rule?
  
11.3 Using criteria, hql or sql queries
  
11.4 Wrapping domains with stateless session bean
  

-- 
View this message in context: http://www.nabble.com/How-to-organize-the-Smartweb-User%27s-Guide-tf4697476s17546.html#a13427690
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

[smartweb-devel] Scoped authorizations are really needed?

[rlogiacco <rlo...@us...>]

I'm wondering if we really need to define scopes into the auth module so
first of all we should define what we intend for scopes...

In my idea scopes are the resources over which a certain permission is
given. Say the user foo is binded to the docmanager role which grants the
permission to access the deleteDocument() method. Imagine each document is
contained into a folder, so each document has an association (1..*) to a
folder... As a sys admin I wish to say the user foo can be a docmanager only
on docs contained into a specific folder set (folders A, B and C for
example) excluding that privilege for any folder not listed.

Actually, to provide such fine grained control on a privilege, we have to
write a custom AuthorizationHandler (say DocumentFolderHandler) binded to
the privilege then, using informations binded to the user's properties (or
the group ones) we should check if the informations match during the
authorization phase.

A less programmatic approach, like something based on a configuration
script, could be a better solution?

Let's start discussion and listen your suggestions...
-- 
View this message in context: http://www.nabble.com/Scoped-authorizations-are-really-needed--tf4529064s17546.html#a12923516
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] How organize documentation

[rlogiacco <rlo...@us...>]

Have you any update on the documentation? We are still waiting your last
revision, as discussed in our last meeting, for inclusion...


amarini wrote:
>=20
> Here I am, take a look to the attached file concerning SmartWeb HomePage,
> it's just a first drawing up, I surely have to more itemize the
> authorization, authentication and auditing exposition and add the
> pertinent link...
>=20
> Just tell me if you agree or not on my laying. So I'll go on :working: in
> that way...
> Thanks
>=20
>  http://www.nabble.com/file/p12652821/Home.apt Home.apt=20
>=20
>=20
> amarini wrote:
>>=20
>> I think I can start...I'll surely need your support, I'll let you know..=
.
>> thanks :-)
>>=20
>>=20
>> rlogiacco wrote:
>>>=20
>>> Agreed! :handshake:
>>>=20
>>> Do you think you can start reorganizing the documentation site? I'll
>>> provide you any support you can need... :-)
>>>=20
>>>=20
>>> amarini wrote:
>>>>=20
>>>> Here some guide lines to organize the documentation.
>>>>=20
>>>> In the first page we should explain who can draw utility by using
>>>> SmartWeb running from the typology of applications for which it is
>>>> recommended, in what it differs from others OpenSource, which
>>>> problematic it tries to resolve and in what way.
>>>>=20
>>>> The user=E2=80=99s manual should be splitted up for the several tier, =
following
>>>> the suggestion that we give, to separate the tasks, for tier. For ever=
y
>>>> tier we should describe how the interaction with the adjacent tier
>>>> happens, which are the tools that we put on hand and how use them. Thi=
s
>>>> manual should cover also JUnit=E2=80=99s tests realization.=20
>>>>=20
>>>> Side by side we should produce a tutorial that could guide step to ste=
p
>>>> in the realization of a web application (e-commerce web site seems to
>>>> be a tempting example). It could also be used inside in order to
>>>> demonstrate the different phases of a project, like how made the
>>>> analysis when and how made tests.=20
>>>>=20
>>>> The guide to the configuration instead should be something much
>>>> specific referred to configuration=E2=80=99s files(currently they are =
only
>>>> copies of external configuration=E2=80=99s files=E2=80=A6.).
>>>>=20
>>>> In this viewpoint the architecture, that at the moment is one of main
>>>> documents, should become a secondary document recalled from other
>>>> documents (in the home, the user=E2=80=99s manual and in the study cas=
e).
>>>>=20
>>>>=20
>>>=20
>>>=20
>>=20
>>=20
>=20
>=20

--=20
View this message in context: http://www.nabble.com/How-organize-documentat=
ion-tf4051907s17546.html#a12922674
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] How organize documentation

[rlogiacco <rlo...@us...>]

I think your work is very good :clap::handshake::clap:

I'm only concerned about the detail level:confused: Do you think this can b=
e
the home page? I'm not really sure: all this infos on the first page may
overwelm a first-time visitor... %-|

What about splitting this into two pages: a lesser detailed one as home pag=
e
and a second one with more detail? Anyway I promise I'll help you with your
SVN problems on first occasion..... so don't forget your notebook this
weekend :-P


amarini wrote:
>=20
> Here I am, take a look to the attached file concerning SmartWeb HomePage,
> it's just a first drawing up, I surely have to more itemize the
> authorization, authentication and auditing exposition and add the
> pertinent link...
>=20
> Just tell me if you agree or not on my laying. So I'll go on :working: in
> that way...
> Thanks
>=20
>  http://www.nabble.com/file/p12652821/Home.apt Home.apt=20
>=20
>=20
> amarini wrote:
>>=20
>> I think I can start...I'll surely need your support, I'll let you know..=
.
>> thanks :-)
>>=20
>>=20
>> rlogiacco wrote:
>>>=20
>>> Agreed! :handshake:
>>>=20
>>> Do you think you can start reorganizing the documentation site? I'll
>>> provide you any support you can need... :-)
>>>=20
>>>=20
>>> amarini wrote:
>>>>=20
>>>> Here some guide lines to organize the documentation.
>>>>=20
>>>> In the first page we should explain who can draw utility by using
>>>> SmartWeb running from the typology of applications for which it is
>>>> recommended, in what it differs from others OpenSource, which
>>>> problematic it tries to resolve and in what way.
>>>>=20
>>>> The user=E2=80=99s manual should be splitted up for the several tier, =
following
>>>> the suggestion that we give, to separate the tasks, for tier. For ever=
y
>>>> tier we should describe how the interaction with the adjacent tier
>>>> happens, which are the tools that we put on hand and how use them. Thi=
s
>>>> manual should cover also JUnit=E2=80=99s tests realization.=20
>>>>=20
>>>> Side by side we should produce a tutorial that could guide step to ste=
p
>>>> in the realization of a web application (e-commerce web site seems to
>>>> be a tempting example). It could also be used inside in order to
>>>> demonstrate the different phases of a project, like how made the
>>>> analysis when and how made tests.=20
>>>>=20
>>>> The guide to the configuration instead should be something much
>>>> specific referred to configuration=E2=80=99s files(currently they are =
only
>>>> copies of external configuration=E2=80=99s files=E2=80=A6.).
>>>>=20
>>>> In this viewpoint the architecture, that at the moment is one of main
>>>> documents, should become a secondary document recalled from other
>>>> documents (in the home, the user=E2=80=99s manual and in the study cas=
e).
>>>>=20
>>>>=20
>>>=20
>>>=20
>>=20
>>=20
>=20
>=20

--=20
View this message in context: http://www.nabble.com/How-organize-documentat=
ion-tf4051907s17546.html#a12659565
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] How organize documentation

[Stefano V <st...@gm...>]

I think the work is good.
No, Let's go on!
:-)

2007/9/13, amarini <ann...@gm...>:
>
>
> Here I am, take a look to the attached file concerning SmartWeb HomePage,
> it's just a first drawing up, I surely have to more itemize the
> authorization, authentication and auditing exposition and add the
> pertinent
> link...
>
> Just tell me if you agree or not on my laying. So I'll go on :working: in
> that way...
> Thanks
>
> http://www.nabble.com/file/p12652821/Home.apt Home.apt
>
>
> amarini wrote:
> >
> > I think I can start...I'll surely need your support, I'll let you
> know...
> > thanks :-)
> >
> >
> > rlogiacco wrote:
> >>
> >> Agreed! :handshake:
> >>
> >> Do you think you can start reorganizing the documentation site? I'll
> >> provide you any support you can need... :-)
> >>
> >>
> >> amarini wrote:
> >>>
> >>> Here some guide lines to organize the documentation.
> >>>
> >>> In the first page we should explain who can draw utility by using
> >>> SmartWeb running from the typology of applications for which it is
> >>> recommended, in what it differs from others OpenSource, which
> >>> problematic it tries to resolve and in what way.
> >>>
> >>> The user's manual should be splitted up for the several tier,
> following
> >>> the suggestion that we give, to separate the tasks, for tier. For
> every
> >>> tier we should describe how the interaction with the adjacent tier
> >>> happens, which are the tools that we put on hand and how use them.
> This
> >>> manual should cover also JUnit's tests realization.
> >>>
> >>> Side by side we should produce a tutorial that could guide step to
> step
> >>> in the realization of a web application (e-commerce web site seems to
> be
> >>> a tempting example). It could also be used inside in order to
> >>> demonstrate the different phases of a project, like how made the
> >>> analysis when and how made tests.
> >>>
> >>> The guide to the configuration instead should be something much
> specific
> >>> referred to configuration's files(currently they are only copies of
> >>> external configuration's files=85.).
> >>>
> >>> In this viewpoint the architecture, that at the moment is one of main
> >>> documents, should become a secondary document recalled from other
> >>> documents (in the home, the user's manual and in the study case).
> >>>
> >>>
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/How-organize-documentation-tf4051907s17546.html#a12=
652821
> Sent from the SmartWeb Developers mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> smartweb-devel mailing list
> sma...@li...
> https://lists.sourceforge.net/lists/listinfo/smartweb-devel
>

Re: [smartweb-devel] How organize documentation

[amarini <ann...@gm...>]

Here I am, take a look to the attached file concerning SmartWeb HomePage,
it's just a first drawing up, I surely have to more itemize the
authorization, authentication and auditing exposition and add the pertinent
link...

Just tell me if you agree or not on my laying. So I'll go on :working: in
that way...
Thanks

http://www.nabble.com/file/p12652821/Home.apt Home.apt=20


amarini wrote:
>=20
> I think I can start...I'll surely need your support, I'll let you know...
> thanks :-)
>=20
>=20
> rlogiacco wrote:
>>=20
>> Agreed! :handshake:
>>=20
>> Do you think you can start reorganizing the documentation site? I'll
>> provide you any support you can need... :-)
>>=20
>>=20
>> amarini wrote:
>>>=20
>>> Here some guide lines to organize the documentation.
>>>=20
>>> In the first page we should explain who can draw utility by using
>>> SmartWeb running from the typology of applications for which it is
>>> recommended, in what it differs from others OpenSource, which
>>> problematic it tries to resolve and in what way.
>>>=20
>>> The user=E2=80=99s manual should be splitted up for the several tier, f=
ollowing
>>> the suggestion that we give, to separate the tasks, for tier. For every
>>> tier we should describe how the interaction with the adjacent tier
>>> happens, which are the tools that we put on hand and how use them. This
>>> manual should cover also JUnit=E2=80=99s tests realization.=20
>>>=20
>>> Side by side we should produce a tutorial that could guide step to step
>>> in the realization of a web application (e-commerce web site seems to b=
e
>>> a tempting example). It could also be used inside in order to
>>> demonstrate the different phases of a project, like how made the
>>> analysis when and how made tests.=20
>>>=20
>>> The guide to the configuration instead should be something much specifi=
c
>>> referred to configuration=E2=80=99s files(currently they are only copie=
s of
>>> external configuration=E2=80=99s files=E2=80=A6.).
>>>=20
>>> In this viewpoint the architecture, that at the moment is one of main
>>> documents, should become a secondary document recalled from other
>>> documents (in the home, the user=E2=80=99s manual and in the study case=
).
>>>=20
>>>=20
>>=20
>>=20
>=20
>=20

--=20
View this message in context: http://www.nabble.com/How-organize-documentat=
ion-tf4051907s17546.html#a12652821
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] How organize documentation

[amarini <ann...@gm...>]

I think I can start...I'll surely need your support, I'll let you know...
thanks :-)


rlogiacco wrote:
>=20
> Agreed! :handshake:
>=20
> Do you think you can start reorganizing the documentation site? I'll
> provide you any support you can need... :-)
>=20
>=20
> amarini wrote:
>>=20
>> Here some guide lines to organize the documentation.
>>=20
>> In the first page we should explain who can draw utility by using
>> SmartWeb running from the typology of applications for which it is
>> recommended, in what it differs from others OpenSource, which problemati=
c
>> it tries to resolve and in what way.
>>=20
>> The user=E2=80=99s manual should be splitted up for the several tier, fo=
llowing
>> the suggestion that we give, to separate the tasks, for tier. For every
>> tier we should describe how the interaction with the adjacent tier
>> happens, which are the tools that we put on hand and how use them. This
>> manual should cover also JUnit=E2=80=99s tests realization.=20
>>=20
>> Side by side we should produce a tutorial that could guide step to step
>> in the realization of a web application (e-commerce web site seems to be
>> a tempting example). It could also be used inside in order to demonstrat=
e
>> the different phases of a project, like how made the analysis when and
>> how made tests.=20
>>=20
>> The guide to the configuration instead should be something much specific
>> referred to configuration=E2=80=99s files(currently they are only copies=
 of
>> external configuration=E2=80=99s files=E2=80=A6.).
>>=20
>> In this viewpoint the architecture, that at the moment is one of main
>> documents, should become a secondary document recalled from other
>> documents (in the home, the user=E2=80=99s manual and in the study case)=
.
>>=20
>>=20
>=20
>=20

--=20
View this message in context: http://www.nabble.com/How-organize-documentat=
ion-tf4051907s17546.html#a12012438
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] Ease auth module integration

[Stefano V <st...@gm...>]

AOP is an elegant solution for our problems.
I decided to integrate the JBoss implementation in smartweb-auth, but I need
some help to execute test for web enviroment.

2007/7/31, rlogiacco <rlo...@us...>:
>
>
> After a long private discussion with svetrini and amarini we've decided to
> move the auth module on an AOP solution to allow easy module
> integration...
> almost transparent to developers which doesn't develop on the auth module
> itself.
> --
> View this message in context:
> http://www.nabble.com/Ease-auth-module-integration-tf4193044s17546.html#a11924274
> Sent from the SmartWeb Developers mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> smartweb-devel mailing list
> sma...@li...
> https://lists.sourceforge.net/lists/listinfo/smartweb-devel
>

[smartweb-devel] Ease auth module integration

[rlogiacco <rlo...@us...>]

After a long private discussion with svetrini and amarini we've decided to
move the auth module on an AOP solution to allow easy module integration...
almost transparent to developers which doesn't develop on the auth module
itself.
-- 
View this message in context: http://www.nabble.com/Ease-auth-module-integration-tf4193044s17546.html#a11924274
Sent from the SmartWeb Developers mailing list archive at Nabble.com.