[Dev] Callout mediator (Axis2 sendRobust method) wraps the request sent out with a soap envelope

[Nirmal Fernando]

Hi All,

$Subject. How can I avoid this?

-- 

Thanks & regards,
Nirmal

Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Turing][Branch] Compilation Error in test-automation-framework - Test Core 4.2.3

[Hasitha Aravinda]

Hi,

I am getting this.

[INFO]

[INFO] Building WSO2 Carbon Automation - Test Core 4.2.3
[INFO]

[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
org.wso2.carbon.automation.core ---
[INFO] Deleting
/data/source/branch/carbon420/platform/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.core/target
[INFO]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
org.wso2.carbon.automation.core ---
[debug] execute contextualize
[WARNING] File encoding has not been set, using platform encoding UTF-8,
i.e. build is platform dependent!
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] Copying 18 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
org.wso2.carbon.automation.core ---
[WARNING] File encoding has not been set, using platform encoding UTF-8,
i.e. build is platform dependent!
[INFO] Compiling 171 source files to
/data/source/branch/carbon420/platform/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.core/target/classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/data/source/branch/carbon420/platform/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.core/src/main/java/org/wso2/carbon/automation/core/utils/ArtifactDeployerUtil.java:[691,42]
unreported exception java.lang.Exception; must be caught or declared to be
thrown
[INFO] 1 error
[INFO] -
[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 Carbon Automation - Parent core project .. SUCCESS [0.383s]
[INFO] WSO2 Carbon Automation - Test API . SUCCESS [9.145s]
[INFO] WSO2 Carbon Automation - Test Core  FAILURE [5.275s]
[INFO] WSO2 Carbon Automation - Common Utils . SKIPPED
[INFO] WSO2 Carbon Automation - Jmeter Test Runner ... SKIPPED
[INFO]

[INFO] BUILD FAILURE


Thanks,
Hasitha.




-- 
Hasitha Aravinda,
Software Engineer,
WSO2 Inc.
Email: hasi...@wso2.com
Mobile: +94 71 8 210 200
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Callout mediator (Axis2 sendRobust method) wraps the request sent out with a soap envelope

[Isuru Udana]

Hi Nirmal,

In ESB 4.8.0, you can do this by setting the messageType to application/xml.
However IFAIK in previous versions that method won't work.


On Sun, Nov 3, 2013 at 2:44 AM, Nirmal Fernando  wrote:

> Hi All,
>
> $Subject. How can I avoid this?
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>


-- 
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Callout mediator (Axis2 sendRobust method) wraps the request sent out with a soap envelope

[Isuru Udana]

Try setting the following property for ESB 4.7.0 or previous versions.


Make sure to set "enableREST" to false after the Callout mediator.




On Sun, Nov 3, 2013 at 11:37 AM, Isuru Udana  wrote:

> Hi Nirmal,
>
> In ESB 4.8.0, you can do this by setting the messageType to
> application/xml.
> However IFAIK in previous versions that method won't work.
>
>
> On Sun, Nov 3, 2013 at 2:44 AM, Nirmal Fernando  wrote:
>
>> Hi All,
>>
>> $Subject. How can I avoid this?
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>
>
> --
> *Isuru Udana*
>  Senior
> * Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
> twitter: http://twitter.com/isudana
>



-- 
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppFactory] Enable deploy only if there is a successful build and after deployed one of successful build

[Danushka Fernando]

"If there is a deployment then the deployment button is enable" I assume
you meant If there is a build then enable the deploy button. But what if
all the builds are unsuccessful? We are not storing about last successful
build in rxt. So at that point this feature is incomplete I guess.

And as ashansa pointed out when deploy is called we are also calling a
build. So if we are going forward with this button disabling thing we may
need to remove that implementation. And currently we are displaying a
message at build and deploy saying build / deploy is submitted, check in a
while. So things are good enough for me.

And yeah polling is not good. So if we really need this my suggestion is to
wait until user clicks the build/deploy button, then check whether there is
a successful build to deploy and if not display a warning message about
that. This will solve it in a better way with lesser no of calls. WDYT?


Thanks & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729


On Sun, Nov 3, 2013 at 8:24 AM, Dimuthu Leelarathne wrote:

> Hi Gayan,
>
>
> On Fri, Nov 1, 2013 at 11:41 AM, Gayan Dhanushka  wrote:
>
>> Hi,
>>
>> IMO we really need to figure out ways to make the UIs more responsive.
>>
>
> +1. That is the whole point.
>
>
>> At the moment they are not responsive enough. For a user it is too
>> misleading sometimes. After clicking the build button it should be disabled
>> until the build finishes. Further more I don't think that we need to look
>> for successful build to deploy (Don't need to go through all the builds to
>> look for a successful build). Considering the last build is enough. Someone
>> who has written new code and pushed it to the repo will not want to deploy
>> an earlier build as his/her is considering only the last build.
>>
>>
> @Harsha - There are other ways. Please don't poll the servers. You can get
> the deployment status from the  rxt in the registry. If there is a
> deployment then the deployment button is enable. I think that is good
> enough. And to make the UI more responsive we can give a message as the
> deployment has been submitted, pls check in a while  blah blah message.
> As for the very first time in app deployment we can do 3 to 5 calls and
> stop.
>
> thanks,
> dimuthu
>
>
>> Thanks.
>> GayanD
>>
>> Gayan Dhanuska
>> Software Engineer
>> http://wso2.com/
>> Lean Enterprise Middleware
>>
>> Mobile
>> 071 666 2327
>>
>> Office
>> Tel   : 94 11 214 5345
>> Fax  : 94 11 214 5300
>>
>> Twitter : https://twitter.com/gayanlggd
>>
>>
>> On Fri, Nov 1, 2013 at 8:12 AM, Ashansa Perera  wrote:
>>
>>> Hi all,
>>>
>>> IMO too enabling deploy button only if there is a successful build would
>>> need a lot of calls to jenkins as Danushka has also explained and it may
>>> not enough to do in page reload time too. So it would be good to show a
>>> notification if no successful build is there. But currently what we do is
>>> we programatically trigger a build if no successful build is there when
>>> user ask to deploy. But yes if that build fails the deployment will fail.
>>> If we are going to do this button disabling if no successful build is
>>> there, we may need to avoid building programatically.
>>>
>>> Regarding enabling the deploy button after the deployment successful :
>>> IMHO this is a main feature that we should add - a notification
>>> framework since most of our actions are async.
>>> And we should enable the button after trying to deploy ( means even the
>>> deployment is successful or not ) Else the user will be stuck if the
>>> deployment fails. But here I agree with Ramith, is there a specific reason
>>> for disabling the button until deployment finishes? For me too it does not
>>> seems to be a must thing to have.
>>>
>>>
>>>
>>>
>>> On Thu, Oct 31, 2013 at 6:12 PM, Ramith Jayasinghe wrote:
>>>
 To me also disabling buttons doesn't look attractive. But if we go down
 this path we can add a tool tip saying when the button is enabled etc.
 What seems best (and simple to implement would be) showing a dialog
 saying there is no build available yet.


 On Thu, Oct 31, 2013 at 5:56 PM, Danushka Fernando 
 wrote:

> Please check inline comments.
>
> On Thu, Oct 31, 2013 at 5:29 PM, Harsha Thirimanna 
> wrote:
>
>>  Hi,
>>
>> *Enable deploy only if there is a successful build*
>> https://wso2.org/jira/browse/APPFAC-1644
>> We can get the lastSuccessfulBuild id from jenkins to given job. When
>> we click on the deploy button, we can check whether there is at least one
>> lastSuccessfulBuild id and if there are no one then show the message to 
>> the
>> user.
>>
>> Any suggestion about this ?
>>
>> Issue is proposing to disable the button when no successful builds
> are there. So
>  1. I thought we have removed lot of disabling buttons because this
> confuses the user.
>  2. If we disable buttons each time this

Re: [Dev] Retail Banking Sample

[Pushpalanka Jayawardhana]

Hi Tom,

May be you got through the following issue.
Just making a note that any one else who face the issue will be benefited
and late is better than never.

The error has been due to the wrong port number. It needs to be changed to
8081 as we are running WSO2ESB with port offset 1 in the sample.So this
should be reflected to AccountDetailService.wsdl and CardService.wsdl. The
sample is updated with this now.

Cheers,

Pushpalanka Jayawardhana

Software Engineer

WSO2 Lanka (pvt) Ltd
[image: 
Facebook]
[image:
Twitter]
[image:
LinkedIn]
[image:
Blogger]
[image:
SlideShare]
Mobile: +94779716248


On Fri, Jul 5, 2013 at 5:16 PM, Tom Shearer  wrote:

>  Hi,
>
>
>
> I’m trying to test the Retail Banking Sample in the latest version of WSO2
> as we’re currently investigating the possible uses within our organisation.
>
>
>
> We’re using all the latest software available and all the latest java
> libs.
>
>
>
> There are a few parts of the documentation that don’t quite match the
> software, which I’m assuming has been updated since the docs were written…
> anyway…
>
>
>
> I’ve managed to configure the whole system and have it mostly running
> until I try to test it when the BPEL service throws the following error.
>
>
>
> Your help is appreciated.
>
>
>
> Best regards,
>
>
>
> Tom
>
>
>
> [2013-07-05 10:55:26,896]  INFO
> {org.apache.axis2.transport.http.HTTPSender} -  Unable to sendViaPost to
> url[http://localhost:8280/services/AccountServiceProxy]
>
> java.net.ConnectException: Connection refused: connect
>
> at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
>
> at
> java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75)
>
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
>
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
>
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
>
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157)
>
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
>
> at java.net.Socket.connect(Socket.java:579)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:601)
>
> at
> org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:140)
>
> at
> org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:125)
>
> at
> org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
>
> at
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
>
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
>
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
>
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
>
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:621)
>
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
>
> at
> org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
>
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:450)
>
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:277)
>
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
>
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
>
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
>
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
>
> at
> org.wso2.carbon.bpel.core.ode.integration.utils.AxisServiceUtils.invokeService(AxisServiceUtils.java:305)
>
> at
> org.wso2.carbon.bpel.core.ode.integration.PartnerService.invoke(PartnerService.java:289)
>
> at
> org.wso2.carbon.bpel.core.ode.integratio

Re: [Dev] Input Event Adaptor - Event Builder CEP 3.0.0 - method onEventCall()

[andresgomez92]

Finally I've solved it, thank you very much!

Andrés Gómez



--
View this message in context: 
http://wso2-oxygen-tank.10903.n7.nabble.com/Input-Event-Adaptor-Event-Builder-CEP-3-0-0-method-onEventCall-tp87973p87985.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Event Builder JSON Builder - Default Value, use????

[andresgomez92]

Hi all,

I have a question about the field "Default Value" on the Event Builder.

I think the following:

If I receive an event like this:

*{"Nombre":"Andres", "Dinero"10, "Other":"100}
*
and I use this: 

 

When the event leaves the event builder, I have this:

*[Andres 10]
*
Now, If I receive an event like this:

*{"Nombre":"Andres", "Other":100}
*
When the event leaves the event builder, I have this:

*[Andres]
*

But I expected to get this:

*[Andres 0]
*

Since the field "Default Value" to "Dinero" is 0.

Do not operate in this manner? Could I do it in any way?

Regards,

Andrés Gómez



--
View this message in context: 
http://wso2-oxygen-tank.10903.n7.nabble.com/Event-Builder-JSON-Builder-Default-Value-use-tp87986.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Turing][Branch] Compilation Error in test-automation-framework - Test Core 4.2.3

[Krishantha Samaraweera]

Fixed. Please check.

On 11/3/13, Hasitha Aravinda  wrote:
> Hi,
>
> I am getting this.
>
> [INFO]
> 
> [INFO] Building WSO2 Carbon Automation - Test Core 4.2.3
> [INFO]
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> org.wso2.carbon.automation.core ---
> [INFO] Deleting
> /data/source/branch/carbon420/platform/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.core/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
> org.wso2.carbon.automation.core ---
> [debug] execute contextualize
> [WARNING] File encoding has not been set, using platform encoding UTF-8,
> i.e. build is platform dependent!
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] Copying 18 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
> org.wso2.carbon.automation.core ---
> [WARNING] File encoding has not been set, using platform encoding UTF-8,
> i.e. build is platform dependent!
> [INFO] Compiling 171 source files to
> /data/source/branch/carbon420/platform/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.core/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /data/source/branch/carbon420/platform/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.core/src/main/java/org/wso2/carbon/automation/core/utils/ArtifactDeployerUtil.java:[691,42]
> unreported exception java.lang.Exception; must be caught or declared to be
> thrown
> [INFO] 1 error
> [INFO] -
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 Carbon Automation - Parent core project .. SUCCESS [0.383s]
> [INFO] WSO2 Carbon Automation - Test API . SUCCESS [9.145s]
> [INFO] WSO2 Carbon Automation - Test Core  FAILURE [5.275s]
> [INFO] WSO2 Carbon Automation - Common Utils . SKIPPED
> [INFO] WSO2 Carbon Automation - Jmeter Test Runner ... SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
>
>
> Thanks,
> Hasitha.
>
>
>
>
> --
> Hasitha Aravinda,
> Software Engineer,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile: +94 71 8 210 200
>


-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Turing][Branch] Compilation Error in test-automation-framework - Test Core 4.2.3

[Hasitha Aravinda]

Checked. It is fixed now.

Thanks,
Hasitha.


On Mon, Nov 4, 2013 at 9:42 AM, Krishantha Samaraweera
wrote:

> Fixed. Please check.
>
> On 11/3/13, Hasitha Aravinda  wrote:
> > Hi,
> >
> > I am getting this.
> >
> > [INFO]
> > 
> > [INFO] Building WSO2 Carbon Automation - Test Core 4.2.3
> > [INFO]
> > 
> > [INFO]
> > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> > org.wso2.carbon.automation.core ---
> > [INFO] Deleting
> >
> /data/source/branch/carbon420/platform/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.core/target
> > [INFO]
> > [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
> > org.wso2.carbon.automation.core ---
> > [debug] execute contextualize
> > [WARNING] File encoding has not been set, using platform encoding UTF-8,
> > i.e. build is platform dependent!
> > [WARNING] Using platform encoding (UTF-8 actually) to copy filtered
> > resources, i.e. build is platform dependent!
> > [INFO] Copying 18 resources
> > [INFO]
> > [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
> > org.wso2.carbon.automation.core ---
> > [WARNING] File encoding has not been set, using platform encoding UTF-8,
> > i.e. build is platform dependent!
> > [INFO] Compiling 171 source files to
> >
> /data/source/branch/carbon420/platform/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.core/target/classes
> > [INFO] -
> > [ERROR] COMPILATION ERROR :
> > [INFO] -
> > [ERROR]
> >
> /data/source/branch/carbon420/platform/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.core/src/main/java/org/wso2/carbon/automation/core/utils/ArtifactDeployerUtil.java:[691,42]
> > unreported exception java.lang.Exception; must be caught or declared to
> be
> > thrown
> > [INFO] 1 error
> > [INFO] -
> > [INFO]
> > 
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] WSO2 Carbon Automation - Parent core project .. SUCCESS
> [0.383s]
> > [INFO] WSO2 Carbon Automation - Test API . SUCCESS
> [9.145s]
> > [INFO] WSO2 Carbon Automation - Test Core  FAILURE
> [5.275s]
> > [INFO] WSO2 Carbon Automation - Common Utils . SKIPPED
> > [INFO] WSO2 Carbon Automation - Jmeter Test Runner ... SKIPPED
> > [INFO]
> > 
> > [INFO] BUILD FAILURE
> >
> >
> > Thanks,
> > Hasitha.
> >
> >
> >
> >
> > --
> > Hasitha Aravinda,
> > Software Engineer,
> > WSO2 Inc.
> > Email: hasi...@wso2.com
> > Mobile: +94 71 8 210 200
> >
>
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>



-- 
Hasitha Aravinda,
Software Engineer,
WSO2 Inc.
Email: hasi...@wso2.com
Mobile: +94 71 8 210 200
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Event Builder JSON Builder - Default Value, use????

[Lasantha Fernando]

Hi Andres,

The default value is triggered if the attribute comes with the event and a
null value or some exception occurs when processing that particular
attribute.

The default value will not be sent if the attribute itself is not there in
the event.

Thanks,
Lasantha


On 4 November 2013 00:04, andresgomez92  wrote:

> Hi all,
>
> I have a question about the field "Default Value" on the Event Builder.
>
> I think the following:
>
> If I receive an event like this:
>
> *{"Nombre":"Andres", "Dinero"10, "Other":"100}
> *
> and I use this:
>
> 
>
> When the event leaves the event builder, I have this:
>
> *[Andres 10]
> *
> Now, If I receive an event like this:
>
> *{"Nombre":"Andres", "Other":100}
> *
> When the event leaves the event builder, I have this:
>
> *[Andres]
> *
>
> But I expected to get this:
>
> *[Andres 0]
> *
>
> Since the field "Default Value" to "Dinero" is 0.
>
> Do not operate in this manner? Could I do it in any way?
>
> Regards,
>
> Andrés Gómez
>
>
>
> --
> View this message in context:
> http://wso2-oxygen-tank.10903.n7.nabble.com/Event-Builder-JSON-Builder-Default-Value-use-tp87986.html
> Sent from the WSO2 Development mailing list archive at Nabble.com.
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
*Lasantha Fernando*
Software Engineer - Data Technologies Team
WSO2 Inc. http://wso2.com

email: lasan...@wso2.com
mobile: (+94) 71 5247551
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Callout mediator (Axis2 sendRobust method) wraps the request sent out with a soap envelope

[Nirmal Fernando]

That didn't work Isuru. Axis2 still wraps the message with a soap envelope.


On Sun, Nov 3, 2013 at 10:11 PM, Isuru Udana  wrote:

> Try setting the following property for ESB 4.7.0 or previous versions.
>  value="true"/>
>
> Make sure to set "enableREST" to false after the Callout mediator.
>
>
>
>
> On Sun, Nov 3, 2013 at 11:37 AM, Isuru Udana  wrote:
>
>> Hi Nirmal,
>>
>> In ESB 4.8.0, you can do this by setting the messageType to
>> application/xml.
>> However IFAIK in previous versions that method won't work.
>>
>>
>> On Sun, Nov 3, 2013 at 2:44 AM, Nirmal Fernando  wrote:
>>
>>> Hi All,
>>>
>>> $Subject. How can I avoid this?
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>
>>
>> --
>> *Isuru Udana*
>>  Senior
>> * Software Engineer*
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>> twitter: http://twitter.com/isudana
>>
>
>
>
> --
> *Isuru Udana*
> Senior
> * Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
> twitter: http://twitter.com/isudana
>



-- 

Thanks & regards,
Nirmal

Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev