On Nov 20, 2007, at 9:39 AM, Jay D. McHugh wrote:

The 1.2 schema managed to sneak into the 2.0.x releases - but nothing is
actually referencing it.  Until you get to 2.1.x (trunk) all of the
programs still refer to 1.1.

So, we should probably figure out whether or not we need to jump up to
1.3 or if we can stay on 1.2.

Although I may have lost track of my activities :-) I think I've been happily updating the 1.2 schema under the impression that it wasn't in use yet. So I'm fine with keeping the 1.2 version for g 2.1.

And, this would make a good opportunity to find out if anyone has any
additional changes that they would like to make to the schema.
Regardless of whether or not we need to change the schema version
immediately - we should be releasing 2.1 soon, and it would be better to get as many changes as possible into the schema now rather than burning
though lots of version numbers.

Even better would be a version-number-free way of dealing with these schemas and their evolution. I don't have any ideas. Does anyone else?


So, does anyone else have a take on new elements that should be added to
the schema and whether or not we need to freeze 1.2?

I'll keep looking for new elements and think we can keep changing 1.2 until g. 2.1 is released.

thanks
david jencks


Jay

Jarek Gawor wrote:
This is a change to an existing and published schema. I think that
needs its own new file and namespace.

Jarek

Modified: geronimo/server/trunk/framework/modules/geronimo-system/ src/main/xsd/attributes-1.2.xsd URL: http://svn.apache.org/viewvc/geronimo/server/trunk/framework/ modules/geronimo-system/src/main/xsd/attributes-1.2.xsd? rev=596542&r1=596541&r2=596542&view=diff ==================================================================== ========== --- geronimo/server/trunk/framework/modules/geronimo-system/src/ main/xsd/attributes-1.2.xsd (original) +++ geronimo/server/trunk/framework/modules/geronimo-system/src/ main/xsd/attributes-1.2.xsd Mon Nov 19 21:25:27 2007
@@ -183,6 +183,19 @@
                         </xsd:documentation>
                     </xsd:annotation>
                 </xsd:attribute>
+ <xsd:attribute name="propertyEditor" use="optional" type="xsd:string">
+                    <xsd:annotation>
+                        <xsd:documentation>
+ The propertyEditor attribute defines the property editor class + to be used to get the value of this attribute based on its
+                            string representation.
+
+ If no editor is specified, then the type of the attribute, as + declared by GBeanAttribute, is used to find a propertyEditor + through the standard JavaBean search strategy.
+                        </xsd:documentation>
+                    </xsd:annotation>
+                </xsd:attribute>
                 <!--<xsd:attribute name="value" use="optional">-->
                     <!--<xsd:annotation>-->
                         <!--<xsd:documentation>-->






Reply via email to