StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15372830
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-12T21:46:33.770
FavoriteCount
0
LastActivityDate
2013-03-12T21:46:33.770
LastEditDate
LastEditorUserId
0
OwnerUserId
2162964
ParentId
11831119
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
As a follow-on to ahus1's answer: if you have a multi-level deployment archive (i.e. a top-level EAR file containing an EJB jar and a war file), you will need to configure the exclusion of <code>org.jboss.resteasy.resteasy-jackson-provider</code> on whichever sub-deployment contains the RESTEasy/JAX-RS components. In my deployment, for example, my REST endpoints were annotated on top of EJBs in my EJB jar file, while my <code>@ApplicationPath</code>-annotated <code>javax.ws.rs.core.Application</code> subclass which activates RESTEasy was in my war file. I found that the approaches of putting the exclusions solely on the top-level (EAR) deployment (as in ahus1's example) or on the EJB-jar-level deployment were ineffective, but I finally got RESTEasy to use Jettison rather than Jackson by putting the exclusions on all 3 levels (EAR, EJB, Web): <pre><code><?xml version="1.0" encoding="UTF-8" ?> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> <deployment> <exclusions> <module name="org.jboss.resteasy.resteasy-jackson-provider" /> </exclusions> <dependencies> <module name="org.jboss.resteasy.resteasy-jettison-provider" /> </dependencies> </deployment> <sub-deployment name="MyApp-ejb.jar"> <exclusions> <module name="org.jboss.resteasy.resteasy-jackson-provider" /> </exclusions> <dependencies> <module name="org.jboss.resteasy.resteasy-jettison-provider" /> </dependencies> </sub-deployment> <sub-deployment name="MyApp.war"> <exclusions> <module name="org.jboss.resteasy.resteasy-jackson-provider" /> </exclusions> <dependencies> <module name="org.jboss.resteasy.resteasy-jettison-provider" /> </dependencies> </sub-deployment> </jboss-deployment-structure> </code></pre> It's very likely that I only needed the exclusions on the subdeployments, and putting it on the main EAR deployment is superfluous; I didn't try it that way, since for now putting it on all three seems to work perfectly well.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSet JSON provider at RESTEasy on JBoss 7.1.1
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USsumitsu
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. This table or related slice is empty.

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.