Re: Re: [Andromda-user] bpm4struts: model validations

2004-08-17 Thread Chad Brandon

- Original Message - 
From: <[EMAIL PROTECTED]>
To: "Chad Brandon" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, August 17, 2004 1:56 AM
Subject: Re: Re: [Andromda-user] bpm4struts: model validations


>
> Hello Chad,
>
> thank you for your detailed answer as sorry for the delay of this
feedback.

You're welcome.

>
> 1. I fixed the bug in the M2 stable release as you said and it seems to
> work pretty well. I tried it with some errors in my model and got very
> helpful validation error messages. That's cool!
>
> 2. I totaly agree with you that meaningful exception messages are an
> absolute must have for a MDA generator framework. My greatest problems
with
> andromda at the beginning were exception messages of the mda target that
> didn't give any clue on what was wrong in the model.
> But one more question on the validation process: will the generator stop
as
> soon as the first error in the model occurs or will it first run a
complete
> validation on the whole model and report them all? (I haven't tried it
out,
> I have to admit...)

It should list them all out when your model is done processing (not stopping
on the first one)

>
> 3. What I would like to have in the log files is an info about which model
> element is currently processed by the templates. Is there any way to add
> this information to the log output? That would be really great. (Or is it
> allready there and I just haven't seen it?)

I think it should be there for each cartridge log, so for example in
andromda-bpm4struts.log, you should see something like this:

2004-08-16 23:20:55,437 - performing VelocityTemplateEngine.processTemplate
with templateFile 'templates/StrutsRolesProperties.vsl' and templateObjects
'{xhtml=false, serverValidation=true, welcomeFileName=index.jsp,
applicationUseCase=org.andromda.metafacades.uml14.ModelElementFacadeLogicImp
l[my.onlinestore.purchase.Purchase Items], security=false,
clientValidation=true, securityRealm=other,
[EMAIL PROTECTED], breadCrumbs=true}'

It basically tells you all the info in the template context, does this work
for you or are you looking for something else?

>
> Regards
> Stefan
>
>
>
>
>
> Unfortunately not everything has constraints defined,
> so some things won't have messages. However in most
> cases, at the end of model processing you should see a
> list of model validation errors telling you what
> you've done wrong (they are collected during
> validation and then listed at the end of processing).
> But, (and this is my fault), there's a bug in the M2
> release, the message telling you exactly what is wrong
> is not being rendered, this means the messages will
> all say something like this:
> "$str.toSingleLine($constraintDocumentation)" (instead
> of the real message).  This bug is fairly annoying and
> we've been contemplating doing an M3 release faily
> soon just so we can have this working correctly (since
> its an important feature).
>
> This bug (its in the meta cartridge) has also lead us
> to realize the importance of testing cartridges each
> time we build.  So we've come up something that should
> work pretty well for that. I'll be getting that
> testing framework done soon.
>
> If you'd like to fix this bug before M3 (or you can
> always build from current CVS), its pretty easy to to
> do, what you'll need to do is the following:
>
> 1) download the M2 source distribution.
> 2) unzip to any directory and navigate to
> andromda-src*/cartridges/andromda-meta/src/META-INF
> 3) Open up andromda-cartridge.xml in that directory
> and change this template object className to be
> "org.andromda.core.common.StringUtilsHelper"
> 4)change back to andromda-src*/
> 5) type 'maven bootstrap-install'
> 6) type 'maven clean'
> 7) type 'maven dist'
>
> You should find the distribution in
> andromda-src*/target/distributions (and they all
> should
> have the correct validation messages)
>
> Chad
>
>
>
>
>
>




---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
___
Andromda-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-user


Re: Re: Re: [Andromda-user] bpm4struts: model validations

2004-08-17 Thread Chad Brandon
Great!  Not a problem.

- Original Message - 
From: <[EMAIL PROTECTED]>
To: "Chad Brandon" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, August 17, 2004 7:35 AM
Subject: Re: Re: Re: [Andromda-user] bpm4struts: model validations


>
> Hi Chad,
>
> the log output you showed in your mail provides all the infos that I would
> like to need.
> It seems that I just didn't read the log file well...
>
> Sorry for that!
>
> Regards
> Stefan
>
>
>
>
>
> |+--->
> ||  "Chad|
> ||  Brandon" |
> ||  <[EMAIL PROTECTED]|
> ||  ahoo.com>|
> ||   |
> ||  17.08.2004   |
> ||  13:17|
> ||   |
> |+--->
>
>---
---------|
>   |
|
>   |   An: <[EMAIL PROTECTED]>
|
>   |   Kopie:  <[EMAIL PROTECTED]>
|
>   |   Thema:  Re: Re: [Andromda-user] bpm4struts: model validations
|
>
>---
-|
>
>
>
>
>
> - Original Message -----
> From: <[EMAIL PROTECTED]>
> To: "Chad Brandon" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, August 17, 2004 1:56 AM
> Subject: Re: Re: [Andromda-user] bpm4struts: model validations
>
>
> >
> > Hello Chad,
> >
> > thank you for your detailed answer as sorry for the delay of this
> feedback.
>
> You're welcome.
>
> >
> > 1. I fixed the bug in the M2 stable release as you said and it seems to
> > work pretty well. I tried it with some errors in my model and got very
> > helpful validation error messages. That's cool!
> >
> > 2. I totaly agree with you that meaningful exception messages are an
> > absolute must have for a MDA generator framework. My greatest problems
> with
> > andromda at the beginning were exception messages of the mda target that
> > didn't give any clue on what was wrong in the model.
> > But one more question on the validation process: will the generator stop
> as
> > soon as the first error in the model occurs or will it first run a
> complete
> > validation on the whole model and report them all? (I haven't tried it
> out,
> > I have to admit...)
>
> It should list them all out when your model is done processing (not
> stopping
> on the first one)
>
> >
> > 3. What I would like to have in the log files is an info about which
> model
> > element is currently processed by the templates. Is there any way to add
> > this information to the log output? That would be really great. (Or is
it
> > allready there and I just haven't seen it?)
>
> I think it should be there for each cartridge log, so for example in
> andromda-bpm4struts.log, you should see something like this:
>
> 2004-08-16 23:20:55,437 - performing
VelocityTemplateEngine.processTemplate
> with templateFile 'templates/StrutsRolesProperties.vsl' and
templateObjects
> '{xhtml=false, serverValidation=true, welcomeFileName=index.jsp,
>
applicationUseCase=org.andromda.metafacades.uml14.ModelElementFacadeLogicImp
>
> l[my.onlinestore.purchase.Purchase Items], security=false,
> clientValidation=true, securityRealm=other,
> [EMAIL PROTECTED], breadCrumbs=true}'
>
> It basically tells you all the info in the template context, does this
work
> for you or are you looking for something else?
>
> >
> > Regards
> > Stefan
> >
> >
> >
> >
> >
> > Unfortunately not everything has constraints defined,
> > so some things won't have messages. However in most
> > cases, at the end of model processing you should see a
> > list of model validation errors telling you what
> > you've done wrong (they are collected during
> > validation and then listed at the end of processing).
> > But, (and this is my fault), there's a bug in the M2
> > release, the message telling you exactly what is wrong
> > is not being rendered, this means the messages will
> > all say something like this:
> > "$str.toSingleLine($constraintDocumentation)" (instead
> > of the real message).  This bug is fairly annoying and
> > we've been contemplating doing an M3 release faily
> > soon just so we can have this working correctl

Re: Re: Re: [Andromda-user] bpm4struts: model validations

2004-08-17 Thread stefan . scheidt

Hi Chad,

the log output you showed in your mail provides all the infos that I would
like to need.
It seems that I just didn't read the log file well...

Sorry for that!

Regards
Stefan





|+--->
||  "Chad|
||  Brandon" |
||  <[EMAIL PROTECTED]|
||  ahoo.com>|
||   |
||  17.08.2004   |
||  13:17|
||   |
|+--->
  
>|
  |
|
  |   An: <[EMAIL PROTECTED]>  
   |
  |   Kopie:  <[EMAIL PROTECTED]>  
      |
  |   Thema:  Re: Re: [Andromda-user] bpm4struts: model validations
|
  
>|





- Original Message -
From: <[EMAIL PROTECTED]>
To: "Chad Brandon" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, August 17, 2004 1:56 AM
Subject: Re: Re: [Andromda-user] bpm4struts: model validations


>
> Hello Chad,
>
> thank you for your detailed answer as sorry for the delay of this
feedback.

You're welcome.

>
> 1. I fixed the bug in the M2 stable release as you said and it seems to
> work pretty well. I tried it with some errors in my model and got very
> helpful validation error messages. That's cool!
>
> 2. I totaly agree with you that meaningful exception messages are an
> absolute must have for a MDA generator framework. My greatest problems
with
> andromda at the beginning were exception messages of the mda target that
> didn't give any clue on what was wrong in the model.
> But one more question on the validation process: will the generator stop
as
> soon as the first error in the model occurs or will it first run a
complete
> validation on the whole model and report them all? (I haven't tried it
out,
> I have to admit...)

It should list them all out when your model is done processing (not
stopping
on the first one)

>
> 3. What I would like to have in the log files is an info about which
model
> element is currently processed by the templates. Is there any way to add
> this information to the log output? That would be really great. (Or is it
> allready there and I just haven't seen it?)

I think it should be there for each cartridge log, so for example in
andromda-bpm4struts.log, you should see something like this:

2004-08-16 23:20:55,437 - performing VelocityTemplateEngine.processTemplate
with templateFile 'templates/StrutsRolesProperties.vsl' and templateObjects
'{xhtml=false, serverValidation=true, welcomeFileName=index.jsp,
applicationUseCase=org.andromda.metafacades.uml14.ModelElementFacadeLogicImp

l[my.onlinestore.purchase.Purchase Items], security=false,
clientValidation=true, securityRealm=other,
[EMAIL PROTECTED], breadCrumbs=true}'

It basically tells you all the info in the template context, does this work
for you or are you looking for something else?

>
> Regards
> Stefan
>
>
>
>
>
> Unfortunately not everything has constraints defined,
> so some things won't have messages. However in most
> cases, at the end of model processing you should see a
> list of model validation errors telling you what
> you've done wrong (they are collected during
> validation and then listed at the end of processing).
> But, (and this is my fault), there's a bug in the M2
> release, the message telling you exactly what is wrong
> is not being rendered, this means the messages will
> all say something like this:
> "$str.toSingleLine($constraintDocumentation)" (instead
> of the real message).  This bug is fairly annoying and
> we've been contemplating doing an M3 release faily
> soon just so we can have this working correctly (since
> its an important feature).
>
> This bug (its in the meta cartridge) has also lead us
> to realize the importance of testing cartridges each
> time we build.  So we've come up something that should
> work pretty well for that. I'll be getting that
> testing framework done soon.
>
> If you'd like to fix this bug before M3 (or you can
> always build from current CVS), its pretty easy to to
> do, what you'll need to do is the following:
>
> 1) download the M2 source dis

Re: Re: [Andromda-user] bpm4struts: model validations

2004-08-16 Thread stefan . scheidt

Hello Chad,

thank you for your detailed answer as sorry for the delay of this feedback.

1. I fixed the bug in the M2 stable release as you said and it seems to
work pretty well. I tried it with some errors in my model and got very
helpful validation error messages. That's cool!

2. I totaly agree with you that meaningful exception messages are an
absolute must have for a MDA generator framework. My greatest problems with
andromda at the beginning were exception messages of the mda target that
didn't give any clue on what was wrong in the model.
But one more question on the validation process: will the generator stop as
soon as the first error in the model occurs or will it first run a complete
validation on the whole model and report them all? (I haven't tried it out,
I have to admit...)

3. What I would like to have in the log files is an info about which model
element is currently processed by the templates. Is there any way to add
this information to the log output? That would be really great. (Or is it
allready there and I just haven't seen it?)

Regards
Stefan





Unfortunately not everything has constraints defined,
so some things won't have messages. However in most
cases, at the end of model processing you should see a
list of model validation errors telling you what
you've done wrong (they are collected during
validation and then listed at the end of processing).
But, (and this is my fault), there's a bug in the M2
release, the message telling you exactly what is wrong
is not being rendered, this means the messages will
all say something like this:
"$str.toSingleLine($constraintDocumentation)" (instead
of the real message).  This bug is fairly annoying and
we've been contemplating doing an M3 release faily
soon just so we can have this working correctly (since
its an important feature).

This bug (its in the meta cartridge) has also lead us
to realize the importance of testing cartridges each
time we build.  So we've come up something that should
work pretty well for that. I'll be getting that
testing framework done soon.

If you'd like to fix this bug before M3 (or you can
always build from current CVS), its pretty easy to to
do, what you'll need to do is the following:

1) download the M2 source distribution.
2) unzip to any directory and navigate to
andromda-src*/cartridges/andromda-meta/src/META-INF
3) Open up andromda-cartridge.xml in that directory
and change this template object className to be
"org.andromda.core.common.StringUtilsHelper"
4)change back to andromda-src*/
5) type 'maven bootstrap-install'
6) type 'maven clean'
7) type 'maven dist'

You should find the distribution in
andromda-src*/target/distributions (and they all
should
have the correct validation messages)

Chad








---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
___
Andromda-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-user


Re: [Andromda-user] bpm4struts: model validations

2004-08-13 Thread Chad Brandon
Unfortunately not everything has constraints defined,
so some things won't have messages. However in most
cases, at the end of model processing you should see a
list of model validation errors telling you what
you've done wrong (they are collected during
validation and then listed at the end of processing). 
But, (and this is my fault), there's a bug in the M2
release, the message telling you exactly what is wrong
is not being rendered, this means the messages will
all say something like this:
"$str.toSingleLine($constraintDocumentation)" (instead
of the real message).  This bug is fairly annoying and
we've been contemplating doing an M3 release faily
soon just so we can have this working correctly (since
its an important feature).  

This bug (its in the meta cartridge) has also lead us
to realize the importance of testing cartridges each
time we build.  So we've come up something that should
work pretty well for that. I'll be getting that
testing framework done soon.

If you'd like to fix this bug before M3 (or you can
always build from current CVS), its pretty easy to to
do, what you'll need to do is the following:

1) download the M2 source distribution.  
2) unzip to any directory and navigate to
andromda-src*/cartridges/andromda-meta/src/META-INF
3) Open up andromda-cartridge.xml in that directory
and change this template object className to be
"org.andromda.core.common.StringUtilsHelper" 
4)change back to andromda-src*/
5) type 'maven bootstrap-install'
6) type 'maven clean'
7) type 'maven dist'

You should find the distribution in
andromda-src*/target/distributions (and they all
should
have the correct validation messages)

Chad


--- [EMAIL PROTECTED] wrote:

> Hi all,
> 
> I'm currently using the bpm4struts cartridge with
> the AndroMDA3.0M2 release
> and have a question about the new model validation
> features.
> 
> I just modeled an activity graph where I forgot to
> assign the FrontEndView
> stereotype to some action states.
> Unfortunately I still got error messages like this:
> 
>  [andromda] ERROR [Cartridge] Error performing
> Cartridge.processWithTemplate with template
> 'templates/StrutsAction.vsl',
> template context '{xhtml=false,
> serverValidation=true,
> welcomeFileName=index.jsp,
>
class=org.andromda.metafacades.uml14.ModelElementFacadeLogicImpl,
> security=false, clientValidation=true,
> securityRealm=other,
>
[EMAIL PROTECTED]'
> and cartridge
> 'bpm4struts'
>  [andromda]
>
org.apache.velocity.exception.MethodInvocationException:
> Invocation of method 'getInput' in  class
>
org.andromda.cartridges.bpm4struts.metafacades.StrutsActionLogicImpl
> threw
> exception class java.lang.ClassCastException : null
>  [andromda] at
>
org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:193)
> ...
> 
> I hoped to get some kind off validation errors which
> at least tells me
> which model element caused the problems.
> 
> Is the model validation allready "active" or is
> there something I have to
> do to activate model validation?
> 
> Regards
> Stefan
> 
> 
> 
> 
> 
>
---
> SF.Net email is sponsored by Shop4tech.com-Lowest
> price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R
> for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping
> and Free Gift.
>
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> ___
> Andromda-user mailing list
> [EMAIL PROTECTED]
>
https://lists.sourceforge.net/lists/listinfo/andromda-user
> 



---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
___
Andromda-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-user