Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL
by Arjan Visser
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Using
the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL
published by the ESB (version 2.1.0). Error
message: Application
has thrown exception, unwinding now javax.wsdl.WSDLException: WSDLException:
faultCode=PARSER_ERROR: Problem parsing 'http://dev.boosttechhouse.com:8780/services/'.:
org.xml.sax.SAXParseException: The element type "hr" must be
terminated by the matching end-tag "</hr>". This
is cause by a missing </hr> tag in the generated 'services' page (example
http://dev.boosttechhouse.com:8780/services/). Code
snippet from generated page: <hr><h2><font
color="blue">Faulty
Services</font></h2><h3><font
color="blue">wso2carbon-sts</font></h3><h3><font
color="blue">XKMS</font></h3> Is
there a workaround for this problem? The reason of the "Faulty
Services" section is because I enabled VFS transport globally and then the
ESB complains: "Unable to configure the service XKMS for the VFS
transport: The service has no configuration for the transport. This service is
being marked as faulty and will not be available over the VFS transport." If I
could manage to get rid of this warning, the "Faulty Services"
section will disappear and parsing of the wsdl will be ok. Arjan _______________________________________________ Esb-java-user mailing list Esb-java-user@... https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user |
|
|
Re: Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL
by Ruwan Linton-3
::
Rate this Message:
Hi Arjan,
First of all this is not a WSDL that you are trying to parse, this is a HTML page that is presented to the user containing the list of services deployed on the server. If you want to get the WSDL of service Foo the WSDL path should be http://dev.boosttechhouse.com:8780/services/Foo?wsdl In the mean time I will fix this HTML to be a welformed HTML. Thanks, Ruwan Arjan Visser wrote: > > Using the Apache CXF 2.2.2 client results in an xml parse error when > parsing a WSDL published by the ESB (version 2.1.0). > > > > Error message: > > Application has thrown exception, unwinding now > javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: > Problem parsing 'http://dev.boosttechhouse.com:8780/services/'.: > org.xml.sax.SAXParseException: The element type "hr" must be > terminated by the matching end-tag "</hr>". > > > > This is cause by a missing </hr> tag in the generated 'services' page > (example http://dev.boosttechhouse.com:8780/services/). > > > > Code snippet from generated page: > > <hr><h2><font color="blue">Faulty Services</font></h2><h3><font > color="blue">wso2carbon-sts</font></h3><h3><font > color="blue">XKMS</font></h3> > > > > Is there a workaround for this problem? The reason of the "Faulty > Services" section is because I enabled VFS transport globally and then > the ESB complains: "Unable to configure the service XKMS for the VFS > transport: The service has no configuration for the transport. This > service is being marked as faulty and will not be available over the > VFS transport." > > If I could manage to get rid of this warning, the "Faulty Services" > section will disappear and parsing of the wsdl will be ok. > > > > Arjan > > ------------------------------------------------------------------------ > > _______________________________________________ > Esb-java-user mailing list > Esb-java-user@... > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ruwan@...; cell: +94 77 341 3097 blog: http://blog.ruwan.org _______________________________________________ Esb-java-user mailing list Esb-java-user@... https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user |
|
|
Re: Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL
by Arjan Visser
::
Rate this Message:
Hi Ruwan,
The CXF client is already configured to parse the wsdl with the full wsdl path, like http://dev.boosttechhouse.com:8780/services/Foo?wsdl. However, apparently the CXF client first parses http://dev.boosttechhouse.com:8780/services/ (I don't know why...). Using the CXF client connecting to a ESB 1.7 is working fine. The problem occurred when I moved the "Foo" service to ESB 2.1. Do you also know how to get rid of the "Faulty Services" XKMS and wso2carbon-sts when VFS is enabled global? This creates for me a workaround, because the horizontal line will disappear if no "Faulty Services" are detected. Arjan -----Original Message----- From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...] On Behalf Of Ruwan Linton Sent: dinsdag 6 oktober 2009 11:05 To: esb-java-user@... Subject: Re: [esb-java-user] Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL Hi Arjan, First of all this is not a WSDL that you are trying to parse, this is a HTML page that is presented to the user containing the list of services deployed on the server. If you want to get the WSDL of service Foo the WSDL path should be http://dev.boosttechhouse.com:8780/services/Foo?wsdl In the mean time I will fix this HTML to be a welformed HTML. Thanks, Ruwan Arjan Visser wrote: > > Using the Apache CXF 2.2.2 client results in an xml parse error when > parsing a WSDL published by the ESB (version 2.1.0). > > > > Error message: > > Application has thrown exception, unwinding now > javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: > Problem parsing 'http://dev.boosttechhouse.com:8780/services/'.: > org.xml.sax.SAXParseException: The element type "hr" must be > terminated by the matching end-tag "</hr>". > > > > This is cause by a missing </hr> tag in the generated 'services' page > (example http://dev.boosttechhouse.com:8780/services/). > > > > Code snippet from generated page: > > <hr><h2><font color="blue">Faulty Services</font></h2><h3><font > color="blue">wso2carbon-sts</font></h3><h3><font > color="blue">XKMS</font></h3> > > > > Is there a workaround for this problem? The reason of the "Faulty > Services" section is because I enabled VFS transport globally and then > the ESB complains: "Unable to configure the service XKMS for the VFS > transport: The service has no configuration for the transport. This > service is being marked as faulty and will not be available over the > VFS transport." > > If I could manage to get rid of this warning, the "Faulty Services" > section will disappear and parsing of the wsdl will be ok. > > > > Arjan > > ------------------------------------------------------------------------ > > _______________________________________________ > Esb-java-user mailing list > Esb-java-user@... > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ruwan@...; cell: +94 77 341 3097 blog: http://blog.ruwan.org _______________________________________________ Esb-java-user mailing list Esb-java-user@... https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user _______________________________________________ Esb-java-user mailing list Esb-java-user@... https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user |
|
|
Re: Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL
by Ruwan Linton-3
::
Rate this Message:
Arjan Visser wrote:
> Hi Ruwan, > > The CXF client is already configured to parse the wsdl with the full wsdl > path, like http://dev.boosttechhouse.com:8780/services/Foo?wsdl. However, > apparently the CXF client first parses > http://dev.boosttechhouse.com:8780/services/ (I don't know why...). > Using the CXF client connecting to a ESB 1.7 is working fine. The problem > occurred when I moved the "Foo" service to ESB 2.1. > OK I think the way CXF parses the WSDL is wrong there is no need to parse the root context to parse the WSDL, it could be dangerous to do so. On the other hand we can fix this non-well-formed HTML on the services page. > Do you also know how to get rid of the "Faulty Services" XKMS and > wso2carbon-sts when VFS is enabled global? This creates for me a workaround, > because the horizontal line will disappear if no "Faulty Services" are > detected. > Yes, you need to go to service list and disable the VFS transport for all the services where you have not configured VFS properly. Go to Services > Service Dashboard (Foo) > Transports > disable VFS Thanks, Ruwan > Arjan > > -----Original Message----- > From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...] > On Behalf Of Ruwan Linton > Sent: dinsdag 6 oktober 2009 11:05 > To: esb-java-user@... > Subject: Re: [esb-java-user] Using the Apache CXF 2.2.2 client results in an > xml parse error when parsing a WSDL > > Hi Arjan, > > First of all this is not a WSDL that you are trying to parse, this is a > HTML page that is presented to the user containing the list of services > deployed on the server. > > If you want to get the WSDL of service Foo the WSDL path should be > http://dev.boosttechhouse.com:8780/services/Foo?wsdl > > In the mean time I will fix this HTML to be a welformed HTML. > > Thanks, > Ruwan > > Arjan Visser wrote: > >> Using the Apache CXF 2.2.2 client results in an xml parse error when >> parsing a WSDL published by the ESB (version 2.1.0). >> >> >> >> Error message: >> >> Application has thrown exception, unwinding now >> javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: >> Problem parsing 'http://dev.boosttechhouse.com:8780/services/'.: >> org.xml.sax.SAXParseException: The element type "hr" must be >> terminated by the matching end-tag "</hr>". >> >> >> >> This is cause by a missing </hr> tag in the generated 'services' page >> (example http://dev.boosttechhouse.com:8780/services/). >> >> >> >> Code snippet from generated page: >> >> <hr><h2><font color="blue">Faulty Services</font></h2><h3><font >> color="blue">wso2carbon-sts</font></h3><h3><font >> color="blue">XKMS</font></h3> >> >> >> >> Is there a workaround for this problem? The reason of the "Faulty >> Services" section is because I enabled VFS transport globally and then >> the ESB complains: "Unable to configure the service XKMS for the VFS >> transport: The service has no configuration for the transport. This >> service is being marked as faulty and will not be available over the >> VFS transport." >> >> If I could manage to get rid of this warning, the "Faulty Services" >> section will disappear and parsing of the wsdl will be ok. >> >> >> >> Arjan >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Esb-java-user mailing list >> Esb-java-user@... >> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user >> >> > > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ruwan@...; cell: +94 77 341 3097 blog: http://blog.ruwan.org _______________________________________________ Esb-java-user mailing list Esb-java-user@... https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user |
|
|
Re: Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL
by Arjan Visser
::
Rate this Message:
Ruwan,
Disabling the VFS transports solved the "Faulty Services". I think there is a caching problem, because in the Management Console UI, VFS was already disabled. I had first to add, and then to remove VFS again in order to disable VFS for the faulty services. Arjan -----Original Message----- From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...] On Behalf Of Ruwan Linton Sent: dinsdag 6 oktober 2009 11:44 To: esb-java-user@... Subject: Re: [esb-java-user] Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL Arjan Visser wrote: > Hi Ruwan, > > The CXF client is already configured to parse the wsdl with the full wsdl > path, like http://dev.boosttechhouse.com:8780/services/Foo?wsdl. However, > apparently the CXF client first parses > http://dev.boosttechhouse.com:8780/services/ (I don't know why...). > Using the CXF client connecting to a ESB 1.7 is working fine. The problem > occurred when I moved the "Foo" service to ESB 2.1. > OK I think the way CXF parses the WSDL is wrong there is no need to parse the root context to parse the WSDL, it could be dangerous to do so. On the other hand we can fix this non-well-formed HTML on the services page. > Do you also know how to get rid of the "Faulty Services" XKMS and > wso2carbon-sts when VFS is enabled global? This creates for me a workaround, > because the horizontal line will disappear if no "Faulty Services" are > detected. > Yes, you need to go to service list and disable the VFS transport for all the services where you have not configured VFS properly. Go to Services > Service Dashboard (Foo) > Transports > disable VFS Thanks, Ruwan > Arjan > > -----Original Message----- > From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...] > On Behalf Of Ruwan Linton > Sent: dinsdag 6 oktober 2009 11:05 > To: esb-java-user@... > Subject: Re: [esb-java-user] Using the Apache CXF 2.2.2 client results in an > xml parse error when parsing a WSDL > > Hi Arjan, > > First of all this is not a WSDL that you are trying to parse, this is a > HTML page that is presented to the user containing the list of services > deployed on the server. > > If you want to get the WSDL of service Foo the WSDL path should be > http://dev.boosttechhouse.com:8780/services/Foo?wsdl > > In the mean time I will fix this HTML to be a welformed HTML. > > Thanks, > Ruwan > > Arjan Visser wrote: > >> Using the Apache CXF 2.2.2 client results in an xml parse error when >> parsing a WSDL published by the ESB (version 2.1.0). >> >> >> >> Error message: >> >> Application has thrown exception, unwinding now >> javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: >> Problem parsing 'http://dev.boosttechhouse.com:8780/services/'.: >> org.xml.sax.SAXParseException: The element type "hr" must be >> terminated by the matching end-tag "</hr>". >> >> >> >> This is cause by a missing </hr> tag in the generated 'services' page >> (example http://dev.boosttechhouse.com:8780/services/). >> >> >> >> Code snippet from generated page: >> >> <hr><h2><font color="blue">Faulty Services</font></h2><h3><font >> color="blue">wso2carbon-sts</font></h3><h3><font >> color="blue">XKMS</font></h3> >> >> >> >> Is there a workaround for this problem? The reason of the "Faulty >> Services" section is because I enabled VFS transport globally and then >> the ESB complains: "Unable to configure the service XKMS for the VFS >> transport: The service has no configuration for the transport. This >> service is being marked as faulty and will not be available over the >> VFS transport." >> >> If I could manage to get rid of this warning, the "Faulty Services" >> section will disappear and parsing of the wsdl will be ok. >> >> >> >> Arjan >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Esb-java-user mailing list >> Esb-java-user@... >> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user >> >> > > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ruwan@...; cell: +94 77 341 3097 blog: http://blog.ruwan.org _______________________________________________ Esb-java-user mailing list Esb-java-user@... https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user _______________________________________________ Esb-java-user mailing list Esb-java-user@... https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user |
|
|
Re: Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL
by Ruwan Linton-3
::
Rate this Message:
Cool, nice to hear you got it to work.
Thanks, Ruwan Arjan Visser wrote: > Ruwan, > > Disabling the VFS transports solved the "Faulty Services". I think there is > a caching problem, because in the Management Console UI, VFS was already > disabled. I had first to add, and then to remove VFS again in order to > disable VFS for the faulty services. > > Arjan > > -----Original Message----- > From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...] > On Behalf Of Ruwan Linton > Sent: dinsdag 6 oktober 2009 11:44 > To: esb-java-user@... > Subject: Re: [esb-java-user] Using the Apache CXF 2.2.2 client results in an > xml parse error when parsing a WSDL > > Arjan Visser wrote: > >> Hi Ruwan, >> >> The CXF client is already configured to parse the wsdl with the full wsdl >> path, like http://dev.boosttechhouse.com:8780/services/Foo?wsdl. However, >> apparently the CXF client first parses >> http://dev.boosttechhouse.com:8780/services/ (I don't know why...). >> Using the CXF client connecting to a ESB 1.7 is working fine. The problem >> occurred when I moved the "Foo" service to ESB 2.1. >> >> > OK I think the way CXF parses the WSDL is wrong there is no need to > parse the root context to parse the WSDL, it could be dangerous to do > so. On the other hand we can fix this non-well-formed HTML on the > services page. > >> Do you also know how to get rid of the "Faulty Services" XKMS and >> wso2carbon-sts when VFS is enabled global? This creates for me a >> > workaround, > >> because the horizontal line will disappear if no "Faulty Services" are >> detected. >> >> > Yes, you need to go to service list and disable the VFS transport for > all the services where you have not configured VFS properly. > > Go to Services > Service Dashboard (Foo) > Transports > disable VFS > > Thanks, > Ruwan > >> Arjan >> >> -----Original Message----- >> From: esb-java-user-bounces@... >> > [mailto:esb-java-user-bounces@...] > >> On Behalf Of Ruwan Linton >> Sent: dinsdag 6 oktober 2009 11:05 >> To: esb-java-user@... >> Subject: Re: [esb-java-user] Using the Apache CXF 2.2.2 client results in >> > an > >> xml parse error when parsing a WSDL >> >> Hi Arjan, >> >> First of all this is not a WSDL that you are trying to parse, this is a >> HTML page that is presented to the user containing the list of services >> deployed on the server. >> >> If you want to get the WSDL of service Foo the WSDL path should be >> http://dev.boosttechhouse.com:8780/services/Foo?wsdl >> >> In the mean time I will fix this HTML to be a welformed HTML. >> >> Thanks, >> Ruwan >> >> Arjan Visser wrote: >> >> >>> Using the Apache CXF 2.2.2 client results in an xml parse error when >>> parsing a WSDL published by the ESB (version 2.1.0). >>> >>> >>> >>> Error message: >>> >>> Application has thrown exception, unwinding now >>> javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: >>> Problem parsing 'http://dev.boosttechhouse.com:8780/services/'.: >>> org.xml.sax.SAXParseException: The element type "hr" must be >>> terminated by the matching end-tag "</hr>". >>> >>> >>> >>> This is cause by a missing </hr> tag in the generated 'services' page >>> (example http://dev.boosttechhouse.com:8780/services/). >>> >>> >>> >>> Code snippet from generated page: >>> >>> <hr><h2><font color="blue">Faulty Services</font></h2><h3><font >>> color="blue">wso2carbon-sts</font></h3><h3><font >>> color="blue">XKMS</font></h3> >>> >>> >>> >>> Is there a workaround for this problem? The reason of the "Faulty >>> Services" section is because I enabled VFS transport globally and then >>> the ESB complains: "Unable to configure the service XKMS for the VFS >>> transport: The service has no configuration for the transport. This >>> service is being marked as faulty and will not be available over the >>> VFS transport." >>> >>> If I could manage to get rid of this warning, the "Faulty Services" >>> section will disappear and parsing of the wsdl will be ok. >>> >>> >>> >>> Arjan >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Esb-java-user mailing list >>> Esb-java-user@... >>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user >>> >>> >>> >> >> > > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ruwan@...; cell: +94 77 341 3097 blog: http://blog.ruwan.org _______________________________________________ Esb-java-user mailing list Esb-java-user@... https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user |
| Free embeddable forum powered by Nabble | Forum Help |
