Home/ Questions/Q 427033
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T19:32:21+00:00

I recently wrote some data access methods (plain old Java) that use immutable objects

  • 0

I recently wrote some data access methods (plain old Java) that use immutable objects for both the request objects and the resulting data objects. I like the immutable objects because they prevent a good deal of confusion from appearing in the client code which I’ve seen in the past when people attempt to mutate and reuse objects.

Anyway, that was months ago. Now a colleague is having trouble with some web service generation stuff (attempting to expose my methods) which expects everything everywhere to be a JavaBean.

My question is: does web service stuff generation stuff always mandate use of JavaBeans? Is there another way?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Most web service frameworks provide some way for you to supply custom serializers/deserializers for types. Sounds like that is what you need here.

    If it isn’t clear why that’s necessary, it is because the framework needs to know how to translate your Java class into XML and vice versa. Serializing and deserializing JavaBeans (classes with get and set properties) is easy if you follow the naming strategy, but you should also be able to supply your custom type serializers for classes that do not follow the bean pattern.

    • 0