Re: CXF on WebLogic 9.2
on CXF2.0.4, it's "geronimo-stax-api_1.0_spec-1.0.jar".
chengas123 <[EMAIL PROTECTED]> wrote:
Haha. I would have realized that was the same .jar
The only one included in 2.0.4 is stax-utils-20060502.jar
YI (William) ZHU wrote:
>
> actually, it's "stax-api-1.0.1.jar".
> (on CXF 2.0.2 and CXF 2.0.3)
>
>
>
> chengas123 wrote:
>
> I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find any file
> name stax-api.jar in the lib directory.
>
>
>
> YI (William) ZHU wrote:
>>
>> stax-api jar file is in \{CXF-home}\lib
>>
>> unpackage it, you will find the javax.xml.namespace.QName class.
>>
>> delete it, and re-package the file.
>>
>> try it.
>>
>
>
--
View this message in context:
http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15213728.html
Sent from the cxf-user mailing list archive at Nabble.com.
-
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
Re: CXF on WebLogic 9.2
actually, it's "stax-api-1.0.1.jar".
(on CXF 2.0.2 and CXF 2.0.3)
chengas123 <[EMAIL PROTECTED]> wrote:
I downloaded apache-cxf-2.0.4-incubator.tar.gz and could not find any file
name stax-api.jar in the lib directory.
YI (William) ZHU wrote:
>
> stax-api jar file is in \{CXF-home}\lib
>
> unpackage it, you will find the javax.xml.namespace.QName class.
>
> delete it, and re-package the file.
>
> try it.
>
>
--
View this message in context:
http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15213356.html
Sent from the cxf-user mailing list archive at Nabble.com.
-
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
Re: CXF on WebLogic 9.2
stax-api jar file is in \{CXF-home}\lib
unpackage it, you will find the javax.xml.namespace.QName class.
delete it, and re-package the file.
try it.
chengas123 wrote:
>
> Hi,
> I was getting a "java.lang.NoSuchMethodError:
> javax.jws.WebService.portName()Ljava/lang/String;" error on WebLogic 9.2,
> but seemed to have solved it by following a post
> (http://forums.bea.com/thread.jspa?threadID=69031) I found and adding
> -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory to
> my WebLogic startup.
> However, I'm now getting:
> java.lang.RuntimeException: [was class java.net.ConnectException] Tried
> all: '1' addresses, but could not connect over HTTP to server:
> 'java.sun.com', port: '80'
> My only guess is it's trying to validate a DTD or something and is being
> blocked by our corporate firewall. I have no idea how to tell weblogic
> about our proxy. Configuring the proxy would be a good short-term
> solution since it would allow development to move forward. However,
> ultimately I'm probably going to need another solution since I'm not sure
> this would fly in our production environment.
>
> Thanks,
> Ben
>
>
--
View this message in context:
http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15213281.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF on WebLogic 9.2
How about you put the jar file "xml-resolver-1.2.jar" in your webLogic classpath? (keep this -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory setting) Or make sure CXF's jars in your classpath. I agree that "Configuring the proxy" is not a good solution. Hope this can help. Yi Zhu chengas123 wrote: > > Hi, > I was getting a "java.lang.NoSuchMethodError: > javax.jws.WebService.portName()Ljava/lang/String;" error on WebLogic 9.2, > but seemed to have solved it by following a post > (http://forums.bea.com/thread.jspa?threadID=69031) I found and adding > -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory to > my WebLogic startup. > However, I'm now getting: > java.lang.RuntimeException: [was class java.net.ConnectException] Tried > all: '1' addresses, but could not connect over HTTP to server: > 'java.sun.com', port: '80' > My only guess is it's trying to validate a DTD or something and is being > blocked by our corporate firewall. I have no idea how to tell weblogic > about our proxy. Configuring the proxy would be a good short-term > solution since it would allow development to move forward. However, > ultimately I'm probably going to need another solution since I'm not sure > this would fly in our production environment. > > Thanks, > Ben > > -- View this message in context: http://www.nabble.com/CXF-on-WebLogic-9.2-tp15193763p15211777.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: JCA demo raises java.lang.UnsupportedOperation when deployed in JBOSS
I tested using JBoss4.0.5 and CXF 2.0.2 as Jeff suggested to the sample, it works. But I still found error messages from JBoss 4.0.5 console. I don't know why there are so many "ERROR"s? although the sample seems function correctly. Is this bug in CXF? Please see the error messages: == ... ERROR [STDERR] ... org.apache.cxf.jca.cxf.ManagedConnectionFactoryImpl ... ERROR [STDERR] ... org.apache.cxf.jca.cxf.AssociatedManagedConnectionFactoryImpl ... ERROR [STDERR] ... org.apache.cxf.jca.cxf.AssociatedManagedConnectionFactoryImpl setResourceAdapter ... ERROR [STDERR] ... org.apache.cxf.jca.cxf.ManagedConnectionFactoryImpl createConnectionFactory ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.JCABusFactory initialiseServants ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.JCABusFactory startPropertiesMonitorThread ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.ConnectionFactoryImpl ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.JCABusFactory $EJBServicePropertiesMonitorRunnable run ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.JCABusFactory loadProperties ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.ConnectionFactoryImpl getConnection Jeff Zhang-2 wrote: > > Hi Ade, > > CXF has tested on Jboss 4.0.x in release. We can do work on Jboss 4.2.x if > you need. Could you raise a JIRA? > > Thanks > Jeff > - Original Message - > From: "Adrian Trenaman" <[EMAIL PROTECTED]> > To: > Sent: Friday, August 17, 2007 6:03 PM > Subject: JCA demo raises java.lang.UnsupportedOperation when deployed in > JBOSS > > >> >> Hi, >> >> Has anyone experienced any problems deploying the JCA adaptor into JBoss? >> I >> was experiencing problems and have reproduced with the demo in >> samples/integration/jca/hello_world. When the servlet invokes on the >> proxy, >> we get: >> >> java.lang.UnsupportedOperationException: setProperty must be >> overridden >> by all subclasses of SOAP Message >> >> I'm using JDK 1.5.0_09, CXF 2.0.1 and JBoss 4.2.1. Have also gotten the >> same >> problem with JBoss 5.0.0 Beta 2. >> >> Google shows that others have also experienced this problem; some >> workarounds are suggested around putting libraries (jboss-jaxrpc.jar, >> jboss-saaj.jar, jaxb-api.jar and jaxws-api.jar) into the JBoss >> lib/endorsed >> directory. I note that the demo already places files in lib/endorsed - do >> we >> need to add more? >> >> Finally (I'm not sure whether this is related or not) - I'm noting that >> the >> stack trace uses CXF classes right down to >> sun.reflect.NativeMethodAccessorImpl, and then JBossWS classes are used >> to >> create the SOAP message. is this right? I would have thought that the >> entire >> interaction should be handled by CXF classes? >> >> Curious, >> Ade. >> -- >> View this message in context: > http://www.nabble.com/JCA-demo-raises-java.lang.UnsupportedOperation-when-deployed-in-JBOSS-tf4284807.html#a12197014 >> Sent from the cxf-user mailing list archive at Nabble.com. >> > > -- View this message in context: http://www.nabble.com/JCA-demo-raises-java.lang.UnsupportedOperation-when-deployed-in-JBOSS-tp12197014p15045592.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: JCA demo raises java.lang.UnsupportedOperation when deployed in JBOSS
Hi, I met some similar troubles with JBoss 4.2.2, CXF2.0.2 and JDK 1.5.0_14. When I deploy the JCA J2ee connector on JBoss, I found the following error messages on JBoss console: ERROR [STDERR] Jan 22, 2008 3:27:29 PM org.apache.cxf.jca.cxf.ManagedConnectionFactoryImpl ERROR [STDERR] Jan 22, 2008 3:27:29 PM org.apache.cxf.jca.cxf.AssociatedManagedConnectionFactoryImpl ERROR [STDERR] Jan 22, 2008 3:27:29 PM org.apache.cxf.jca.cxf.AssociatedManagedConnectionFactoryImpl setResourceAdapter INFO: Associate Resource Adapter with ManagedConnectionFactory by appserver. ra = null ERROR [STDERR] Jan 22, 2008 3:27:29 PM org.apache.cxf.jca.cxf.ManagedConnectionFactoryImpl createConnectionFactory Could someone tell me that the CXF j2ee connector (CXF2.0.2) tested with JBoss4.2.2? Thanks, Adrian Trenaman wrote: > > Hi, > > Has anyone experienced any problems deploying the JCA adaptor into JBoss? > I was experiencing problems and have reproduced with the demo in > samples/integration/jca/hello_world. When the servlet invokes on the > proxy, we get: > > java.lang.UnsupportedOperationException: setProperty must be > overridden by all subclasses of SOAP Message > > I'm using JDK 1.5.0_09, CXF 2.0.1 and JBoss 4.2.1. Have also gotten the > same problem with JBoss 5.0.0 Beta 2. > > Google shows that others have also experienced this problem; some > workarounds are suggested around putting libraries (jboss-jaxrpc.jar, > jboss-saaj.jar, jaxb-api.jar and jaxws-api.jar) into the JBoss > lib/endorsed directory. I note that the demo already places files in > lib/endorsed - do we need to add more? > > Finally (I'm not sure whether this is related or not) - I'm noting that > the stack trace uses CXF classes right down to > sun.reflect.NativeMethodAccessorImpl, and then JBossWS classes are used to > create the SOAP message. is this right? I would have thought that the > entire interaction should be handled by CXF classes? > > Curious, > Ade. > -- View this message in context: http://www.nabble.com/JCA-demo-raises-java.lang.UnsupportedOperation-when-deployed-in-JBOSS-tp12197014p15028522.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: About sample "integration\JBI\external_provider_internal_consumer"
Thanks for your reply!
Actually I'm using ServiceMix 3.2.1, and also using the CXF component with
ServiceMix (not the one with CXF2.0.2).
I just wondering that this maybe a bug in CXF component, if someone can
confirm that.
Regards,
gnodet wrote:
>
> Could you please try with the servicemix CXF components instead ? They are
> much more tested than this one AFAIK. I'm not very familiar with this
> very component, so I can't help much, but I think it would be wise to try
> and start the CXF components that come with ServiceMix instead.
> ServiceMix distribution also comes with an example that you will be able
> to deploy.
>
>
> YI (William) ZHU wrote:
>>
>> Hi,
>>
>> I'm studing the sample
>> "integration\JBI\external_provider_internal_consumer" of CXF 2.0.2.
>>
>> I followed the README, when I started the "CXF Service Engine", I found
>> the following message on ServiceMix console:
>>
>> ...
>> SEVERE: Could not find Apache CXF configuration in
>>
>> C:\apps\servicemix321\data\smx\components\CXFServiceEngine\version_1\META-INF
>> ...
>> ...ServiceEngineShutdown changeState
>> INFO: in shutdown state
>> ...
>>
>> It seems that CXF Service Engine was shutdown, but when I continue
>> to Deploy and start CXF demo service assembly, everything were working.
>>
>> First, I don't understand why when there is a "SEVERE" error, the example
>> still works;
>> Second, actually there is a file "cxf-config.xml" under that folder, but
>> with empty contents;
>>
>> Could anyone help answer this question?
>>
>>
>> Thanks,
>> YI ZHU
>>
>> (details as below)
>>
>> Jan 16, 2008 1:50:15 PM org.apache.cxf.jbi.se.CXFBootstrap init
>> INFO: Bootstrap.init called
>> Jan 16, 2008 1:50:15 PM org.apache.cxf.jbi.se.CXFBootstrap onInstall
>> INFO: Bootstrap.onInstall called
>> Jan 16, 2008 1:50:16 PM org.apache.cxf.jbi.se.CXFBootstrap cleanUp
>> INFO: Bootstrap.cleanUp called
>> INFO - ComponentMBeanImpl - Starting component:
>> CXFServiceEngine
>> INFO - ComponentMBeanImpl - Initializing component:
>> CXFServiceEngine
>> Jan 16, 2008 1:50:33 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
>> changeState
>> INFO: in shutdown state
>> Jan 16, 2008 1:50:33 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
>> initSE
>> SEVERE: Could not find Apache CXF configuration in
>> C:\apps\servicemix321\data\smx\components\CXFServiceEngine\version_1\META-INF
>> Jan 16, 2008 1:50:33 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
>> initializeBus
>> INFO: initializing bus
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
>> initializeBus
>> INFO: init bus complete
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.transport.jbi.JBITransportFactory
>> setDeliveryChannel
>> INFO: configuring DeliveryChannel: DeliveryChannel{CXFServiceEngine}
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
>> initSE
>> INFO: Apache CXF Service Engine installation
>> root:C:\apps\servicemix321\data\smx\components\CXFServiceEngine\version_1
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
>> initSE
>> INFO: CXF Service Engine init complete
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.CXFServiceEngine start
>> INFO: CXFServiceEngine starting
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineStop
>> changeState
>> INFO: in stop state
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.transport.jbi.JBITransportFactory
>> setDeliveryChannel
>> INFO: configuring DeliveryChannel: DeliveryChannel{CXFServiceEngine}
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineStop
>> startSE
>> INFO: CXFServiceEngine startup complete
>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/About-sample-%22integration%5CJBI%5Cexternal_provider_internal_consumer%22-tp14889400p15028317.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: About sample "integration\JBI\external_provider_internal_consumer"
... (after stoping & shuting down CXF Service Engine) then I try to uninstall
CSE,
but I got the following message on ServiceMix console:
INFO - JBIContainer - Deactivating component
CXFServiceEngine
Jan 18, 2008 2:56:59 PM org.apache.cxf.jbi.se.CXFBootstrap onUninstall
INFO: Bootstrap.onUninstall called
Jan 18, 2008 2:56:59 PM org.apache.cxf.jbi.se.CXFBootstrap cleanUp
INFO: Bootstrap.cleanUp called
WARN - EnvironmentContext - Failed to remove directory
structure for component [version]:
CXFServiceEngine [CXFServiceEngine]
The ServiceMix failed to remove CSE, further more this caused that we can
not install CSE next time.
(the workaround is to manually remove the CSE folder).
Could someone confirm this issue?
Thanks,
YI (William) ZHU wrote:
>
> When I stop CXF Service Engine component, I got the following message from
> ServiceMix console:
>
> INFO - ComponentMBeanImpl - Stopping component:
> CXFServiceEngine
> Jan 18, 2008 2:48:23 PM org.apache.cxf.jbi.se.CXFServiceEngine stop
> INFO: CXFServiceEngine stopped
> Jan 18, 2008 2:48:23 PM org.apache.cxf.jbi.se.state.ServiceEngineStart
> changeState
> INFO: in start state
>
> Is the information given "in start state" correct? seems it should be "in
> stop state".
>
> Could anyone anwser this question?
>
> Thanks,
>
>
>
>
>
>
>
>
>
>
>
> YI (William) ZHU wrote:
>>
>> Hi,
>>
>> I'm studing the sample
>> "integration\JBI\external_provider_internal_consumer" of CXF 2.0.2.
>>
>> I followed the README, when I started the "CXF Service Engine", I found
>> the following message on ServiceMix console:
>>
>> ...
>> SEVERE: Could not find Apache CXF configuration in
>>
>> C:\apps\servicemix321\data\smx\components\CXFServiceEngine\version_1\META-INF
>> ...
>> ...ServiceEngineShutdown changeState
>> INFO: in shutdown state
>> ...
>>
>> It seems that CXF Service Engine was shutdown, but when I continue
>> to Deploy and start CXF demo service assembly, everything were working.
>>
>> First, I don't understand why when there is a "SEVERE" error, the example
>> still works;
>> Second, actually there is a file "cxf-config.xml" under that folder, but
>> with empty contents;
>>
>> Could anyone help answer this question?
>>
>>
>> Thanks,
>> YI ZHU
>>
>> (details as below)
>>
>> Jan 16, 2008 1:50:15 PM org.apache.cxf.jbi.se.CXFBootstrap init
>> INFO: Bootstrap.init called
>> Jan 16, 2008 1:50:15 PM org.apache.cxf.jbi.se.CXFBootstrap onInstall
>> INFO: Bootstrap.onInstall called
>> Jan 16, 2008 1:50:16 PM org.apache.cxf.jbi.se.CXFBootstrap cleanUp
>> INFO: Bootstrap.cleanUp called
>> INFO - ComponentMBeanImpl - Starting component:
>> CXFServiceEngine
>> INFO - ComponentMBeanImpl - Initializing component:
>> CXFServiceEngine
>> Jan 16, 2008 1:50:33 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
>> changeState
>> INFO: in shutdown state
>> Jan 16, 2008 1:50:33 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
>> initSE
>> SEVERE: Could not find Apache CXF configuration in
>> C:\apps\servicemix321\data\smx\components\CXFServiceEngine\version_1\META-INF
>> Jan 16, 2008 1:50:33 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
>> initializeBus
>> INFO: initializing bus
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
>> initializeBus
>> INFO: init bus complete
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.transport.jbi.JBITransportFactory
>> setDeliveryChannel
>> INFO: configuring DeliveryChannel: DeliveryChannel{CXFServiceEngine}
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
>> initSE
>> INFO: Apache CXF Service Engine installation
>> root:C:\apps\servicemix321\data\smx\components\CXFServiceEngine\version_1
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
>> initSE
>> INFO: CXF Service Engine init complete
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.CXFServiceEngine start
>> INFO: CXFServiceEngine starting
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineStop
>> changeState
>> INFO: in stop state
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.transport.jbi.JBITransportFactory
>> setDeliveryChannel
>> INFO: configuring DeliveryChannel: DeliveryChannel{CXFServiceEngine}
>> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineStop
>> startSE
>> INFO: CXFServiceEngine startup complete
>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/About-sample-%22integration%5CJBI%5Cexternal_provider_internal_consumer%22-tp14889400p14957786.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: About sample "integration\JBI\external_provider_internal_consumer"
When I stop CXF Service Engine component, I got the following message from
ServiceMix console:
INFO - ComponentMBeanImpl - Stopping component:
CXFServiceEngine
Jan 18, 2008 2:48:23 PM org.apache.cxf.jbi.se.CXFServiceEngine stop
INFO: CXFServiceEngine stopped
Jan 18, 2008 2:48:23 PM org.apache.cxf.jbi.se.state.ServiceEngineStart
changeState
INFO: in start state
Is the information given "in start state" correct? seems it should be "in
stop state".
Could anyone anwser this question?
Thanks,
YI (William) ZHU wrote:
>
> Hi,
>
> I'm studing the sample
> "integration\JBI\external_provider_internal_consumer" of CXF 2.0.2.
>
> I followed the README, when I started the "CXF Service Engine", I found
> the following message on ServiceMix console:
>
> ...
> SEVERE: Could not find Apache CXF configuration in
>
> C:\apps\servicemix321\data\smx\components\CXFServiceEngine\version_1\META-INF
> ...
> ...ServiceEngineShutdown changeState
> INFO: in shutdown state
> ...
>
> It seems that CXF Service Engine was shutdown, but when I continue
> to Deploy and start CXF demo service assembly, everything were working.
>
> First, I don't understand why when there is a "SEVERE" error, the example
> still works;
> Second, actually there is a file "cxf-config.xml" under that folder, but
> with empty contents;
>
> Could anyone help answer this question?
>
>
> Thanks,
> YI ZHU
>
> (details as below)
>
> Jan 16, 2008 1:50:15 PM org.apache.cxf.jbi.se.CXFBootstrap init
> INFO: Bootstrap.init called
> Jan 16, 2008 1:50:15 PM org.apache.cxf.jbi.se.CXFBootstrap onInstall
> INFO: Bootstrap.onInstall called
> Jan 16, 2008 1:50:16 PM org.apache.cxf.jbi.se.CXFBootstrap cleanUp
> INFO: Bootstrap.cleanUp called
> INFO - ComponentMBeanImpl - Starting component:
> CXFServiceEngine
> INFO - ComponentMBeanImpl - Initializing component:
> CXFServiceEngine
> Jan 16, 2008 1:50:33 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
> changeState
> INFO: in shutdown state
> Jan 16, 2008 1:50:33 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
> initSE
> SEVERE: Could not find Apache CXF configuration in
> C:\apps\servicemix321\data\smx\components\CXFServiceEngine\version_1\META-INF
> Jan 16, 2008 1:50:33 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
> initializeBus
> INFO: initializing bus
> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
> initializeBus
> INFO: init bus complete
> Jan 16, 2008 1:50:41 PM org.apache.cxf.transport.jbi.JBITransportFactory
> setDeliveryChannel
> INFO: configuring DeliveryChannel: DeliveryChannel{CXFServiceEngine}
> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
> initSE
> INFO: Apache CXF Service Engine installation
> root:C:\apps\servicemix321\data\smx\components\CXFServiceEngine\version_1
> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
> initSE
> INFO: CXF Service Engine init complete
> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.CXFServiceEngine start
> INFO: CXFServiceEngine starting
> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineStop
> changeState
> INFO: in stop state
> Jan 16, 2008 1:50:41 PM org.apache.cxf.transport.jbi.JBITransportFactory
> setDeliveryChannel
> INFO: configuring DeliveryChannel: DeliveryChannel{CXFServiceEngine}
> Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineStop
> startSE
> INFO: CXFServiceEngine startup complete
>
>
>
--
View this message in context:
http://www.nabble.com/About-sample-%22integration%5CJBI%5Cexternal_provider_internal_consumer%22-tp14889400p1495.html
Sent from the cxf-user mailing list archive at Nabble.com.
About sample "integration\JBI\external_provider_internal_consumer"
Hi,
I'm studing the sample "integration\JBI\external_provider_internal_consumer"
of CXF 2.0.2.
I followed the README, when I started the "CXF Service Engine", I found the
following message on ServiceMix console:
...
SEVERE: Could not find Apache CXF configuration in
C:\apps\servicemix321\data\smx\components\CXFServiceEngine\version_1\META-INF
...
...ServiceEngineShutdown changeState
INFO: in shutdown state
...
It seems that CXF Service Engine was shutdown, but when I continue
to Deploy and start CXF demo service assembly, everything were working.
First, I don't understand why when there is a "SEVERE" error, the example
still works;
Second, actually there is a file "cxf-config.xml" under that folder, but
with empty contents;
Could anyone help answer this question?
Thanks,
YI ZHU
(details as below)
Jan 16, 2008 1:50:15 PM org.apache.cxf.jbi.se.CXFBootstrap init
INFO: Bootstrap.init called
Jan 16, 2008 1:50:15 PM org.apache.cxf.jbi.se.CXFBootstrap onInstall
INFO: Bootstrap.onInstall called
Jan 16, 2008 1:50:16 PM org.apache.cxf.jbi.se.CXFBootstrap cleanUp
INFO: Bootstrap.cleanUp called
INFO - ComponentMBeanImpl - Starting component:
CXFServiceEngine
INFO - ComponentMBeanImpl - Initializing component:
CXFServiceEngine
Jan 16, 2008 1:50:33 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
changeState
INFO: in shutdown state
Jan 16, 2008 1:50:33 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
initSE
SEVERE: Could not find Apache CXF configuration in
C:\apps\servicemix321\data\smx\components\CXFServiceEngine\version_1\META-INF
Jan 16, 2008 1:50:33 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
initializeBus
INFO: initializing bus
Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
initializeBus
INFO: init bus complete
Jan 16, 2008 1:50:41 PM org.apache.cxf.transport.jbi.JBITransportFactory
setDeliveryChannel
INFO: configuring DeliveryChannel: DeliveryChannel{CXFServiceEngine}
Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
initSE
INFO: Apache CXF Service Engine installation
root:C:\apps\servicemix321\data\smx\components\CXFServiceEngine\version_1
Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineShutdown
initSE
INFO: CXF Service Engine init complete
Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.CXFServiceEngine start
INFO: CXFServiceEngine starting
Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineStop
changeState
INFO: in stop state
Jan 16, 2008 1:50:41 PM org.apache.cxf.transport.jbi.JBITransportFactory
setDeliveryChannel
INFO: configuring DeliveryChannel: DeliveryChannel{CXFServiceEngine}
Jan 16, 2008 1:50:41 PM org.apache.cxf.jbi.se.state.ServiceEngineStop
startSE
INFO: CXFServiceEngine startup complete
--
View this message in context:
http://www.nabble.com/About-sample-%22integration%5CJBI%5Cexternal_provider_internal_consumer%22-tp14889400p14889400.html
Sent from the cxf-user mailing list archive at Nabble.com.
about sample "ws_addressing"
Hi there, I'm studying the sample "ws_addressing" of CXF2.0.2. I have two questions about the configure file "handler_chain.xml": 1) where is the Java file for "demo.ws_addressing.common.HeaderSnooper" class? I have searched the whole samples, but can not find it; 2) when this file "handler_chain.xml" is used? Please help answer this question! Thanks, YI ZHU -- View this message in context: http://www.nabble.com/about-sample-%22ws_addressing%22-tp14673937p14673937.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: sample failure: restfull_http_binding
Hi,
I have done some testing to the page "test.html".
Two fixes:
1) works with IE 6 and FireFox 2 now;
2) customers table is refreshed, not appended.
Please validate.
Cheers,
YI ZHU
http://www.nabble.com/file/p14437670/test.html test.html
dkulp wrote:
>
>
>
> I think these are logged as:
>
> https://issues.apache.org/jira/browse/CXF-873
> https://issues.apache.org/jira/browse/CXF-889
>
> Patches are most welcome.
>
> Dan
>
>
> On Friday 14 December 2007, YI (William) ZHU wrote:
>> Hi,
>>
>> I found that there two issues in the CXF 2.0.2 sample
>> "restfull_http_binding":
>>
>> 1) the "test.html" page to test the "Jettison/CXF AJAX Demo" is not
>> working, I found that the javascript has problem.
>>
>> 2) if I change the "CustomerServiceImpl.java" file to let the web
>> service to return two customers, not the original 1 customer. Then
>> following links work fine:
>>http://localhost:8080/xml/customers
>>http://localhost:8080/xml/customers/123
>>http://localhost:8080/json/customers/123
>>
>> but this link "http://localhost:8080/json/customers"; return:
>>
>> {"acme.Customers":{"acme.customer":[{"acme.id":"789","acme.name":"Will
>>iam Zhu"},{"acme.id":"123","acme.name":"Dan Diephouse"}]}}
>>
>> I thought that's not correct, they should return two "acme.customer"
>> items.
>>
>> Can someone check the implementation of JSON on CXF is OK?
>>
>>
>> Thanks,
>> YI ZHU
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer, IONA
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
>
--
View this message in context:
http://www.nabble.com/sample-failure%3A-restfull_http_binding-tp14339771p14437670.html
Sent from the cxf-user mailing list archive at Nabble.com.
RE: sample failure: restfull_http_binding
Hi Jervis,
Thanks for your reply.
I have tested the sample with FireFox 2, it works but not in a correct way:
Everytime when I click the "Get Customers!" button, the same customers were
appended to the page.
I think they should be refreshed but not appended.
Regards,
YI ZHU
Liu, Jervis wrote:
>
> For your information, CXF-889 has been fixed in CXF2.0.3, though the "Get
> Customers!" button is still not working with IE (works with Firefox). I
> created https://issues.apache.org/jira/browse/CXF-1306 to track this.
>
> Cheers,
> Jervis
>
>
>> -Original Message-
>> From: Daniel Kulp [mailto:[EMAIL PROTECTED]
>> Sent: 2007年12月15日 4:20
>> To: cxf-user@incubator.apache.org
>> Cc: YI (William) ZHU
>> Subject: Re: sample failure: restfull_http_binding
>>
>>
>>
>> I think these are logged as:
>>
>> https://issues.apache.org/jira/browse/CXF-873
>> https://issues.apache.org/jira/browse/CXF-889
>>
>> Patches are most welcome.
>>
>> Dan
>>
>>
>> On Friday 14 December 2007, YI (William) ZHU wrote:
>> > Hi,
>> >
>> > I found that there two issues in the CXF 2.0.2 sample
>> > "restfull_http_binding":
>> >
>> > 1) the "test.html" page to test the "Jettison/CXF AJAX Demo" is not
>> > working, I found that the javascript has problem.
>> >
>> > 2) if I change the "CustomerServiceImpl.java" file to let the web
>> > service to return two customers, not the original 1 customer. Then
>> > following links work fine:
>> >http://localhost:8080/xml/customers
>> >http://localhost:8080/xml/customers/123
>> >http://localhost:8080/json/customers/123
>> >
>> > but this link "http://localhost:8080/json/customers"; return:
>> >
>> >
>> {"acme.Customers":{"acme.customer":[{"acme.id":"789","acme.name":"Wil
>> l
>> >iam Zhu"},{"acme.id":"123","acme.name":"Dan Diephouse"}]}}
>> >
>> > I thought that's not correct, they should return two "acme.customer"
>> > items.
>> >
>> > Can someone check the implementation of JSON on CXF is OK?
>> >
>> >
>> > Thanks,
>> > YI ZHU
>>
>>
>>
>> --
>> J. Daniel Kulp
>> Principal Engineer, IONA
>> [EMAIL PROTECTED]
>> http://www.dankulp.com/blog
>
>
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
>
>
--
View this message in context:
http://www.nabble.com/sample-failure%3A-restfull_http_binding-tp14339771p14373995.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: sample failure: restfull_http_binding
...continue...
should the return from JSON server be like:
{"acme.Customers":{"acme.customer":[{"acme.id":"789","acme.name":"William
Zhu"},{"acme.id":"123","acme.name":"Dan Diephouse"}]}}
or like this?
{"acme.Customers":{"acme.customer":{"acme.id":"789","acme.name":"William
Zhu"}},{"acme.customer":{"acme.id":"123","acme.name":"Dan Diephouse"}}}
I think that second one is correct. The first one is from server (JSON).
--
View this message in context:
http://www.nabble.com/sample-failure%3A-restfull_http_binding-tp14339771p14339790.html
Sent from the cxf-user mailing list archive at Nabble.com.
sample failure: restfull_http_binding
Hi,
I found that there two issues in the CXF 2.0.2 sample
"restfull_http_binding":
1) the "test.html" page to test the "Jettison/CXF AJAX Demo" is not working,
I found that the javascript has problem.
2) if I change the "CustomerServiceImpl.java" file to let the web service to
return two customers, not the original 1 customer. Then following links
work fine:
http://localhost:8080/xml/customers
http://localhost:8080/xml/customers/123
http://localhost:8080/json/customers/123
but this link "http://localhost:8080/json/customers"; return:
{"acme.Customers":{"acme.customer":[{"acme.id":"789","acme.name":"William
Zhu"},{"acme.id":"123","acme.name":"Dan Diephouse"}]}}
I thought that's not correct, they should return two "acme.customer" items.
Can someone check the implementation of JSON on CXF is OK?
Thanks,
YI ZHU
--
View this message in context:
http://www.nabble.com/sample-failure%3A-restfull_http_binding-tp14339771p14339771.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Basic problem with running CXF samples
The server will time-out in 5 minutes (You can change it in server class). So you need to test your client in 5 minutes after the server was started. Hope this can give your help. [EMAIL PROTECTED] wrote: I'm using the CXF binary distribution apache-cxf-2.0.2-incubator. I tried running 'ant server' from the samples/java_first_pojo directory. Then from a second shell I ran 'ant client' but the client failed to connect after a SocketTimeoutException. When the server comes up it does give the message "Server ready...". Running netstat -tea does show port 9000 to be open but trying to open http://localhost:9000/Hello from a browser fails to connect also. I've tried a couple of other examples (java_first_jaxws and wsdl_first) with the same result. Also, I just downloaded version 2.0.1 and tried running the hello_world sample and had the same experience. Any suggestions on how to get the examples working or find out what is wrong? Thanks, Rossen __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: sample "wsdl_first_pure_xml" don't work in CXF 2.0.2
Hi Bo,
THanks for your reply!
I downloaded "apache-cxf-2.0.3-incubator-20071023.180556-5.zip" this
morning,
and tried it. It has the same bug of 2.0.2 release.
Can I know how to fix it?
Thanks,
Bozhong Lin wrote:
>
> I can confirm that this is a bug of 2.0.2 release, but it appears to have
> been fixed in the latest trunk and 2.0.x branch. We will keep an eye on
> this
> for 2.0.3 release.
>
> Thanks for reporting issue.
>
> Cheers,
> Bo
>
> On 10/26/07, YI (William) ZHU <[EMAIL PROTECTED]> wrote:
>>
>>
>> I'm using the following command(under folder :
>> samples\wsdl_first_pure_xml)
>>
>> ant client
>> or ant server
>>
>> (up to now, I'v tried several other examples, and all others are working,
>> except this one).
>>
>> Thanks,
>>
>>
>>
>> YI (William) ZHU wrote:
>> >
>> > Hi there,
>> >
>> > I'm using CXF 2.0.2, and trying to test the example
>> "wsdl_first_pure_xml".
>> > But when I'm building the example, I got the following error message:
>> >
>> > ===
>> > [java] WSDLToJava Error :
>> > Binding(Greeter_XMLBinding):BindingOperation({htt
>> > p://apache.org/hello_world_xml_http/bare}testMultiParamPart)-input:
>> wrong
>> > value
>> > of rootNode attribute, the value should be
>> > {http://apache.org/hello_world_xml_ht
>> > tp/bare}testMultiParamPart
>> > [java]
>> > [java] org.apache.cxf.tools.common.ToolException:
>> > Binding(Greeter_XMLBindin
>> > g):BindingOperation({
>> http://apache.org/hello_world_xml_http/bare}testMultiParamP
>> > art)-input: wrong value of rootNode attribute, the value should be
>> > {http://apach
>> > e.org/hello_world_xml_http/bare}testMultiParamPart
>> > [java]
>> > [java] at
>> > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.validate(WSDL
>> > ToJavaContainer.java:545)
>> > [java] at
>> > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(
>> WSDLToJavaContainer.java:219)
>> > [java] at
>> > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLT
>> > oJavaContainer.java:259)
>> > [java] at
>> > org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java
>> :83)
>> > [java] at
>> > org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:102)
>> > [java] at
>> > org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:171)
>> >
>> > BUILD FAILED
>> > =
>> >
>> > I think that there are errors in "hello_world.wsdl", but I don't know
>> what
>> > exactly wrong there.
>> >
>> > Can someone try the example "wsdl_first_pure_xml"? An know the what the
>> > problem?
>> >
>> > Thanks,
>> > YI ZHU
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/sample-%22wsdl_first_pure_xml%22-don%27t-work-in-CXF-2.0.2-tf4692143.html#a13413288
>> Sent from the cxf-user mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/sample-%22wsdl_first_pure_xml%22-don%27t-work-in-CXF-2.0.2-tf4692143.html#a13428711
Sent from the cxf-user mailing list archive at Nabble.com.
Re: sample "wsdl_first_pure_xml" don't work in CXF 2.0.2
I'm using the following command(under folder : samples\wsdl_first_pure_xml)
ant client
or ant server
(up to now, I'v tried several other examples, and all others are working,
except this one).
Thanks,
YI (William) ZHU wrote:
>
> Hi there,
>
> I'm using CXF 2.0.2, and trying to test the example "wsdl_first_pure_xml".
> But when I'm building the example, I got the following error message:
>
> ===
> [java] WSDLToJava Error :
> Binding(Greeter_XMLBinding):BindingOperation({htt
> p://apache.org/hello_world_xml_http/bare}testMultiParamPart)-input: wrong
> value
> of rootNode attribute, the value should be
> {http://apache.org/hello_world_xml_ht
> tp/bare}testMultiParamPart
> [java]
> [java] org.apache.cxf.tools.common.ToolException:
> Binding(Greeter_XMLBindin
> g):BindingOperation({http://apache.org/hello_world_xml_http/bare}testMultiParamP
> art)-input: wrong value of rootNode attribute, the value should be
> {http://apach
> e.org/hello_world_xml_http/bare}testMultiParamPart
> [java]
> [java] at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.validate(WSDL
> ToJavaContainer.java:545)
> [java] at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:219)
> [java] at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLT
> oJavaContainer.java:259)
> [java] at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:83)
> [java] at
> org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:102)
> [java] at
> org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:171)
>
> BUILD FAILED
> =
>
> I think that there are errors in "hello_world.wsdl", but I don't know what
> exactly wrong there.
>
> Can someone try the example "wsdl_first_pure_xml"? An know the what the
> problem?
>
> Thanks,
> YI ZHU
>
--
View this message in context:
http://www.nabble.com/sample-%22wsdl_first_pure_xml%22-don%27t-work-in-CXF-2.0.2-tf4692143.html#a13413288
Sent from the cxf-user mailing list archive at Nabble.com.
sample "wsdl_first_pure_xml" don't work in CXF 2.0.2
Hi there,
I'm using CXF 2.0.2, and trying to test the example "wsdl_first_pure_xml".
But when I'm building the example, I got the following error message:
===
[java] WSDLToJava Error :
Binding(Greeter_XMLBinding):BindingOperation({htt
p://apache.org/hello_world_xml_http/bare}testMultiParamPart)-input: wrong
value
of rootNode attribute, the value should be
{http://apache.org/hello_world_xml_ht
tp/bare}testMultiParamPart
[java]
[java] org.apache.cxf.tools.common.ToolException:
Binding(Greeter_XMLBindin
g):BindingOperation({http://apache.org/hello_world_xml_http/bare}testMultiParamP
art)-input: wrong value of rootNode attribute, the value should be
{http://apach
e.org/hello_world_xml_http/bare}testMultiParamPart
[java]
[java] at
org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.validate(WSDL
ToJavaContainer.java:545)
[java] at
org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:219)
[java] at
org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLT
oJavaContainer.java:259)
[java] at
org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:83)
[java] at
org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:102)
[java] at
org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:171)
BUILD FAILED
=
I think that there are errors in "hello_world.wsdl", but I don't know what
exactly wrong there.
Can someone try the example "wsdl_first_pure_xml"? An know the what the
problem?
Thanks,
YI ZHU
--
View this message in context:
http://www.nabble.com/sample-%22wsdl_first_pure_xml%22-don%27t-work-in-CXF-2.0.2-tf4692143.html#a13411173
Sent from the cxf-user mailing list archive at Nabble.com.
