Hi,

Ok, this should be caused by your env stax implementation, we already have woodstox in $SMX_HOME/lib folder, so by default woodstox should be pick up as stax implementation.
However somehow in your env use some other stax implementation.

Some questions
1. You platform?
2. You JDK vendor and version?
3. Do you endorse your JDK?
4. Do you specify javax.xml.stream.XMLInputFactory somewhere else but you're not aware of that?
5. could add system properties like
-Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory - Djavax.xml.stream.XMLOutputFactory=com.ctc.wstx.stax.WstxOutputFactory in servicemix startup script to ensure always use woodstox stax implementation.



Freeman

On 2011-6-3, at 下午3:23, jaikishore wrote:

Hi Freeman,



I changed name attribute like {WSDL Namespace}portName.http-conduit as u said.

Still I am getting the same xception. Please help me to solve this.



[javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,196]

Message: http://www.w3.org/TR/1999/REC-xml-names-19990114#ElementPrefixUnbound ?http&http:client]

at com .sun .xml .bind .v2 .runtime .unmarshaller .UnmarshallerImpl.handleStreamException(UnmarshallerImpl.java:397)

at com .sun .xml .bind .v2 .runtime .unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:335)

at com .sun .xml .bind .v2 .runtime .unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:312)

at org .apache .cxf .configuration .spring.JAXBBeanFactory.createJAXBBean(JAXBBeanFactory.java:51)

       ... 37 more

Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,196]



Cxf.xml ::

<beans xmlns="http://www.springframework.org/schema/beans";

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:sec="http://cxf.apache.org/configuration/security";

     xmlns:http="http://cxf.apache.org/transports/http/configuration";

     xmlns:jaxws="http://java.sun.com/xml/ns/jaxws";

     xsi:schemaLocation="

     http://cxf.apache.org/configuration/security

     http://cxf.apache.org/schemas/configuration/security.xsd

     http://cxf.apache.org/transports/http/configuration

     http://cxf.apache.org/schemas/configuration/http-conf.xsd

     http://www.springframework.org/schema/beans

http://www.springframework.org/schema/beans/spring- beans-2.0.xsd">

     <http:conduit

name="{http://www.americanexpress.com/businesstravel/profilerouter }ProfileRouterMgmtServicePort.http-conduit">

           <http:client AutoRedirect="true" Connection="Keep-Alive" />

     </http:conduit>

</beans>





Regards

Jai Kishore P, AMEX-GTT

N:0441-8212,M:9884041281.



From: Freeman-2 [via ServiceMix] [mailto:[email protected] ]
Sent: Friday, June 03, 2011 12:37 PM
To: Polepalli, JaiKishore
Subject: Re: cxf:bc provider with proxy configuration



Hi,

About the http:conduit name, you should take a look about the link[1]
which I've pointed to you, more importantly.

The first thing to notice is the "name" attribute on <http:conduit>.
This allows CXF to associate this HTTP Conduit configuration with a
particular WSDL Port. The name includes the service's namespace, the
WSDL port name (as found in the wsdl:service section of the WSDL), and
".http-conduit". It follows this template: "{WSDL
Namespace}portName.http-conduit". Note: it's the PORT name, not the
service name. Thus, it's likely something like "MyServicePort", not
"MyService". If you are having trouble getting the template to work,
another (temporary) option for the name value is simply "*.http-
conduit".

There's an obvious error in your configuration, you shouldn't have an
":" between the namespace and port name.

Btw, please don't post same question several times on the list, we're
glad to help but we can't guarantee the response time, so please don't
post same question every half hour like this.

Please be patient,  if you really need some immediate response, I
think you may need consider some commercial support[2]

[1]http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html
[2]http://servicemix.apache.org/support.html

Freeman


On 2011-6-3, at 下午2:32, jaikishore wrote:


Hi Freeman,

                      There’s no any whitespaces in front xml
declaration
line in cxf.xml. Still it’s not working{getting same xception}.
Then I tried to give exact name space and port endpoint with “:”
character
in cxf.xml{please check the below configurations}.
now I am not getting the below exception. At the same time messages
are not
routing through this proxy{which we are defined in cxf.xml} getting
connection timed out xception.
can u please check the configuration http:conduit
name="{http://www.jack.com/businesstravel/
profilerouter}:ProfileRouterMgmtServicePort.http-conduit
given in cxf.xml is true or not. please help me in this regards…

cxf.xml ::  <?xml version="1.0" encoding="UTF-8"?>










Xbean.xml:
<?xml version="1.0" encoding="UTF-8"?>


          .






--
View this message in context: 
http://servicemix.396122.n5.nabble.com/cxf-bc-provider-with-proxy-configuration-tp4447568p4450300.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.


---------------------------------------------
Freeman Fang

FuseSource
Email:[hidden email]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
Connect at CamelOne May 24-26
The Open Source Integration Conference











________________________________

If you reply to this email, your message will be added to the discussion below:

http://servicemix.396122.n5.nabble.com/cxf-bc-provider-with-proxy-configuration-tp4447568p4450372.html

To unsubscribe from cxf:bc provider with proxy configuration, click here <http://servicemix.396122.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4447568&code=amFpa2lzaG9yZV9wb2xlcGFsbGlAc3ludGVsaW5jLmNvbXw0NDQ3NTY4fDE2NDY1NDE5MjA= > .


Confidential: This electronic message and all contents contain information from Syntel, Inc. which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee only. If you are not the addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited. If you have received this electronic message in error, please notify the sender immediately and destroy the original message and all copies.


--
View this message in context: 
http://servicemix.396122.n5.nabble.com/cxf-bc-provider-with-proxy-configuration-tp4447568p4450401.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

---------------------------------------------
Freeman Fang

FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
Connect at CamelOne May 24-26
The Open Source Integration Conference








Reply via email to