#4 — Poseidon 4.0 support missing

StateResolved
Version: 1.4.0
AreaUML tool support
Issue typeBug
SeverityCritical
Submitted byReinout van Rees
Submitted onDec 14, 2005
Responsible Philipp Auersperg
Target release: 1.4.1
Return to tracker
Last modified on Jan 05, 2009 by Matthew Wilkes




With Poseidon 4.0, AGX generates StringFields instead of LinesFields, IntegerFields, etc.

Added by(anonymous)onDec 22, 2005 07:00 PM
Severity: CriticalImportant
Target release: 1.4.1None
FWIW: Same problem here.
Added by(anonymous)onDec 27, 2005 10:47 PM
In the XMI output of Poseidon 4.0 I've substituted globally, with a text editor
  UML2:TypedElement
with
  UML:StructuralFeature
in order to recover the syntax of the XMI of Poseidon 3.x
It sems to work!

Giovanni Toffoli
toffoli at uni.net
Added by(anonymous)onJan 06, 2006 09:59 PM
Thanks, that workaround worked for me too!
Added bynilshaagenonJan 09, 2006 10:17 AM
I did it the other way around: in XMIParser.py substitute " UML:StructuralFeature " with "UML2:TypedElement"; seems to be working and is more convenient when you generate frequently...
^^Thanks for the hint.


Added byReinout van ReesonJan 09, 2006 10:50 AM
Issue state: openin-progress
I've added that latest fix to XMIParser.py on trunk. In a bit different way (I didn't replace, I only turned it into a list with both the old and the new option).

Could someone test it with poseidon 4.0? It doesn't break old code, at least. I won't close the issue yet as there might be other 4.0-related things.
Added byLarsonJan 09, 2006 01:01 PM
Target release: None1.4.1
Sorry, but I to report that this fix does not resolve the problems here when using .zuml files from Poseidon 4.0. I still get only string fields instead of int/float/...





Added bydavidpetraitisonJan 16, 2006 02:21 PM
I added the patch to XMIParser.py and the fields are now generated properly but...

I have a problem that 4.0 put the tagged values in the model OUTSIDE of the widget. This means that I have to hand edit the schema to get e.g. the labels and descriptions to appear. Is this a user error or soemthing in Poseidon 4.0?

David




Added bydavidpetraitisonJan 17, 2006 02:16 PM
 

Reinout,
This is weird! When I did a replace on the UMLType with the UML2Type that seems to work.
What happened in 3.2 now seems also to be the case in 4.0 (patched): Whe I have tagged values such as 'label' and 'description' in order for them to be rendered with the widget they need to be inside the widget declaration like

  StringField('logURLdescription',
       widget=StringWidget(
           label='URL',
           description="Lien à la déscription longue de editeur",
           label_msgid='epfLogiciel_label_logURLdescription',
           description_msgid='epfLogiciel_help_logURLdescription',
           i18n_domain='epfLogiciel',
       ),
   ),

What AGX is spitting out is:

   StringField('logURLdescription',
       widget=StringWidget(
           label='logURLdescription',
           description="Lien à la déscription longue de editeur",
           label_msgid='epfLogiciel_label_logURLdescription',
           description_msgid='epfLogiciel_help_logURLdescription',
           i18n_domain='epfLogiciel',
       ),
       description="Lien à la déscription longue de editeur",
       label="URL"
   ),

Which renders the ugly internal field name as the widget label and drops the description.

Also you are right about going backwards in Poseidon - it doesn't work. I had to redo the design from scratch 8^(-

I am cross posting this onto http://plone.org/products/archgenxml/issues/4
Regards,
David


Reinout van Rees wrote:



  David Petraitis wrote:



  Rienhout,

I noticed that you posted a workaround to the "string only" ouptut for Poseidon 4.0. Due to that problem I went back to 3.2 and found that 3.2 has problems as well in my configuarion. Can you tell me where to download the 4.0 patch?
 

My patch didn't work. There's a workaround (by hand => nasty) published on http://plone.org/products/archgenxml/issues/4 .

What kind of problems do you have with 3.2? (Using a model from a newer poseidon version in an older one is often a problem, btw).

Reinout

 


Added bydavidpetraitisonJan 17, 2006 03:02 PM
Sorry for last post found the problem ...

just a little to quick in writing my tagged values!





Added by(anonymous)onJan 17, 2006 03:10 PM
Hi,

It now seems to be working Ok for me with the following patch;
(assumes XMI 1.1)

SVN update as of 15:00 GMT (17 Jan) .. apply;

461c461,462
< TYPE = 'UML:StructuralFeature.type'
---
> #TYPE = 'UML:StructuralFeature.type'
> TYPE = 'UML2:TypedElement.type'

..

:-)

hth
Gareth.
Added by(anonymous)onJan 17, 2006 03:26 PM
.. As I'm here .. if someone could fix the comment order on this page (possibly sort by date) and even the ability to register and/or log in to the site , that would be great .. :)
Added byReinout van ReesonJan 17, 2006 10:40 PM
Severity: ImportantCritical
Too many people are asking about this, so I upped the severity to "critical".
Added by(anonymous)onJan 18, 2006 12:03 AM
Lack of order in these responses is a little worrying (!)
Added byLarsonJan 21, 2006 06:59 PM

Now works great here with changes from SVN as of today. Thanks a lot zworkb!

Lars
Added byJens W. KleinonJan 28, 2006 11:51 AM
Issue state: in-progressresolved
Phil fixed it in trunk. Lets close the issue :-)

Add response

Please enter your response below