Message:

   The following issue has been reopened.

   Reopener: Howard M. Lewis Ship
       Date: Thu, 23 Sep 2004 5:24 AM

I can see how the interraction between <push-attribute> can cause this. With no 
property to assign, the translator is passed the default, java.lang.Object, and 
can't translate to it.  In this situation, we don't want any translator ... 
have to see if translator="" will work (on the <attribute> or the 
<push-attribute> elements). If not, that may be the right course of action ... 
to allow no translator at all (leaving the string a string!).
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/HIVEMIND-15

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HIVEMIND-15
    Summary: hivemind fails on translating a string attribute in a string
       Type: Wish

     Status: Reopened
   Priority: Major

    Project: HiveMind
 Components: 
             framework
   Versions:
             1.0

   Assignee: Howard M. Lewis Ship
   Reporter: Christian Domsch

    Created: Fri, 2 Jul 2004 5:46 AM
    Updated: Thu, 23 Sep 2004 5:24 AM
Environment: Windows 2000, Eclipse 3.0, j2sdk1.4.2

Description:
I have a configuration-point that builds a list of strings. When I build the 
schema for the cp, hivemind expects a translator for an attribute. Since I want 
to have Strings in my list, I don't need a translator.

Sadly the SmartTranslator fails on translating a string into a string, so I had 
to write my own (very simple implementation :-). Maybe I did something wrong in 
my configuration-point:

configuration-point (id=model) {
  schema {
    element (name=model) {
      attribute (name=name required=true)

      rules {
        push-attribute (attribute=name)
        invoke-parent (method=addElement)
      }
    }
  }
}

contribution (configuration-id=model) {
  model (name=MyModelName)
}

If this is correct, it would be a great enhancement, if hivemind would be able 
to "translate" strings into strings without implementing a custom translator. 
This is not very intuitive.

Greetings,

Christian Domsch


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to