Quantcast
Channel: Question and Answer » web-services
Viewing all articles
Browse latest Browse all 136

Where to store (data) classes for webservices

$
0
0

So I’m pretty new in my current company and my current task is to create a webservice that sends some serialized java objects from service A to service B using jaxws (webservices). The senior on the team encouraged me to copy (ctrl + c) the beans from project A into project B. I think this is not a good idea. As soon as some attribute would be added to a bean of project A, project B wouldn’t know of this attribute.

So I could fail or just ignore it – that would be terrible.

So basically my question is what is the normals solution for this? I thought about a project C that is a dependency of project A and project B and holds all the beans that both project send to each other. In project C I could also test the serialization.


Viewing all articles
Browse latest Browse all 136

Trending Articles