StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhere to package Class file so that both Client apps and EJBs on Server have access?
primarykey
Id
6259048
data
AcceptedAnswerId
6259205
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-06-06T23:12:43.513
FavoriteCount
0
LastActivityDate
2011-06-06T23:34:40.393
LastEditDate
2011-06-06T23:24:51.253
LastEditorUserId
3916
OwnerUserId
786632
ParentId
0
PostTypeId
1
Score
0
ViewCount
78
LastEditorDisplayName
text
Body
I am new to the Java EE platform and I am building a simple JMS app. I created a class that is being sent in an ObjectMessage. My problem arose when both the client app creating the message and the MDB on the server needed access to the same class file(the class composed in the ObjectMessage). I currently have the class file in both the client library and EJB library and this is working. However I would like to have only one location for the class file where both the client and MDB can access it. I believe I need to package the entire app in a certain way, but I having a hard time figuring it out. Any help will be greatly appreciated. Thank you.
Tags
<java><java-ee-6>
Title
Where to package Class file so that both Client apps and EJBs on Server have access?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USVineet Reynolds
UserOwnerUserId
1. USMike L.
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
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.