Ok, no I got the problem solved. It seems that there where several reasons,
one of course the package(s)/names and also at least another which I find
very confusing.
To which extended am I allowed to alter the classes generated by wsimport?
As I figured out one of my domain classes I was using as a replacement for
the generated class had an attribute (long with getter and setter) which
didn't occur in the wsdl and therefore was also missing in the generated
class.
After removing the additional parameter (as I was searching for differences
between generated and handmade classes) the "ReadSomething not known to the
context error" vanished.
I'm really surprised that an attribute could cause so much trouble.
Wolfgang, can you tell me why's that?
Cheers
Simon
Wolfgang Laun-2 wrote:
>
> You might also check the tutorial section "Defining Package Names" and
> run a simple example to see where the changed name comes up in the
> generated code; then you may check whether you have all of that in
> your own patched code, correspondingly.
>
> I guess that's all that anybody can advise, based on the sparse info
> you've provided.
>
> -W
>
> On 21/05/2010, schneidc <simon.work_at_gmx.de> wrote:
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>
>
>
--
View this message in context: http://old.nabble.com/JAXB-problem-with-%22com.xyz.ReadSomething-nor-any-of-its-super-class-is-known-to-this-context.%22-tp28631676p28670028.html
Sent from the java.net - jaxb users mailing list archive at Nabble.com.