Hi,
No, the locationURI specified for your cxf bc consumer or provider
endpoint configuration will always override the one from wsdl.
Freeman
On 2009-11-18, at 下午8:22, Håkon Sagehaug wrote:
Hi Freeman,
The new bc is working fine for most times, but sometimes it seems
that it
uses the locationURI property for the provider as the published
address to
the outside. It should normally take the address from the supplied
wsdl
correct?Is there a posibility to set the wanted published address in
the
consumer bean?
Don't know if anyone else have seen this problem, as I said it only
happens
some times and i admit very strange also.
Any ideas why it could happen?
cheers, Håkon
2009/11/17 Freeman Fang <[email protected]>
On 2009-11-17, at 下午10:28, Håkon Sagehaug wrote:
Hi
I'll try to remove the data folder, but when I just dropped the
fuse-bc
installer into the hotdeploy with the old smx-bc there, it worked.
But
I'll
try to remove the data folder and just have the fuse bc there.
Another thing, we see some problems with our cxf-bc provider when
the XML
messages gets over a certain size, what happens we are not sure,
but it
seems that the maybe some of the XML message is chopped off. I
there a
limitation to what size the XML message scan be, or a property
that needs
to
be set. If we send the SOAP request directly to the service it
works fine,
but not through smx.
There's no real limitation for the messasge size IMO.
Freeman
I know that this is not much to go on, but any hint on the top of
your
head?
cheers, Håkon
2009/11/17 Freeman Fang <[email protected]>
Hi,
You need clean remove $SMX_HOME/data folder firstly.
Could you provide the log when install new servicemix-cxf-bc
component if
you already remove data folder?
Freeman
On 2009-11-17, at 下午10:03, Håkon Sagehaug wrote:
Hi
Thansk for the tip, I'm not able to deploy my service assebler
now, do I
need to change something in the xbean file for the service unit
to for
using
the fuse installer? My xbean look like this now
<beans xmlns="http://www.springframework.org/schema/beans";
xmlns:cxfbc="http://servicemix.apache.org/cxfbc/1.0";
xmlns:xsi="http://
http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://servicemix.apache.org/cxfbc/1.0
http://servicemix.apache.org/schema/servicemix-cxfbc-3.2.3.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd";
xmlns:ech="http://www.bccs.uib.no/EchoService.wsdl";>
<cxfbc:consumer wsdl="classpath:service.wsdl"
endpoint="EchoService"
targetEndpoint="EchoServiceProxy"
targetService="ech:EchoService"
schemaValidationEnabled="true" />
<cxfbc:provider wsdl="classpath:service.wsdl"
locationURI="http://129.177.20.229:8080/axis2/services/EchoService/
"
endpoint="EchoServiceProxy" service="ech:EchoService"
interfaceName="ech:EchoServicePortType">
<!--
<cxfbc:inInterceptors> <bean
class="org.apache.cxf.interceptor.LoggingInInterceptor" />
</cxfbc:inInterceptors> <cxfbc:outInterceptors> <bean
class="org.apache.cxf.interceptor.LoggingOutInterceptor" />
</cxfbc:outInterceptors>
-->
</cxfbc:provider>
</beans>
When I try to deply the assembler I get this warning
WARN - AutoDeploymentService - Components servicemix-
cxf-bc
are
not installed yet: the service assembly echo-bc-sa deployment is
suspended
and will be resumed once the listed components are installed
I removed the old bc and copied the new one I downloaded to
SMX_Home/hotdeploy. Also to me it seems that the cxf-bc does not
start
like
the other components.
cheers, Håkon
2009/11/17 Freeman Fang <[email protected]>
On 2009-11-17, at 下午4:23, Håkon Sagehaug wrote:
Hi all,
I've got tow question about the validation component in smx.
1. When I try to create a service unit using maven
mvn archetype:create -
DarchetypeGroupId=org.apache.servicemix.tooling
-DarchetypeArtifactId=servicemix-validation-service-unit
-DgroupId=no.uib.bccs.hakont -DartifactId=echo-validator
with this command I get this error
Error creating from archetype
Embedded error:
org.apache.maven.archetype.downloader.DownloadNotFoundException:
Requested
download does not exist.
Unable to determine the release version
I've got smx 3.3.1 as servicemix_home.
2. My current flow is client -> cxf-bc(consumer) -> cxf-
bc(provider)
->
end-service. Should I place the validation component after the
consumer,
so
that the targetEndpoitn of the consumer is the endpoint of the
validator.
Is
the service attribute the service that the validator sends the
message
to,
or is the extracted from the message??
What you want to validate?
If you just want to validate the incoming soap message against
the
schema
defined in wsdl, then just add schemaValidationEnabled="true"
for your
cxf
bc consumer endpoint configuration, not need to use validate
component
in
this case.
Note, smx 3.3.1 release not have this feature, you need use
fuse side
servicemix release servicemix-cxf-bc-2009.02.0.0-fuse-
installer.zip[1]
to
take advantage of this new feature.
[1]
http://repo.open.iona.com/maven2/org/apache/servicemix/servicemix-cxf-bc/2009.02.0.0-fuse/
Freeman
help appreciated
cheers, Håkon
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
[email protected], phone +47 55584125
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
[email protected], phone +47 55584125
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
[email protected], phone +47 55584125
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
[email protected], phone +47 55584125
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
