2 Replies Latest reply on Jul 18, 2013 7:01 AM by magick93

How to tell marshaller to ignore classes - or perhaps there is a better solution?

magick93 Jul 18, 2013 5:39 AM

I am trying to add http://www.querydsl.com/ to help us more easily develop our persistence requirements.

This generates classes based on our jpa entities.

The problem

Our entities are in app.client.shared.datamodel and the the generated classes are also in the shared package. So, I assume that is the problem.

The generated classes are complex, and cannot be marshalled. And we also do not intend to use them on the client - only for working with backend persistence. But we do wish to use our entities for both 'jpa in the browser' and jpa in the traditional backend db.

Querydsl does not all use - I believe - to specify the package that the generated classe are in.

What would you recommend?

1. Re: How to tell marshaller to ignore classes - or perhaps there is a better solution?

edewit Jul 18, 2013 5:54 AM (in response to magick93)

Hi Anton,

Looking at the documentation you can specify the target folder of the generated classes, so one posbile solution is to let the querydsl generate to different directory and have an ant script inside your maven build to create a jar and put that in your war file...

Not ideal, but a work around, best solution is to ask the guys at querydsl to make the package configurable, but maybe the generated classes need to be in the same package?

Cheers,
Erik Jan
1 of 1 people found this helpful
Actions
2. Re: How to tell marshaller to ignore classes - or perhaps there is a better solution?

magick93 Jul 18, 2013 7:01 AM (in response to edewit)

Thanks Erik

Yes, I have posted to the QueryDsl group to see what/how it can be configured.
Actions

Go to original post