Missing DTOs in Client JAR Using Appc

Question

Hello,
I've been running Appc on my server JAR to generate my client JAR. It works great,
except that some of the files utilized by the application, namely the DTOs, are
not being packaged into the JAR. I think I know why this is occurring, but I'm
not sure how to fix it. Let me explain how a simplified version of the app works:
It's a security administration app, so there's this idea of users and their roles.
The only remote bean in the JAR is a stateless session bean. It has the following
methods:
public UserDTO getUser(String pUserId);
public List getRolesForUser(String pUserId);
public void updateUser(UserDTO pUser);
public void replaceRolesForUser(List pRoles);
Simple enough, right? The Appc process knows to place the UserDTO class in the
client JAR since it is referenced in the interface. However, what the Appc process
does not realize is that the List of roles being returned is actually a List of
RoleDTOs.
The calling client application uses the RoleDTO class when iterating through the
list of roles. Since the client application is a remote application and thus
has only the client EJB JAR in its classpath, the client app can't compile; it
can't find a definition for RoleDTO. Is there some way to force the Appc process
to include all DTOs?
Thanks,
Leo

Answer 1

Thanks. That's what I thought!
Rob Woollen <[email protected]> wrote:
Your analysis is correct. There's no real clean solution in this case
other than returning a RoleDTO[] or updating the client-jar file with
the missing classes.
-- Rob
Leo J. Hart IV wrote:
Hello,
I've been running Appc on my server JAR to generate my client JAR.It works great,
except that some of the files utilized by the application, namely theDTOs, are
not being packaged into the JAR. I think I know why this is occurring,but I'm
not sure how to fix it. Let me explain how a simplified version ofthe app works:
It's a security administration app, so there's this idea of users andtheir roles.
The only remote bean in the JAR is a stateless session bean. It hasthe following
methods:
public UserDTO getUser(String pUserId);
public List getRolesForUser(String pUserId);
public void updateUser(UserDTO pUser);
public void replaceRolesForUser(List pRoles);
Simple enough, right? The Appc process knows to place the UserDTOclass in the
client JAR since it is referenced in the interface. However, whatthe Appc process
does not realize is that the List of roles being returned is actuallya List of
RoleDTOs.
The calling client application uses the RoleDTO class when iteratingthrough the
list of roles. Since the client application is a remote applicationand thus
has only the client EJB JAR in its classpath, the client app can'tcompile; it
can't find a definition for RoleDTO. Is there some way to force theAppc process
to include all DTOs?
Thanks,
Leo