Hakan, The ?wsdl generator is 'configured' by the sum of all your @nnotations plus whatever options you supply to the service factory. Generally, a discrepancy of this kind results from service factory options, since the @nnotations are equally visible to the tools and the dynamic runtime.
Have you posted your service endpoint configuration? --benson On Tue, Dec 2, 2008 at 12:40 PM, hakan eryargi <[EMAIL PROTECTED]> wrote: > hi Dan, > >> Under the covers, they do use the same service factories and such. However, >> the CXF factories are very configurable and most likely, the tooling is >> setting some configuration differently than the default configuration used in >> the ?wsdl case. I'd definitely need to debug deep in (preferrably with a >> testcase) to figure out exactly what setting is causing it and see which is >> the "correct" setting according to specs. > > i've looked at the documentation but couldnt find any option to > configure ?wsdl generator. a testcase seems hard at the moment but if > you really need it i may try to think of something. > >> Now THAT is very strange and I'm not sure what would cause that. Do the >> types >> have JAXB annotations and such? Any chance you could put a logging >> properties file in place to turn on FINE/FINEST logging and re-run the >> java2ws? Maybe package up an example and send it along? > > my data types have JAXB annotations. but i cant claim that they are > perfect or error free :/ but i can say standalone JAXBContext can > marshal/unmarshal them. a CXF client also works correctly. if you need > them i can send java sources to your email > > i'm attaching 3 log files. two of them are java2ws log and output, > third one is cxf log taken from tomcat. for the third one, when i hit > refresh on the browser for ?wsdl nothing is appended to log. > > regards, > r a f t > >> >> Dan >> >> >> >> On Wednesday 26 November 2008 1:52:26 pm raft wrote: >>> thank you Daniel :) that reduced the number of wsdl files to one. >>> >>> but i have also noticed that my types aren't included in the schema part of >>> wsdl file. java2ws includes them correctly. do you knowhow to correct it ? >>> >>> and for curiosity, what tool is running when i invoke serviceName?wsdl ? >>> isn't it a part of cxf ? if so i don't understand why java2ws and ?wsdl >>> generates different results >>> >>> thanks, >>> r a f t >>> >>> dkulp wrote: >>> > On Wednesday 26 November 2008 11:12:24 am raft wrote: >>> >> hello, >>> >> >>> >> i'm using java first approach. the java2ws and serviceUrl?wsdl generate >>> >> different forms of wsdl documents. to be precise the later generates two >>> >> wsdl documents where one imports the other. is it possible to change >>> >> this behaviour ? >>> > >>> > Technically, the one generated from java2ws is wrong, or at least not per >>> > jaxws/jws spec. Probably a bug in the tool. >>> > >>> >> is it possible to configure or specify the wsdl generator >>> >> running in response to serviceUrl?wsdl ? >>> > >>> > Make sure both the "Impl" class and the Interface have @WebService >>> > annotations >>> > and that both of them have the SAME targetNamespace defined. That >>> > should do >>> > it. Per spec, if they don't have the same target namespace, the >>> > "logical" >>> > part should be in one wsdl/namespace and the physical part in another. >>> > That's what you are seeing. >>> > >>> > -- >>> > Daniel Kulp >>> > [EMAIL PROTECTED] >>> > http://dankulp.com/blog >> >> >> >> -- >> Daniel Kulp >> [EMAIL PROTECTED] >> http://dankulp.com/blog >> >
