You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Sharmarke Aden (JIRA)" <ji...@apache.org> on 2012/11/19 06:16:58 UTC
[jira] [Updated] (AVRO-1205) Add Stereotype Annotation to Generated
Beans
[ https://issues.apache.org/jira/browse/AVRO-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sharmarke Aden updated AVRO-1205:
---------------------------------
Attachment: vcs-diff6870599675664484518.patch
> Add Stereotype Annotation to Generated Beans
> --------------------------------------------
>
> Key: AVRO-1205
> URL: https://issues.apache.org/jira/browse/AVRO-1205
> Project: Avro
> Issue Type: New Feature
> Components: java
> Affects Versions: 1.7.2
> Reporter: Sharmarke Aden
> Priority: Minor
> Attachments: vcs-diff6870599675664484518.patch
>
>
> Avro generated schema beans currently lack a formal way of distinguishing them as Avro schema beans at runtime. I would like to propose that a new stereotype annotation be added to Avro Core and the ability to have all Avro generated schema beans annotated with this newly created stereotype annotation.
> I'm planning on adding a FallbackTypeConverter to the Camel-Avro project and I hoping this feature will allow me to cleanly detect Avro beans for conversion at runtime.
> If this feature is implemented Avro schema beans would look something like this:
> {code}
> ...
> @org.apache.avro.reflect.AvroSchema
> public class User extends org.apache.avro.specific.SpecificRecordBase implements org.apache.avro.specific.SpecificRecord {
> ...
> }
> ...
> {code}
> The maven plugin configuration would look something like this:
> {code}
> <plugin>
> <groupId>org.apache.avro</groupId>
> <artifactId>avro-maven-plugin</artifactId>
> <executions>
> <execution>
> <goals>
> <goal>schema</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <stereotype>true</stereotype>
> </configuration>
> </plugin>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira