[
https://issues.jboss.org/browse/ROASTER-44?page=com.atlassian.jira.plugin...
]
George Gastaldi commented on ROASTER-44:
----------------------------------------
My only concern with addAnnotationValue(Class<?>) is to add the import. I am not
100% sure that setName() should be the overloaded option.
This is my implementation of the addAnnotationValue(Class<?>):
{code}
@Override
public AnnotationSource<O> addAnnotationValue(Class<? extends
java.lang.annotation.Annotation> type)
{
if (!getOrigin().hasImport(type))
{
getOrigin().addImport(type);
}
return addAnnotationValue().setName(type.getSimpleName());
}
@Override
public AnnotationSource<O> addAnnotationValue(String name, Class<? extends
java.lang.annotation.Annotation> type)
{
if (!getOrigin().hasImport(type))
{
getOrigin().addImport(type);
}
return addAnnotationValue(name).setName(type.getSimpleName());
}
{code}
Support writing of nested annotation arrays
-------------------------------------------
Key: ROASTER-44
URL:
https://issues.jboss.org/browse/ROASTER-44
Project: Roaster
Issue Type: Feature Request
Components: API, JDT
Affects Versions: 2.9.0.Final
Reporter: George Gastaldi
Assignee: Matt Benson
Fix For: 2.9.1.Final
Roaster should allow annotation nesting, like:
{code}
@NamedQueries({
@NamedQuery(name="Customer.findAll", query="select C from Customer
C"),
@NamedQuery(name="Customer.findByName", query="select C from Customer
C where C.name = :name"),
@NamedQuery(name="Customer.findById", query="select C from Customer C
where C.id = :id")
})
@Entity
public class Customer {...}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)