-
1. Re: How does WSDL get generated when publishign a Java based WS?
asoldano Mar 13, 2012 2:13 PM (in response to vatsanm)The migration from JBoss 4.2.2 to 7.1.x is quite a long jump ;-)
Anyway, please provide more info on the "error" you're seeing, it's not clear from your sentences above. Consider posting an example.
-
2. Re: How does WSDL get generated when publishign a Java based WS?
vatsanm Mar 13, 2012 3:17 PM (in response to asoldano)I have a WS that was created under JB4.2.2 that is running as expcted. Below is the error that I get when publishing the same exact code base under JB-7.1.0. The WS is created as a SOAP document style. The Web method tahes classes (JAXB generated from xsd). If I query for teh wsdl 9lik e- http://localhost//myservice/ias?wsdl ) I get the WSDl generated by JB (or JAX-WS) and as an example, calculateTaxType is used prior to its declraration in teh WSDL type. I think thats the cause of the issue below of not finding tags.
14:42:58,757 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}calculateTax references undefined type calculateTaxType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,760 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}changeCostCenterIndicator references undefined type eCareChangeCostCenterIndicatorType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,763 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}restoreSubscriber references undefined type eCareRestoreType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,765 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}suspendSubscriber references undefined type eCareSuspendType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,767 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}retailAddSubscriber references undefined type retailAddSubscriberType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,769 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}occReasonCodeListInquiryResponse references undefined type OCCReasonCodeListInquiryResponseType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,781 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}changeBillingAddress references undefined type eCareChangeBillingAddressType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,783 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}batchOrder references undefined type batchOrderType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,785 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}executePendingUpgradeResponse references undefined type POSPendingOrderResponseType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,788 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}changeEsn references undefined type eCareChangeESNType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,789 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}changeVoicemailPassword references undefined type eCareVoicemailPasswordChangeType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,803 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}updateSubscriber references undefined type eCareUpdateSubscriberType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,805 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}validateAddress references undefined type addressValidationType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,807 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}changeCostCenter references undefined type eCareChangeCostCenterType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,809 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}executeNewEsnChangeResponse references undefined type POSPendingOrderResponseType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,812 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}occPhoneProductListInquiryResponse references undefined type OCCPhoneProductListInquiryResponseType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,814 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}changeNumber references undefined type eCareChangeNumberType for service {http://oas.ws.etm.vzw.com/}OasServiceService.
14:42:58,816 SEVERE [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Schema element {http://oas.ws.etm.vzw.com/}retailServiceOnly references undefined type retailServiceOnlyType for service {http://oas.ws.etm.vzw.com/}OasServiceService. -
3. Re: How does WSDL get generated when publishign a Java based WS?
vatsanm Mar 16, 2012 10:46 AM (in response to vatsanm)I fixed teh issues for teh error above. They were caued by duplicate XM tags with the same namespace. But I still want to understand the sequence of how Jboss creates WSDL requests when teh design approach s bottom up (WSDL is not created ahread o ftime). In logs I see that JB creates WSDL from the WS definition, but I would like to understand the sequence.
-
4. Re: How does WSDL get generated when publishign a Java based WS?
spyhunter99 Mar 16, 2012 10:51 AM (in response to vatsanm)It's some kind of reflection algorithm. See org.jboss.ws.metadata.builder package.
Basically, look for classes annotated with @WebService.
Scan for functions annotated with @WebMethod
etc
-
5. Re: How does WSDL get generated when publishign a Java based WS?
vatsanm Mar 16, 2012 4:16 PM (in response to spyhunter99)Thx spyhunter99. i will take a look at the package.