For the report functionality, I have to say, that this part
can not be
meant stable in my working environment. Maybe I do something
wrong, but
it appears quite often, that when I add some column or row
content to
the report, Scarab can not render the default.vm afterwards
and crashes.
The report is defined as it should be (so I concentrate on
other
things), but it doesn't look stable to the user (and it is
not in fact).
Andrey Larionov schrieb:
> Trunk is stable only if we exclude locale bundles with
errors
> (reported on our maven instance). Also LDAPSecurity
have some
> unpredictable behaviour (password change, expiration
and so on), also
> current implementation (without my patch apply) don't
support ldap
> auth (criticaly for MS AD) - as for me it should be
marked as
> Experimental, before we complete or rewrite to make use
as primary
> security service.
>
> We use scarab trunk for more then 7 month. No crashes
or critical
> errors occurred (we don't use report functionality)
>
> Maybe your should copy trunk to branch, and work on
it?
>
> On Wed, Mar 26, 2008 at 5:57 PM, Hussayn Dabbous
> <hussayn.dabbous saxess.com> wrote:
>
>> Hi;
>>
>> I know, trunk is always considered a risk...
>> But is it worth a try to use it as a replacement
>> for 0.21 ? I ask, because i want to start new
>> functionality now, but i prefer to start right
>> from trunk, instead of our 0.21 release, so that
>> Scarab can profit as a whole from my next 2
months
>> work...
>>
>> Do i have to be prepared for any known and severe
problems ?
>> (I can live with the normal risk of getting
unexpected behaviour
>> from untested development version...)
>>
>> Any input for decision making is welcome.
>>
>> regards, hussayn
>> --
>> Dr. Hussayn Dabbous
>> SAXESS Software Design GmbH
>> Neuenhöfer Allee 125
>> 50935 Köln
>>
>> tel.: +49 221 560 11 0
>> fax.: +49 221 560 11 20
>>
>> mailto:infosaxess.de
>> http://www.saxess.de
>> http://www.saxess.com
>> http://www.saxess.org
>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribescarab.tigris.org
>> For additional commands, e-mail: dev-helpscarab.tigris.org
>>
>>
>>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribescarab.tigris.org
> For additional commands, e-mail: dev-helpscarab.tigris.org
>
>
>
>
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribescarab.tigris.org
For additional commands, e-mail: dev-helpscarab.tigris.org
|