Hello there.
In my current project，I have to use web service as the RPC method。So the loaded object must be transformed to XML SOAP. My problem is when the jboss server try to that, I would get the lazy loading after session closed exception because some properties are not loaded when the session is open and I don't want them to be loaded either. So I wonder if there is any method I can make the getProperties() call silently return null instead of throwing an exception?

Any response would be highly appreciated!

First, you should render your web service response within the scope of a transaction so that you don't have this problem. Second, you can tell if something is loaded by using Hibernate.isInitialized():

http://www.hibernate.org/hib_docs/v3/ap ... ang.Object)

Thank you for your answer, but it doesn't help.
If I make the web service response rendered within the transaction, the response would contain too much collection properties that I don't want actually. The problem is, I DON'T want them!

dude

try to utilize filters. i used this technique long time ago but in this case u have to make sure about the transactions

Before rendering the response you could detach these objects and set all associations, which you don't want to null.
Anyway, I have not much experience about webservices, but there surely is a possibility to determine which fields to map to the response and which not, isn't there?

Have you considered providing the Web service with a decorator object that encapsulates access to your real persisted object?

That way you can pick and choose what you allow the service to see.


--
Stephen Souness

Also, letting what is fetched and what isn't determine the contract of your web service sounds like trouble to me. Imagine if you change a mapping that affects loading, then you all of a sudden break your clients.

Whatever is rendering your web service (you said it was JBoss, that sounds like a SLSB to me, so it would be inside a transaction) should know what it needs to return and just consume whatever data it needs. The fact that the data is or is not initialized should not matter at all.