I'll try, but it might take a while before I have time for the patch (today is 
my last day before my summer holidays).

Thanks for your help,
Ciao,
Philipp Rossmanith

ITC Analyst
Systems Integration 
T-Systems ITC Iberia S.A.U.

Edifici 22@
Sancho d'Àvila 110-130
08018 Barcelona

Office:     + 34 93 501 56 22
Main:       + 34 93 501 50 00 
Fax:        + 34 93 501 52 41
Email:      [EMAIL PROTECTED]
Internet:   www.t-systems.com

> -----Mensaje original-----
> De: Nodet Guillaume [mailto:[EMAIL PROTECTED]
> Enviado el: miércoles, 22 de agosto de 2007 11:43
> Para: [email protected]
> Asunto: Re: servicemix-http - classpath-supplied WSDL file not visible
> Importancia: Baja
> 
> Sure, please raise a JIRA.
> Would you try to write a patch too ?
> 
> cheers,
> Guillaume Nodet
> 
> On Aug 22, 2007, at 11:14 AM, Rossmanith, Philipp wrote:
> 
> > Guillaume,
> >
> > You were right. I gave the WSN-Publisher endpoint for which I want
> > to expose a WSDL the same name as was indicated by the WSDL file/
> > HTTP consumer endpoint, and now the WSDL is showing.
> >
> > Let me know if you want me to add an issue to JIRA.
> >
> > Ciao,
> > Philipp
> >
> >> -----Mensaje original-----
> >> De: Guillaume Nodet [mailto:[EMAIL PROTECTED]
> >> Enviado el: miércoles, 22 de agosto de 2007 9:18
> >> Para: [email protected]
> >> Asunto: Re: servicemix-http - classpath-supplied WSDL file not
> >> visible
> >> Importancia: Baja
> >>
> >> I think I have found the problem.
> >> If you look at the log, you see
> >>
> >> 16:50:10,775 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >> HttpComponent
> >> | e.servicemix.http.HttpEndpoint  184 | PortType for
> >> targetService/targetEndpoint could not be found
> >>
> >> So looking at the code, it seems the problem comes from the
> >>   HttpEndpoint#getTargetPortType method.
> >>
> >> This method tries to find the *target* PortType.  And the problem
> >> is that
> >> your target PortType (or interface QName) is not the same as the
> >> one you
> >> expose.
> >> So you need to make them match somehow.
> >>
> >> I guess this can be considered as a bug.  Maybe the getTargetPortType
> >> should be a series of
> >>    if (portType == null && xxx) {
> >>       ...
> >>    }
> >> rather than if / else if.
> >> I think it would work in your case.
> >>
> >>
> >> On 8/20/07, Rossmanith, Philipp <[EMAIL PROTECTED]>
> >> wrote:
> >>> Hi again,
> >>>
> >>> Set the log level for org.apache.servicemix.jbi.deployment to
> >>> DEBUG, as
> >>> well. However, the output I get*) doesn't reveal anything new and
> >>> doesn't indicate any error (except for something about the JBI
> >>> descriptor - which is Maven-tooling generated).
> >>>
> >>> Any ideas?
> >>>
> >>> Thanks in advance,
> >>> Ciao, Philipp
> >>>
> >>>
> >>> *)
> >>> 16:50:10,137 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> AutoDeploymentService    | ramework.AutoDeploymentService  319 | SA
> >>> dependencies: [servicemix-http]
> >>>
> >>> 16:50:10,137 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> DeploymentService        | bi.framework.DeploymentService  459 |
> >>> Moving
> >>> C:\3.1.1\data\smx\tmp\mag-sub-sa-0.1-SNAPSHOT.0.tmp to
> >>> C:\3.1.1\data\smx\service-assemblies\mag-sub-sa\version_1\install
> >>>
> >>> 16:50:10,153 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> DeploymentService        | bi.framework.DeploymentService  509 |
> >>> Unpack
> >>> service unit archive
> >>> C:\3.1.1\data\smx\service-assemblies\mag-sub-sa\version_1\install
> >>> \mag-IM
> >>> Message-sub-http-0.1-SNAPSHOT.zip to
> >>> C:\3.1.1\data\smx\service-assemblies\mag-sub-sa\version_1\sus
> >>> \servicemix
> >>> -http\mag-IMMessage-sub-http
> >>>
> >>> 16:50:10,265 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> HttpComponent
> >>> | .common.BaseServiceUnitManager   61 | Deploying service unit
> >>>
> >>> 16:50:10,265 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> HttpComponent
> >>> | on.xbean.AbstractXBeanDeployer   53 | Looking for
> >>> C:\3.1.1\data\smx\service-assemblies\mag-sub-sa\version_1\sus
> >>> \servicemix
> >>> -http\mag-IMMessage-sub-http\xbean.xml: true
> >>>
> >>> 16:50:10,504 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> HttpComponent
> >>> | .common.BaseServiceUnitManager   75 | Service unit deployed
> >>>
> >>> 16:50:10,711 | INFO  | RMI TCP Connection(5)-10.49.7.32 |
> >>> DescriptorFactory        | deployment.DescriptorFactory$1  104 |
> >>> Validation error on
> >>> file:/C:/3.1.1/data/smx/service-assemblies/mag-sub-sa/version_1/
> >>> sus/serv
> >>> icemix-http/mag-IMMessage-sub-http/META-INF/jbi.xml:
> >>> org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute
> >>> 'interface-name' must appear on element 'consumes'.
> >>>
> >>> 16:50:10,727 | INFO  | RMI TCP Connection(5)-10.49.7.32 |
> >>> ServiceAssemblyLifeCycle | ework.ServiceAssemblyLifeCycle  109 |
> >>> Starting service assembly: mag-sub-sa
> >>>
> >>> 16:50:10,727 | INFO  | RMI TCP Connection(5)-10.49.7.32 |
> >>> ServiceUnitLifeCycle     | framework.ServiceUnitLifeCycle   78 |
> >>> Initializing service unit: mag-IMMessage-sub-http
> >>>
> >>> 16:50:10,727 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> HttpComponent
> >>> | .common.BaseServiceUnitManager  100 | Initializing service unit
> >>>
> >>> 16:50:10,727 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> HttpComponent
> >>> | .common.BaseServiceUnitManager  118 | Service unit initialized
> >>>
> >>> 16:50:10,727 | INFO  | RMI TCP Connection(5)-10.49.7.32 |
> >>> ServiceUnitLifeCycle     | framework.ServiceUnitLifeCycle   97 |
> >>> Starting service unit: mag-IMMessage-sub-http
> >>>
> >>> 16:50:10,727 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> HttpComponent
> >>> | .common.BaseServiceUnitManager  137 | Starting service unit
> >>>
> >>> 16:50:10,775 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> HttpComponent
> >>> | e.servicemix.http.HttpEndpoint  184 | PortType for
> >>> targetService/targetEndpoint could not be found
> >>>
> >>> 16:50:10,775 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> HttpComponent
> >>> | e.servicemix.soap.SoapEndpoint  276 | Retrieving proxied endpoint
> >>> definition
> >>>
> >>> 16:50:10,918 | INFO  | RMI TCP Connection(5)-10.49.7.32 | jetty
> >>> | ervicemix.http.jetty.JCLLogger   80 | jetty-6.0.1
> >>>
> >>> 16:50:11,110 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> JettyContextManager      | ntextManager$ThreadPoolWrapper  441 |
> >>> Dispatching job: [EMAIL PROTECTED]
> >>>
> >>> 16:50:11,110 | INFO  | RMI TCP Connection(5)-10.49.7.32 | jetty
> >>> | ervicemix.http.jetty.JCLLogger   80 | Started
> >>> SelectChannelConnector @
> >>> 0.0.0.0:8192
> >>>
> >>> 16:50:11,174 | DEBUG | RMI TCP Connection(5)-10.49.7.32 |
> >>> HttpComponent
> >>> | .common.BaseServiceUnitManager  153 | Service unit started
> >>>
> >>> 16:50:11,189 | DEBUG | RMI TCP Connection(5)-10.49.7.32 | SedaFlow
> >>> | emix.jbi.nmr.flow.AbstractFlow  149 | Called Flow resume
> >>>
> >>>> -----Mensaje original-----
> >>>> De: Rossmanith, Philipp
> >>>> Enviado el: lunes, 20 de agosto de 2007 14:20
> >>>> Para: [email protected]
> >>>> Asunto: RE: servicemix-http - classpath-supplied WSDL file not
> >>>> visible
> >>>> Importancia: Baja
> >>>>
> >>>> Hi,
> >>>>
> >>>> I set the level to DEBUG for org.apache.servicemix, but the only
> >>> output
> >>>> I got for my endpoint is that a request has been received, that the
> >>>> portType for targetService/targetEndpoint cannot be found, and that
> >>> the
> >>>> proxied endpoint definition is to be retrieved.**)
> >>>>
> >>>> Any ideas?
> >>>>
> >>>> Thanks in advance,
> >>>> Ciao, Philipp
> >>>>
> >>>>>>
> >>>> 13:11:01,349 | DEBUG | btpool0-1  | ConsumerProcessor        |
> >>>> p.processors.ConsumerProcessor  120 | Receiving HTTP request: GET
> >>>> /IMMessageNotificationService/?wsdl HTTP/1.1
> >>>> Host: localhost:8192
> >>>>
> >>>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> >>> rv:1.8.1.6)
> >>>> Gecko/20070725 Firefox/2.0.0.6
> >>>>
> >>>> Accept:
> >>>>
> >>> text/xml,application/xml,application/xhtml+xml,text/
> >>> html;q=0.9,text/plai
> >>>> n;q=0.8,image/png,*/*;q=0.5
> >>>>
> >>>> Accept-Language: en-us,en;q=0.5
> >>>>
> >>>> Accept-Encoding: gzip,deflate
> >>>>
> >>>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> >>>>
> >>>> Keep-Alive: 300
> >>>>
> >>>> Connection: keep-alive
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> 13:11:01,380 | DEBUG | btpool0-1  | ConsumerProcessor        |
> >>>> p.processors.ConsumerProcessor  120 | Receiving HTTP request: GET
> >>>> /IMMessageNotificationService/main.wsdl HTTP/1.1
> >>>> Host: localhost:8192
> >>>>
> >>>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> >>> rv:1.8.1.6)
> >>>> Gecko/20070725 Firefox/2.0.0.6
> >>>>
> >>>> Accept:
> >>>>
> >>> text/xml,application/xml,application/xhtml+xml,text/
> >>> html;q=0.9,text/plai
> >>>> n;q=0.8,image/png,*/*;q=0.5
> >>>>
> >>>> Accept-Language: en-us,en;q=0.5
> >>>>
> >>>> Accept-Encoding: gzip,deflate
> >>>>
> >>>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> >>>>
> >>>> Keep-Alive: 300
> >>>>
> >>>> Connection: keep-alive
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> 13:11:01,396 | DEBUG | btpool0-1  | HttpComponent            |
> >>>> e.servicemix.http.HttpEndpoint  184 | PortType for
> >>>> targetService/targetEndpoint could not be found
> >>>>
> >>>> 13:11:01,396 | DEBUG | btpool0-1  | HttpComponent            |
> >>>> e.servicemix.soap.SoapEndpoint  276 | Retrieving proxied endpoint
> >>>> definition
> >>>> <<
> >>>>
> >>>>> -----Mensaje original-----
> >>>>> De: Nodet Guillaume [mailto:[EMAIL PROTECTED]
> >>>>> Enviado el: viernes, 17 de agosto de 2007 23:20
> >>>>> Para: [email protected]
> >>>>> Asunto: Re: servicemix-http - classpath-supplied WSDL file not
> >>> visible
> >>>>> Importancia: Baja
> >>>>>
> >>>>> Have you tried setting the log level to DEBUG and see if something
> >>>>> interesting
> >>>>> shows in the console ?
> >>>>>
> >>>>> Cheers,
> >>>>> Guillaume Nodet
> >>>>>
> >>>>> On Aug 17, 2007, at 6:30 PM, Rossmanith, Philipp wrote:
> >>>>>
> >>>>>> Dear all,
> >>>>>>
> >>>>>> I'm trying to publish an HTTP consumer endpoint with a
> >>>>>> classpath-supplied WSDL connecting to a servicemix.xml-configured
> >>>>>> publisher. The setup is:
> >>>>>> HTTP consumer EP --> publisher EP
> >>>>>>
> >>>>>> I use the same xbean.xml configuration I usually use for
> >>> HTTP/JSR181
> >>>>>> SAs*), and create the deployment units with Maven. I also took
> >>> care
> >>>>>> that
> >>>>>> the information about service and endpoint supplied in the
> >>>> xbean.xml*)
> >>>>>> matches the one supplied in the WSDL file**), setting the service
> >>>> name
> >>>>>> to <namespace prefix>:<WSDL service name> and setting the
> >>>>>> endpoint
> >>>>>> name
> >>>>>> to the value of the port's name. The WSDL file is present at the
> >>>>>> top-level in the ZIP-file for the SU.
> >>>>>>
> >>>>>> Nevertheless, my WSDL file is not showing when consulting
> >>>>>> http://localhost:8192/IMMessageNotificationService/main.wsdl.
> >>>>>>
> >>>>>> QUESTIONS:
> >>>>>> Is there anything wrong with my configuration?
> >>>>>> Or is it because the connected-to service is an internal service
> >>> and
> >>>>>> doesn't publish a WSDL?
> >>>>>>
> >>>>>> Any help would be highly appreciated.
> >>>>>>
> >>>>>> Thanks in advance,
> >>>>>> Ciao,
> >>>>>> Philipp
> >>>>>>
> >>>>>> *)
> >>>>>> <?xml version="1.0" encoding="UTF-8"?>
> >>>>>> <beans xmlns:http="http://servicemix.apache.org/http/1.0";
> >>>>>>   xmlns:mag="http://mag.icing.eu/notification/1.0";
> >>>>>>
> >>>>>>
> >>> xmlns:csapi="http://www.csapi.org/wsdl/parlayx/multimedia_messaging/
> >>>>>> noti
> >>>>>> fication/v2_0/service"
> >>>>>>   xmlns:pub="http://iisys.icing.eu/publisher/1.0";
> >>>>>>
> >>>>>>
> >>> xmlns:impl="http://www.csapi.org/wsdl/parlayx/multimedia_messaging/
> >>>>>> notif
> >>>>>> ication/v2_0/service">
> >>>>>>   <classpath>
> >>>>>>           <location>.</location>
> >>>>>>   </classpath>
> >>>>>>
> >>>>>>   <http:endpoint service="impl:IMMessageNotificationService"
> >>>>>>           endpoint="IMMessageNotification" role="consumer"
> >>>>>>
> >>>>>> locationURI="http://0.0.0.0:8192/IMMessageNotificationService/";
> >>>>>>           soap="true"
> >>>>>> wsdlResource="classpath:IMMessageNotification.wsdl"
> >>>>>>           targetService="pub:IMMessagePublisher"
> >>>>>> targetEndpoint="ep" />
> >>>>>> </beans>
> >>>>>>
> >>>>>> **)
> >>>>>> <wsdl:definitions
> >>>>>>
> >>>>>> targetNamespace="http://www.csapi.org/wsdl/parlayx/
> >>>>>> multimedia_messaging/
> >>>>>> notification/v2_0/service" ...>
> >>>>>> ...
> >>>>>>       <wsdl:service name="IMMessageNotificationService">
> >>>>>>           <wsdl:port
> >>>>>> binding="impl:IMMessageNotificationSoapBinding"
> >>>>>>                   name="IMMessageNotification">
> >>>>>>                   <wsdlsoap:address
> >>>>>> location="http://0.0.0.0:8192/IMMessageNotificationService/"; />
> >>>>>>           </wsdl:port>
> >>>>>>   </wsdl:service>
> >>>>>> ...
> >>>>>> </ wsdl:definitions>
> >>>>>>
> >>>>>>
> >>>>>> This e-mail and any attachments may contain confidential or
> >>>>>> privileged information. Any unauthorised copying, use or
> >>>>>> distribution of
> >>>>>> this information is strictly prohibited.
> >>>>
> >>>>
> >>>> This e-mail and any attachments may contain confidential or
> >>>> privileged information. Any unauthorised copying, use or
> >>>> distribution
> >>> of
> >>>> this information is strictly prohibited.
> >>>
> >>> This e-mail and any attachments may contain confidential or
> >>> privileged information. Any unauthorised copying, use or
> >>> distribution of
> >>> this information is strictly prohibited.
> >>>
> >>
> >>
> >> --
> >> Cheers,
> >> Guillaume Nodet
> >> ------------------------
> >> Blog: http://gnodet.blogspot.com/
> >
> > This e-mail and any attachments may contain confidential or
> > privileged information. Any unauthorised copying, use or
> > distribution of
> > this information is strictly prohibited.


This e-mail and any attachments may contain confidential or
privileged information. Any unauthorised copying, use or distribution of
this information is strictly prohibited.

Reply via email to