StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20045443
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-11-18T10:25:38.123
FavoriteCount
0
LastActivityDate
2013-11-18T10:25:38.123
LastEditDate
LastEditorUserId
0
OwnerUserId
435187
ParentId
20003827
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<h2>Consrtutor Injection</h2> When CDI container instantiate a bean class then it call the bean constructor of CDI bean. CDI looks for the either default bean constructor or annotated with @Inject to get the the instance of bean. <ul> <li>No parameter/default bean constructor will accepted by CDI container if CDI bean doesn't explicitly declare a constructor using @Inject.</li> <li>CDI bean constructor may have any number of parameters and container initialize/inject all those paramters which are injection point for the bean constructor.</li> <li>CDI bean class can only have single constructor annotated with @Inject. If CDI container finds multiple constructor annotated with @Inject then it throws error.</li> </ul> <blockquote> There is one advantage of bean constructor injection it allows the bean to be immutable. </blockquote> The Problem in your case is IncidentContainer bean class does not have any default constructor or a constructor annotated with @Injection. You can set as following <pre><code>public class IncidentContainer extends JPAContainer<Incident> { // @Inject no need to do filed injection here private EntityProviderBean<Incident> provider; @Inject // add this one public IncidentContainer(EntityProviderBean<Incident> provider) { super(Incident.class); this.provider = provider; } @PostConstruct protected void init() { setEntityProvider(provider); } } </code></pre> EntityProviderBean bean class does not have any default constructor or a constructor annotated with @Injection. You can set as following <pre><code>public class EntityProviderBean<T> extends CachingMutableLocalEntityProvider<T> { public EntityProviderBean(Class<T> entityClass) { super(entityClass); setTransactionsHandledByProvider(false); } // add this cdi bean construtor @Inject public EntityProviderBean(Incident incident) { this((Class<T>) incident.getClass()); } protected void runInTransaction(String operation) { super.runInTransaction(operation); } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to @Inject object with generic type
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAsif Bhutto
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COHey, thanks for an idea, but I am still getting the same error, when I want to `@Inject IncidentContainer` somewhere.
 singulars
 PostPostId
 PO
 UserUserId
 USs0vet
2. COFinally I get it to work. I am able to inject IncidentContainer, but when I want to save some entity into it, I got `javax.persistence.TransactionRequiredException`. That is because of `@TransactionManagement` annotation, which apparently does not work :( Do you have any ideas ?
 singulars
 PostPostId
 PO
 UserUserId
 USs0vet

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.