Personal tools
You are here: Home Products ArchGenXML Issue tracker Poseidon 4.0 support missing
Document Actions

#4 — Poseidon 4.0 support missing

State Resolved
Version: 1.4.0
Area UML tool support
Issue type Bug
Severity Critical
Submitted by Reinout van Rees
Submitted on Dec 14, 2005
Responsible Philipp Auersperg
Target release: 1.4.1
Return to tracker
Last modified on Jan 28, 2006 by Jens W. Klein




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

Added by (anonymous) on December 22, 2005 - 19:00
Severity: CriticalImportant
Target release: 1.4.1None
FWIW: Same problem here.
Added by (anonymous) on December 27, 2005 - 22:47
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) on January 6, 2006 - 21:59
Thanks, that workaround worked for me too!
Added by nilshaagen on January 9, 2006 - 10:17
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 by Reinout van Rees on January 9, 2006 - 10:50
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 by Lars on January 9, 2006 - 13:01
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 by davidpetraitis on January 16, 2006 - 14:21
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 by davidpetraitis on January 17, 2006 - 14:16
 

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 by davidpetraitis on January 17, 2006 - 15:02
Sorry for last post found the problem ...

just a little to quick in writing my tagged values!





Added by (anonymous) on January 17, 2006 - 15:10
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) on January 17, 2006 - 15:26
.. 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 by Reinout van Rees on January 17, 2006 - 22:40
Severity: ImportantCritical
Too many people are asking about this, so I upped the severity to "critical".
Added by (anonymous) on January 18, 2006 - 00:03
Lack of order in these responses is a little worrying (!)
Added by Lars on January 21, 2006 - 18:59

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

Lars
Added by Jens W. Klein on January 28, 2006 - 11:51
Issue state: in-progressresolved
Phil fixed it in trunk. Lets close the issue :-)

For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by