You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wsrp4j-dev@portals.apache.org by Diego Louzán <di...@metalicana.org> on 2005/02/14 11:08:17 UTC
Duplicated wsrp_v1_types.xsd file?
I'm currently implementing some ant tasks for automatically generating source
files from wsdl files. That would make easier the WSRP 2.0 transition later.
Anyway, I downloaded the most recent v1 .wsdl and .xsd definitions from OASIS
website and generated sources. Until then there was no problem, but it arises
when trying to compile wsrp4j with those generated sources. It complains about
not finding some method setLang in LocalizedString.java. What a surprise
finding that this method does not exist in my generated LocalizedString.java
but it exists in wsrp4j cvs source. Then I realize (call me nerd) there are two
.xsd files for type definition in wsdl/ directory of wsrp4j. I do a diff and
find one is the same as I have downloaded from OASIS website and the other has
two differences: instead of relying in xml:lang attributes, it hardcodes them
as "name" attributes in LocalizedString and ResourceValue types.
So, after all this story, could anyone tell me why these "workaround" (or
so it seems) is needed? Is it an Axis problem, related with WSDL2Java
generation tool?
Regards.
Diego.
Re: Duplicated wsrp_v1_types.xsd file?
Posted by Diego Louzán <di...@metalicana.org>.
I forgot, Property type is affected by this too.
Diego Louzán wrote:
> I'm currently implementing some ant tasks for automatically generating
> source files from wsdl files. That would make easier the WSRP 2.0
> transition later. Anyway, I downloaded the most recent v1 .wsdl and .xsd
> definitions from OASIS website and generated sources. Until then there
> was no problem, but it arises when trying to compile wsrp4j with those
> generated sources. It complains about not finding some method setLang in
> LocalizedString.java. What a surprise finding that this method does not
> exist in my generated LocalizedString.java but it exists in wsrp4j cvs
> source. Then I realize (call me nerd) there are two .xsd files for type
> definition in wsdl/ directory of wsrp4j. I do a diff and find one is the
> same as I have downloaded from OASIS website and the other has two
> differences: instead of relying in xml:lang attributes, it hardcodes
> them as "name" attributes in LocalizedString and ResourceValue types.
> So, after all this story, could anyone tell me why these
> "workaround" (or so it seems) is needed? Is it an Axis problem, related
> with WSDL2Java generation tool?
>
> Regards.
> Diego.
Re: Duplicated wsrp_v1_types.xsd file?
Posted by Richard Jacob <ja...@apache.org>.
Diego Louzán wrote:
> It seems I found some clues on this old Julie's conversation:
> http://lists.oasis-open.org/archives/wsrp-interop/200306/msg00006.html
> So it's an Axis bug, but... it isn't resolved yet?
>
no, unfortunatly it isn't resoleved at least with the last versions we
tried (1.2b)
cheers
Richard
Re: Duplicated wsrp_v1_types.xsd file?
Posted by Diego Louzán <di...@metalicana.org>.
It seems I found some clues on this old Julie's conversation:
http://lists.oasis-open.org/archives/wsrp-interop/200306/msg00006.html
So it's an Axis bug, but... it isn't resolved yet?
Regards.
Diego.
Diego Louzán wrote:
> I'm currently implementing some ant tasks for automatically generating
> source files from wsdl files. That would make easier the WSRP 2.0
> transition later. Anyway, I downloaded the most recent v1 .wsdl and .xsd
> definitions from OASIS website and generated sources. Until then there
> was no problem, but it arises when trying to compile wsrp4j with those
> generated sources. It complains about not finding some method setLang in
> LocalizedString.java. What a surprise finding that this method does not
> exist in my generated LocalizedString.java but it exists in wsrp4j cvs
> source. Then I realize (call me nerd) there are two .xsd files for type
> definition in wsdl/ directory of wsrp4j. I do a diff and find one is the
> same as I have downloaded from OASIS website and the other has two
> differences: instead of relying in xml:lang attributes, it hardcodes
> them as "name" attributes in LocalizedString and ResourceValue types.
> So, after all this story, could anyone tell me why these
> "workaround" (or so it seems) is needed? Is it an Axis problem, related
> with WSDL2Java generation tool?
>
> Regards.
> Diego.