from:"Andun Sameera"

Re: [Dev] XACML based Axis2 Entitlement Handler and Authentication Filter for Webapp security

2012-11-28 Thread Andun Sameera

Hi Thilini,

I had a offline chat with Senaka. What he want is check the overhead added
by the the authentication mechanism. Basically we have to check the number
of requests handled by the Web App with authentication filter enabled and
without.

Thanks
AndunSLG

On Sat, Nov 24, 2012 at 6:23 PM, Senaka Fernando  wrote:

> Hi all,
>
> What are the performance numbers with and without this? I'd like to know
> the overhead this is going to introduce.
>
> Thanks,
> Senaka.
>
>
> On Sat, Nov 24, 2012 at 5:20 PM, Sagara Gunathunga wrote:
>
>> On Sat, Nov 24, 2012 at 2:20 PM, Johann Nallathamby 
>> wrote:
>> > Hi Thilini,
>> >
>> > Why did you have to implement a new "Simple Authenticator" instead of
>> using
>> > the default Carbon backend authenticator? Are there any advantages or
>> > performance improvement we get by using this "Simple Authenticator"?
>>
>> Being a Wep App container AS has a requirement to enable Carbon
>> security for web apps too but default Carbon backend authenticator
>> always expects login permission  to AS.  Here each web app can have
>> their own set of users and they needed to be authenticated through
>> Carbon but they don't have any permission to login AS admin console
>> they just users of particular web app.  This is the use case for above
>> new Authenticator.
>>
>> Thanks !
>>
>> >
>> > Has this code been committed to a public location? If so can we have the
>> > location?
>> >
>> > Thanks,
>> > Johann.
>> >
>> > On Sat, Nov 24, 2012 at 1:23 PM, Thilini Shanika 
>> wrote:
>> >>
>> >> Hi all,
>> >>
>> >> An Axis2 entitlement handler and an Authentication filter were
>> implemented
>> >> and we had a code review and a demo on the implementation and samples.
>> >>
>> >> XACML based entitlement handler is to authorize web service requests
>> after
>> >> the authentication and it can be engaged to a service via engaging
>> >> implemented  'entitlement module'. The authentication filter is to
>> >> authenticate web application requests. For the filter implementation,
>> a new
>> >> feature called 'simple authenticator 'was introduced to IS to for
>> >> authentication purpose.
>> >>
>> >> During the review, we have discussed the following future improvements
>> and
>> >> changes to be applied to the entitlement handler and authentication
>> filter.
>> >>
>> >> Future Improvements and Changes
>> >>
>> >> XACML based Entitlement Handler
>> >>
>> >> Adding new improvement to Carbon UI to get XACML configuration and
>> enable
>> >> authorization per service by engaging the 'entitlement module' .
>> >> Adding new improvement to Carbon UI to enable authorization for
>> services
>> >> via engaging module globally.
>> >>
>> >>
>> >> Authentication Filter
>> >>
>> >> Simple Authenticator feature has to be integrated to IS.
>> >> Persisting authentication data to session and using them for XACML
>> based
>> >> entitlement filter.
>> >> Adding a sample web application for implemented authentication filter.
>> >>
>> >>
>> >> ___
>> >> Dev mailing list
>> >> Dev@wso2.org
>> >> http://wso2.org/cgi-bin/mailman/listinfo/dev
>> >>
>> >
>> >
>> > ___
>> > Dev mailing list
>> > Dev@wso2.org
>> > http://wso2.org/cgi-bin/mailman/listinfo/dev
>> >
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Technical Lead; WSO2, Inc.;  http://wso2.com
>> V.P Apache Web Services ;  http://ws.apache.org/
>> Blog ;  http://ssagara.blogspot.com
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> *Senaka Fernando*
> Member - Integration Technologies Management Committee;
> Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Need to clarify : Are the queries asked in the issue is possible ?

2012-11-28 Thread Andun Sameera

Hi all,

Are these customization possible in a RXT ?
https://support.wso2.com/jira/browse/WSOTWOSUPDEV-2. If possible can you
provide me a example.

Thanks
AndunSLG
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failure in org.wso2.carbon.cassandra.cluster.mgt.ui

2012-11-21 Thread Andun Sameera

Still getting $Subject.

Thanks
AndunSLG

On Mon, Nov 19, 2012 at 10:09 PM, Deependra Ariyadewa  wrote:

>
>
> On Mon, Nov 19, 2012 at 9:43 PM, Sinthuja Ragendran wrote:
>
>> Hi,
>>
>> compilation failure in org.wso2.carbon.cassandra.cluster.mgt.ui/4.0.5. I
>> believe service-stub is not updated properly.
>>
>
> We will check the issue.
>
> Thanks,
>
> Deependra.
>
>>
>> [INFO] -
>> [ERROR] COMPILATION ERROR :
>> [INFO] -
>> [ERROR]
>> /home/sinthuja/projects/backup_trunk/platform/branches/4.0.0/components/cassandra/org.wso2.carbon.cassandra.cluster.mgt.ui/4.0.5/src/main/java/org/wso2/carbon/cassandra/cluster/mgt/ui/operation/ClusterNodeOperationsAdminClient.java:[30,60]
>> cannot find symbol
>> symbol  : class ProxyKeyspaceInitialInfo
>> location: package org.wso2.carbon.cassandra.cluster.proxy.stub.data.xsd
>> [ERROR]
>> /home/sinthuja/projects/backup_trunk/platform/branches/4.0.0/components/cassandra/org.wso2.carbon.cassandra.cluster.mgt.ui/4.0.5/src/main/java/org/wso2/carbon/cassandra/cluster/mgt/ui/operation/ClusterNodeOperationsAdminClient.java:[31,60]
>> cannot find symbol
>> symbol  : class ProxyNodeInitialInfo
>> location: package org.wso2.carbon.cassandra.cluster.proxy.stub.data.xsd
>> [ERROR]
>> /home/sinthuja/projects/backup_trunk/platform/branches/4.0.0/components/cassandra/org.wso2.carbon.cassandra.cluster.mgt.ui/4.0.5/src/main/java/org/wso2/carbon/cassandra/cluster/mgt/ui/operation/ClusterNodeOperationsAdminClient.java:[371,11]
>> cannot find symbol
>> symbol  : class ProxyNodeInitialInfo
>> location: class
>> org.wso2.carbon.cassandra.cluster.mgt.ui.operation.ClusterNodeOperationsAdminClient
>> [ERROR]
>> /home/sinthuja/projects/backup_trunk/platform/branches/4.0.0/components/cassandra/org.wso2.carbon.cassandra.cluster.mgt.ui/4.0.5/src/main/java/org/wso2/carbon/cassandra/cluster/mgt/ui/operation/ClusterNodeOperationsAdminClient.java:[380,11]
>> cannot find symbol
>> symbol  : class ProxyKeyspaceInitialInfo
>> location: class
>> org.wso2.carbon.cassandra.cluster.mgt.ui.operation.ClusterNodeOperationsAdminClient
>> [ERROR]
>> /home/sinthuja/projects/backup_trunk/platform/branches/4.0.0/components/cassandra/org.wso2.carbon.cassandra.cluster.mgt.ui/4.0.5/src/main/java/org/wso2/carbon/cassandra/cluster/mgt/ui/operation/ClusterNodeOperationsAdminClient.java:[374,49]
>> cannot find symbol
>> symbol  : method getNodeInitialInfo(java.lang.String)
>> location: class
>> org.wso2.carbon.cassandra.cluster.proxy.stub.operation.ClusterOperationProxyAdminStub
>> [ERROR]
>> /home/sinthuja/projects/backup_trunk/platform/branches/4.0.0/components/cassandra/org.wso2.carbon.cassandra.cluster.mgt.ui/4.0.5/src/main/java/org/wso2/carbon/cassandra/cluster/mgt/ui/operation/ClusterNodeOperationsAdminClient.java:[383,49]
>> cannot find symbol
>> symbol  : method getKeyspaceInitialInfo(java.lang.String)
>> location: class
>> org.wso2.carbon.cassandra.cluster.proxy.stub.operation.ClusterOperationProxyAdminStub
>> [INFO] 6 errors
>> [INFO] -
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 2.799s
>> [INFO] Finished at: Mon Nov 19 21:39:26 IST 2012
>> [INFO] Final Memory: 25M/618M
>>
>> Thanks,
>> Sinthuja.
>>
>>
>
>
> --
> Deependra Ariyadewa
> WSO2, Inc. http://wso2.com/ http://wso2.org
>
> email d...@wso2.com; cell +94 71 403 5996 ;
> Blog http://risenfall.wordpress.com/
> PGP info: KeyID: 'DC627E6F'
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build Failure in Load Balancer component

2012-11-21 Thread Andun Sameera

Hi,

I have fixed this by deleting the org.wso2.carbon.lb.common folder form my
m2 repo. Then it download the correct jar form nexues.

Thanks
AndunSLG

On Thu, Nov 22, 2012 at 9:49 AM, Andun Sameera  wrote:

> Still getting $Subject.
>
> Thanks
> AndunSLG
>
> On Tue, Nov 20, 2012 at 6:18 PM, Tharindu Mathew wrote:
>
>> Hi,
>>
>> $subject!
>>
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 13.807s
>> [INFO] Finished at: Tue Nov 20 18:16:59 IST 2012
>> [INFO] Final Memory: 71M/139M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project org.wso2.carbon.autoscaler.service:
>> Compilation failure: Compilation failure:
>> [ERROR]
>> /Users/mackie/source-checkouts/carbon/platform/branches/4.0.0/components/load-balancer/autoscaler-service/org.wso2.carbon.autoscaler.service/1.0.0/src/main/java/org/wso2/carbon/autoscaler/service/util/ServiceTemplate.java:[32,44]
>> cannot find symbol
>> [ERROR] symbol  : variable DEFAULT_SUB_DOMAIN
>> [ERROR] location: class org.wso2.carbon.lb.common.conf.util.Constants
>> [ERROR]
>> /Users/mackie/source-checkouts/carbon/platform/branches/4.0.0/components/load-balancer/autoscaler-service/org.wso2.carbon.autoscaler.service/1.0.0/src/main/java/org/wso2/carbon/autoscaler/service/impl/AutoscalerServiceImpl.java:[386,37]
>> cannot find symbol
>> [ERROR] symbol  : variable DEFAULT_SUB_DOMAIN
>> [ERROR] location: class org.wso2.carbon.lb.common.conf.util.Constants
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>
>> --
>> Regards,
>>
>> Tharindu
>>
>> blog: http://mackiemathew.com/
>> M: +9459908
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build Failure in Load Balancer component

2012-11-21 Thread Andun Sameera

Still getting $Subject.

Thanks
AndunSLG

On Tue, Nov 20, 2012 at 6:18 PM, Tharindu Mathew  wrote:

> Hi,
>
> $subject!
>
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 13.807s
> [INFO] Finished at: Tue Nov 20 18:16:59 IST 2012
> [INFO] Final Memory: 71M/139M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.autoscaler.service:
> Compilation failure: Compilation failure:
> [ERROR]
> /Users/mackie/source-checkouts/carbon/platform/branches/4.0.0/components/load-balancer/autoscaler-service/org.wso2.carbon.autoscaler.service/1.0.0/src/main/java/org/wso2/carbon/autoscaler/service/util/ServiceTemplate.java:[32,44]
> cannot find symbol
> [ERROR] symbol  : variable DEFAULT_SUB_DOMAIN
> [ERROR] location: class org.wso2.carbon.lb.common.conf.util.Constants
> [ERROR]
> /Users/mackie/source-checkouts/carbon/platform/branches/4.0.0/components/load-balancer/autoscaler-service/org.wso2.carbon.autoscaler.service/1.0.0/src/main/java/org/wso2/carbon/autoscaler/service/impl/AutoscalerServiceImpl.java:[386,37]
> cannot find symbol
> [ERROR] symbol  : variable DEFAULT_SUB_DOMAIN
> [ERROR] location: class org.wso2.carbon.lb.common.conf.util.Constants
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> --
> Regards,
>
> Tharindu
>
> blog: http://mackiemathew.com/
> M: +9459908
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging StreamingXPATH + RawXSLT Mediator to ESB 4.6.0

2012-11-16 Thread Andun Sameera

Hi Dushan,

I have checked the mediator functionality. The send to a endpoint part is
working fine. But when a response come from the endpoint server, it fails
with a null pointer. Here is the exception,

[2012-11-16 20:39:27,182] ERROR - RawXSLTMediator Error creating XSLT
transformer using : transform/transform_back.xslt
org.apache.synapse.SynapseException: Cannot convert null to a StreamSource
at
org.apache.synapse.config.SynapseConfigUtils.handleException(SynapseConfigUtils.java:576)
at
org.apache.synapse.config.SynapseConfigUtils.getStreamSource(SynapseConfigUtils.java:77)
at
org.wso2.carbon.mediator.rawXSLT.RawXSLTMediator.createTemplate(RawXSLTMediator.java:198)
at
org.wso2.carbon.mediator.rawXSLT.RawXSLTMediator.mediate(RawXSLTMediator.java:138)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:70)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:114)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:227)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:417)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:160)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:191)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

This happens when it try to get the xslt style sheet from
the response message context. Please Check.

Also I think the way of taking a input stream when PT enable is working
fine. So I will configure the Streaming XPath with this.

Thanks
AndunSLG

On Fri, Nov 16, 2012 at 6:12 PM, Dushan Abeyruwan  wrote:

> HI Andun,
>   Please find the patch attachment herewith
>
> cheers
> Dushan
>
> On Fri, Nov 16, 2012 at 6:00 PM, Dushan Abeyruwan  wrote:
>
>> Hi
>>   I have integrated RAW XSLT Patch to  PT and seems its working fine !
>>   FYI : Andun Pls take the update on RAWXSLT project and synapse and run
>> the sample, let me know your feed back
>>
>> cheers
>> Dushan
>>
>>
>>
>> On Fri, Nov 16, 2012 at 3:06 PM, Dushan Abeyruwan wrote:
>>
>>> HI
>>>I'll be working to integrate XSLT patch to PT, since now we are
>>> already fix all the issues related to integration test in PT.
>>>
>>> cheers
>>> Dushan
>>>
>>>
>>> On Fri, Nov 16, 2012 at 2:21 PM, Andun Sameera  wrote:
>>>
>>>> Hi All,
>>>>
>>>> Previously StreamingXPATH , RawXSLT Mediator was build on top of Binary
>>>> Relay mode of the ESB. Since ESB is moving to the improved
>>>> PassThrough transport I have moved those two to work on top of PT.  But
>>>> there is a confusion of getting an input stream to the incoming message. I
>>>> have kept a open method to add that logic in both cases. I have added the
>>>> RawXSLT mediator as a Carbon Mediator. Also added the StreamingXPath parser
>>>> to Synapse 2.1.1.wso2v1. Following will be the Jiras for the patches.
>>>>
>>>> RawXSLT Mediator - https://wso2.org/jira/browse/CARBON-13996
>>>> Streaming XPath Parser - https://wso2.org/jira/browse/CARBON-13997
>>>>
>>>> Thanks
>>>> AndunSLG
>>>>
>>>
>>>
>>>
>>> --
>>> Dushan Abeyruwan
>>> *Senior Software Engineer*
>>> *Integration Technologies Team*
>>> *WSO2 Inc. http://wso2.com/*
>>> *Mobile:(+94)714408632*
>>>
>>>
>>
>>
>> --
>> Dushan Abeyruwan
>> *Senior Software Engineer*
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com/*
>> *Mobile:(+94)714408632*
>>
>>
>
>
> --
> Dushan Abeyruwan
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)714408632*
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Merging StreamingXPATH + RawXSLT Mediator to ESB 4.6.0

2012-11-16 Thread Andun Sameera

Hi All,

Previously StreamingXPATH , RawXSLT Mediator was build on top of Binary
Relay mode of the ESB. Since ESB is moving to the improved
PassThrough transport I have moved those two to work on top of PT.  But
there is a confusion of getting an input stream to the incoming message. I
have kept a open method to add that logic in both cases. I have added the
RawXSLT mediator as a Carbon Mediator. Also added the StreamingXPath parser
to Synapse 2.1.1.wso2v1. Following will be the Jiras for the patches.

RawXSLT Mediator - https://wso2.org/jira/browse/CARBON-13996
Streaming XPath Parser - https://wso2.org/jira/browse/CARBON-13997

Thanks
AndunSLG
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Confusion in ESB

2012-11-15 Thread Andun Sameera

Hi All,

I have solved the problem by overriding the isContentAware() function in my
mediator. This was no there before.

Thanks
AndunSLG

On Thu, Nov 15, 2012 at 10:18 PM, Andun Sameera  wrote:

> After some debugging, I have found the place where the the change of the
> message happens. In the InMediator it has the following code which does
> the change,
>
>if (contentAware) {
> try {
> RelayUtils.buildMessage(((Axis2MessageContext)
> synCtx).getAxis2MessageContext(),false);
> } catch (Exception e) {
> handleException("Error while building message", e,
> synCtx);
> }
> }
>
> Is this the default nature form 4.6.0 ?
>
> Thanks
> AndunSLG
>
> On Thu, Nov 15, 2012 at 9:17 PM, Andun Sameera  wrote:
>
>> Hi All,
>>
>> I have enabled the nio-HTTP transport + the binary relay in the 4.6.0 ESB
>> by changing the default PT transport. But I see the relay is not working.
>> So I debug the code and found that binary relay builder builds the message
>> as usual like  given below,
>>
>>
>> http://www.w3.org/2003/05/soap-envelope";>> xmlns:ns="http://ws.apache.org/commons/ns/payload
>> ">PD94bWwgdmVyc2lvbj0nMS4wJyBlbmNvZGluZz0nVVRGLTgnPz48c29hcGVudjpFbnZlbG9wZSB4bWxuczpzb2FwZW52PSJodHRwOi8vc2NoZW1hcy54bWxzb2FwLm9yZy9zb2FwL2VudmVsb3BlLyI+PHNvYXBlbnY6SGVhZGVyIHhtbG5zOndzYT0iaHR0cDovL3d3dy53My5vcmcvMjAwNS8wOC9hZGRyZXNzaW5nIj48d3NhOlRvPmh0dHA6Ly9sb2NhbGhvc3Q6OTAwMC9zZXJ2aWNlcy9TaW1wbGVTdG9ja1F1b3RlU2VydmljZTwvd3NhOlRvPjx3c2E6TWVzc2FnZUlEPnVybjp1dWlkOmVjYzQxZTJiLWE4MTEtNDA2Yi05YzcwLWJjOGRjNzYzZmNhMjwvd3NhOk1lc3NhZ2VJRD48d3NhOkFjdGlvbj51cm46Z2V0UXVvdGU8L3dzYTpBY3Rpb24+PC9zb2FwZW52OkhlYWRlcj48c29hcGVudjpCb2R5PjxtMDpDaGVja1ByaWNlUmVxdWVzdCB4bWxuczptMD0iaHR0cDovL3NlcnZpY2VzLnNhbXBsZXMiPjxtMDpDb2RlPklCTTwvbTA6Q29kZT48L20wOkNoZWNrUHJpY2VSZXF1ZXN0Pjwvc29hcGVudjpCb2R5Pjwvc29hcGVudjpFbnZlbG9wZT4=
>>
>> But when it comes to a log mediator it shows as follows.
>>
>> To : http://localhost:9000/services/SimpleStockQuoteService
>> WSAction : urn:getQuote
>> SOAPAction : urn:getQuote
>> ReplyTo : http://www.w3.org/2005/08/addressing/anonymous
>> MessageID : urn:uuid:15da20ee-6b83-4b56-9e01-a7faf28f7593
>> Headers :
>> To : http://localhost:9000/services/SimpleStockQuoteService
>>  MessageID : urn:uuid:15da20ee-6b83-4b56-9e01-a7faf28f7593
>> Action : urn:getQuote
>> Body : http://schemas.xmlsoap.org/soap/envelope/";>> xmlns:m0="http://services.samples
>> ">IBM
>>
>> What has gone wrong here ?
>>
>> Thanks
>> AndunSLG
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Confusion in ESB

2012-11-15 Thread Andun Sameera

After some debugging, I have found the place where the the change of the
message happens. In the InMediator it has the following code which does
the change,

   if (contentAware) {
try {
RelayUtils.buildMessage(((Axis2MessageContext)
synCtx).getAxis2MessageContext(),false);
} catch (Exception e) {
handleException("Error while building message", e,
synCtx);
}
}

Is this the default nature form 4.6.0 ?

Thanks
AndunSLG

On Thu, Nov 15, 2012 at 9:17 PM, Andun Sameera  wrote:

> Hi All,
>
> I have enabled the nio-HTTP transport + the binary relay in the 4.6.0 ESB
> by changing the default PT transport. But I see the relay is not working.
> So I debug the code and found that binary relay builder builds the message
> as usual like  given below,
>
>
> http://www.w3.org/2003/05/soap-envelope";> xmlns:ns="http://ws.apache.org/commons/ns/payload
> ">PD94bWwgdmVyc2lvbj0nMS4wJyBlbmNvZGluZz0nVVRGLTgnPz48c29hcGVudjpFbnZlbG9wZSB4bWxuczpzb2FwZW52PSJodHRwOi8vc2NoZW1hcy54bWxzb2FwLm9yZy9zb2FwL2VudmVsb3BlLyI+PHNvYXBlbnY6SGVhZGVyIHhtbG5zOndzYT0iaHR0cDovL3d3dy53My5vcmcvMjAwNS8wOC9hZGRyZXNzaW5nIj48d3NhOlRvPmh0dHA6Ly9sb2NhbGhvc3Q6OTAwMC9zZXJ2aWNlcy9TaW1wbGVTdG9ja1F1b3RlU2VydmljZTwvd3NhOlRvPjx3c2E6TWVzc2FnZUlEPnVybjp1dWlkOmVjYzQxZTJiLWE4MTEtNDA2Yi05YzcwLWJjOGRjNzYzZmNhMjwvd3NhOk1lc3NhZ2VJRD48d3NhOkFjdGlvbj51cm46Z2V0UXVvdGU8L3dzYTpBY3Rpb24+PC9zb2FwZW52OkhlYWRlcj48c29hcGVudjpCb2R5PjxtMDpDaGVja1ByaWNlUmVxdWVzdCB4bWxuczptMD0iaHR0cDovL3NlcnZpY2VzLnNhbXBsZXMiPjxtMDpDb2RlPklCTTwvbTA6Q29kZT48L20wOkNoZWNrUHJpY2VSZXF1ZXN0Pjwvc29hcGVudjpCb2R5Pjwvc29hcGVudjpFbnZlbG9wZT4=
>
> But when it comes to a log mediator it shows as follows.
>
> To : http://localhost:9000/services/SimpleStockQuoteService
> WSAction : urn:getQuote
> SOAPAction : urn:getQuote
> ReplyTo : http://www.w3.org/2005/08/addressing/anonymous
> MessageID : urn:uuid:15da20ee-6b83-4b56-9e01-a7faf28f7593
> Headers :
> To : http://localhost:9000/services/SimpleStockQuoteService
>  MessageID : urn:uuid:15da20ee-6b83-4b56-9e01-a7faf28f7593
> Action : urn:getQuote
> Body : http://schemas.xmlsoap.org/soap/envelope/";> xmlns:m0="http://services.samples
> ">IBM
>
> What has gone wrong here ?
>
> Thanks
> AndunSLG
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Confusion in ESB

2012-11-15 Thread Andun Sameera

Hi All,

I have enabled the nio-HTTP transport + the binary relay in the 4.6.0 ESB
by changing the default PT transport. But I see the relay is not working.
So I debug the code and found that binary relay builder builds the message
as usual like  given below,


http://www.w3.org/2003/05/soap-envelope";>http://ws.apache.org/commons/ns/payload
">PD94bWwgdmVyc2lvbj0nMS4wJyBlbmNvZGluZz0nVVRGLTgnPz48c29hcGVudjpFbnZlbG9wZSB4bWxuczpzb2FwZW52PSJodHRwOi8vc2NoZW1hcy54bWxzb2FwLm9yZy9zb2FwL2VudmVsb3BlLyI+PHNvYXBlbnY6SGVhZGVyIHhtbG5zOndzYT0iaHR0cDovL3d3dy53My5vcmcvMjAwNS8wOC9hZGRyZXNzaW5nIj48d3NhOlRvPmh0dHA6Ly9sb2NhbGhvc3Q6OTAwMC9zZXJ2aWNlcy9TaW1wbGVTdG9ja1F1b3RlU2VydmljZTwvd3NhOlRvPjx3c2E6TWVzc2FnZUlEPnVybjp1dWlkOmVjYzQxZTJiLWE4MTEtNDA2Yi05YzcwLWJjOGRjNzYzZmNhMjwvd3NhOk1lc3NhZ2VJRD48d3NhOkFjdGlvbj51cm46Z2V0UXVvdGU8L3dzYTpBY3Rpb24+PC9zb2FwZW52OkhlYWRlcj48c29hcGVudjpCb2R5PjxtMDpDaGVja1ByaWNlUmVxdWVzdCB4bWxuczptMD0iaHR0cDovL3NlcnZpY2VzLnNhbXBsZXMiPjxtMDpDb2RlPklCTTwvbTA6Q29kZT48L20wOkNoZWNrUHJpY2VSZXF1ZXN0Pjwvc29hcGVudjpCb2R5Pjwvc29hcGVudjpFbnZlbG9wZT4=

But when it comes to a log mediator it shows as follows.

To : http://localhost:9000/services/SimpleStockQuoteService
WSAction : urn:getQuote
SOAPAction : urn:getQuote
ReplyTo : http://www.w3.org/2005/08/addressing/anonymous
MessageID : urn:uuid:15da20ee-6b83-4b56-9e01-a7faf28f7593
Headers :
To : http://localhost:9000/services/SimpleStockQuoteService
MessageID : urn:uuid:15da20ee-6b83-4b56-9e01-a7faf28f7593
Action : urn:getQuote
Body : http://schemas.xmlsoap.org/soap/envelope/";>http://services.samples
">IBM

What has gone wrong here ?

Thanks
AndunSLG
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Compilation Failure at org.wso2.carbon.dataservices.core - 4.0.5

2012-11-11 Thread Andun Sameera

I think that was the problem. Thanks For the Help.



On Mon, Nov 12, 2012 at 12:17 PM, Lakmali Baminiwatta wrote:

> Hi Andun,
>
> I checked this after cleaning my 4.0.2 jars, and it got downloaded from
> the nexus repo. Jars will get downloaded from the repository only they are
> not found in your local repository.
>
> Thanks,
> Lakmali
>
>
> On 12 November 2012 12:10, Andun Sameera  wrote:
>
>> Hi,
>>
>> I have updated those two components and then manually build. Then it
>> works. I think the jar is not downloading from nexus repo.
>>
>> Thanks
>> AndunSLG
>>
>>
>> On Mon, Nov 12, 2012 at 11:59 AM, Dinusha Senanayaka wrote:
>>
>>> Hi Andun,
>>>
>>> We don't get this issue locally. Seems your data-services.common &
>>> data-services.sql.driver 4.0.2 modules are not up to date. Could you please
>>> update them and try to build or build on-line ?
>>>
>>> Regards,
>>> Dinusha.
>>>
>>>
>>> On Mon, Nov 12, 2012 at 11:29 AM, Andun Sameera  wrote:
>>>
>>>> Hi All,
>>>>
>>>> I am getting this error in the latest branch update,
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>>>> (default-compile) on project org.wso2.carbon.dataservices.core: Compilation
>>>> failure: Compilation failure:
>>>> [ERROR]
>>>> /media/Software/Carbon_SVN/platform/branches/4.0.0/components/data-services/org.wso2.carbon.dataservices.core/4.0.5/src/main/java/org/wso2/carbon/dataservices/core/description/config/TabularDataBasedConfig.java:[115,35]
>>>> cannot find symbol
>>>> [ERROR] symbol  : variable DRIVER_PROPERTIES
>>>> [ERROR] location: class
>>>> org.wso2.carbon.dataservices.sql.driver.parser.Constants
>>>> [ERROR]
>>>> /media/Software/Carbon_SVN/platform/branches/4.0.0/components/data-services/org.wso2.carbon.dataservices.core/4.0.5/src/main/java/org/wso2/carbon/dataservices/core/description/config/TabularDataBasedConfig.java:[325,32]
>>>> cannot find symbol
>>>> [ERROR] symbol  : constructor
>>>> ColumnInfo(int,java.lang.String,java.lang.String,int,int)
>>>> [ERROR] location: class
>>>> org.wso2.carbon.dataservices.sql.driver.query.ColumnInfo
>>>>
>>>>
>>>> Thanks
>>>> AndunSLG
>>>>
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Lakmali Baminiwatta*
> *
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> mobile:  +94 71 2335936
> *
> *
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Compilation Failure at org.wso2.carbon.dataservices.core - 4.0.5

2012-11-11 Thread Andun Sameera

Hi,

I have updated those two components and then manually build. Then it works.
I think the jar is not downloading from nexus repo.

Thanks
AndunSLG

On Mon, Nov 12, 2012 at 11:59 AM, Dinusha Senanayaka wrote:

> Hi Andun,
>
> We don't get this issue locally. Seems your data-services.common &
> data-services.sql.driver 4.0.2 modules are not up to date. Could you please
> update them and try to build or build on-line ?
>
> Regards,
> Dinusha.
>
>
> On Mon, Nov 12, 2012 at 11:29 AM, Andun Sameera  wrote:
>
>> Hi All,
>>
>> I am getting this error in the latest branch update,
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project org.wso2.carbon.dataservices.core: Compilation
>> failure: Compilation failure:
>> [ERROR]
>> /media/Software/Carbon_SVN/platform/branches/4.0.0/components/data-services/org.wso2.carbon.dataservices.core/4.0.5/src/main/java/org/wso2/carbon/dataservices/core/description/config/TabularDataBasedConfig.java:[115,35]
>> cannot find symbol
>> [ERROR] symbol  : variable DRIVER_PROPERTIES
>> [ERROR] location: class
>> org.wso2.carbon.dataservices.sql.driver.parser.Constants
>> [ERROR]
>> /media/Software/Carbon_SVN/platform/branches/4.0.0/components/data-services/org.wso2.carbon.dataservices.core/4.0.5/src/main/java/org/wso2/carbon/dataservices/core/description/config/TabularDataBasedConfig.java:[325,32]
>> cannot find symbol
>> [ERROR] symbol  : constructor
>> ColumnInfo(int,java.lang.String,java.lang.String,int,int)
>> [ERROR] location: class
>> org.wso2.carbon.dataservices.sql.driver.query.ColumnInfo
>>
>>
>> Thanks
>> AndunSLG
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Compilation Failure at org.wso2.carbon.dataservices.core - 4.0.5

2012-11-11 Thread Andun Sameera

Hi All,

I am getting this error in the latest branch update,

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.dataservices.core: Compilation
failure: Compilation failure:
[ERROR]
/media/Software/Carbon_SVN/platform/branches/4.0.0/components/data-services/org.wso2.carbon.dataservices.core/4.0.5/src/main/java/org/wso2/carbon/dataservices/core/description/config/TabularDataBasedConfig.java:[115,35]
cannot find symbol
[ERROR] symbol  : variable DRIVER_PROPERTIES
[ERROR] location: class
org.wso2.carbon.dataservices.sql.driver.parser.Constants
[ERROR]
/media/Software/Carbon_SVN/platform/branches/4.0.0/components/data-services/org.wso2.carbon.dataservices.core/4.0.5/src/main/java/org/wso2/carbon/dataservices/core/description/config/TabularDataBasedConfig.java:[325,32]
cannot find symbol
[ERROR] symbol  : constructor
ColumnInfo(int,java.lang.String,java.lang.String,int,int)
[ERROR] location: class
org.wso2.carbon.dataservices.sql.driver.query.ColumnInfo


Thanks
AndunSLG
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] org.wso2.carbon.identity.entitlement.proxy build failure

2012-10-01 Thread Andun Sameera

Thanks Dileepa It is Fixed Now,

On Tue, Oct 2, 2012 at 11:13 AM, Dileepa Jayakody  wrote:

> Hi Andun,
>
> The balana jars have been deployed and Dhanushka synched the nexus repos.
> You can try building it now.
>
> Thanks,
> Dileepa
>
>
> On Tue, Oct 2, 2012 at 10:56 AM, Andun Sameera  wrote:
>
>> Hi,
>>
>> This happens because the org.wso2.balana-1.0.0-wso2v2.jar is not deployed
>> in the wso2 nexus repo due to a build failure in the balana it self.
>> Dileepa has fixed that and deployed the jar in to nexus. You can fix this
>> problem in a while.
>>
>> Thank
>> AndunSLG
>>
>> On Tue, Oct 2, 2012 at 9:42 AM, Lakmali Baminiwatta wrote:
>>
>>> *
>>> *
>>> Hi,
>>>
>>> Following error is thrown when building
>>> org.wso2.carbon.identity.entitlement.proxy in a clean repo.
>>>
>>> [ERROR] Failed to execute goal on project
>>> org.wso2.carbon.identity.entitlement.proxy: Could not resolve dependencies
>>> for project
>>> org.wso2.carbon:org.wso2.carbon.identity.entitlement.proxy:bundle:4.0.2:
>>> Failure to find org.wso2.balana:org.wso2.balana:jar:1.0.0-wso2v2 in
>>> http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in
>>> the local repository, resolution will not be reattempted until the update
>>> interval of wso2-nexus has elapsed or updates are forced
>>>
>>> Please have a look.
>>>
>>> Thanks,
>>> Lakmali
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Dileepa Jayakody,
> Software Engineer, WSO2 Inc.
> Lean . Enterprise . Middleware
>
> Mobile : +94777-857616
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] org.wso2.carbon.identity.entitlement.proxy build failure

2012-10-01 Thread Andun Sameera

Hi,

This happens because the org.wso2.balana-1.0.0-wso2v2.jar is not deployed
in the wso2 nexus repo due to a build failure in the balana it self.
Dileepa has fixed that and deployed the jar in to nexus. You can fix this
problem in a while.

Thank
AndunSLG

On Tue, Oct 2, 2012 at 9:42 AM, Lakmali Baminiwatta wrote:

> *
> *
> Hi,
>
> Following error is thrown when building
> org.wso2.carbon.identity.entitlement.proxy in a clean repo.
>
> [ERROR] Failed to execute goal on project
> org.wso2.carbon.identity.entitlement.proxy: Could not resolve dependencies
> for project
> org.wso2.carbon:org.wso2.carbon.identity.entitlement.proxy:bundle:4.0.2:
> Failure to find org.wso2.balana:org.wso2.balana:jar:1.0.0-wso2v2 in
> http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
> local repository, resolution will not be reattempted until the update
> interval of wso2-nexus has elapsed or updates are forced
>
> Please have a look.
>
> Thanks,
> Lakmali
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB

2012-09-17 Thread Andun Sameera

Hi Amila,

Agree with you, I did with this way because I ran all these in my PC for
have an abstract idea. No perf testing environment was setup. But will do
a exact test with the XPATH optimization changes.

Thanks
AndunSLG


On Mon, Sep 17, 2012 at 6:38 PM, Amila Suriarachchi  wrote:

>
>
> On Mon, Sep 17, 2012 at 6:11 PM, Andun Sameera  wrote:
>
>> Hi All,
>>
>> I have developed the custom mediator AKA RawXSLTMediator to transform
>> streams in binary relay mood. Samisa suggested some further improvements
>> after looking at the code and currently I am working on those. With the
>> existing implementation I did some test with ESB. The results of those
>> tests are given below. For large message sizes, it has
>> improved nearly twice.
>>
>
> great.
>
> BTW did you warm up the server before taking the readings. For lower
> concurrencies you are not sending enough messages. Better to vary both
> concurrency and messags so that total would be around 50,000.
>
> thanks,
> Amila.
>
>>
>> 8k Message Raw XSLT Mediator Normal XSLT Mediator
>>
>> Request Per Second Time Taken Request Per Second Time Taken
>>
>> n=100, c=1 55.97 1.786816 55.89 1.789259
>> n=100, c=5 295.55 1.691735 158.39 3.156814
>> n=100, c=10 298.41 3.351045 162.28 6.162070
>> n=100, c=20 177.38 11.275533 168.38 11.877941
>> n=100, c=40 226.15 17.687198 170.03 23.524984
>> n=100, c=80 187.01 42.778756 165.54 48.325473
>> n=100, c=160 168.49 94.962065 165.00 96.969543
>> n=100, c=320 169.63 188.643735 164.23 194.848353
>> n=100, c=640 165.60 386.484129 122.07 524.308358
>>
>> 100k Message  Raw XSLT Mediator Normal XSLT Mediator
>>
>>  Reuest Per Second Time Taken Request Per Second Time Taken
>> n=100, c=1 49.85 2.005901 12.48 8.012235
>> n=100, c=5 233.87 2.137914 105.34 4.746719
>> n=100, c=10 297.86 3.357259 135.02 7.406090
>> n=100, c=20 294.79 6.784513 159.66 12.526382
>> n=100, c=40 263.21 15.196750 177.38 22.550458
>> n=100, c=80 228.47 35.015699 154.64 51.731678
>> n=100, c=160 230.33 69.465916 132.66 120.606647
>> n=100, c=320 232.24 137.787760 119.52 267.728523
>> n=100, c=640 243.97 262.322362 122.07 524.308358
>>
>> Thanks
>> AndunSLG
>>
>> On Sun, Sep 16, 2012 at 3:13 PM, Paul Fremantle  wrote:
>>
>>> Also presumably this approach would work very simply if someone didn't
>>> use SOAP but simply wanted to transform Plain Ole XML.
>>>
>>> Paul
>>>
>>> On 16 September 2012 09:37, Andun Sameera  wrote:
>>>
>>>> Hi,
>>>>
>>>> +1 For the idea about
>>>> the trade-off between Performance and Flexibility. This will solve
>>>> the problem I think. Because here I used a XSLT which will transform and
>>>> give a element of the message. So If we give the responsibility to the
>>>> person who write the transformation to preserve the SOAP message, It will
>>>> solve all the issues.
>>>> Also will try to find a way to  write a extension which will give some
>>>> more flexibility to user.
>>>>
>>>> Thanks
>>>> AndunSLG
>>>>
>>>>
>>>> On Sun, Sep 16, 2012 at 12:45 PM, Sanjiva Weerawarana >>> > wrote:
>>>>
>>>>> IIRC the old xslt mediator had a "source" parameter to indicate what
>>>>> should be sent in. Without that, its correct that we send in the entire
>>>>> message - if its SOAP its the whole envelope etc.. If the transform should
>>>>> produce a SOAP message that's up to the person to generate it.
>>>>>
>>>>> So IMO we should call this new high perf XSLT mediator a "raw xslt"
>>>>> mediator or something like that and make clear what the responsibility of
>>>>> the person writing the transform is.
>>>>>
>>>>> We could also (later) write an extension that supports a few source
>>>>> parameters - e.g. "body" and then do some byte level parsing (a very basic
>>>>> xml parser) that strips out the other stuff and passes the body thru.
>>>>>
>>>>> IMO we don't need that - we have a high perf one that requires you to
>>>>> process the whole message and we have the current one which gives you a 
>>>>> lot
>>>>> more flexibility at a performance tradeoff.
>>>>>
>>>>> So in other words, lets finish this and ship it!
>>>

Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB

2012-09-17 Thread Andun Sameera

Hi All,

I have developed the custom mediator AKA RawXSLTMediator to transform
streams in binary relay mood. Samisa suggested some further improvements
after looking at the code and currently I am working on those. With the
existing implementation I did some test with ESB. The results of those
tests are given below. For large message sizes, it has
improved nearly twice.

8k Message Raw XSLT Mediator Normal XSLT Mediator

Request Per Second Time Taken Request Per Second Time Taken

n=100, c=1 55.97 1.786816 55.89 1.789259
n=100, c=5 295.55 1.691735 158.39 3.156814
n=100, c=10 298.41 3.351045 162.28 6.162070
n=100, c=20 177.38 11.275533 168.38 11.877941
n=100, c=40 226.15 17.687198 170.03 23.524984
n=100, c=80 187.01 42.778756 165.54 48.325473
n=100, c=160 168.49 94.962065 165.00 96.969543
n=100, c=320 169.63 188.643735 164.23 194.848353
n=100, c=640 165.60 386.484129 122.07 524.308358

100k Message  Raw XSLT Mediator Normal XSLT Mediator

Reuest Per Second Time Taken Request Per Second Time Taken
n=100, c=1 49.85 2.005901 12.48 8.012235
n=100, c=5 233.87 2.137914 105.34 4.746719
n=100, c=10 297.86 3.357259 135.02 7.406090
n=100, c=20 294.79 6.784513 159.66 12.526382
n=100, c=40 263.21 15.196750 177.38 22.550458
n=100, c=80 228.47 35.015699 154.64 51.731678
n=100, c=160 230.33 69.465916 132.66 120.606647
n=100, c=320 232.24 137.787760 119.52 267.728523
n=100, c=640 243.97 262.322362 122.07 524.308358

Thanks
AndunSLG

On Sun, Sep 16, 2012 at 3:13 PM, Paul Fremantle  wrote:

> Also presumably this approach would work very simply if someone didn't use
> SOAP but simply wanted to transform Plain Ole XML.
>
> Paul
>
> On 16 September 2012 09:37, Andun Sameera  wrote:
>
>> Hi,
>>
>> +1 For the idea about the trade-off between Performance and Flexibility.
>> This will solve the problem I think. Because here I used a XSLT which
>> will transform and give a element of the message. So If we give the
>> responsibility to the person who write the transformation to preserve the
>> SOAP message, It will solve all the issues.
>> Also will try to find a way to  write a extension which will give some
>> more flexibility to user.
>>
>> Thanks
>> AndunSLG
>>
>>
>> On Sun, Sep 16, 2012 at 12:45 PM, Sanjiva Weerawarana 
>> wrote:
>>
>>> IIRC the old xslt mediator had a "source" parameter to indicate what
>>> should be sent in. Without that, its correct that we send in the entire
>>> message - if its SOAP its the whole envelope etc.. If the transform should
>>> produce a SOAP message that's up to the person to generate it.
>>>
>>> So IMO we should call this new high perf XSLT mediator a "raw xslt"
>>> mediator or something like that and make clear what the responsibility of
>>> the person writing the transform is.
>>>
>>> We could also (later) write an extension that supports a few source
>>> parameters - e.g. "body" and then do some byte level parsing (a very basic
>>> xml parser) that strips out the other stuff and passes the body thru.
>>>
>>> IMO we don't need that - we have a high perf one that requires you to
>>> process the whole message and we have the current one which gives you a lot
>>> more flexibility at a performance tradeoff.
>>>
>>> So in other words, lets finish this and ship it!
>>>
>>> Sanjiva.
>>>
>>> On Sun, Sep 16, 2012 at 10:35 AM, Andun Sameera  wrote:
>>>
>>>>
>>>>
>>>> On Sun, Sep 16, 2012 at 5:50 AM, Hiranya Jayathilaka <
>>>> hiranya...@gmail.com> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Sat, Sep 15, 2012 at 5:19 PM, Hiranya Jayathilaka <
>>>>> hiranya...@gmail.com> wrote:
>>>>>
>>>>>> I don't know for sure whether this problem can be solved. But
>>>>>> sometime back I wrote a custom mediator to do XSLT transformations using
>>>>>> the StAX support available in the Java TrAX API. It showed a fairly good
>>>>>> performance improvement against the existing implementation too.
>>>>>>
>>>>>> Solving the problem mentioned in this thread will be pretty hard.
>>>>>> Perhaps we can relax the conditions a bit. We can wrap the output of the
>>>>>> transformation in a SOAP envelope and put that back in the data handler. 
>>>>>> We
>>>>>> will use
>>>>>>
>>>>>
>>>>> s/use/loose/
>>>>>
>>>>>
>>>>>> any

Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB

2012-09-16 Thread Andun Sameera

Hi,

+1 For the idea about the trade-off between Performance and Flexibility.
This will solve the problem I think. Because here I used a XSLT which
will transform and give a element of the message. So If we give the
responsibility to the person who write the transformation to preserve the
SOAP message, It will solve all the issues.
Also will try to find a way to  write a extension which will give some more
flexibility to user.

Thanks
AndunSLG

On Sun, Sep 16, 2012 at 12:45 PM, Sanjiva Weerawarana wrote:

> IIRC the old xslt mediator had a "source" parameter to indicate what
> should be sent in. Without that, its correct that we send in the entire
> message - if its SOAP its the whole envelope etc.. If the transform should
> produce a SOAP message that's up to the person to generate it.
>
> So IMO we should call this new high perf XSLT mediator a "raw xslt"
> mediator or something like that and make clear what the responsibility of
> the person writing the transform is.
>
> We could also (later) write an extension that supports a few source
> parameters - e.g. "body" and then do some byte level parsing (a very basic
> xml parser) that strips out the other stuff and passes the body thru.
>
> IMO we don't need that - we have a high perf one that requires you to
> process the whole message and we have the current one which gives you a lot
> more flexibility at a performance tradeoff.
>
> So in other words, lets finish this and ship it!
>
> Sanjiva.
>
> On Sun, Sep 16, 2012 at 10:35 AM, Andun Sameera  wrote:
>
>>
>>
>> On Sun, Sep 16, 2012 at 5:50 AM, Hiranya Jayathilaka <
>> hiranya...@gmail.com> wrote:
>>
>>>
>>>
>>> On Sat, Sep 15, 2012 at 5:19 PM, Hiranya Jayathilaka <
>>> hiranya...@gmail.com> wrote:
>>>
>>>> I don't know for sure whether this problem can be solved. But sometime
>>>> back I wrote a custom mediator to do XSLT transformations using the StAX
>>>> support available in the Java TrAX API. It showed a fairly good performance
>>>> improvement against the existing implementation too.
>>>>
>>>> Solving the problem mentioned in this thread will be pretty hard.
>>>> Perhaps we can relax the conditions a bit. We can wrap the output of the
>>>> transformation in a SOAP envelope and put that back in the data handler. We
>>>> will use
>>>>
>>>
>>> s/use/loose/
>>>
>>>
>>>> any information in the original SOAP headers, but that won't be an
>>>> issue for most practical scenarios.
>>>>
>>>
>> Hi Hiranya,
>>
>> Your argument is correct Hirnaya. But I am also blocked while doing "wrap
>> the output of the transformation in a SOAP envelope", because I don't know
>> which part of the message is transformed. I blindly pass the input
>> stream to transformer, because of the requirement of avoid opening the
>> input stream using AXIOM. So without knowing which part of the message
>> is transformed and given back, how can I find the place to replace in the
>> newly created SOAP envelop. Sometimes it can be Envelop,Body, element etc.
>> So any solution ?
>>
>> Thanks
>> AndunSLG
>>
>>
>>>> Thanks,
>>>> Hiranya
>>>>
>>>> On Sat, Sep 15, 2012 at 9:23 AM, Andun Sameera  wrote:
>>>>
>>>>> Hi Amila,
>>>>>
>>>>> On Sat, Sep 15, 2012 at 9:22 PM, Amila Suriarachchi wrote:
>>>>>
>>>>>> Does xslt engine supports xml stream level transformations?
>>>>>
>>>>>
>>>>> Yes. But not 100% streams, but we can transform StreamSource object to
>>>>> a StreamResult using the Transformer.
>>>>>
>>>>>
>>>>>> After xslt transformations users may want to do further processing
>>>>>> with the message. So in that case we can avoid building request Axiom
>>>>>> object but may required to create the transformed Axiom object.
>>>>>>
>>>>>
>>>>> Yes your argument is correct, sometimes we have to create the result
>>>>> message. But I got in to trouble even before. In the present scenario, 
>>>>> XSLT
>>>>> mediator  read some parameters from the request using AXIOM. It read
>>>>> weather transformation is happening to SOAP body or SOAP envelop etc. 
>>>>> Based
>>>>> on those parameters after the transformation mediator refor

Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB

2012-09-15 Thread Andun Sameera

On Sun, Sep 16, 2012 at 5:50 AM, Hiranya Jayathilaka
wrote:

>
>
> On Sat, Sep 15, 2012 at 5:19 PM, Hiranya Jayathilaka  > wrote:
>
>> I don't know for sure whether this problem can be solved. But sometime
>> back I wrote a custom mediator to do XSLT transformations using the StAX
>> support available in the Java TrAX API. It showed a fairly good performance
>> improvement against the existing implementation too.
>>
>> Solving the problem mentioned in this thread will be pretty hard. Perhaps
>> we can relax the conditions a bit. We can wrap the output of the
>> transformation in a SOAP envelope and put that back in the data handler. We
>> will use
>>
>
> s/use/loose/
>
>
>> any information in the original SOAP headers, but that won't be an issue
>> for most practical scenarios.
>>
>
Hi Hiranya,

Your argument is correct Hirnaya. But I am also blocked while doing "wrap
the output of the transformation in a SOAP envelope", because I don't know
which part of the message is transformed. I blindly pass the input
stream to transformer, because of the requirement of avoid opening the
input stream using AXIOM. So without knowing which part of the message
is transformed and given back, how can I find the place to replace in the
newly created SOAP envelop. Sometimes it can be Envelop,Body, element etc.
So any solution ?

Thanks
AndunSLG


>> Thanks,
>> Hiranya
>>
>> On Sat, Sep 15, 2012 at 9:23 AM, Andun Sameera  wrote:
>>
>>> Hi Amila,
>>>
>>> On Sat, Sep 15, 2012 at 9:22 PM, Amila Suriarachchi wrote:
>>>
>>>> Does xslt engine supports xml stream level transformations?
>>>
>>>
>>> Yes. But not 100% streams, but we can transform StreamSource object to
>>> a StreamResult using the Transformer.
>>>
>>>
>>>> After xslt transformations users may want to do further processing with
>>>> the message. So in that case we can avoid building request Axiom object but
>>>> may required to create the transformed Axiom object.
>>>>
>>>
>>> Yes your argument is correct, sometimes we have to create the result
>>> message. But I got in to trouble even before. In the present scenario, XSLT
>>> mediator  read some parameters from the request using AXIOM. It read
>>> weather transformation is happening to SOAP body or SOAP envelop etc. Based
>>> on those parameters after the transformation mediator reform the message.
>>> You can fine that logic in 
>>> [1]<http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.0.0/dependencies/synapse/2.1.0-wso2v7/modules/core/src/main/java/org/apache/synapse/mediators/transform/XSLTMediator.java?view=markup>
>>> .
>>>
>>> But here I have no such parameters, I have only a input stream and
>>> I transform it using the XSLT file. After transformation I have no clue
>>> to reform the message. What I do is set the output stream to
>>> the data-handler in binary relay dummy message. So some parts of the
>>> original message get dropped and everything crashes here after.
>>>
>>>
>>>> thanks,
>>>> Amila.
>>>>
>>>>
>>>> On Sat, Sep 15, 2012 at 4:16 PM, Andun Sameera  wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> My requirement is $Subject. Purpose of this is avoid using AXIOM to to
>>>>> XSLT transformation. Our plan was to do all the transformation using 
>>>>> Input,
>>>>> Output Streams. javax.xml.transform.Transformer is used to do
>>>>> the transformation using streams. I developed the mediator using
>>>>> the following logic,
>>>>>
>>>>>
>>>>>- In the Binary Relay We get the Message as a Data Handler in a
>>>>>Dummy SOAP Message. From that we can get a Input Stream for the SOAP
>>>>>message which needs to be transformed using XSLT.
>>>>>- We can Get the input Stream for the XSLT file, which is in
>>>>>registry or local.
>>>>>- Using those two we can do the XSLT transformation. As a result
>>>>>we get a stream for the transformed SOAP message.
>>>>>- Finally I create a DataHandler using the stream and attached it
>>>>>to the Relay's Dummy SOAP message replacing existing one.
>>>>>
>>>>> The output of the mediator follows this logic is given below. I used
>>>>> the Sample 
>>>>> 8<http://wso2.o

Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB

2012-09-15 Thread Andun Sameera

Hi Amila,

On Sat, Sep 15, 2012 at 9:22 PM, Amila Suriarachchi  wrote:

> Does xslt engine supports xml stream level transformations?


Yes. But not 100% streams, but we can transform StreamSource object to
a StreamResult using the Transformer.


> After xslt transformations users may want to do further processing with
> the message. So in that case we can avoid building request Axiom object but
> may required to create the transformed Axiom object.
>

Yes your argument is correct, sometimes we have to create the result
message. But I got in to trouble even before. In the present scenario, XSLT
mediator  read some parameters from the request using AXIOM. It read
weather transformation is happening to SOAP body or SOAP envelop etc. Based
on those parameters after the transformation mediator reform the message.
You can fine that logic in
[1]<http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.0.0/dependencies/synapse/2.1.0-wso2v7/modules/core/src/main/java/org/apache/synapse/mediators/transform/XSLTMediator.java?view=markup>
.

But here I have no such parameters, I have only a input stream and
I transform it using the XSLT file. After transformation I have no clue
to reform the message. What I do is set the output stream to
the data-handler in binary relay dummy message. So some parts of the
original message get dropped and everything crashes here after.


> thanks,
> Amila.
>
>
> On Sat, Sep 15, 2012 at 4:16 PM, Andun Sameera  wrote:
>
>> Hi All,
>>
>> My requirement is $Subject. Purpose of this is avoid using AXIOM to to
>> XSLT transformation. Our plan was to do all the transformation using Input,
>> Output Streams. javax.xml.transform.Transformer is used to do
>> the transformation using streams. I developed the mediator using
>> the following logic,
>>
>>
>>- In the Binary Relay We get the Message as a Data Handler in a Dummy
>>SOAP Message. From that we can get a Input Stream for the SOAP message
>>which needs to be transformed using XSLT.
>>- We can Get the input Stream for the XSLT file, which is in registry
>>or local.
>>- Using those two we can do the XSLT transformation. As a result we
>>get a stream for the transformed SOAP message.
>>- Finally I create a DataHandler using the stream and attached it to
>>the Relay's Dummy SOAP message replacing existing one.
>>
>> The output of the mediator follows this logic is given below. I used the 
>> Sample
>> 8<http://wso2.org/project/esb/java/4.0.3/docs/samples/message_mediation_samples.html#Sample8>of
>>  ESB. I replaced the XSLT mediator with my custom mediator in the Binary
>> Relay.
>> But there is a major problem here. Because of the logic we used the
>> original SOAP message,
>>
>> http://schemas.xmlsoap.org/soap/envelope/";>http://www.w3.org/2005/08/addressing";>
>> http://localhost:9000/services/SimpleStockQuoteServiceurn:uuid:0f7403b4-c5bc-4347-8921-562f2736a2aburn:getQuote> xmlns:m0="http://services.samples
>> ">IBM
>>
>>  is now converted to.
>>
>> http://services.samples";>
>>
>>   IBM
>>
>> 
>>
>> At the end Binary Relay Formatter will read the DataHandler and above
>> SOAP message will be sent to the AXIS2 Server and It will crash, because
>> this is not a valid SOAP message.
>> This problem occurs because we are not using AXIOM anymore. In the normal
>> XSLT mediator it uses org.apache.synapse.util.xpath.SourceXPathSupport
>> class to find the part of the message which transformed using XSLT. So it
>> can replace the transformed part of the original message. But here we cant
>> use that kind of a logic. Because we use only streams. We cant build
>> OMElements or etc.
>>
>> Need help to solve this problem. The custom mediator java files are
>> attached here.
>>
>> Thanks
>> AndunSLG
>>
>> References :
>>
>> [1] -
>> http://wso2.org/project/esb/java/4.0.3/docs/samples/message_mediation_samples.html#Sample8
>>
>>
>> Console Output for the Custom Mediator :
>>
>> .Original SOAP Envelop..
>> http://www.w3.org/2003/05/soap-envelope";>> xmlns:ns="http://ws.apache.org/commons/ns/payload
>> ">PD94bWwgdmVyc2lvbj0nMS4wJyBlbmNvZGluZz0nVVRGLTgnPz48c29hcGVudjpFbnZlbG9wZSB4bWxuczpzb2FwZW52PSJodHRwOi8vc2NoZW1hcy54bWxzb2FwLm9yZy9zb2FwL2VudmVsb3BlLyI+PHNvYXBlbnY6SGVhZGVyIHhtbG5zOndzYT0iaHR0cDovL3d3dy53My5vcmcvMjAwNS8wOC9hZGRyZXNzaW5nIj48d3NhOlRvPmh0dHA6Ly9sb2NhbGhvc3Q6OTAwMC9zZXJ2aWNlcy9TaW1wbGVTdG9ja1F1b3RlU2VydmljZTwvd3NhOlRvPj

[Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB

2012-09-15 Thread Andun Sameera

Hi All,

My requirement is $Subject. Purpose of this is avoid using AXIOM to to XSLT
transformation. Our plan was to do all the transformation using Input,
Output Streams. javax.xml.transform.Transformer is used to do
the transformation using streams. I developed the mediator using
the following logic,

- In the Binary Relay We get the Message as a Data Handler in a Dummy
SOAP Message. From that we can get a Input Stream for the SOAP message
which needs to be transformed using XSLT.
- We can Get the input Stream for the XSLT file, which is in registry or
local.
- Using those two we can do the XSLT transformation. As a result we get
a stream for the transformed SOAP message.
- Finally I create a DataHandler using the stream and attached it to the
Relay's Dummy SOAP message replacing existing one.

The output of the mediator follows this logic is given below. I used the Sample
8of
ESB. I replaced the XSLT mediator with my custom mediator in the
Binary
Relay.
But there is a major problem here. Because of the logic we used the
original SOAP message,

http://schemas.xmlsoap.org/soap/envelope/";>http://www.w3.org/2005/08/addressing";>
http://localhost:9000/services/SimpleStockQuoteServiceurn:uuid:0f7403b4-c5bc-4347-8921-562f2736a2aburn:getQuotehttp://services.samples
">IBM

is now converted to.

http://services.samples";>

IBM

At the end Binary Relay Formatter will read the DataHandler and above SOAP
message will be sent to the AXIS2 Server and It will crash, because this is
not a valid SOAP message.
This problem occurs because we are not using AXIOM anymore. In the normal
XSLT mediator it uses org.apache.synapse.util.xpath.SourceXPathSupport
class to find the part of the message which transformed using XSLT. So it
can replace the transformed part of the original message. But here we cant
use that kind of a logic. Because we use only streams. We cant build
OMElements or etc.

Need help to solve this problem. The custom mediator java files are
attached here.

Thanks
AndunSLG

References :

[1] -
http://wso2.org/project/esb/java/4.0.3/docs/samples/message_mediation_samples.html#Sample8

Console Output for the Custom Mediator :

.Original SOAP Envelop..
http://www.w3.org/2003/05/soap-envelope";>http://ws.apache.org/commons/ns/payload
">PD94bWwgdmVyc2lvbj0nMS4wJyBlbmNvZGluZz0nVVRGLTgnPz48c29hcGVudjpFbnZlbG9wZSB4bWxuczpzb2FwZW52PSJodHRwOi8vc2NoZW1hcy54bWxzb2FwLm9yZy9zb2FwL2VudmVsb3BlLyI+PHNvYXBlbnY6SGVhZGVyIHhtbG5zOndzYT0iaHR0cDovL3d3dy53My5vcmcvMjAwNS8wOC9hZGRyZXNzaW5nIj48d3NhOlRvPmh0dHA6Ly9sb2NhbGhvc3Q6OTAwMC9zZXJ2aWNlcy9TaW1wbGVTdG9ja1F1b3RlU2VydmljZTwvd3NhOlRvPjx3c2E6TWVzc2FnZUlEPnVybjp1dWlkOjBmNzQwM2I0LWM1YmMtNDM0Ny04OTIxLTU2MmYyNzM2YTJhYjwvd3NhOk1lc3NhZ2VJRD48d3NhOkFjdGlvbj51cm46Z2V0UXVvdGU8L3dzYTpBY3Rpb24+PC9zb2FwZW52OkhlYWRlcj48c29hcGVudjpCb2R5PjxtMDpDaGVja1ByaWNlUmVxdWVzdCB4bWxuczptMD0iaHR0cDovL3NlcnZpY2VzLnNhbXBsZXMiPjxtMDpDb2RlPklCTTwvbTA6Q29kZT48L20wOkNoZWNrUHJpY2VSZXF1ZXN0Pjwvc29hcGVudjpCb2R5Pjwvc29hcGVudjpFbnZlbG9wZT4=

.Original SOAP Message
http://schemas.xmlsoap.org/soap/envelope/";>http://www.w3.org/2005/08/addressing";>
http://localhost:9000/services/SimpleStockQuoteServiceurn:uuid:0f7403b4-c5bc-4347-8921-562f2736a2aburn:getQuotehttp://services.samples
">IBM

Transforming On Progress.

...Transformed SOAP Message...
http://services.samples";>

IBM

...Transformed SOAP Envelop..
http://www.w3.org/2003/05/soap-envelope";>http://ws.apache.org/commons/ns/payload
">PG06Z2V0UXVvdGUgeG1sbnM6bT0iaHR0cDovL3NlcnZpY2VzLnNhbXBsZXMiPgogICA8bTpyZXF1ZXN0PgogICAgICA8bTpzeW1ib2w+SUJNPC9tOnN5bWJvbD4KICAgPC9tOnJlcXVlc3Q+CjwvbTpnZXRRdW90ZT4K
..

MessageDataSource.java
Description: Binary data

MessageOMDataSource.java
Description: Binary data

XMLConvertor.java
Description: Binary data

transform.xslt
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Custom Mediator for XSLT Transformation

2012-09-14 Thread Andun Sameera

Hi All,

Miyuru has point me the fault for the previous exception I got about
addressing. So in the binary relay mood we have to add a address end point
to send the message. So doing that I have sent the message successfully to
axis2 server. But it gives some exceptions. So I look at the message sent
form ESB. The message was false.

False Message :

http://schemas.xmlsoap.org/soap/envelope/";>http://www.w3.org/2005/08/addressing";>
http://localhost:9000/services/SimpleStockQuoteService
urn:uuid:f540f7a0-e450-4901-9fb8-38424e1d4c43
urn:getQuote


http://services.samples";>
IBM
<
/soapenv:Body>


Correct Message :

http://schemas.xmlsoap.org/soap/envelope/";>http://www.w3.org/2005/08/addressing"/>

http://services.samples";>
   
  IBM
   




I think the problem here is the binary relay formatter drops the newly
added child of the SOAP body. So what will be the solution ?

Thanks
AndunSLG




On Fri, Sep 14, 2012 at 5:44 PM, Andun Sameera  wrote:

> Here is the Syanpse Config I used,
>
> 
> http://ws.apache.org/ns/synapse";>
> 
> file:repository/samples/resources/
> eter>
> 15000
> 
> 
> src="file:repository/samples/resources/transform/transform.xslt"/>
> 
> 
> 
>  expression="get-property('ERROR_CODE')"/>
>  expression="get-property('ERROR_MESSAGE')"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> Thanks
> AndunSLG
>
>  On Fri, Sep 14, 2012 at 5:40 PM, Andun Sameera  wrote:
>
>> Hi Samisa,
>>
>> I have changed the Mediator code as you requested.
>>
>>- I have created a implementation  OMDataSource interface in
>>MessageOMDataSource class.
>>- Then I created a OMElement using that OMDataSource.
>>- After that I have attached the newly created element as a child for
>>the SOAP Body of the Synpase Message Context.
>>
>> The changed function which writes the transformed stream for the message
>> context is given bellow,
>>
>> private boolean writeResult(MessageContext synCtx) throws IOException,
>> XMLStreamException {
>>
>> SOAPFactory factory = OMAbstractFactory.getSOAP12Factory();
>> SOAPEnvelope env = synCtx.getEnvelope();
>>
>> if (resulMessage != null) {
>> XMLStreamReader reader =
>> StAXUtils.createXMLStreamReader(resulMessage.getInputStream());
>> StAXOMBuilder sb=new StAXOMBuilder(reader);
>> System.out.println("Transformed Stream");
>> System.out.println(sb.getDocumentElement());
>> System.out.println("..");
>>
>> OMDataSource omDataSource=new
>> MessageOMDataSource(resulMessage.getOverflowBlob());
>> OMElement omEle =
>> factory.createOMElement(omDataSource,sb.getDocumentElement().getQName());
>> synCtx.setDoingMTOM(false);
>> env.getBody().addChild(omEle);
>>
>> System.out.println("Child Added Body..");
>> System.out.println(env);
>> System.out.println("..");
>> return true;
>> }
>> return false;
>> }
>>
>> But while doing that I faced following difficulties.
>>
>>- When I create the OMElment using the stream I have pass the name
>>space of the element to the factory. For that I have to read the Stream. 
>> Is
>>it OK?
>>- Also Message is not send to the endpoint as expected, Server
>>Console Shows the following Logs,
>>
>> Transforming On Progress.
>> Transformed Stream
>> http://services.samples";>
>>
>>   IBM
>>
>> 
>> ..
>> Child Added Body..
>> http://www.w3.org/2003/05/soap-envelope";>> xmlns:ns="http://ws.apache.org/commons/ns/payload";>PD94bWwgdmVyc2lvbj0nMS4wJyBlbmNvZGluZz0nVVRGLTgnPz48c29hcGVudjpFbnZlbG9wZSB4bWxuczpzb2FwZW52PSJodHRwOi8vc2NoZW1hcy54bWxzb2FwLm9yZy9zb2FwL2VudmVsb3BlLyI+PHNvYXBlbnY6SGVhZGVyIHhtbG5zOndzYT0iaHR0cDovL3d3dy53My5vcmcvMjAwNS8wOC9hZGRyZXNzaW5nIj48d3NhOlRvPmh0dHA6Ly9sb2NhbGhvc3Q6OTAwMC9zZXJ2aWNlcy9TaW1wbGVTdG9ja1F1b3RlU2VydmljZTwvd3NhOlRvPjx3c2E6TWVzc2FnZUlEPnVybjp1dWlkOmE5YTc4M2I1LTFmNmQtNGUzNy1hZDNhLWM5YWQ3Y2M0N

Re: [Dev] FailOver endpoint is failing to invoke FailOver Logic for special Error Codes

2012-08-30 Thread Andun Sameera

Hi,
The logic worked. Test case is added to ESB. Thanks for all the help.
AndubSLG
On Aug 30, 2012 11:22 AM, "Andun Sameera"  wrote:

> Hi Hiranya,
>
> Thanks for looking in to this. I don't understand a way to Assert to check 
> takes
> >= 3 errors. So after discussing with Miyuru I thought a another
> alternative.
>
>- Specify Non Retry codes for all error codes expect 101504
>- Generate a 101505
>- So client will timeout without getting a response and we can assert
>that.
>- Then generate a 101504, so failover will eecuted and reply will come
>from second endpoint and we can assert that.
>
> I will try this logic and let you know.
>
> Thanks
> AndunSLG
>
>
>
> On Thu, Aug 30, 2012 at 10:51 AM, Hiranya Jayathilaka <
> hiranya...@gmail.com> wrote:
>
>>
>>
>> On Thu, Aug 30, 2012 at 8:45 AM, Andun Sameera  wrote:
>>
>>> Hi,
>>>
>>> I have tried int the way which Dushan explained. So I have change my
>>> proxy config like this,
>>>
>>> >>   transports="http https"
>>>   startOnLoad="true">
>>>   
>>>  
>>> 
>>>
>>>   
>>>  
>>> http://localhost:9001/services/LBService1";>
>>>
>>>   2000
>>>
>>>
>>>   6
>>>   2.0
>>>
>>>
>>>
>>> 101000,101500,101501,101503,101505,101506,101507,101509
>>>
>>> 3
>>>
>>>  
>>>  
>>>  
>>> http://localhost:9002/services/LBService1"/>
>>>   
>>>   
>>>
>>> 
>>>  
>>>  
>>> 
>>>  
>>>   
>>>
>>>
>>> Here the endpoint "9001 Server" is marked for suspension for all the
>>> error codes but the 101504. Target of doing that is to verify that the
>>> endpoint will go to suspend state only if 101504 happens. But my argument
>>> is wrong.
>>> Because Let say if I generate 101505, then  "9001 Server" will be
>>> timeout. But Failover will retry same "9001 Server" for three times again.
>>> Because it is marked as timeout and eligible for send a message. After
>>> three retires "9001 Server" will be suspended. So my argument of "The
>>> endpoint will go to suspend state only if 101504 happens" is wrong.
>>>
>>
>> Why don't you alter you test? If it fails immediately, then you know it's
>> due to a 101504 immediate suspension. If it takes >= 3 errors to fail then
>> it's some other error.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> So Is there a way to verify that the failover logic is working fine for
>>> specific error codes?
>>>
>>> Thanks
>>> AndunSLG
>>>
>>>
>>> On Wed, Aug 29, 2012 at 10:14 PM, Dushan Abeyruwan wrote:
>>>
>>>> Hi
>>>>
>>>>  AFAIU, the failover logic is working as follows, In your endpoint if
>>>> its defines as
>>>> 
>>>> 2000
>>>> 
>>>>
>>>> 
>>>>
>>>> 101504,101508
>>>>
>>>> 0
>>>> 0
>>>> 
>>>>
>>>> based on 101504,101508 errocodes always the endpoint will
>>>> get marked as TIMEOUT and it wont try  and IF the endpoints are failover
>>>> then the FAILOVER will be invoked the next NONSUSPENDED endpoint.. actually
>>>> the point you need to Note that the FAILOVER will be working only
>>>> for 101504,101508,(according to your current configuration) so In your case
>>>> let say need to invoke next NONSUSPNEDED endpoint when CONNECTION CLOSED.(
>>>&g

Re: [Dev] FailOver endpoint is failing to invoke FailOver Logic for special Error Codes

2012-08-29 Thread Andun Sameera

Hi Hiranya,

Thanks for looking in to this. I don't understand a way to Assert to
check takes
>= 3 errors. So after discussing with Miyuru I thought a another
alternative.

   - Specify Non Retry codes for all error codes expect 101504
   - Generate a 101505
   - So client will timeout without getting a response and we can assert
   that.
   - Then generate a 101504, so failover will eecuted and reply will come
   from second endpoint and we can assert that.

I will try this logic and let you know.

Thanks
AndunSLG



On Thu, Aug 30, 2012 at 10:51 AM, Hiranya Jayathilaka
wrote:

>
>
> On Thu, Aug 30, 2012 at 8:45 AM, Andun Sameera  wrote:
>
>> Hi,
>>
>> I have tried int the way which Dushan explained. So I have change my
>> proxy config like this,
>>
>> >   transports="http https"
>>   startOnLoad="true">
>>   
>>  
>> 
>>
>>   
>>  
>> http://localhost:9001/services/LBService1";>
>>
>>   2000
>>
>>
>>   6
>>   2.0
>>
>>
>>
>> 101000,101500,101501,101503,101505,101506,101507,101509
>>
>> 3
>>
>>  
>>  
>>  
>> http://localhost:9002/services/LBService1"/>
>>   
>>   
>>
>> 
>>  
>>  
>> 
>>  
>>   
>>
>>
>> Here the endpoint "9001 Server" is marked for suspension for all the
>> error codes but the 101504. Target of doing that is to verify that the
>> endpoint will go to suspend state only if 101504 happens. But my argument
>> is wrong.
>> Because Let say if I generate 101505, then  "9001 Server" will be
>> timeout. But Failover will retry same "9001 Server" for three times again.
>> Because it is marked as timeout and eligible for send a message. After
>> three retires "9001 Server" will be suspended. So my argument of "The
>> endpoint will go to suspend state only if 101504 happens" is wrong.
>>
>
> Why don't you alter you test? If it fails immediately, then you know it's
> due to a 101504 immediate suspension. If it takes >= 3 errors to fail then
> it's some other error.
>
> Thanks,
> Hiranya
>
>
>>
>> So Is there a way to verify that the failover logic is working fine for
>> specific error codes?
>>
>> Thanks
>> AndunSLG
>>
>>
>> On Wed, Aug 29, 2012 at 10:14 PM, Dushan Abeyruwan wrote:
>>
>>> Hi
>>>
>>>  AFAIU, the failover logic is working as follows, In your endpoint if
>>> its defines as
>>> 
>>> 2000
>>> 
>>>
>>> 
>>>
>>> 101504,101508
>>>
>>> 0
>>> 0
>>> 
>>>
>>> based on 101504,101508 errocodes always the endpoint will
>>> get marked as TIMEOUT and it wont try  and IF the endpoints are failover
>>> then the FAILOVER will be invoked the next NONSUSPENDED endpoint.. actually
>>> the point you need to Note that the FAILOVER will be working only
>>> for 101504,101508,(according to your current configuration) so In your case
>>> let say need to invoke next NONSUSPNEDED endpoint when CONNECTION CLOSED.(
>>> *101505)*. then you should include that in MarkForSuspence, so please
>>> try with following
>>>
>>> 
>>> 101504,101508,*
>>> 101505*
>>>
>>> 0
>>> 0
>>> 
>>>
>>>  so what will happen now the IF BE is closed then the EP will be
>>> marked as TIMEOUT for 101504,101508,*101505 then as I
>>> explained earlier it will invoke next active NONSUSPNEDED endpoint,*
>>> **
>>> *   *

Re: [Dev] FailOver endpoint is failing to invoke FailOver Logic for special Error Codes

2012-08-29 Thread Andun Sameera

Hi,

I tried using this config also,


  
 

   
  
 
http://10.200.3.190:8280/services/echo
">
   
  2000
  
   
   
  6
  2.0
   
   

101000,101500,101501,101503,101505,101506,101507,101509

3
   
   

101000,101500,101501,101503,101505,101506,101507,101509
   

 
 
http://10.200.3.190:8281/services/echo
"/>
 
  
   

 
 

 
  
   

Here the "9001 Server" endpoint not went for Suspend even if I generate a
101505. But the message was not send to other endpoint in the failover.
Following error was logged.

[2012-08-30 08:59:01,244]  WARN - EndpointContext Endpoint : 9001 Server is
marked as TIMEOUT and will be retried : 1 more time/s after : Thu Aug 30
08:59:01 IST 2012 until its marked SUSPENDED for failure
[2012-08-30 08:59:01,246]  WARN - FailoverEndpoint Endpoint
[endpoint_218db703f9e9add3370273ee4bba8167f6bb648b510a8e0e] Detect a
Failure in a child endpoint : Endpoint [9001 Server]
[2012-08-30 08:59:01,247]  WARN - FailoverEndpoint Failover endpoint :
endpoint_218db703f9e9add3370273ee4bba8167f6bb648b510a8e0e - one of the
child endpoints encounterd a non-retry error, not sending message to
another endpoint


Thanks
AndunSLG


On Thu, Aug 30, 2012 at 8:45 AM, Andun Sameera  wrote:

> Hi,
>
> I have tried int the way which Dushan explained. So I have change my proxy
> config like this,
>
>transports="http https"
>   startOnLoad="true">
>   
>  
> 
>
>   
>  
> http://localhost:9001/services/LBService1";>
>
>   2000
>
>
>   6
>   2.0
>
>
>
> 101000,101500,101501,101503,101505,101506,101507,101509
>
> 3
>
> 
>  
>  
> http://localhost:9002/services/LBService1"/>
>  
>   
>
> 
>  
>  
> 
>  
>   
>
>
> Here the endpoint "9001 Server" is marked for suspension for all the error
> codes but the 101504. Target of doing that is to verify that the endpoint
> will go to suspend state only if 101504 happens. But my argument is wrong.
> Because Let say if I generate 101505, then  "9001 Server" will be timeout.
> But Failover will retry same "9001 Server" for three times again. Because
> it is marked as timeout and eligible for send a message. After three
> retires "9001 Server" will be suspended. So my argument of "The endpoint
> will go to suspend state only if 101504 happens" is wrong.
>
> So Is there a way to verify that the failover logic is working fine for
> specific error codes?
>
> Thanks
> AndunSLG
>
>
> On Wed, Aug 29, 2012 at 10:14 PM, Dushan Abeyruwan wrote:
>
>> Hi
>>
>>  AFAIU, the failover logic is working as follows, In your endpoint if its
>> defines as
>> 
>> 2000
>> 
>>
>> 
>>
>> 101504,101508
>>
>> 0
>> 0
>> 
>>
>> based on 101504,101508 errocodes always the endpoint will get
>> marked as TIMEOUT and it wont try  and IF the endpoints are failover then
>> the FAILOVER will be invoked the next NONSUSPENDED endpoint.. actually the
>> point you need to Note that the FAILOVER will be working only
>> for 101504,101508,(according to your current configuration) so In your case
>> let say need to invoke next NONSUSPNEDED endpoint when CONNECTION CLOSED.(
>> *101505)*. then you should include that in MarkForSuspence, so please
>> try with following
>>
>>

Re: [Dev] FailOver endpoint is failing to invoke FailOver Logic for special Error Codes

2012-08-29 Thread Andun Sameera

Hi,

I have tried int the way which Dushan explained. So I have change my proxy
config like this,


  
 

   
  
 
http://localhost:9001/services/LBService1";>
   
  2000
   
   
  6
  2.0
   
   

101000,101500,101501,101503,101505,101506,101507,101509

3
   

 
 
http://localhost:9002/services/LBService1"/>
 
  
   

 
 

 
  
   

Here the endpoint "9001 Server" is marked for suspension for all the error
codes but the 101504. Target of doing that is to verify that the endpoint
will go to suspend state only if 101504 happens. But my argument is wrong.
Because Let say if I generate 101505, then  "9001 Server" will be timeout.
But Failover will retry same "9001 Server" for three times again. Because
it is marked as timeout and eligible for send a message. After three
retires "9001 Server" will be suspended. So my argument of "The endpoint
will go to suspend state only if 101504 happens" is wrong.

So Is there a way to verify that the failover logic is working fine for
specific error codes?

Thanks
AndunSLG

On Wed, Aug 29, 2012 at 10:14 PM, Dushan Abeyruwan  wrote:

> Hi
>
>  AFAIU, the failover logic is working as follows, In your endpoint if its
> defines as
> 
> 2000
> 
>
> 
>
> 101504,101508
>
> 0
> 0
> 
>
> based on 101504,101508 errocodes always the endpoint will get
> marked as TIMEOUT and it wont try  and IF the endpoints are failover then
> the FAILOVER will be invoked the next NONSUSPENDED endpoint.. actually the
> point you need to Note that the FAILOVER will be working only
> for 101504,101508,(according to your current configuration) so In your case
> let say need to invoke next NONSUSPNEDED endpoint when CONNECTION CLOSED.(
> *101505)*. then you should include that in MarkForSuspence, so please try
> with following
>
> 
> 101504,101508,*101505*
> 
>
> 0
> 0
> 
>
>  so what will happen now the IF BE is closed then the EP will be
> marked as TIMEOUT for 101504,101508,*101505 then as I
> explained earlier it will invoke next active NONSUSPNEDED endpoint,*
> **
> *   *Persoally i havent try this out but if looking
> http://wso2.org/library/articles/wso2-enterprise-service-bus-endpoint-error-handling
> the logic is clearly explained please give more attention to
> the highlighted text
>
> e.g
>
> 
> 
> 
> http://localhost/myendpoint"; statistics="enable" 
> trace="disable">
> 
> 6
> 
>
> 
> 101504, 101505, 101500
> 3
> 1
> 
>
> 
> 1000
> 2
> 64000
> 
>
> 
> 
> 
> 
>
>
> "Here the Sample_First endpoint is marked as *TIMEOUT if a connection runs 
> out of time, a connection close or sends IO errors. For all the other 
> errors*, it will be marked as suspended. *When this error occurs the fail 
> over will retry using the first non SUSPENDED endpoint.* In this case, it is 
> the same endpoint (Sample_First). It will retry until the retry count becomes 
> 0. The retry happens in parrellel. Since messages do come to this endpoint 
> using many threads, the same message may not be retired 3 times. Another 
> message may fail and can reduce the retry count. So it is important to note 
> that the retry count is not a per message based setting, it is a per endpoint 
> based setting."
>
>
>
> cheers
> Dushan
>
>
>
> On Wed, Aug 29, 2012 at 7:57 PM, Andun Sameera  wrote:
>
>> Hi All,
>>
>> I am trying to check the functionality of the Fail Over Endpoint. I want
>> to verify that the failover logic is happening

[Dev] FailOver endpoint is failing to invoke FailOver Logic for special Error Codes

2012-08-29 Thread Andun Sameera

Hi All,

I am trying to check the functionality of the Fail Over Endpoint. I want to
verify that the failover logic is happening to specific error codes. I
used  proxy given below for that,

According to 
[1],
error code 101504,101508 for timeouts. So I used following test case
to produce the scenario,

My logic was this,

   1. Send a request to proxy to check it is functioning.
   2. Shutdown http://localhost:9001 server.
   3. Then send Send a request to proxy again. So the first endpoint should
   be failed. But it cant be suspend. Because it is only suspending for
   timeouts.
   4. Response should come from second server.
   5. Then Start the http://localhost:9001 server.
   6. Then send Send a request to proxy again. Response should come from
   server1. Because it is not suspended.( I am trying this with in the suspend
   time period of 9001-server endpoint, so if is suspended, response should
   come from server2)

But when I tried this, in the 3rd step of the logic (Red Highlighted line
of the code) it fails. The endpoint is suspending for connection refused
created by shutting down the server. According to spec it cant be. Is this
a bug or am I doing something wrong here? Please look at this ASAP we need
this to wind up Test Automation Hackathon tomorrow.

Thanks
AndunSLG

[1] -
http://wso2.org/library/articles/wso2-enterprise-service-bus-endpoint-error-handling

Proxy Service :








http://localhost:9001/services/LBService1";>

2000




101504,101508

0
0




6

2




http://localhost:9002/services/LBService1";>

2000



101509

0
0




6

2













Test Case :

@Test(groups = "wso2.esb", description = "Test sending request to Fail Over
Endpoint which Suspend Endpoints to Specific Errors")
public void testSendingFailOverEndpoint_With_Specific_Errors() throws
IOException, InterruptedException {
//Check the fail over endpoint is functioning well
String response =
lbClient.sendLoadBalanceRequest(getProxyServiceURL("failoverEndPoint_Specific_Errors"),
null);
Assert.assertNotNull(response);
Assert.assertTrue(response.toString().contains("Response from
server: Server_1"));

//Stop one server to generate a failure in one endpoint
//But the suspend cant be triggered here. because suspend the
endpoint happen only for Timeouts 101504,101508
axis2Server1.stop();

response =
lbClient.sendLoadBalanceRequest(getProxyServiceURL("failoverEndPoint_Specific_Errors"),
null);
Assert.assertNotNull(response);
Assert.assertTrue(response.toString().contains("Response from
server: Server_2"));

axis2Server1.start();

int counter=0;
while(!AxisServiceClientUtils.isServiceAvailable("
http://localhost:9001/services/LBService1";)) {
if(counter>100){
break;
}
counter++;
}

if(counter>100){
throw new AssertionError("Axis2 Server didn't started with in
expected time period.") ;
}
else{
//Checaxiaxis2Server1.start()s2Server1.stop()k that the
endpoint one is not suspended.
//If reply comes that means not suspended.
//Because suspend duration of the endpoint is 20 seconds. So
reply cant come in this time.
response =
lbClient.sendLoadBalanceRequest(getProxyServiceURL("failoverEndPoint_Specific_Errors"),
null);
Assert.assertNotNull(response);
Assert.assertTrue(response.toString().contains("Response from
server: Server_1"));

//Invoke a web service method which will invoke a time out and
cause the endpoint to suspend.
response =
lbClient.sendSleepRequest(getProxyServiceURL("failoverEndPoint_Specific_Errors"),"4000");
As

Re: [Dev] Clarification needed for the properties of the ESB's VFS transport : Some abnormal behaviors observed

2012-08-26 Thread Andun Sameera

Hi All,

Amila and Deep thanks for the help. As you advice I have clarify some of
the scenarios. I have replied for the issues I have found.

On Mon, Aug 27, 2012 at 9:50 AM, Amila Maha Arachchi wrote:

> Hi Andun,
>
> Please see some comments in-line.
>
> On Fri, Aug 24, 2012 at 9:25 PM, Andun Sameera  wrote:
>
>> Hi All,
>>
>> I am developing some test scenarios for the VFS transport to
>> check properties given in 
>> [1]<http://wso2.org/project/esb/java/3.0.1/docs/transports/transports-catalog.html#VfsTrp>.
>> Want to clarify the observation which I noticed are
>> correct. Some suspicious behaviors are observed and those observations are
>> given in RED.
>>
>> Thanks
>> AndunSLG
>>
>

> [1] -
>> http://wso2.org/project/esb/java/3.0.1/docs/transports/transports-catalog.html#VfsTrp
>>
>> *1 - Deploying a proxy with transport.vfs.FileURI = Invalid URI, I used
>> a folder which not exists.*
>>
>> *Proxy :*
>>
>> >transports="vfs"
>>startOnLoad="true"
>>trace="disable">
>> 
>> 
>> http://localhost:9000/services/SimpleStockQuoteService";
>>  format="soap12"/>
>> 
>> 
>> 
>> 
>> 
>> > uri="vfs:file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/out/out.xml"/>
>> 
>> 
>> 
>> 
>> 1
>>  > name="transport.vfs.FileURI">file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test
>> /invalid/
>> .*\.xml
>> text/xml
>> 
>>
>> *Observations :*
>>
>> Proxy Deployed Successfully.
>>
>
> VFS proxies do not validate the file URIs as http/s proxies validate the
> endpoint. So, the proxy should get deployed successfully. You may see some
> errors when the proxy tries to poll the specified file location,, which is
> acceptable.
>

>> *2 - Deploying a proxy with transport.vfs.ContentType = Invalid*
>>
>> *Proxy :*
>>
>> >transports="vfs"
>>startOnLoad="true"
>>trace="disable">
>> 
>> 
>> http://localhost:9000/services/SimpleStockQuoteService";
>>  format="soap12"/>
>> 
>> 
>> 
>> 
>> 
>> > uri="vfs:file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/out/out.xml"/>
>> 
>> 
>> 
>> 
>> 1
>>  > name="transport.vfs.FileURI">file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/
>> .*\.xml
>> invalid/invalid
>> 
>>
>> *Observations :*
>>
>> Proxy Deployed Successfully.
>> The input file was successfully processed, and out put was
>> created successfully.
>>
>
> I am not sure about this. I think there may be a default message builder
> which gets picked up if the content type is invalid (i.e. non existing
> content types). AFAIU this content type is needed after the file is
> processed and when it is building the message.
>

>> *3 - Deploying a proxy with transport.vfs.ContentType = Not Specified, This
>> was a mandatory property in spec.*
>>
>> *Proxy :*
>>
>> 
>> 
>> 
>> http://localhost:9000/services/SimpleStockQuoteService";
>>  format="soap12"/>
>> 
>> 
>> 
>> 
>> 
>> > uri="vfs:file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/out/out.xml"/>
>> 
>> 
>> 
>> 
>> 1
>>  > name="transport.vfs.FileURI">file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTr

Re: [Dev] Clarification needed for the properties of the ESB's VFS transport : Some abnormal behaviors observed

2012-08-26 Thread Andun Sameera

Hi All,

We are going to end the ESB test automation this week. So I need these to
by clarified before adding test cases. It will be great some one can help
me.

Thanks
AndunSLG

On Fri, Aug 24, 2012 at 9:25 PM, Andun Sameera  wrote:

> Hi All,
>
> I am developing some test scenarios for the VFS transport to
> check properties given in 
> [1]<http://wso2.org/project/esb/java/3.0.1/docs/transports/transports-catalog.html#VfsTrp>.
> Want to clarify the observation which I noticed are
> correct. Some suspicious behaviors are observed and those observations are
> given in RED.
>
> Thanks
> AndunSLG
>
> [1] -
> http://wso2.org/project/esb/java/3.0.1/docs/transports/transports-catalog.html#VfsTrp
>
> *1 - Deploying a proxy with transport.vfs.FileURI = Invalid URI, I used a
> folder which not exists.*
>
> *Proxy :*
>
> transports="vfs"
>startOnLoad="true"
>trace="disable">
> 
> 
> http://localhost:9000/services/SimpleStockQuoteService";
>  format="soap12"/>
> 
> 
> 
> 
> 
>  uri="vfs:file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/out/out.xml"/>
> 
> 
> 
> 
> 1
>   name="transport.vfs.FileURI">file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test
> /invalid/
> .*\.xml
> text/xml
> 
>
> *Observations :*
>
> Proxy Deployed Successfully.
>
> *2 - Deploying a proxy with transport.vfs.ContentType = Invalid*
>
> *Proxy :*
>
> transports="vfs"
>startOnLoad="true"
>trace="disable">
> 
> 
> http://localhost:9000/services/SimpleStockQuoteService";
>  format="soap12"/>
> 
> 
> 
> 
> 
>  uri="vfs:file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/out/out.xml"/>
> 
> 
> 
> 
> 1
>   name="transport.vfs.FileURI">file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/
> .*\.xml
> invalid/invalid
> 
>
> *Observations :*
>
> Proxy Deployed Successfully.
> The input file was successfully processed, and out put was
> created successfully.
>
> *3 - Deploying a proxy with transport.vfs.ContentType = Not Specified, This
> was a mandatory property in spec.*
>
> *Proxy :*
>
> 
> 
> 
> http://localhost:9000/services/SimpleStockQuoteService";
>  format="soap12"/>
> 
> 
> 
> 
> 
>  uri="vfs:file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/out/out.xml"/>
> 
> 
> 
> 
> 1
>   name="transport.vfs.FileURI">file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/
> .*\.xml
> 
>
> *Observations :*
>
> Proxy Deployed Successfully.
>
> *4 - Deploying a proxy with transport.PollInterval  **=Non Integer, *
>
> *Proxy :*
>
> transports="vfs"
>startOnLoad="true"
>trace="disable">
> 
> 
> http://localhost:9000/services/SimpleStockQuoteService";
>  format="soap12"/>
> 
> 
> 
> 
> 
>  uri="vfs:file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/out/out.xml"/>
> 
> 
> 
> 
> 1.1
>  name="transport.vfs.FileURI">file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/i

[Dev] Clarification needed for the properties of the ESB's VFS transport : Some abnormal behaviors observed

2012-08-24 Thread Andun Sameera

Hi All,

I am developing some test scenarios for the VFS transport to
check properties given in
[1].
Want to clarify the observation which I noticed are
correct. Some suspicious behaviors are observed and those observations are
given in RED.

Thanks
AndunSLG

[1] -
http://wso2.org/project/esb/java/3.0.1/docs/transports/transports-catalog.html#VfsTrp

*1 - Deploying a proxy with transport.vfs.FileURI = Invalid URI, I used a
folder which not exists.*

*Proxy :*




http://localhost:9000/services/SimpleStockQuoteService
"
 format="soap12"/>










1
 file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test
/invalid/
.*\.xml
text/xml


*Observations :*

Proxy Deployed Successfully.

*2 - Deploying a proxy with transport.vfs.ContentType = Invalid*

*Proxy :*




http://localhost:9000/services/SimpleStockQuoteService
"
 format="soap12"/>










1
 file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/
.*\.xml
invalid/invalid


*Observations :*

Proxy Deployed Successfully.
The input file was successfully processed, and out put was
created successfully.

*3 - Deploying a proxy with transport.vfs.ContentType = Not Specified, This
was a mandatory property in spec.*

*Proxy :*




http://localhost:9000/services/SimpleStockQuoteService
"
 format="soap12"/>










1
 file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/
.*\.xml


*Observations :*

Proxy Deployed Successfully.

*4 - Deploying a proxy with transport.PollInterval  **=Non Integer, *

*Proxy :*




http://localhost:9000/services/SimpleStockQuoteService
"
 format="soap12"/>










1.1
file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/
.*\.xml
text/xml


*Observations :*

Proxy Deployed Successully.
The input file was not processed.

*5 - Deploying a proxy with **transport.vfs.ActionAfterProcess = Invalid, *

*Proxy :*




http://localhost:9000/services/SimpleStockQuoteService
"
 format="soap12"/>










MOVEDD
1
file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/original/
file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/
.*\.xml
text/xml


*Observations :*

Proxy Deployed Successfully.
The input file was successfully processed, and out put was
created successfully.

*6 - Deploying a proxy with **transport.vfs.ActionAfterFailure = Invalid, *

*Proxy :*




http://localhost:9000/services/SimpleStockQuoteService";
 format="soap12"/>










1
file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/
file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/failure/
.*\.xml
text/xml
MOVEDD


*Observations :*

Proxy Deployed Successfully.
Failure Happens due to file content.

*7 - Deploying a proxy with **transport.vfs.MoveAfterProcess = Invalid, *

*Proxy :*




http://localhost:9000/services/SimpleStockQuoteService
"
 format="soap12"/>










MOVE
1
file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test
/invalid/
file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests

Re: [Dev] Error in ESB's VFS Transport

2012-08-22 Thread Andun Sameera

Hi Amila,

Solved the problem. This was happening due to a permission issue. At the
first time I have created only the File Pointer without creating Folders
specifically when running through the Clarity. So that caused the problem.
When I tried the same folders with a separate server again that fails.
So now I create the folders  specifically for the testing. So Now the
scenario works fine.

Thanks
AndunSLG

On Wed, Aug 22, 2012 at 10:52 PM, Amila Maha Arachchi wrote:

>
>
> On Wed, Aug 22, 2012 at 9:09 PM, Andun Sameera  wrote:
>
>> Hi Amila,
>>
>> As you suggested I have check with this config,
>>
>> >   transports="vfs"
>>   startOnLoad="true"
>>   trace="disable">
>>   
>>  
>> 
>> 
>> 
>>
>>   > uri="vfs:file:///home/andunslg/test/out/out.txt"/>
>>
>> 
>>  
>>   
>>   1
>>   MOVE
>>   > name="transport.vfs.FileURI">/home/andunslg/test/in
>>   > name="transport.vfs.MoveAfterProcess">file:///home/andunslg/test/original
>>.*.txt
>>   text/plain
>>
>>
>> And It works fine. So what is the reason for this behavior ? When run via
>> clarity can make permission issues, but even I run the
>> server separately it happened. That was the weird thing.
>>
>
> Still can be a permission issue. But int the code segment I pasted in the
> previous reply, there are some places I dont understand. So cannot predict
> the exact reason.
>
> BTW, did you check permission for the relevant directories in the failed
> case without Clarity (I think you used the same folder paths for clarity
> and without clarity). You also can debug and see.
>
> Regards,
> AmilaM.
>
>>
>> Thanks
>> AndunSLG
>>
>> On Wed, Aug 22, 2012 at 7:41 PM, Amila Maha Arachchi wrote:
>>
>>> Hi Andun,
>>>
>>> I tried this with ESB 4.0.3 and it works fine (I dont have a 4.5.0 to
>>> test). Nothing has been changed after 4.0.3 in the relevant code.
>>>
>>> Following code segment is the responsible for this. You can debug
>>> commons-vfs's AbstractFileObject class and see where exactly it goes wrong.
>>>
>>> BTW, when you tried without Clarity, did you try using a separate file
>>> location (not in integration/tests/target, but some other place like your
>>> home folder to see whether this is permission problem)?
>>>
>>> if (canRenameTo(destFile))
>>> {
>>>* // issue rename on same filesystem*
>>> try
>>> {
>>> attach();
>>> doRename(destFile);
>>>
>>>
>>> (FileObjectUtils.getAbstractFileObject(destFile)).handleCreate(getType());
>>>
>>> destFile.close(); // now the destFile is no longer
>>> imaginary. force reattach.
>>>
>>> handleDelete(); // fire delete-events. This file-object
>>> (src) is like deleted.
>>> }
>>> catch (final RuntimeException re)
>>> {
>>> throw re;
>>> }
>>> catch (final Exception exc)
>>> {
>>> *throw new
>>> FileSystemException("vfs.provider/rename.error", new Object[]
>>> {
>>> getName(),
>>> destFile.getName()
>>> }, exc);*
>>> }
>>> }
>>>
>>> Regards,
>>> AmilaM.
>>>
>>>  On Wed, Aug 22, 2012 at 6:11 PM, Andun Sameera  wrote:
>>>
>>>>  Hi All,
>>>>
>>>> I am trying to test the functionality of transport.vfs.MoveAfterProcess
>>>> using the following configuration,
>>>>
>>>>  >>>   transports="vfs"
>>>>   startOnLoad="true"
>>>>   trace="disable">
>>>>   
>>>>  
>>>> 
>>>> 
>>>> 
>>>>
>>>>   >>> uri="vfs:file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/targe

Re: [Dev] Error in ESB's VFS Transport

2012-08-22 Thread Andun Sameera

Hi Amila,

As you suggested I have check with this config,


  
 



   
  
   

 
  
  1
  MOVE
  /home/andunslg/test/in
  file:///home/andunslg/test/original
  .*.txt
  text/plain
   

And It works fine. So what is the reason for this behavior ? When run via
clarity can make permission issues, but even I run the
server separately it happened. That was the weird thing.

Thanks
AndunSLG

On Wed, Aug 22, 2012 at 7:41 PM, Amila Maha Arachchi wrote:

> Hi Andun,
>
> I tried this with ESB 4.0.3 and it works fine (I dont have a 4.5.0 to
> test). Nothing has been changed after 4.0.3 in the relevant code.
>
> Following code segment is the responsible for this. You can debug
> commons-vfs's AbstractFileObject class and see where exactly it goes wrong.
>
> BTW, when you tried without Clarity, did you try using a separate file
> location (not in integration/tests/target, but some other place like your
> home folder to see whether this is permission problem)?
>
> if (canRenameTo(destFile))
> {
>* // issue rename on same filesystem*
> try
> {
> attach();
> doRename(destFile);
>
>
> (FileObjectUtils.getAbstractFileObject(destFile)).handleCreate(getType());
>
> destFile.close(); // now the destFile is no longer
> imaginary. force reattach.
>
> handleDelete(); // fire delete-events. This file-object
> (src) is like deleted.
> }
> catch (final RuntimeException re)
> {
> throw re;
> }
> catch (final Exception exc)
> {
> *throw new
> FileSystemException("vfs.provider/rename.error", new Object[]
> {
> getName(),
> destFile.getName()
> }, exc);*
> }
> }
>
> Regards,
> AmilaM.
>
> On Wed, Aug 22, 2012 at 6:11 PM, Andun Sameera  wrote:
>
>> Hi All,
>>
>> I am trying to test the functionality of transport.vfs.MoveAfterProcess
>> using the following configuration,
>>
>>  >   transports="vfs"
>>   startOnLoad="true"
>>   trace="disable">
>>   
>>  
>> 
>> 
>> 
>>
>>   > uri="vfs:file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/out/out.txt"/>
>>
>> 
>>  
>>   
>>   MOVE
>>   1
>>   > name="transport.vfs.MoveAfterProcess">file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/original/
>>   > name="transport.vfs.FileURI">/media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/
>>   .*.txt
>>   text/plain
>>
>>
>> When I put a file to the in folder following exception is thrown in
>> console continues. Also I am uploading the config via the Clarity
>> Framework. Also I tried without Clarity just running a ESB instance. That
>> also fails in the same manner.
>>
>> TID: [] [WSO2 Enterprise Service Bus] [2012-08-22 18:00:49,992] ERROR
>> {org.apache.synapse.transport.vfs.VFSTransportListener} - Error moving file
>> :
>> file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/test.txt
>> to
>> file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/original/
>> {org.apache.synapse.transport.vfs.VFSTransportListener}
>> org.apache.commons.vfs2.FileSystemException: Could not rename
>> "file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/test.txt"
>> to
>> "file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/

Re: [Dev] Error in ESB's VFS Transport

2012-08-22 Thread Andun Sameera

Ubuntu 12.04

On Wed, Aug 22, 2012 at 6:57 PM, Paul Fremantle  wrote:

> Which OS are you on?
>
> Paul
>
> On 22 August 2012 13:41, Andun Sameera  wrote:
>
>> Hi All,
>>
>> I am trying to test the functionality of transport.vfs.MoveAfterProcess
>> using the following configuration,
>>
>>  >   transports="vfs"
>>   startOnLoad="true"
>>   trace="disable">
>>   
>>  
>> 
>> 
>> 
>>
>>   > uri="vfs:file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/out/out.txt"/>
>>
>> 
>>  
>>   
>>   MOVE
>>   1
>>   > name="transport.vfs.MoveAfterProcess">file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/original/
>>   > name="transport.vfs.FileURI">/media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/
>>   .*.txt
>>   text/plain
>>
>>
>> When I put a file to the in folder following exception is thrown in
>> console continues. Also I am uploading the config via the Clarity
>> Framework. Also I tried without Clarity just running a ESB instance. That
>> also fails in the same manner.
>>
>> TID: [] [WSO2 Enterprise Service Bus] [2012-08-22 18:00:49,992] ERROR
>> {org.apache.synapse.transport.vfs.VFSTransportListener} - Error moving file
>> :
>> file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/test.txt
>> to
>> file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/original/
>> {org.apache.synapse.transport.vfs.VFSTransportListener}
>> org.apache.commons.vfs2.FileSystemException: Could not rename
>> "file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/test.txt"
>> to
>> "file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/original/test.txt".
>> at
>> org.apache.commons.vfs2.provider.AbstractFileObject.moveTo(AbstractFileObject.java:1117)
>> at
>> org.apache.synapse.transport.vfs.VFSTransportListener.moveOrDeleteAfterProcessing(VFSTransportListener.java:425)
>> at
>> org.apache.synapse.transport.vfs.VFSTransportListener.scanFileOrDirectory(VFSTransportListener.java:322)
>> at
>> org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:158)
>> at
>> org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:107)
>> at
>> org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67)
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
>> at java.lang.Thread.run(Thread.java:619)
>>
>> When I change the transport.vfs.MoveAfterProcess to DELETE it works fine.
>>
>> Thanks
>> AndunSLG
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> p...@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error in ESB's VFS Transport

2012-08-22 Thread Andun Sameera

Hi All,

I am trying to test the functionality of transport.vfs.MoveAfterProcess
using the following configuration,

 
  
 



   
  
   

 
  
  MOVE
  1
  file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/original/
  /media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/
  .*.txt
  text/plain
   

When I put a file to the in folder following exception is thrown in console
continues. Also I am uploading the config via the Clarity Framework. Also I
tried without Clarity just running a ESB instance. That also fails in the
same manner.

TID: [] [WSO2 Enterprise Service Bus] [2012-08-22 18:00:49,992] ERROR
{org.apache.synapse.transport.vfs.VFSTransportListener} - Error moving file
:
file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/test.txt
to
file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/original/
{org.apache.synapse.transport.vfs.VFSTransportListener}
org.apache.commons.vfs2.FileSystemException: Could not rename
"file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/in/test.txt"
to
"file:///media/Studies/My_Works/WSO2_Carbon_Trunk/platform_4.0.0/4.0.0/products/esb/4.5.0/modules/integration/tests/target/test-classes/artifacts/ESB/synapseconfig/vfsTransport/test/original/test.txt".
at
org.apache.commons.vfs2.provider.AbstractFileObject.moveTo(AbstractFileObject.java:1117)
at
org.apache.synapse.transport.vfs.VFSTransportListener.moveOrDeleteAfterProcessing(VFSTransportListener.java:425)
at
org.apache.synapse.transport.vfs.VFSTransportListener.scanFileOrDirectory(VFSTransportListener.java:322)
at
org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:158)
at
org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:107)
at
org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)

When I change the transport.vfs.MoveAfterProcess to DELETE it works fine.

Thanks
AndunSLG
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] XACML based Axis2 Entitlement Handler and Authentication Filter for Webapp security

[Dev] Need to clarify : Are the queries asked in the issue is possible ?

Re: [Dev] Build failure in org.wso2.carbon.cassandra.cluster.mgt.ui

Re: [Dev] Build Failure in Load Balancer component

Re: [Dev] Build Failure in Load Balancer component

Re: [Dev] Merging StreamingXPATH + RawXSLT Mediator to ESB 4.6.0

[Dev] Merging StreamingXPATH + RawXSLT Mediator to ESB 4.6.0

Re: [Dev] Confusion in ESB

Re: [Dev] Confusion in ESB

[Dev] Confusion in ESB

Re: [Dev] Compilation Failure at org.wso2.carbon.dataservices.core - 4.0.5

Re: [Dev] Compilation Failure at org.wso2.carbon.dataservices.core - 4.0.5

[Dev] Compilation Failure at org.wso2.carbon.dataservices.core - 4.0.5

Re: [Dev] org.wso2.carbon.identity.entitlement.proxy build failure

Re: [Dev] org.wso2.carbon.identity.entitlement.proxy build failure

Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB

Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB

Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB

Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB

Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB

[Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB

Re: [Dev] Custom Mediator for XSLT Transformation

Re: [Dev] FailOver endpoint is failing to invoke FailOver Logic for special Error Codes

Re: [Dev] FailOver endpoint is failing to invoke FailOver Logic for special Error Codes

Re: [Dev] FailOver endpoint is failing to invoke FailOver Logic for special Error Codes

Re: [Dev] FailOver endpoint is failing to invoke FailOver Logic for special Error Codes

[Dev] FailOver endpoint is failing to invoke FailOver Logic for special Error Codes

Re: [Dev] Clarification needed for the properties of the ESB's VFS transport : Some abnormal behaviors observed

Re: [Dev] Clarification needed for the properties of the ESB's VFS transport : Some abnormal behaviors observed

[Dev] Clarification needed for the properties of the ESB's VFS transport : Some abnormal behaviors observed

Re: [Dev] Error in ESB's VFS Transport

Re: [Dev] Error in ESB's VFS Transport

Re: [Dev] Error in ESB's VFS Transport

[Dev] Error in ESB's VFS Transport

34 matches

Site Navigation

Mail list logo

Footer information