1 a.m.
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
- shorthand field value syntax
You can do <ns:MyBean fieldName="fieldValue" />
- Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
- Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e> tags.
The <value> element was not able to be used like this in the original spec, so it
was not possible to apply annotations and set the field value.
- <overrides> and <specializes> tags
- Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
- Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes that
implement that interface.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:34 a.m.
New subject: [JBoss JIRA] Updated: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated SEAMXML-8:
----------------------------
Description:
There a quite a few changes from the draft spec, I have listed them below:
- shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
- Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
- Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e> tags.
The <value> element was not able to be used like this in the original spec, so it
was not possible to apply annotations and set the field value.
- <overrides> and <specializes> tags
- Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
- Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes that
implement that interface.
was:
There a quite a few changes from the draft spec, I have listed them below:
- shorthand field value syntax
You can do <ns:MyBean fieldName="fieldValue" />
- Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
- Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e> tags.
The <value> element was not able to be used like this in the original spec, so it
was not possible to apply annotations and set the field value.
- <overrides> and <specializes> tags
- Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
- Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes that
implement that interface.
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
- shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
- Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
- Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
- <overrides> and <specializes> tags
- Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
- Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:36 a.m.
New subject: [JBoss JIRA] Updated: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated SEAMXML-8:
----------------------------
Description:
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e> tags.
The <value> element was not able to be used like this in the original spec, so it
was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes that
implement that interface.
was:
There a quite a few changes from the draft spec, I have listed them below:
- shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
- Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
- Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e> tags.
The <value> element was not able to be used like this in the original spec, so it
was not possible to apply annotations and set the field value.
- <overrides> and <specializes> tags
- Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
- Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes that
implement that interface.
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:38 a.m.
New subject: [JBoss JIRA] Commented: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on SEAMXML-8:
---------------------------------
To me, (2) and (5) are obvious improvements.
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:40 a.m.
New subject: [JBoss JIRA] Commented: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on SEAMXML-8:
---------------------------------
I don't love the shorthand in (3), but I know that without it people will complain.
Otherwise looks good.
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:42 a.m.
New subject: [JBoss JIRA] Commented: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on SEAMXML-8:
---------------------------------
(1) I think is another case where the shorthand doesn't reduce readability enough to
be an issue.
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:52 a.m.
New subject: [JBoss JIRA] Commented: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on SEAMXML-8:
---------------------------------
IMO (6) should be removed. The way in which annotations which are placed on interfaces
should be identical in both Java and XML. If we want this feature in CDI, then let's
write a portable extension that does it for both.
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:06 a.m.
New subject: [JBoss JIRA] Updated: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Stuart Douglas updated SEAMXML-8:
---------------------------------
Description:
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e> tags.
The <value> element was not able to be used like this in the original spec, so it
was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes that
implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of beans
generic that are related to a primary bean. Every time the user wires up a bean based on
the primary bean Seam XML installs a corresponding version of each of the secondary beans,
with the same qualifiers as the bean the user wired up. e.g. the Drools module uses this
feature to install multiple beans every time the user wires up a DroolsConfig bean.
was:
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e> tags.
The <value> element was not able to be used like this in the original spec, so it
was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes that
implement that interface.
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of
beans generic that are related to a primary bean. Every time the user wires up a bean
based on the primary bean Seam XML installs a corresponding version of each of the
secondary beans, with the same qualifiers as the bean the user wired up. e.g. the Drools
module uses this feature to install multiple beans every time the user wires up a
DroolsConfig bean.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:10 a.m.
New subject: [JBoss JIRA] Commented: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on SEAMXML-8:
---------------------------------
(7) looks great to me.
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of
beans generic that are related to a primary bean. Every time the user wires up a bean
based on the primary bean Seam XML installs a corresponding version of each of the
secondary beans, with the same qualifiers as the bean the user wired up. e.g. the Drools
module uses this feature to install multiple beans every time the user wires up a
DroolsConfig bean.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:52 p.m.
New subject: [JBoss JIRA] Updated: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Stuart Douglas updated SEAMXML-8:
---------------------------------
Description:
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e> tags.
The <value> element was not able to be used like this in the original spec, so it
was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes that
implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of beans
generic that are related to a primary bean. Every time the user wires up a bean based on
the primary bean Seam XML installs a corresponding version of each of the secondary beans,
with the same qualifiers as the bean the user wired up. e.g. the Drools module uses this
feature to install multiple beans every time the user wires up a DroolsConfig bean.
8) Multi dimensional arrays
The dimensions attribute of the <array> tag was not in the original spec. It allows
you to configure methods that take a multi-dimansional array as an argument.
was:
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e> tags.
The <value> element was not able to be used like this in the original spec, so it
was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes that
implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of beans
generic that are related to a primary bean. Every time the user wires up a bean based on
the primary bean Seam XML installs a corresponding version of each of the secondary beans,
with the same qualifiers as the bean the user wired up. e.g. the Drools module uses this
feature to install multiple beans every time the user wires up a DroolsConfig bean.
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of
beans generic that are related to a primary bean. Every time the user wires up a bean
based on the primary bean Seam XML installs a corresponding version of each of the
secondary beans, with the same qualifiers as the bean the user wired up. e.g. the Drools
module uses this feature to install multiple beans every time the user wires up a
DroolsConfig bean.
8) Multi dimensional arrays
The dimensions attribute of the <array> tag was not in the original spec. It allows
you to configure methods that take a multi-dimansional array as an argument.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:55 p.m.
New subject: [JBoss JIRA] Updated: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Stuart Douglas updated SEAMXML-8:
---------------------------------
Description:
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e> tags.
The <value> element was not able to be used like this in the original spec, so it
was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes that
implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of beans
generic that are related to a primary bean. Every time the user wires up a bean based on
the primary bean Seam XML installs a corresponding version of each of the secondary beans,
with the same qualifiers as the bean the user wired up. e.g. the Drools module uses this
feature to install multiple beans every time the user wires up a DroolsConfig bean.
8) Multi dimensional arrays
The dimensions attribute of the <array> tag was not in the original spec. It allows
you to configure methods that take a multi-dimansional array as an argument.
9) Limiting the type of an injection point
The original spec did not allow you to limit the type that is available for injection into
an injection point:
<n:myField>
<s:Inject/>
<s:type>
<n:SubType/>
</s:type>
<n:myField/>
was:
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e> tags.
The <value> element was not able to be used like this in the original spec, so it
was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes that
implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of beans
generic that are related to a primary bean. Every time the user wires up a bean based on
the primary bean Seam XML installs a corresponding version of each of the secondary beans,
with the same qualifiers as the bean the user wired up. e.g. the Drools module uses this
feature to install multiple beans every time the user wires up a DroolsConfig bean.
8) Multi dimensional arrays
The dimensions attribute of the <array> tag was not in the original spec. It allows
you to configure methods that take a multi-dimansional array as an argument.
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of
beans generic that are related to a primary bean. Every time the user wires up a bean
based on the primary bean Seam XML installs a corresponding version of each of the
secondary beans, with the same qualifiers as the bean the user wired up. e.g. the Drools
module uses this feature to install multiple beans every time the user wires up a
DroolsConfig bean.
8) Multi dimensional arrays
The dimensions attribute of the <array> tag was not in the original spec. It allows
you to configure methods that take a multi-dimansional array as an argument.
9) Limiting the type of an injection point
The original spec did not allow you to limit the type that is available for injection
into an injection point:
<n:myField>
<s:Inject/>
<s:type>
<n:SubType/>
</s:type>
<n:myField/>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:53 a.m.
New subject: [JBoss JIRA] Commented: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on SEAMXML-8:
---------------------------------
(8) also looks obviously good.
(9) We should implement via @Exact, not in a custom fashion - see
http://www.seamframework.org/Weld/PortableExtensionsPackage#H-TtExactttQu...
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of
beans generic that are related to a primary bean. Every time the user wires up a bean
based on the primary bean Seam XML installs a corresponding version of each of the
secondary beans, with the same qualifiers as the bean the user wired up. e.g. the Drools
module uses this feature to install multiple beans every time the user wires up a
DroolsConfig bean.
8) Multi dimensional arrays
The dimensions attribute of the <array> tag was not in the original spec. It allows
you to configure methods that take a multi-dimansional array as an argument.
9) Limiting the type of an injection point
The original spec did not allow you to limit the type that is available for injection
into an injection point:
<n:myField>
<s:Inject/>
<s:type>
<n:SubType/>
</s:type>
<n:myField/>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:53 a.m.
New subject: [JBoss JIRA] Assigned: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Pete Muir reassigned SEAMXML-8:
-------------------------------
Assignee: Stuart Douglas
Assign to stuart to implement the decisions above.
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
Assignee: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of
beans generic that are related to a primary bean. Every time the user wires up a bean
based on the primary bean Seam XML installs a corresponding version of each of the
secondary beans, with the same qualifiers as the bean the user wired up. e.g. the Drools
module uses this feature to install multiple beans every time the user wires up a
DroolsConfig bean.
8) Multi dimensional arrays
The dimensions attribute of the <array> tag was not in the original spec. It allows
you to configure methods that take a multi-dimansional array as an argument.
9) Limiting the type of an injection point
The original spec did not allow you to limit the type that is available for injection
into an injection point:
<n:myField>
<s:Inject/>
<s:type>
<n:SubType/>
</s:type>
<n:myField/>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:25 p.m.
New subject: [JBoss JIRA] Commented: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Stuart Douglas commented on SEAMXML-8:
--------------------------------------
To get @Exact to work properly we need to resolve WELD-485
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
Assignee: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of
beans generic that are related to a primary bean. Every time the user wires up a bean
based on the primary bean Seam XML installs a corresponding version of each of the
secondary beans, with the same qualifiers as the bean the user wired up. e.g. the Drools
module uses this feature to install multiple beans every time the user wires up a
DroolsConfig bean.
8) Multi dimensional arrays
The dimensions attribute of the <array> tag was not in the original spec. It allows
you to configure methods that take a multi-dimansional array as an argument.
9) Limiting the type of an injection point
The original spec did not allow you to limit the type that is available for injection
into an injection point:
<n:myField>
<s:Inject/>
<s:type>
<n:SubType/>
</s:type>
<n:myField/>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:18 p.m.
New subject: [JBoss JIRA] Resolved: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Stuart Douglas resolved SEAMXML-8.
----------------------------------
Fix Version/s: 3.0.0.Beta1
Resolution: Done
done
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
Assignee: Stuart Douglas
Fix For: 3.0.0.Beta1
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of
beans generic that are related to a primary bean. Every time the user wires up a bean
based on the primary bean Seam XML installs a corresponding version of each of the
secondary beans, with the same qualifiers as the bean the user wired up. e.g. the Drools
module uses this feature to install multiple beans every time the user wires up a
DroolsConfig bean.
8) Multi dimensional arrays
The dimensions attribute of the <array> tag was not in the original spec. It allows
you to configure methods that take a multi-dimansional array as an argument.
9) Limiting the type of an injection point
The original spec did not allow you to limit the type that is available for injection
into an injection point:
<n:myField>
<s:Inject/>
<s:type>
<n:SubType/>
</s:type>
<n:myField/>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:32 a.m.
New subject: [JBoss JIRA] Closed: (SEAMXML-8) Review all deviations from the original JSR-299 draft spec
[
https://jira.jboss.org/browse/SEAMXML-8?page=com.atlassian.jira.plugin.sy...
]
Stuart Douglas closed SEAMXML-8.
--------------------------------
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMXML-8
URL: https://jira.jboss.org/browse/SEAMXML-8
Project: Seam XML Bean Config
Issue Type: Task
Reporter: Stuart Douglas
Assignee: Stuart Douglas
Fix For: 3.0.0.Alpha3
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of
beans generic that are related to a primary bean. Every time the user wires up a bean
based on the primary bean Seam XML installs a corresponding version of each of the
secondary beans, with the same qualifiers as the bean the user wired up. e.g. the Drools
module uses this feature to install multiple beans every time the user wires up a
DroolsConfig bean.
8) Multi dimensional arrays
The dimensions attribute of the <array> tag was not in the original spec. It allows
you to configure methods that take a multi-dimansional array as an argument.
9) Limiting the type of an injection point
The original spec did not allow you to limit the type that is available for injection
into an injection point:
<n:myField>
<s:Inject/>
<s:type>
<n:SubType/>
</s:type>
<n:myField/>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:12 p.m.
New subject: [JBoss JIRA] Moved: (SEAMCONFIG-35) Review all deviations from the original JSR-299 draft spec
[
https://issues.jboss.org/browse/SEAMCONFIG-35?page=com.atlassian.jira.plu...
]
Jason Porter moved SEAMXML-8 to SEAMCONFIG-35:
----------------------------------------------
Project: Seam Config (fixed) (was: Seam Config)
Key: SEAMCONFIG-35 (was: SEAMXML-8)
Workflow: Seam Workflow (was: GIT Pull Request workflow )
Fix Version/s: (was: 3.0.0.Alpha3)
Review all deviations from the original JSR-299 draft spec
-----------------------------------------------------------
Key: SEAMCONFIG-35
URL: https://issues.jboss.org/browse/SEAMCONFIG-35
Project: Seam Config (fixed)
Issue Type: Task
Reporter: Stuart Douglas
Assignee: Stuart Douglas
There a quite a few changes from the draft spec, I have listed them below:
1) shorthand field value syntax
You can do <ns:Company name="Red Hat, Inc." />
2) Producer method / field syntax was:
<ns:Bean>
<ns:field>
<Producer>
<ns:SomeQualifier/>
</Producer>
</ns:field>
</ns:Bean>
I have changed this to:
<ns:Bean>
<ns:field>
<Producer/>
<ns:SomeQualifier/>
</ns:field>
</ns:Bean>
3) Setting initial field values
You can now do:
<ns:Bean>
<ns:field>
<Producer/>
<value>10</value>
</ns:field>
<ns:field2>5</ns:field2>
<ns:mapField>
<entry><key>a</key><value>b</value></entry>
<e><k>c</k><v>d</v></e>
</ns:mapField/>
</ns:Bean>
The value key and entry tags can be shorted to just <v><k> and <e>
tags. The <value> element was not able to be used like this in the original spec, so
it was not possible to apply annotations and set the field value.
4) <overrides> and <specializes> tags
5) Change of syntax for constructor and method parameters
In the draft spec method parameters are specified as direct children of the method like
so:
<ns:Bean>
<ns:method>
<Producer/>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:SomeOtherAnnotation/>
<ns:ParamType2/>
</ns:method>
</ns:Bean>
This has been changed to:
<ns:Bean>
<ns:method>
<Producer/>
<ns:SomeOtherAnnotation/>
<parameters>
<ns:ParamType1><ns:SomeAnntation/></ns:ParamType1>
<ns:ParamType2/>
</parameters/>
</ns:method>
</ns:Bean>
6) Interface configuration
Annotations / field values applied to an interface via XML are applied to all classes
that implement that interface.
7) Generic Beans
Intended as a tool for framework writers, generic beans allow you to define a set of
beans generic that are related to a primary bean. Every time the user wires up a bean
based on the primary bean Seam XML installs a corresponding version of each of the
secondary beans, with the same qualifiers as the bean the user wired up. e.g. the Drools
module uses this feature to install multiple beans every time the user wires up a
DroolsConfig bean.
8) Multi dimensional arrays
The dimensions attribute of the <array> tag was not in the original spec. It allows
you to configure methods that take a multi-dimansional array as an argument.
9) Limiting the type of an injection point
The original spec did not allow you to limit the type that is available for injection
into an injection point:
<n:myField>
<s:Inject/>
<s:type>
<n:SubType/>
</s:type>
<n:myField/>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4919
days inactive
5228
days old
16 comments
3 participants
participants (3)
-
Jason Porter (JIRA) -
Pete Muir (JIRA)
-
Stuart Douglas (JIRA)