Re: [Dev] GSoC Project: HTTP Load Balancer On Top Of WSO2 Gateway Discussion

[Ravi Undupitiya]

Hi Venkat,

Please find answers inline below.

On Tue, May 24, 2016 at 9:29 PM, Venkat Raman  wrote:
>
>
> 1) Why are we pushing variables in carbon message variables stack..??
>

One of the features of the language is to have variables we can declare and
use throughout the mediation flow. We are able to populate variables during
loading and during runtime and so variable stack is kept inside the carbon
message so each thread has its own variable stack. Hope that clarifies.


> 2) Also could you kindly explain how AbstractFlowController and
> FlowControllerCallback are working together.  My understanding is not quite
> clear on this.
>

AbstractFlowControllers are mediators that require controlling the flow
(like filter mediator) where we the mediation flow branching out, in which
case we want to mediate only the branch we're in and FlowControllerCallback
is a CarbonCallback that we pass on to receive method of mediators of a
particular branch. This allows us to continue mediation from the parent
once a branch is complete. You can test this out by debugging the
FilterMediator, try passing on the usual callback and then check by passing
on a FlowControllerCallback.

@IsuruR, please correct me if I'm wrong. :)


Thanks,
-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712
<%2B94%C2%A0772%20930%20712>*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.9.0 JSM client error

[Ravi Undupitiya]

In that case we should update the samples doc and document the system
properties that can be updated. I've created doc JIRA [1] to track this.

[1] https://wso2.org/jira/browse/DOCUMENTATION-3316


Thanks,

On Tue, May 10, 2016 at 2:49 PM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> Hi Ravi,
>
> Seems activemq is used by GenericJMSClient [1] by default.
>
> [1] -
> https://github.com/wso2/product-esb/blob/master/modules/samples/product/src/main/java/samples/userguide/GenericJMSClient.java
>
> Thanks.
>
> On Tue, May 10, 2016 at 2:37 PM, Ravi Undupitiya  wrote:
>
>> Hi Aruna,
>>
>> ActiveMQ jars are not required to connect to MB. Would you happen to have
>> ActiveMQ context factory set in some config file?
>>
>>
>> On Tue, May 10, 2016 at 2:24 PM, Aruna Karunarathna 
>> wrote:
>>
>>> Hi Jagath,
>>>
>>> Thanks for the reply, No I haven't setup ActiveMQ, instead I've followed
>>> instructions in [1] to configure with WSO2MB, and it doesn't mention to add
>>> ActiveMQ jars,
>>>
>>> After adding the mentioned jars resolved the issue.
>>>
>>> Isn't it better to add as a prerequisite before configuring MB?.
>>>
>>> [1].
>>> https://docs.wso2.com/display/ESB490/Configure+with+WSO2+Message+Broker
>>>
>>> Regards,
>>> Aruna
>>>
>>> On Tue, May 10, 2016 at 2:01 PM, Jagath Sisirakumara Ariyarathne <
>>> jaga...@wso2.com> wrote:
>>>
>>>> Hi Aruna,
>>>>
>>>> Did you add required jar files to lib folder as mentioned in[1].
>>>>
>>>> [1] - https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ
>>>>
>>>> Thanks.
>>>>
>>>> On Tue, May 10, 2016 at 1:39 PM, Aruna Karunarathna 
>>>> wrote:
>>>>
>>>>> Hi ESB team,
>>>>>
>>>>> When trying to invoke the JMSClient [1] getting the below error. Seems
>>>>> like the activemq jar is not present in the classpath.
>>>>>
>>>>>  ant jmsclient -Djms_type=pox -Djms_dest=dynamicQueues/StockQuoteProxy
>>>>> -Djms_payload=MSFT
>>>>> Buildfile: /home/aruna//wso2esb-4.9.0/samples/axis2Client/build.xml
>>>>>
>>>>> init:
>>>>>
>>>>> compile:
>>>>>
>>>>> jmsclient:
>>>>>  [java] Exception in thread "main"
>>>>> javax.naming.NoInitialContextException: Cannot instantiate class:
>>>>> org.apache.activemq.jndi.ActiveMQInitialContextFactory [Root exception is
>>>>> java.lang.ClassNotFoundException:
>>>>> org.apache.activemq.jndi.ActiveMQInitialContextFactory]
>>>>>  [java] at
>>>>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:674)
>>>>>  [java] at
>>>>> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
>>>>>  [java] at
>>>>> javax.naming.InitialContext.init(InitialContext.java:242)
>>>>>  [java] at
>>>>> javax.naming.InitialContext.(InitialContext.java:216)
>>>>>  [java] at samples.userguide.GenericJMSClient.connect(Unknown
>>>>> Source)
>>>>>  [java] at samples.userguide.GenericJMSClient.main(Unknown Source)
>>>>>  [java] Caused by: java.lang.ClassNotFoundException:
>>>>> org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>>>>  [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
>>>>>  [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
>>>>>  [java] at java.security.AccessController.doPrivileged(Native
>>>>> Method)
>>>>>  [java] at
>>>>> java.net.URLClassLoader.findClass(URLClassLoader.java:354)
>>>>>  [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>>>>>  [java] at
>>>>> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
>>>>>  [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>>>>>  [java] at java.lang.Class.forName0(Native Method)
>>>>>  [java] at java.lang.Class.forName(Class.java:270)
>>>>>  [java] at
>>>>> com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:72)
>>>>>  [java] at
>>>>> com.sun.naming.internal

Re: [Dev] ESB 4.9.0 JSM client error

[Ravi Undupitiya]

Hi Aruna,

ActiveMQ jars are not required to connect to MB. Would you happen to have
ActiveMQ context factory set in some config file?


On Tue, May 10, 2016 at 2:24 PM, Aruna Karunarathna  wrote:

> Hi Jagath,
>
> Thanks for the reply, No I haven't setup ActiveMQ, instead I've followed
> instructions in [1] to configure with WSO2MB, and it doesn't mention to add
> ActiveMQ jars,
>
> After adding the mentioned jars resolved the issue.
>
> Isn't it better to add as a prerequisite before configuring MB?.
>
> [1].
> https://docs.wso2.com/display/ESB490/Configure+with+WSO2+Message+Broker
>
> Regards,
> Aruna
>
> On Tue, May 10, 2016 at 2:01 PM, Jagath Sisirakumara Ariyarathne <
> jaga...@wso2.com> wrote:
>
>> Hi Aruna,
>>
>> Did you add required jar files to lib folder as mentioned in[1].
>>
>> [1] - https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ
>>
>> Thanks.
>>
>> On Tue, May 10, 2016 at 1:39 PM, Aruna Karunarathna 
>> wrote:
>>
>>> Hi ESB team,
>>>
>>> When trying to invoke the JMSClient [1] getting the below error. Seems
>>> like the activemq jar is not present in the classpath.
>>>
>>>  ant jmsclient -Djms_type=pox -Djms_dest=dynamicQueues/StockQuoteProxy
>>> -Djms_payload=MSFT
>>> Buildfile: /home/aruna//wso2esb-4.9.0/samples/axis2Client/build.xml
>>>
>>> init:
>>>
>>> compile:
>>>
>>> jmsclient:
>>>  [java] Exception in thread "main"
>>> javax.naming.NoInitialContextException: Cannot instantiate class:
>>> org.apache.activemq.jndi.ActiveMQInitialContextFactory [Root exception is
>>> java.lang.ClassNotFoundException:
>>> org.apache.activemq.jndi.ActiveMQInitialContextFactory]
>>>  [java] at
>>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:674)
>>>  [java] at
>>> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
>>>  [java] at javax.naming.InitialContext.init(InitialContext.java:242)
>>>  [java] at
>>> javax.naming.InitialContext.(InitialContext.java:216)
>>>  [java] at samples.userguide.GenericJMSClient.connect(Unknown
>>> Source)
>>>  [java] at samples.userguide.GenericJMSClient.main(Unknown Source)
>>>  [java] Caused by: java.lang.ClassNotFoundException:
>>> org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>>  [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
>>>  [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
>>>  [java] at java.security.AccessController.doPrivileged(Native
>>> Method)
>>>  [java] at
>>> java.net.URLClassLoader.findClass(URLClassLoader.java:354)
>>>  [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>>>  [java] at
>>> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
>>>  [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>>>  [java] at java.lang.Class.forName0(Native Method)
>>>  [java] at java.lang.Class.forName(Class.java:270)
>>>  [java] at
>>> com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:72)
>>>  [java] at
>>> com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:61)
>>>  [java] at
>>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
>>>  [java] ... 5 more
>>>  [java] Java Result: 1
>>>
>>> BUILD SUCCESSFUL
>>>
>>> [1]. https://docs.wso2.com/display/ESB490/JMS+Transactions
>>>
>>> Regards,
>>> Aruna
>>> --
>>>
>>> *Aruna Sujith Karunarathna *
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>> Email: ar...@wso2.com | Web: www.wso2.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Jagath Ariyarathne
>> Technical Lead
>> WSO2 Inc.  http://wso2.com/
>> Email: jaga...@wso2.com
>> Mob  : +94 77 386 7048
>>
>>
>
>
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Synapse] Odd behavior in picking the API definition with the correct version, in Synapse 2.1.3.wso2v3

[Ravi Undupitiya]

>>>> http://ws.apache.org/ns/synapse"; name="_WSO2AMRevokeAPI_"
>>>>> context="/revoke">
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> https://localhost:9443/oauth2/revoke
>>>>> "/>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> >>>> class="org.wso2.carbon.appmgt.gateway.handlers.ext.APIManagerCacheExtensionHandler"/>
>>>>> 
>>>>> 
>>>>>
>>>>> http://ws.apache.org/ns/synapse";
>>>>>  name="_WSO2AMStatisticsAPI_"
>>>>>  transports="http"
>>>>>  context="/statistics">
>>>>>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>
>>>>>
>>>>>  
>>>>>
>>>>> 
>>>>>
>>>>> 
>>>>> 
>>>>>
>>>>> http://ws.apache.org/ns/synapse";
>>>>> name="_WSO2APPMTokenAPI_" context="/token">
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> https://localhost:9443/appmoauth2/token"/>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> >>>> class="org.wso2.carbon.appmgt.gateway.handlers.ext.APIManagerCacheExtensionHandler"/>
>>>>> 
>>>>> 
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Rushmin Fernando*
>>>>> *Technical Lead*
>>>>>
>>>>> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware
>>>>>
>>>>> email : rush...@wso2.com
>>>>> mobile : +94772310855
>>>>>
>>>>>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Malintha Amarasinghe
>>>> Software Engineer
>>>> *WSO2, Inc. - lean | enterprise | middleware*
>>>> http://wso2.com/
>>>>
>>>> Mobile : +94 712383306
>>>>
>>>
>>>
>>>
>>> --
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware
>>>
>>> email : rush...@wso2.com
>>> mobile : +94772310855
>>>
>>>
>>>
>>
>>
>> --
>> --
>> Chanaka Fernando
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 773337238
>> Blog : http://soatutorials.blogspot.com
>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>> Twitter:https://twitter.com/chanakaudaya
>> Wordpress:http://chanakaudaya.wordpress.com
>>
>>
>>
>>
>


-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Improving URI Template support in HTTP Endpoint

[Ravi Undupitiya]

Hi all,

Currently with the HTTP Endpoint it is difficult to handle a large set of
query parameters, and this is doubly so when we have to handle individual
query params when running into encoding related issues.

As an example ESB connectors handle query parameters by using script
mediator to create a long query param string and then passing this on to
the HTTP Endpoint.

The underlying library we use for URI Templates support RFC 6570 including
{?param*} operators which when provided with a map will handle the query
parameters in a cleaner way allowing to group a set of parameters without
having to worry about escaping things like & delimiter.

In addition to this, there are several more operators that can only be
supported by passing a map including: {+param*}, {list*}, {&list*}.

Based on this shall we enable support for these operators in HTTP Endpoint?

We can provide this functionality in the following manner (which is the
least intrusive when we consider changes in dev studio and synapse):

Similar to uri.var prefixed properties we have
uri.map... This will allow us to generate a set of
maps with a unique map name that we can then use to pass onto to the
template library.



http://"; />





Above will result in:
http://localhost:8280/services/Position?lng=80%C2%B0%2013%27%2019.8048%27%27%20E&lat=7%C2%B0%207%27%202.0820%27%27%20N



Thanks,
-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Automation Test coverage of ESB 4.9.0 new features

[Ravi Undupitiya]

For HTTP HEAD Method support for REST API's you can find the integration
test at:
https://github.com/wso2/product-esb/blob/master/modules/integration/tests-integration/tests-service/src/test/java/org/wso2/carbon/esb/rest/test/api/APIHeadMethod.java

On Fri, Jul 10, 2015 at 10:12 AM, Asanthi Kulasinghe 
wrote:

> Hi  ESB Team,
>
> We are currently in the process of analyzing gaps between ESB 4.9.0
> manually executed and automated test cases.
> As a start we are looking into to the automation test case coverage of
> 4.9.0 specific new features.
> Out of the feature list from [1] we couldn't find automation tests for
> some of the features mentioned below.
>
> *Features with automation tests*
>
>- Add RabbitMQ transport receiver/sender
>- Persisting Messages from ESB Message Store {jdbc storage to work
>with MSSQL}
>- Supporting Class mediators in Stratos
>- OCSP/CRL Validation at Transport Listener
>- Enabling HTTP Cache Control headers (Etag, etc)
>- Coordination support for Message Stores and Processors
>- For-each mediator
>- Inbound Endpoints :
>
>- Inbound HL7 Endpoint
>- HTTP Inbound Endpoint
>- HTTPS Inbound Endpoint
>- HTTPS Inbound Endpoint
>- CXF WS-RM Inbound Endpoint
>- JMS
>- File
>- Custom
>
> *Features without automation tests*
>
>- Dynamic SSL Profiles for sender and listener
>- Support HTTP Patch
>- HTTP HEAD Method support for REST API's
>- Inbound Endpoints:
>
>   - Kafka support in ESB
>   - MQTT Inbound transport
>
> To my understanding there are tests for some of the above features that
> are yet to be merged.
> Could you please confirm the accuracy of the above lists (automation test
> availability)  and reason for the absence of automation tests for certain
> features  (Eg:  Not yet merged,  Automation is not possible  etc)
>
> [1] https://redmine.wso2.com/versions/43
>
>
> Thanks & Regards
> *Asanthi Kulasinghe*
> WSO2 Inc; http://www.wso2.com/.
> Mobile: +94777355522
>
>
>


-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Automation Test coverage of ESB 4.9.0 new features

[Ravi Undupitiya]

Hi Asanthi,

For HTTP HEAD method we didn't have client support when this feature was
done, but Chanaka has built a client with this support for HTTP PATCH. I'll
use this to create a test case and let you know.


On Fri, Jul 10, 2015 at 10:12 AM, Asanthi Kulasinghe 
wrote:

> Hi  ESB Team,
>
> We are currently in the process of analyzing gaps between ESB 4.9.0
> manually executed and automated test cases.
> As a start we are looking into to the automation test case coverage of
> 4.9.0 specific new features.
> Out of the feature list from [1] we couldn't find automation tests for
> some of the features mentioned below.
>
> *Features with automation tests*
>
>- Add RabbitMQ transport receiver/sender
>- Persisting Messages from ESB Message Store {jdbc storage to work
>with MSSQL}
>- Supporting Class mediators in Stratos
>- OCSP/CRL Validation at Transport Listener
>- Enabling HTTP Cache Control headers (Etag, etc)
>- Coordination support for Message Stores and Processors
>- For-each mediator
>- Inbound Endpoints :
>
>- Inbound HL7 Endpoint
>- HTTP Inbound Endpoint
>- HTTPS Inbound Endpoint
>- HTTPS Inbound Endpoint
>- CXF WS-RM Inbound Endpoint
>- JMS
>- File
>- Custom
>
> *Features without automation tests*
>
>- Dynamic SSL Profiles for sender and listener
>- Support HTTP Patch
>- HTTP HEAD Method support for REST API's
>- Inbound Endpoints:
>
>   - Kafka support in ESB
>   - MQTT Inbound transport
>
> To my understanding there are tests for some of the above features that
> are yet to be merged.
> Could you please confirm the accuracy of the above lists (automation test
> availability)  and reason for the absence of automation tests for certain
> features  (Eg:  Not yet merged,  Automation is not possible  etc)
>
> [1] https://redmine.wso2.com/versions/43
>
>
> Thanks & Regards
> *Asanthi Kulasinghe*
> WSO2 Inc; http://www.wso2.com/.
> Mobile: +94777355522
>
>
>


-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2-uri-templates (1.6.4) public git repository

[Ravi Undupitiya]

Hi Kevin/Sanjeewa,

As per the discussion on this in the other thread, we have now moved
wso2-uri-templates into synapse.
https://github.com/wso2/wso2-synapse/pull/245


Thanks,
Ravi

On Tue, Jun 9, 2015 at 2:33 PM, Sanjeewa Malalgoda 
wrote:

> AFAIR latest uri-template version is 1.6.5(released on svn). So we may
> need to get that to git and release(we may do as a part of commons).
> Please run all unit tests before merge fixes. Also add tests to cover your
> use case.
>
> Thanks,
> sanjeewa.
>
> On Tue, Jun 9, 2015 at 2:03 PM, Isuru Udana  wrote:
>
>> Hi,
>>
>> 1.6.4 version was released from svn.
>> Is this available in somewhere in git ? Or else do we need to bring it
>> into in git ?
>>
>>
>> Thanks.
>>
>>
>> On Tue, Jun 9, 2015 at 1:57 PM, Kevin Ratnasekera  wrote:
>>
>>> Hi all,
>>> I need some fixes to be included with $subject with related to public
>>> jira[1]. Where can I find the released version of $subject?
>>> [1]https://wso2.org/jira/browse/ESBJAVA-3751
>>> Regards
>>> Kevin
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Isuru Udana*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>>
>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
>  <http://sanjeewamalalgoda.blogspot.com/>blog
> :http://sanjeewamalalgoda.blogspot.com/
> <http://sanjeewamalalgoda.blogspot.com/>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] NDatasource stub and class loading issue

[Ravi Undupitiya]

Hi All,

There's a class loading issue affecting ESB described in [1]. This has
happened due to changes in [2].

We can fix this issue using [3] however kernel team suggests the fix in [2]
breaks the package naming convention used as per other UI stubs. @Manoj has
more details on this.

Please advise whether we should go ahead with fix in [3].


[1] https://wso2.org/jira/browse/ESBJAVA-3734
[2]
https://github.com/wso2/carbon-commons/commit/3cb5ee0b3f3086fb0e300e2bae7a91f7b365f197
[3] https://github.com/wso2/carbon-commons/pull/103/files



Thanks,
-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Should serialize method of a Mediator throw an exception on input invalidation ?

[Ravi Undupitiya]

Hi Nirmal,

You can use handleException method in AbstractMediatorSerializer which
already does this.


Thanks,
Ravi

On Wed, Jun 24, 2015 at 10:19 AM, Nirmal Fernando  wrote:

> Hi,
>
> $subject please. If so what's the exception type it should throw?
>
> --
>
> Thanks & regards,
> Nirmal
>
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.9.0 with carbon-commons 4.4.2

[Ravi Undupitiya]

Hi Manoj,

Some thing else we noticed was that we had xercesImpl jar in pack with
commons-4.4.1 and we did not see that error (this pack is located in [1]).


[1]
https://svn.wso2.com/wso2/custom/projects/scratch/ravi/wso2esb-4.9.0-ALPHA-SNAPSHOT.zip


Ravi

On Thu, May 21, 2015 at 3:18 PM, Isuru Udana  wrote:

> IS also packing the same bundle. Are they also facing the same issue ?
> Actually we packed this jar from entitlement.mediator feature since
> entitlement.proxy (in carbon-identity) requires it.
>
> On Thu, May 21, 2015 at 3:10 PM, Manoj Kumara  wrote:
>
>> Hi Ravi,
>>
>> I manually deleted 'xercesImpl_2.8.1.wso2v2.jar' from the pack and things
>> seems to be working fine. You may required to bundle that one. I think the
>> root course is it export unnecessary packages and this cause issue.
>>
>> Regards,
>> Manoj
>>
>>
>> *Manoj Kumara*
>> Software Engineer
>> WSO2 Inc. http://wso2.com/
>> *lean.enterprise.middleware*
>> Mobile: +94713448188
>>
>> On Thu, May 21, 2015 at 2:59 PM, Ravi Undupitiya  wrote:
>>
>>> Hi Manoj,
>>>
>>> You can find the pack at [1].
>>>
>>> [1]
>>> https://svn.wso2.com/wso2/custom/projects/scratch/ravi/commons-4.4.2/wso2esb-4.9.0-M8-SNAPSHOT.zip
>>>
>>> On Thu, May 21, 2015 at 2:54 PM, Manoj Kumara  wrote:
>>>
>>>> Hi Ravi,
>>>>
>>>> Can you share a ESB server.
>>>>
>>>> Regards,
>>>> Manoj
>>>>
>>>>
>>>> *Manoj Kumara*
>>>> Software Engineer
>>>> WSO2 Inc. http://wso2.com/
>>>> *lean.enterprise.middleware*
>>>> Mobile: +94713448188
>>>>
>>>> On Thu, May 21, 2015 at 2:49 PM, Ravi Undupitiya  wrote:
>>>>
>>>>> We're also seeing this error when trying to upload a CApp after
>>>>> upgrade to carbon-commons 4.4.2.
>>>>>
>>>>> [2015-05-21 14:07:31,654]  INFO - ApplicationManager Deploying Carbon
>>>>> Application : esb-test_1.0.0.car...
>>>>> [2015-05-21 14:07:32,797] ERROR - CappAxis2Deployer Error while
>>>>> deploying carbon application
>>>>> /home/wso2builder/WSO2/product-esb/modules/distribution/target/wso2esb-4.9.0-M8-SNAPSHOT/repository/deployment/server/carbonapps/esb-test_1.0.0.car
>>>>> java.lang.NullPointerException
>>>>> at
>>>>> org.wso2.carbon.application.deployer.AppDeployerUtils.areAllFeaturesInstalled(AppDeployerUtils.java:610)
>>>>> at
>>>>> org.wso2.carbon.application.deployer.AppDeployerUtils.buildAcceptanceList(AppDeployerUtils.java:634)
>>>>> at
>>>>> org.wso2.carbon.application.deployer.handler.DefaultAppDeployer.isAccepted(DefaultAppDeployer.java:214)
>>>>> at
>>>>> org.wso2.carbon.application.deployer.handler.DefaultAppDeployer.deployRecursively(DefaultAppDeployer.java:152)
>>>>> at
>>>>> org.wso2.carbon.application.deployer.handler.DefaultAppDeployer.deployArtifacts(DefaultAppDeployer.java:69)
>>>>> at
>>>>> org.wso2.carbon.application.deployer.internal.ApplicationManager.deployCarbonApp(ApplicationManager.java:263)
>>>>> at
>>>>> org.wso2.carbon.application.deployer.CappAxis2Deployer.deploy(CappAxis2Deployer.java:72)
>>>>> at
>>>>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>>>>> at
>>>>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
>>>>> at
>>>>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>>>>> at
>>>>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>>>>> at
>>>>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>>>>> at
>>>>> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
>>>>> at
>>>>> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
>>>>> at
>>>>> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
>>>>> at
>>>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
>>>>> at
>>>>> org.wso2.carbon.core.deployment.CarbonDe

Re: [Dev] ESB 4.9.0 with carbon-commons 4.4.2

[Ravi Undupitiya]

Hi Manoj,

You can find the pack at [1].

[1]
https://svn.wso2.com/wso2/custom/projects/scratch/ravi/commons-4.4.2/wso2esb-4.9.0-M8-SNAPSHOT.zip

On Thu, May 21, 2015 at 2:54 PM, Manoj Kumara  wrote:

> Hi Ravi,
>
> Can you share a ESB server.
>
> Regards,
> Manoj
>
>
> *Manoj Kumara*
> Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94713448188
>
> On Thu, May 21, 2015 at 2:49 PM, Ravi Undupitiya  wrote:
>
>> We're also seeing this error when trying to upload a CApp after upgrade
>> to carbon-commons 4.4.2.
>>
>> [2015-05-21 14:07:31,654]  INFO - ApplicationManager Deploying Carbon
>> Application : esb-test_1.0.0.car...
>> [2015-05-21 14:07:32,797] ERROR - CappAxis2Deployer Error while deploying
>> carbon application
>> /home/wso2builder/WSO2/product-esb/modules/distribution/target/wso2esb-4.9.0-M8-SNAPSHOT/repository/deployment/server/carbonapps/esb-test_1.0.0.car
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.application.deployer.AppDeployerUtils.areAllFeaturesInstalled(AppDeployerUtils.java:610)
>> at
>> org.wso2.carbon.application.deployer.AppDeployerUtils.buildAcceptanceList(AppDeployerUtils.java:634)
>> at
>> org.wso2.carbon.application.deployer.handler.DefaultAppDeployer.isAccepted(DefaultAppDeployer.java:214)
>> at
>> org.wso2.carbon.application.deployer.handler.DefaultAppDeployer.deployRecursively(DefaultAppDeployer.java:152)
>> at
>> org.wso2.carbon.application.deployer.handler.DefaultAppDeployer.deployArtifacts(DefaultAppDeployer.java:69)
>> at
>> org.wso2.carbon.application.deployer.internal.ApplicationManager.deployCarbonApp(ApplicationManager.java:263)
>> at
>> org.wso2.carbon.application.deployer.CappAxis2Deployer.deploy(CappAxis2Deployer.java:72)
>> at
>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
>> at
>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>> at
>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>> at
>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>> at
>> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
>> at
>> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
>> at
>> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
>> at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
>> at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> On Thu, May 21, 2015 at 2:36 PM, Ravi Undupitiya  wrote:
>>
>>> Hi all,
>>>
>>> We upgraded carbon-commons to 4.4.2 and we are getting [1] when loading
>>> the carbon console.
>>>
>>> [1] Stack Trace
>>> [2015-05-21 14:00:56,449]  INFO - CarbonUIServiceComponent Mgt Console
>>> URL  : https://10.100.0.22:10343/carbon/
>>> [2015-05-21 14:01:32,657] ERROR - ApplicationDispatcher
>>> Servlet.service() for servlet bridgeservlet threw exception
>>> java.lang.ClassCastException:
>>> org.apache.xerces.jaxp.DocumentBuilderFactoryImpl cannot be cast to
>>> javax.xml.parsers.DocumentBuilderFactory
>>> at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
>>> at
>>> org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:115)
>>> at
>>> org.apache.jasper.compiler.JspConfig.processWebDotXml(JspConfig.java:95)
>>> at org.apache.jasper.compiler.JspConfig.init(JspConfig.java:243)
>>> at
>>> org.apache.jasper.compiler.JspConfig.findJspProperty(JspConfig.java:302)
>>> at org.apache.jasper.

Re: [Dev] ESB 4.9.0 with carbon-commons 4.4.2

[Ravi Undupitiya]

We're also seeing this error when trying to upload a CApp after upgrade to
carbon-commons 4.4.2.

[2015-05-21 14:07:31,654]  INFO - ApplicationManager Deploying Carbon
Application : esb-test_1.0.0.car...
[2015-05-21 14:07:32,797] ERROR - CappAxis2Deployer Error while deploying
carbon application
/home/wso2builder/WSO2/product-esb/modules/distribution/target/wso2esb-4.9.0-M8-SNAPSHOT/repository/deployment/server/carbonapps/esb-test_1.0.0.car
java.lang.NullPointerException
at
org.wso2.carbon.application.deployer.AppDeployerUtils.areAllFeaturesInstalled(AppDeployerUtils.java:610)
at
org.wso2.carbon.application.deployer.AppDeployerUtils.buildAcceptanceList(AppDeployerUtils.java:634)
at
org.wso2.carbon.application.deployer.handler.DefaultAppDeployer.isAccepted(DefaultAppDeployer.java:214)
at
org.wso2.carbon.application.deployer.handler.DefaultAppDeployer.deployRecursively(DefaultAppDeployer.java:152)
at
org.wso2.carbon.application.deployer.handler.DefaultAppDeployer.deployArtifacts(DefaultAppDeployer.java:69)
at
org.wso2.carbon.application.deployer.internal.ApplicationManager.deployCarbonApp(ApplicationManager.java:263)
at
org.wso2.carbon.application.deployer.CappAxis2Deployer.deploy(CappAxis2Deployer.java:72)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

On Thu, May 21, 2015 at 2:36 PM, Ravi Undupitiya  wrote:

> Hi all,
>
> We upgraded carbon-commons to 4.4.2 and we are getting [1] when loading
> the carbon console.
>
> [1] Stack Trace
> [2015-05-21 14:00:56,449]  INFO - CarbonUIServiceComponent Mgt Console URL
>  : https://10.100.0.22:10343/carbon/
> [2015-05-21 14:01:32,657] ERROR - ApplicationDispatcher Servlet.service()
> for servlet bridgeservlet threw exception
> java.lang.ClassCastException:
> org.apache.xerces.jaxp.DocumentBuilderFactoryImpl cannot be cast to
> javax.xml.parsers.DocumentBuilderFactory
> at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> at
> org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:115)
> at org.apache.jasper.compiler.JspConfig.processWebDotXml(JspConfig.java:95)
> at org.apache.jasper.compiler.JspConfig.init(JspConfig.java:243)
> at org.apache.jasper.compiler.JspConfig.findJspProperty(JspConfig.java:302)
> at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:115)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:374)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:354)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:341)
> at
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:657)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAli

[Dev] ESB 4.9.0 with carbon-commons 4.4.2

[Ravi Undupitiya]

va:727)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)



-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712
<%2B94%C2%A0772%20930%20712>*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] ESB develop branch build fails.

[Ravi Undupitiya]

Hi Iqbal,

We're in the middle of a release and fixing these issues at the moment.


Thanks

On Fri, May 15, 2015 at 4:56 PM, Irham Iqbal  wrote:

> Hi,
>
> I am getting the following BUILD FAILURE when building esb[1] from develop
> branch. I have build the carbon mediator[2] develop branch before building
> esb.
>
> [1] https://github.com/wso2/product-esb
> [2] https://github.com/wso2/carbon-mediation/
>
>
> Installing org.apache.axis2.transport.xmpp.feature.group 1.1.0.wso2v14.
>
> Installing org.apache.axis2.transport.rabbitmq.feature.group 1.1.0.wso2v14.
>
> Installation failed.Cannot complete the install because one or more
> required items could not be found.
>
>  Software being installed: WSO2 Carbon - Mediation Admin Features
> 4.4.1.SNAPSHOT (org.wso2.carbon.mediation.admin.feature.group
> 4.4.1.SNAPSHOT)
>
>  Missing requirement: WSO2 Carbon - Mediation Initializer Server Feature
> 4.4.1.SNAPSHOT (org.wso2.carbon.mediation.initializer.server.feature.group
> 4.4.1.SNAPSHOT) requires 'org.wso2.carbon.event.server.feature.group
> [4.4.1,4.5.0)' but it could not be found
>
>  Cannot satisfy dependency:
>
>   From: WSO2 Carbon - Mediation Admin Features 4.4.1.SNAPSHOT
> (org.wso2.carbon.mediation.admin.feature.group 4.4.1.SNAPSHOT)
>
>   To: org.wso2.carbon.mediation.initializer.server.feature.group
> [4.4.1.SNAPSHOT,4.5.0)
>
> Application failed, log file location:
> /Users/irham/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1431684607601.log
>
>
> [INFO]
> 
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] WSO2 ESB - Aggregator Module .. SUCCESS [0.605s]
>
> [INFO] WSO2 ESB - Styles Parent .. SUCCESS [0.023s]
>
> [INFO] WSO2 ESB - Styles . SUCCESS [1.412s]
>
> [INFO] WSO2 ESB - Samples Parent . SUCCESS [0.020s]
>
> [INFO] WSO2 ESB - Samples  SUCCESS [4.275s]
>
> [INFO] WSO2 ESB - Features Parent  SUCCESS [0.018s]
>
> [INFO] WSO2 ESB - Features Aggregator Module . SUCCESS [0.015s]
>
> [INFO] WSO2 ESB - Styles Features  SUCCESS [0.835s]
>
> [INFO] WSO2 ESB - Samples Features ... SUCCESS [0.411s]
>
> [INFO] WSO2 ESB - P2 Profile Generation .. FAILURE
> [22.683s]
>
> [INFO] WSO2 ESB - Distribution ... SKIPPED
>
> Thanks,
> Iqbal
> --
> Irham Iqbal
> Software Engineer - Test Automation
>  WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
> phone: +94 777888452
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Reading zip file form VFS

[Ravi Undupitiya]

Hi Manuranga,

You can place the file connector inside a scheduled task.

On Tue, Apr 28, 2015 at 9:42 AM, Manuranga Perera  wrote:

> But then how does the proxy get started ?
> On 28 Apr 2015 09:40, "Malaka Silva"  wrote:
>
>> Hi,
>>
>> IMO you can write a connector to the job. It'll be similar to file
>> connector. [1]
>>
>> Anyway message is already build when it's invoking the class mediator.
>>
>> [1]
>> https://storepreview.wso2.com/store/assets/esbconnector/f0550184-88c4-4d5e-b73f-ea51b1b5ab98
>>
>> On Mon, Apr 27, 2015 at 5:58 PM, Manuranga Perera  wrote:
>>
>>> I am reading a zip file from VFS transport. I need to read and merge all
>>> the files in the zip (from a custom mediator).
>>>
>>> I can write the unzip logic in my custom mediator by reading the zip
>>> file as a byte stream. but is there a better way to do this?
>>> --
>>> With regards,
>>> *Manu*ranga Perera.
>>>
>>> phone : 071 7 70 20 50
>>> mail : m...@wso2.com
>>>
>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> <http://wso2.com/about/team/malaka-silva/>
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Senduran Balasubramaniyam

[Ravi Undupitiya]

Congratulations Senduran!

On Wed, Feb 18, 2015 at 3:36 AM, Kasun Indrasiri  wrote:

> Hi devs,
>
> Its my pleasure to welcome Senduran Balasubramaniyam as a WSO2 Committer.
>
> Senduran, welcome aboard and keep up the good work!
>
> Thanks.
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Buddhima Wijeweera

[Ravi Undupitiya]

Congratulations Buddhima!!

On Mon, Dec 29, 2014 at 7:55 AM, Kasun Indrasiri  wrote:

> Hi devs,
>
> Its my pleasure to welcome Buddhima Wijeweera as a WSO2 Committer.
>
> Buddhima, welcome aboard and keep up the good work.
>
> Thanks.
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Sandamal Weerasinghe

[Ravi Undupitiya]

Congratulations Sandamal!!

On Mon, Dec 29, 2014 at 7:54 AM, Kasun Indrasiri  wrote:

> Hi devs,
>
> Its my pleasure to welcome Sandamal Weerasinghe as a WSO2 Committer.
>
> Sandamal, welcome aboard and keep up the good work.
>
> Thanks.
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Isuru Ranawaka

[Ravi Undupitiya]

t;> Data & APIs Technologies Team
>>>>>>>>> Mobile : +94 773922820
>>>>>>>>>
>>>>>>>>> <http://stackoverflow.com/users/515034>
>>>>>>>>> <http://lk.linkedin.com/in/abimaran>
>>>>>>>>> <http://www.lkabimaran.blogspot.com/>
>>>>>>>>> <https://github.com/abimaran>  <https://twitter.com/abimaran>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ___
>>>>>>>>> Dev mailing list
>>>>>>>>> Dev@wso2.org
>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Chamin Nalinda*
>>>>>>>>
>>>>>>>> Intern - Engineering
>>>>>>>> WSO2 Inc. http://www.wso2.com
>>>>>>>> lean.enterprise.middleware
>>>>>>>>
>>>>>>>> Mobile: (+94) 77 241 66 04
>>>>>>>> Linkedin: https://www.linkedin.com/in/chaminnalinda
>>>>>>>> Web: http://www.ckreativity.com
>>>>>>>> Blog: http://techspiro.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>> ___
>>>>>>>> Dev mailing list
>>>>>>>> Dev@wso2.org
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Milinda Perera
>>>>>>> Software Engineer;
>>>>>>> WSO2 Inc. http://wso2.com ,
>>>>>>> Mobile: (+94) 714 115 032
>>>>>>>
>>>>>>>
>>>>>>> ___
>>>>>>> Dev mailing list
>>>>>>> Dev@wso2.org
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Prasanna Dangalla
>>>>>> Software Engineer, WSO2, Inc.; http://wso2.com/
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> cell: +94 777 55 80 30 | +94 718 11 27 51
>>>>>> twitter: @prasa77
>>>>>>
>>>>>> ___
>>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Shashika Prabath Karunatilaka,
>>>> Software Engineer,
>>>> WSO2, Inc: http://wso2.com/
>>>> mobile : +94 77 7487792
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Priya Kishok
>>> Software Engineer
>>> WSO2, Inc : http://wso2.com
>>> Mob : +94774457404
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Niranda Perera*
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-71-554-8430
>> Twitter: @n1r44 <https://twitter.com/N1R44>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618
> Blog:harshcreationz.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 App Manager Latest Build - 2014-06-09

[Ravi Undupitiya]

https://svn.wso2.org/repos/wso2/people/ravi/appm/09-06-2014-wso2appmanager-1.0.0.zip


Thanks
-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712
<%2B94%C2%A0772%20930%20712>*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 App Manager - Latest Build 2014-06-03

[Ravi Undupitiya]

Latest pack:
https://svn.wso2.org/repos/wso2/people/ravi/appm/03-06-2014-wso2appmanager-1.0.0.zip


Thanks

-- 
*Ravi Undupitiya*
Senior Software Engineer; WSO2 http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in invoking APIs with POST request (with different content types)

[Ravi Undupitiya]

Hi Kasun,

At present the Axis2FlexibleMEPClient detects a REST request by checking
the HTTP method used and if the content type belongs to any of the
following:
application/xml
application/x-www-form-urlencoded
multipart/form-data
application/json

If the HTTP method is anything other than POST - then the request is
assumed to be REST.
If it is a POST, it checks to see if the messageType is one of the above.

IMO these criteria aren't enough to decide if a request is REST.

I'll look into see if we can find a better way to do this.

Thanks

On Tue, May 13, 2014 at 7:18 PM, Kasun Indrasiri  wrote:

> -1
> HTTP EP is designed for outbound REST calls. So putting format=rest, is
> meaningless and hinders its whole purpose. We need to find a better
> alternative. May be we have to filter-out SOAP vs POX at the
> Axis2FlexibleMEPClient level ?
>
>
> On Wed, May 14, 2014 at 1:25 AM, Ravi Undupitiya  wrote:
>
>> Hi guys,
>>
>> Looks like format support is already there for HTTP Endpoint - just not
>> in the UI. We can add the attribute format="rest" to solve this issue. :)
>>
>>
>> Thanks
>>
>>
>> On Tue, May 13, 2014 at 6:51 PM, Ravi Undupitiya  wrote:
>>
>>> Hello all,
>>>
>>> Isuru and I had a look at this, and we found the reason for this
>>> behaviour is to do with the isRest property not being set to true - by
>>> default when we send text/xml we assume that the invocation is not rest and
>>> therefor is a SOAP service invocation.
>>>
>>> The problem with this is that a valid REST invocation can also look like
>>> a SOAP invocation when the deciding factor is only the content type.
>>>
>>> To work around this the address endpoints have the format attribute
>>> where we can set format=rest. HTTP Endpoints don't have a mechanism to set
>>> the format at present.
>>>
>>> Shall we include the ability to set the format in HTTP Endpoint? Is this
>>> a correct fix?
>>>
>>>
>>> Thanks
>>>
>>>
>>>  On Wed, May 7, 2014 at 6:59 PM, Sanjeewa Malalgoda 
>>> wrote:
>>>
>>>> Hi,
>>>> We observed following behavior in API Manager 1.7.0 which built on top
>>>> of synapse 2.1.2.wso2v5. We sent same request to API created by fronting
>>>> basic jaxrs service. Only difference is setting 2 content types. Backend
>>>> service support both content types and we can invoke it without any issue.
>>>>
>>>> 01. Content-Type: text/xml
>>>> [2014-05-07 18:36:31,114] DEBUG - headers http-outgoing-6 >> POST
>>>> http://10.100.1.65:9764/jaxrs_basic/services/customers HTTP/1.1
>>>>
>>>> 02. Content-Type: application/xml
>>>> [2014-05-07 18:36:11,805] DEBUG - headers http-outgoing-6 >> POST
>>>> http://10.100.1.65:9764/jaxrs_basic/services/customers/
>>>> *customerservice/customers* HTTP/1.1
>>>>
>>>> When content type is text/xml we can see part of the request is
>>>> dropping. It send request directly to the endpoint defined in API without
>>>> appending other things in client request url. Any idea what went wrong?
>>>>
>>>> Here is my API
>>>>  >>> version-type="url">
>>>> >>> uri-template="/*">
>>>> 
>>>> >>> scope="axis2"/>
>>>> 
>>>> 
>>>> 
>>>> >>> name="admin--jaxrs_APIproductionEndpoint_0">
>>>> http://10.100.1.65:9764/jaxrs_basic/services/customers";>
>>>> 
>>>> 3
>>>>
>>>> fault
>>>> 
>>>> 
>>>> -1
>>>>
>>>> 0
>>>>
>>>> 1.0
>>>>
>>>> 0
>>>> 
>>>> 
>>>> -1
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 

Re: [Dev] Issue in invoking APIs with POST request (with different content types)

[Ravi Undupitiya]

Hi guys,

Looks like format support is already there for HTTP Endpoint - just not in
the UI. We can add the attribute format="rest" to solve this issue. :)


Thanks


On Tue, May 13, 2014 at 6:51 PM, Ravi Undupitiya  wrote:

> Hello all,
>
> Isuru and I had a look at this, and we found the reason for this behaviour
> is to do with the isRest property not being set to true - by default when
> we send text/xml we assume that the invocation is not rest and therefor is
> a SOAP service invocation.
>
> The problem with this is that a valid REST invocation can also look like a
> SOAP invocation when the deciding factor is only the content type.
>
> To work around this the address endpoints have the format attribute where
> we can set format=rest. HTTP Endpoints don't have a mechanism to set the
> format at present.
>
> Shall we include the ability to set the format in HTTP Endpoint? Is this a
> correct fix?
>
>
> Thanks
>
>
> On Wed, May 7, 2014 at 6:59 PM, Sanjeewa Malalgoda wrote:
>
>> Hi,
>> We observed following behavior in API Manager 1.7.0 which built on top
>> of synapse 2.1.2.wso2v5. We sent same request to API created by fronting
>> basic jaxrs service. Only difference is setting 2 content types. Backend
>> service support both content types and we can invoke it without any issue.
>>
>> 01. Content-Type: text/xml
>> [2014-05-07 18:36:31,114] DEBUG - headers http-outgoing-6 >> POST
>> http://10.100.1.65:9764/jaxrs_basic/services/customers HTTP/1.1
>>
>> 02. Content-Type: application/xml
>> [2014-05-07 18:36:11,805] DEBUG - headers http-outgoing-6 >> POST
>> http://10.100.1.65:9764/jaxrs_basic/services/customers/
>> *customerservice/customers* HTTP/1.1
>>
>> When content type is text/xml we can see part of the request is dropping.
>> It send request directly to the endpoint defined in API without appending
>> other things in client request url. Any idea what went wrong?
>>
>> Here is my API
>>  > version-type="url">
>> 
>> 
>> 
>> 
>> 
>> 
>> > name="admin--jaxrs_APIproductionEndpoint_0">
>> http://10.100.1.65:9764/jaxrs_basic/services/customers";>
>> 
>> 3
>>
>> fault
>> 
>> 
>> -1
>>
>> 0
>>
>> 1.0
>>
>> 0
>> 
>> 
>> -1
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> > class="org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler"/>
>> > class="org.wso2.carbon.apimgt.gateway.handlers.throttling.APIThrottleHandler">
>> 
>> > value="gov:/apimgt/applicationdata/tiers.xml"/>
>> 
>> > class="org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageHandler"/>
>> > class="org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler">
>> > value="gov:/apimgt/statistics/ga-config.xml"/>
>> 
>> > class="org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler"/>
>> 
>> 
>>
>> Thanks,
>> sanjeewa.
>> --
>>
>> *Sanjeewa Malalgoda*
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>>  <http://sanjeewamalalgoda.blogspot.com/>blog
>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
>>
>>
>>
>
>
> --
> *Ravi Undupitiya*
> Software Engineer; WSO2 Inc.; http://wso2.com
>
>
> *E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712
> <%2B94%C2%A0772%20930%20712>*
>
> Lean . Enterprise . Middleware
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in invoking APIs with POST request (with different content types)

[Ravi Undupitiya]

Hello all,

Isuru and I had a look at this, and we found the reason for this behaviour
is to do with the isRest property not being set to true - by default when
we send text/xml we assume that the invocation is not rest and therefor is
a SOAP service invocation.

The problem with this is that a valid REST invocation can also look like a
SOAP invocation when the deciding factor is only the content type.

To work around this the address endpoints have the format attribute where
we can set format=rest. HTTP Endpoints don't have a mechanism to set the
format at present.

Shall we include the ability to set the format in HTTP Endpoint? Is this a
correct fix?


Thanks


On Wed, May 7, 2014 at 6:59 PM, Sanjeewa Malalgoda wrote:

> Hi,
> We observed following behavior in API Manager 1.7.0 which built on top
> of synapse 2.1.2.wso2v5. We sent same request to API created by fronting
> basic jaxrs service. Only difference is setting 2 content types. Backend
> service support both content types and we can invoke it without any issue.
>
> 01. Content-Type: text/xml
> [2014-05-07 18:36:31,114] DEBUG - headers http-outgoing-6 >> POST
> http://10.100.1.65:9764/jaxrs_basic/services/customers HTTP/1.1
>
> 02. Content-Type: application/xml
> [2014-05-07 18:36:11,805] DEBUG - headers http-outgoing-6 >> POST
> http://10.100.1.65:9764/jaxrs_basic/services/customers/
> *customerservice/customers* HTTP/1.1
>
> When content type is text/xml we can see part of the request is dropping.
> It send request directly to the endpoint defined in API without appending
> other things in client request url. Any idea what went wrong?
>
> Here is my API
>   version-type="url">
> 
> 
> 
> 
> 
> 
>  name="admin--jaxrs_APIproductionEndpoint_0">
> http://10.100.1.65:9764/jaxrs_basic/services/customers";>
> 
> 3
>
> fault
> 
> 
> -1
>
> 0
>
> 1.0
>
> 0
> 
> 
> -1
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  class="org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler"/>
>  class="org.wso2.carbon.apimgt.gateway.handlers.throttling.APIThrottleHandler">
> 
>  value="gov:/apimgt/applicationdata/tiers.xml"/>
> 
>  class="org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageHandler"/>
>  class="org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler">
>  value="gov:/apimgt/statistics/ga-config.xml"/>
> 
>  class="org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler"/>
> 
> 
>
> Thanks,
> sanjeewa.
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
>  <http://sanjeewamalalgoda.blogspot.com/>blog
> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
>
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Application Manager - Latest Build 2014-05-12

[Ravi Undupitiya]

Please find the latest build at [1].

[1] http://builder1.us1.wso2.org/~appm/12-05-2014/

Latest Build includes several bug fixes and additional improvements:
- Tagging and Rating
- SAML SSO Provider configurator
- Google analytics integration


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 10 - Build Failure in a clean repo

[Ravi Undupitiya]

Small correction:

We have to build [1] and [2] to resolve.

[1]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/ode/1.3.5-wso2v11/<https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/ode/1.3.5-wso2v12/bpel-extensions/e4x>
[2]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/ode/1.3.5-wso2v12/<https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/ode/1.3.5-wso2v12/bpel-extensions/e4x>


On Wed, May 7, 2014 at 10:55 AM, Thilini Ishaka  wrote:

> Hi Ravi,
>
> We'll check on the build failure. Anyway BPS is not going release with
> ch-11. So we'll remove bps related stuffs from the ch-11 build.
> Waruna, please note.
>
> Thanks
> Thilini
>
>
> On Tue, May 6, 2014 at 10:23 PM, Ravi Undupitiya  wrote:
>
>> Hi,
>>
>> Got the same error on a clean repo build of chunk-11. Building [1] fixed.
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/ode/1.3.5-wso2v12/bpel-extensions/e4x
>>
>>
>> On Thu, Apr 24, 2014 at 11:54 PM, Isuru Udana  wrote:
>>
>>> Hi,
>>>
>>> I am getting the following.
>>>
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 2:43.266s
>>> [INFO] Finished at: Thu Apr 24 23:43:23 IST 2014
>>> [INFO] Final Memory: 323M/592M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal on project ode: Could not resolve
>>> dependencies for project org.apache.ode.wso2:ode:bundle:1.3.5.wso2v12: The
>>> following artifacts could not be resolved:
>>> org.wso2.bpel.extensions:ode-bpel-extensions-e4x:jar:1.0.0-wso2v11,
>>> org.wso2.bpel.extensions:ode-bpel-extensions-long-running:jar:1.0.0-wso2v11:
>>> Failure to find
>>> org.wso2.bpel.extensions:ode-bpel-extensions-e4x:jar:1.0.0-wso2v11 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 -> [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/DependencyResolutionException
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with the
>>> command
>>> [ERROR]   mvn  -rf :ode
>>>
>>>
>>> --
>>> *Isuru Udana*
>>>  Senior
>>> * Software Engineer*
>>> WSO2 Inc.; http://wso2.com
>>> email: isu...@wso2.com cell: +94 77 3791887
>>> blog: http://mytecheye.blogspot.com/
>>> twitter: http://twitter.com/isudana
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Ravi Undupitiya*
>>  Software Engineer; WSO2 Inc.; http://wso2.com
>>
>>
>> *E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712
>> <%2B94%C2%A0772%20930%20712>*
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> Thilini Ishaka
> Senior Software Engineer
> Phone: +94 11 214 5345
> WSO2 Inc. http://wso2.com
>
> blog: thiliniishaka.blogspot.com
> linkedin: http://lk.linkedin.com/in/thiliniishaka
> twitter: https://twitter.com/#!/ThiliniIsh
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 10 - Build Failure in a clean repo

[Ravi Undupitiya]

Hi,

Got the same error on a clean repo build of chunk-11. Building [1] fixed.

[1]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/ode/1.3.5-wso2v12/bpel-extensions/e4x


On Thu, Apr 24, 2014 at 11:54 PM, Isuru Udana  wrote:

> Hi,
>
> I am getting the following.
>
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 2:43.266s
> [INFO] Finished at: Thu Apr 24 23:43:23 IST 2014
> [INFO] Final Memory: 323M/592M
> [INFO]
> 
> [ERROR] Failed to execute goal on project ode: Could not resolve
> dependencies for project org.apache.ode.wso2:ode:bundle:1.3.5.wso2v12: The
> following artifacts could not be resolved:
> org.wso2.bpel.extensions:ode-bpel-extensions-e4x:jar:1.0.0-wso2v11,
> org.wso2.bpel.extensions:ode-bpel-extensions-long-running:jar:1.0.0-wso2v11:
> Failure to find
> org.wso2.bpel.extensions:ode-bpel-extensions-e4x:jar:1.0.0-wso2v11 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 -> [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/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :ode
>
>
> --
> *Isuru Udana*
>  Senior
> * Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
> twitter: http://twitter.com/isudana
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Do we need the capability to publish same web application through the multiple applications in AppManager

[Ravi Undupitiya]

Hi Dinusha,

>From the GA perspective, I don't think this is an issue (if I'm
understanding you correctly, sorry if i'm not).

Currently the unique ID sent to google analytics is stored in a cookie that
takes the API name into consideration. So for each app manager app in your
scenario (even if they use the same backend app) there will be two unique
ID's - and hence will be treated as separate invocations (also the document
paths stored will be different - it will be up to the user to identify the
different apps on GA by looking at the paths) .

For both applications, if we use the same tracking code, it doesn't matter
as we create two unique ID's as explained above.


On Thu, May 1, 2014 at 12:06 PM, Dinusha Senanayaka wrote:

>
> Hi,
>
> $subject is something practical (AFAIS).
>
> Say we have a web-app "A". Then we have published two applications in AppM
> by pointing to the web-app "A" as endpoint. If we need to collect stats, we
> need to include the tracking code generated by AppM for that particular
> web-app.
>
> Can we include multiple tracking codes with the js script that we are
> using ? (If we include only single code,then the counters will not be
> correct)
>
> Regards,
> Dinusha.
>
> --
> Dinusha Dilrukshi
> Senior Software Engineer
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.8.1 RC2 Released

[Ravi Undupitiya]

Hi Shavantha,

It's not possible to have two HL7 proxies listening on the same port, since
these are servers, only the first proxy you deploy will bind to the port
and the second proxy should not deploy and it should give an error. Did you
not observe an error when you deployed the second proxy?


Ravi


On Thu, Jan 30, 2014 at 11:15 PM, Shavantha Weerasinghe
wrote:

> Hi Kasun
>
> Need a clarification on the way transport work: If there are 2 active
> proxies listing to the same port for incoming HL7 messages, and if one
> proxy writes to the file system and the second proxy writes to a data
> base, currently if a message comes the message gets delivered via only
> one proxy. In this scenario I am not using clone mediator. Also the
> proxy via which the message was passed was deactivated and reactivated
> then continuously the message seems to go through the proxy which was
> active.
>
> Is this the way axis2 transport works
>
> Regards,
> Shavantha Weerasinghe
> Senior Software Engineer QA
> WSO2, Inc.
> lean.enterprise.middleware.
> http://wso2.com
> http://wso2.org
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
>
>
> On Thu, Jan 30, 2014 at 5:55 PM, Malaka Silva  wrote:
> > http://svn.wso2.org/repos/wso2/people/malaka/ESB/ESB4.8.1/30-01/
> >
> > --
> >
> > Best Regards,
> >
> > Malaka Silva
> > Senior Tech Lead
> > M: +94 777 219 791
> > Tel : 94 11 214 5345
> > Fax :94 11 2145300
> > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> > Blog : http://mrmalakasilva.blogspot.com/
> >
> > WSO2, Inc.
> > lean . enterprise . middleware
> > http://www.wso2.com/
> > http://www.wso2.com/about/team/malaka-silva/
> >
> > Save a tree -Conserve nature & Save the world for your future. Print this
> > email only if it is absolutely necessary.
> >
> > ___
> > 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
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.8.1 pack and p2-repo - 21 Jan

[Ravi Undupitiya]

Hi Shavantha,

You can also test the HL7 Store - please use the pack/repo built this
morning.


Ravi


On Tue, Jan 21, 2014 at 8:33 PM, Shavantha Weerasinghe
wrote:

> Hi Malaka
>
> Are their new hl7 features that can be tested with this release
>
> Upto now we are able to test
> Reading from hl7
> Reading from FTP
> Use threadpool for sender/receiver
> Pass through invalid mesages
>
> Regards,shavantha
> On 21 Jan 2014 18:07, "Malaka Silva"  wrote:
>
>> https://svn.wso2.org/repos/wso2/people/malaka/ESB/ESB4.8.1/21-01/
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/<http://wso2.com/about/team/malaka-silva/>
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Property mediator being URL - encoded on ESB

[Ravi Undupitiya]

The encoding is done by the URI Template library. There was a similar issue
fixed to decode ':' and '/' in HTTP Endpoint. I think the correct fix is to
use a decoding library that will handle all cases.

Some thing like:
URL url = new URL(URLDecoder.decode(template.expand(),
"UTF-8"));
evaluatedUri = url.toURI().toString();

I've added JIRA at [1] to track this issue.

[1] - https://wso2.org/jira/browse/ESBJAVA-2860

On Tue, Dec 31, 2013 at 9:01 AM, indika prasad  wrote:

> (Reposting)
> Hi,
>
> I am using the following Synapse template to query the LinkedIn APIs
> connections endpoint:
>
> http://ws.apache.org/ns/synapse";>
>  description="contains the security information for a login
> session and identifies the user, the users groups, and the users
> privileges"
> />
>  description="fields of the connections that are required to
> be returned" />
>
>
> 
>  />
> expression="$func:accessToken" />
>
> 
>
>   uri-template="
> https://api.linkedin.com/v1/people/~/connections:({uri.var.fields})?oauth2_access_token={uri.var.accessToken}&format=json
> "
> />
> 
> 
>
> 
> 
>
> Here, the uri.var.fields parameter is supposed to be sent as a comma
> separated list such as first-name,last-name,header.
>
> However, when it is sent as a comma-separated list, the comma seems to get
> URL-encoded, causing the service call to fail.
>
> Wire output when sending the fields first-name,last-name:
>
>  DEBUG - wire << "GET
>
> /v1/people/~/connections:(first-name%2Clast-name)?oauth2_access_token=AQWE6N2hAjyHx9LIS6UU_0AktUN9aNN0ZFyIkUNYpSe10Vj559ppL4wur2QBOdCSOLBI3P2MEjHjV-Pz93xrZte3e2XfgrzkB30N5-twK9exifpuucMA5ZgvL7n2bpOx7dFxHfGM2eRfaoao0hKdSW1hnjL7i3GbrCeyrKhUZGECbv7agC4&format=json
> HTTP/1.1[\r][\n]"
>
>
> Is there any way to prevent the comma from getting URL encoded?
>
> Thanks.
>
>
>
> --
> View this message in context:
> http://wso2-oxygen-tank.10903.n7.nabble.com/Property-mediator-being-URL-encoded-on-ESB-tp90214.html
> Sent from the WSO2 Development mailing list archive at Nabble.com.
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue with ESB 4.8 and SoupUI

[Ravi Undupitiya]

Please see https://wso2.org/jira/browse/ESBJAVA-2815 for details on this
issue.


On Sat, Dec 28, 2013 at 3:17 PM, indika prasad  wrote:

> Hi,
>
> I have a issue with below proxy and SoupUI.
>
> Proxy
> 
> 
> http://ws.apache.org/ns/synapse";
>name="souptest"
>transports="https,http"
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>   
>  
> {
>   "contentType":"linkedin-html",
>   "body":"update body"
> }
> 
>  
>   scope="axis2"/>
>  
> 
>http://localhost:8281/services/jsonService";
> format="rest"/>
> 
>  
>   
>
>
> 
>
> 
>
> 01. Using SoupUI with following request send the expected massage to the
> given endpoint.
> http://schemas.xmlsoap.org/soap/envelope/
> "
> >
> soap request-
> 
>
>   aaa
>   
> 
>  
> TCPMon out put-
> POST /services/jsonService HTTP/1.1
> Accept-Encoding: gzip,deflate
> Content-Type: application/json
> SOAPAction:
> Transfer-Encoding: chunked
> Host: 127.0.0.1:8281
> Connection: Keep-Alive
> User-Agent: Synapse-PT-HttpComponents-NIO
>
> 47
> {
> "contentType":"linkedin-html",
> "body":"update body"
> }
> 0
>
> 
>
> 02. Using SoapUI with following request send the strange massage to the
> endpoint. Where the payload has replaced by the second element of the soup
> request!
> --soup request
> http://schemas.xmlsoap.org/soap/envelope/
> "
> >
>
>
>   aaa
>   bbb
>   
> 
> ---
> TCPMon out put-
> POST /services/jsonService HTTP/1.1
> Accept-Encoding: gzip,deflate
> Content-Type: application/json
> SOAPAction:
> Transfer-Encoding: chunked
> Host: 127.0.0.1:8281
> Connection: Keep-Alive
> User-Agent: Synapse-PT-HttpComponents-NIO
>
> c
> {"b1":"bbb"}
> 0
>
> 
>
> Thanks
> Indika
>
>
>
> --
> View this message in context:
> http://wso2-oxygen-tank.10903.n7.nabble.com/Issue-with-ESB-4-8-and-SoupUI-tp90206.html
> Sent from the WSO2 Development mailing list archive at Nabble.com.
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue with ESB 4.8 and SoupUI

[Ravi Undupitiya]

This is a bug. For the time being a work around is to wrap the separate
elements inside a root element like:


  aaa
  bbb





On Sat, Dec 28, 2013 at 3:17 PM, indika prasad  wrote:

> Hi,
>
> I have a issue with below proxy and SoupUI.
>
> Proxy
> 
> 
> http://ws.apache.org/ns/synapse";
>name="souptest"
>transports="https,http"
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>   
>  
> {
>   "contentType":"linkedin-html",
>   "body":"update body"
> }
> 
>  
>   scope="axis2"/>
>  
> 
>http://localhost:8281/services/jsonService";
> format="rest"/>
> 
>  
>   
>
>
> 
>
> 
>
> 01. Using SoupUI with following request send the expected massage to the
> given endpoint.
> http://schemas.xmlsoap.org/soap/envelope/
> "
> >
> soap request-
> 
>
>   aaa
>   
> 
>  
> TCPMon out put-
> POST /services/jsonService HTTP/1.1
> Accept-Encoding: gzip,deflate
> Content-Type: application/json
> SOAPAction:
> Transfer-Encoding: chunked
> Host: 127.0.0.1:8281
> Connection: Keep-Alive
> User-Agent: Synapse-PT-HttpComponents-NIO
>
> 47
> {
> "contentType":"linkedin-html",
> "body":"update body"
> }
> 0
>
> 
>
> 02. Using SoapUI with following request send the strange massage to the
> endpoint. Where the payload has replaced by the second element of the soup
> request!
> --soup request
> http://schemas.xmlsoap.org/soap/envelope/
> "
> >
>
>
>   aaa
>   bbb
>   
> 
> ---
> TCPMon out put-
> POST /services/jsonService HTTP/1.1
> Accept-Encoding: gzip,deflate
> Content-Type: application/json
> SOAPAction:
> Transfer-Encoding: chunked
> Host: 127.0.0.1:8281
> Connection: Keep-Alive
> User-Agent: Synapse-PT-HttpComponents-NIO
>
> c
> {"b1":"bbb"}
> 0
>
> 
>
> Thanks
> Indika
>
>
>
> --
> View this message in context:
> http://wso2-oxygen-tank.10903.n7.nabble.com/Issue-with-ESB-4-8-and-SoupUI-tp90206.html
> Sent from the WSO2 Development mailing list archive at Nabble.com.
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] JSON string in request being reformatted by ESB

[Ravi Undupitiya]

Hi Indika,


This is a JSON to JSON scenario? In that case you can try something like
the following:


http://ws.apache.org/ns/synapse";
   name="TestProxy"
   transports="https,http"
   statistics="disable"
   trace="disable"
   startOnLoad="true">
   
  

 
 
 
 
 

 

{
"contentType":"$1",
"body":"$2"
}


   
   

 

 

 
 

   http://localhost:8281/"/>

 
 
  
  
 
  
   
   




On Thu, Dec 26, 2013 at 7:07 PM, Dushan Abeyruwan  wrote:

> HI
>  Enable wire logs and post the logs
>
>
> On Thu, Dec 26, 2013 at 4:32 PM, indika prasad wrote:
>
>> Reposting:
>>
>> Hi Dushan,
>>
>> Thanks for your response.
>>
>> However, we're seeing the correct output with the proxy you provided, but
>> the request times out with our synapse template + proxy combo.
>>
>> Contents of the template:
>>
>> http://ws.apache.org/ns/synapse"; name="sendActivity">
>>
>>
>>
>>   
>>
>>   
>>
>>   {"contentType":"linkedin-html","body":"hello Test"}
>> 
>>
>>   
>>
>>   > scope="axis2">
>>
>>  > scope="axis2">
>>
>>   
>>
>>  
>>
>> > uri-template="http://localhost:8281/";>
>>
>>  
>>
>>   
>>
>>
>>
>> 
>>
>> Proxy:
>>
>>
>> 
>> http://ws.apache.org/ns/synapse";
>>name="sendActivity"
>>transports="https,http"
>>statistics="disable"
>>trace="disable"
>>startOnLoad="true">
>>
>>   
>>  
>>  
>>  
>>   
>>   
>>  
>>   
>>
>>
>> 
>>
>> The JSON message sent out to TCP Mon is correct now. Copy pasting the TCP
>> mon request headers and body to SoapUI and running as a REST project
>> returns
>> the correct 201 status from the LinkedIn API, so we know this
>> configuration
>> is sending out the correct message. When redirecting the synapse template
>> to
>> LinkedIn by setting the correct URL in it, the request times out. Could
>> this
>> be because LinkedIn is returning an HTTP 201 status?
>>
>>
>>
>> Thanks.
>>
>>
>>
>> --
>> View this message in context:
>> http://wso2-oxygen-tank.10903.n7.nabble.com/JSON-string-in-request-being-reformatted-by-ESB-tp90183p90195.html
>> Sent from the WSO2 Development mailing list archive at Nabble.com.
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> Dushan Abeyruwan | Associate Tech Lead
> Integration Technologies Team
> PMC Member Apache Synpase
> WSO2 Inc. http://wso2.com/
> Blog:http://dushansview.blogspot.com/
> Mobile:(0094)713942042
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB JSON support

[Ravi Undupitiya]

ESB 4.8.0 docs also have updated Property[1], Filter[2], Switch and Log
mediator explaining JSON path usage.  PF mediator docs also contain some
JSON instructions.

[1] - http://docs.wso2.org/display/ESB480/Property+Mediator
[2] - http://docs.wso2.org/display/ESB480/Filter+Mediator
[3] - http://docs.wso2.org/display/ESB480/PayloadFactory+Mediator


On Fri, Dec 20, 2013 at 1:35 PM, Ishan Jayawardena  wrote:

> Hi Samisa,
> I believe you are looking at this [1]. In addition to that the wiki has
> two samples on how to handle JSON within ESB [2] but ESB 4.8.0 has more
> improved support for JSON and we will add more samples covering those areas
> as well.
>
> [1] http://docs.wso2.org/display/ESB480/JSON+Support
> [2] http://docs.wso2.org/display/ESB480/Mediating+JSON+Messages
>
> Thanks,
> Ishan.
>
>
>
> On Fri, Dec 20, 2013 at 12:30 PM, Samisa Abeysinghe wrote:
>
>> Does this doc has all the information on the kind of JSON support we have
>> in the ESB?
>>
>>  Thanks,
>> Samisa...
>>
>>
>> Samisa Abeysinghe
>>
>> Vice President Training
>>
>> WSO2 Inc.
>> http://wso2.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ishan Jayawardena
> Senior Software Engineer
> Mobile: +94 (77) 408 2330
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 getting POST-PUT http parameters

[Ravi Undupitiya]

Hi Ailosha,


The code you're trying is specific to HTTP Servlet's - it may not work if
you're invoking the ESB through nhttp transports on port 8280 (try port
9763).

If you're also working with REST, you might find it easier to work with
API's in WSO2 ESB. Please refer the documentation at
http://docs.wso2.org/display/ESB480/Using+the+REST+API


On Mon, Dec 16, 2013 at 1:39 AM, Aliosha  wrote:

> hi,
> im on WSO2 ESB 4.7/4.8
> i'm trying to create/update a REST resource using POST and PUT verbs in my
> rest uri.
> I have to send a list of some values to (i.e. List1=value1, List2=value2
> ...), os i thought about using POST and PUT http parameter for doing this.
>
> This is the proxy i use:
> 
> http://ws.apache.org/ns/synapse";
>name="DiogeneDynamicEP"
>transports="https,http"
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>   
>   name="it.innovapuglia.sistemapuglia.endpoint.DynamicEndpointConfiguration"/>
>   
>   
>  
>   
>
>
> 
>
> It simply get the request end sends it to my custom mediator.
> In my mediator i have to get the parameters inside the http request but
> i'm facing up with few difficulties.
> I tried this code:
> public boolean mediate(MessageContext synapseMsgContext) {
>  org.apache.axis2.context.MessageContext axis2MsgContext;
> axis2MsgContext = ((Axis2MessageContext)
> synapseMsgContext).getAxis2MessageContext();
>  HttpServletRequest obj = (HttpServletRequest)axis2MsgContext.getProperty(
> "transport.http.servletRequest");
> if (obj != null) {
> System.out.println("Method :"+ obj.getMethod());
> System.out.println("Content-type :" +obj.getContentType());
> System.out.println("Content-length :"+obj.getContentLength());
> System.out.println("Remote
> addtress"+obj.getSession().getLastAccessedTime());
> }
>
> as suggested in this blog
> http://vvratha.blogspot.it/2013/08/extracting-http-level-information-in.html
>
> But the obj variable i got is alway NULL.
> It's similar to this issue:http://wso2.com/forum/thread/10508
>
> Am i missing anything?
> Thanks
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Turing Ch-04][Build Failure] org.wso2.carbon.mediator.payloadfactory.ui: Compilation failure

[Ravi Undupitiya]

Hi Subash,


Are you building inside turing? The updates to Synapse dependency are
there, I can see the getExpression() method is implemented in turing branch
on SVN (it's implemented in the super class). Shafreen built a pack on a
clean repo today and there was no such issue.

Could you try updating synapse 2.1.2-wso2v2, then build
2.1.2-wso2v2/modules/core and then try and build
org.wso2.carbon.mediator.payloadfactory.ui ?


On Thu, Nov 21, 2013 at 9:08 PM, Subash Chaturanga  wrote:

> Hi,
> I updated the synapse module again and seems getExpression() method not
> yet commited. Seems some uncommited local changes are there. Please fi
> ASAP.
>
> FO] Final Memory: 1414M/1884M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.mediator.payloadfactory.ui:
> Compilation failure
> [ERROR]
> /home/subash/development/carbon/platform/branches/4.2.0/components/mediators/payloadFactory/org.wso2.carbon.mediator.payloadfactory.ui/4.2.0/src/main/java/org/wso2/carbon/mediator/payloadfactory/PayloadFactoryMediator.java:[120,100]
> cannot find symbol
> [ERROR] symbol  : method getExpression()
> [ERROR] location: class org.apache.synapse.util.xpath.SynapseJsonPath
> [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
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :org.wso2.carbon.mediator.payloadfactory.ui
> s
>
>
> --
> Thanks
> /subash
>
> *Subash Chaturanga*
> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
>
> email: sub...@wso2.com
> blog:  http://subashsdm.blogspot.com/
> twitter: @subash89
> phone: +9477 2225922
> Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712
<%2B94%C2%A0772%20930%20712>*

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Blocker][Build Failure][chunk-02 Final Pack] Build failure Synapse-Core 2.1.2-wso2v1

[Ravi Undupitiya]

Hi Ruwan,

This looks like it's due to changes we did earlier today in synapse core.
Could you try applying the attached patch at
https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/

That should fix this problem, if not I'll fix this tomorrow morning - as I
don't have commit rights to do this now.



Ravi




On Mon, Oct 21, 2013 at 11:28 PM, Ruwan Yatawara  wrote:

> Hi All,
>
> Getting the following build failure when trying to build
> Synapse 2.1.2-wso2v1. We were in the process of removing components not
> released with chunk-02 when this was encountered, all the changes we did
> have been reverted, but the issue still remains.
>
> A quick search seems to reveal this might be related to an axis2 version
> incompatibility issue.
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.0:compile
> (default-compile) on project synapse-core: Compilation failure: Compilation
> failure:
> [ERROR]
> /build/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorFactoryFinder.java:[37,15]
> sun.misc.Service is Sun proprietary API and may be removed in a future
> release
> [ERROR]
> [ERROR]
> /build/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/src/main/java/org/apache/synapse/endpoints/algorithms/RoundRobin.java:[27,26]
> sun.security.action.LoadLibraryAction is Sun proprietary API and may be
> removed in a future release
> [ERROR]
> [ERROR]
> /build/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/src/main/java/org/apache/synapse/config/xml/ConfigurationFactoryAndSerializerFinder.java:[29,15]
> sun.misc.Service is Sun proprietary API and may be removed in a future
> release
> [ERROR]
> [ERROR]
> /build/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/src/main/java/org/apache/synapse/config/xml/StartupFinder.java:[37,15]
> sun.misc.Service is Sun proprietary API and may be removed in a future
> release
> [ERROR]
> [ERROR]
> /build/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorSerializerFinder.java:[27,15]
> sun.misc.Service is Sun proprietary API and may be removed in a future
> release
> [ERROR]
> [ERROR]
> /build/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorFactoryFinder.java:[154,22]
> sun.misc.Service is Sun proprietary API and may be removed in a future
> release
> [ERROR]
> [ERROR]
> /build/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/src/main/java/org/apache/synapse/config/xml/ConfigurationFactoryAndSerializerFinder.java:[117,22]
> sun.misc.Service is Sun proprietary API and may be removed in a future
> release
> [ERROR]
> [ERROR]
> /build/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/src/main/java/org/apache/synapse/util/xpath/SynapseJsonPath.java:[65,38]
> JSON_STREAM has private access in org.apache.axis2.json.JSONBuilder
> [ERROR]
> [ERROR]
> /build/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/src/main/java/org/apache/synapse/util/xpath/SynapseJsonPath.java:[81,62]
> JSON_STREAM has private access in org.apache.axis2.json.JSONBuilder
> [ERROR]
> [ERROR]
> /build/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/src/main/java/org/apache/synapse/util/xpath/SynapseJsonPath.java:[108,35]
> JSON_STREAM has private access in org.apache.axis2.json.JSONBuilder
> [ERROR]
> [ERROR]
> /build/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/src/main/java/org/apache/synapse/config/xml/StartupFinder.java:[115,25]
> sun.misc.Service is Sun proprietary API and may be removed in a future
> release
> [ERROR]
> [ERROR]
> /build/branches/turing/dependencies/synapse/2.1.2-wso2v1/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorSerializerFinder.java:[120,22]
> sun.misc.Service is Sun proprietary API and may be removed in a future
> release
> [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
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :synapse-core
>
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Software Engineer,
> WSO2 Inc.
> lean . enterprise . middleware
>
> email : ruw...@wso2.c

Re: [Dev] [DEV][Blocker]StAX dialect detection fails on IBM JRE 1.7

[Ravi Undupitiya]

Hi Manoj,

Please find the carbon kernel patch attached to [1].


[1] https://wso2.org/jira/browse/ESBJAVA-2462


On Tue, Sep 24, 2013 at 10:41 AM, Manoj Kumara  wrote:

> Hi Ravi,
>
> Can you create the relevant kernel patches for relevant branches and
> attach that to the above JIRA issue. So we can commit that. Please follow
> the instructions given on [1].
>
> [1] http://docs.wso2.org/display/Carbon420/Creating+a+Carbon+Kernel+Patch
>
>
> Thanks,
> Manoj
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Mon, Sep 23, 2013 at 11:57 PM, Ravi Undupitiya  wrote:
>
>> Hi Sagara,
>>
>> It wasn't clear what the other two commits were, so I left those out.
>> I'll look into merging those.
>>
>> What should we do if the code is too out of sync (since the version we
>> are patching is quite old), IIRC one of those commits was fixing a
>> regression issue and seemed to be out of sync with the version we're using.
>>
>>
>> Thanks
>>
>>
>> On Mon, Sep 23, 2013 at 11:13 PM, Sagara Gunathunga wrote:
>>
>>>
>>>
>>>
>>> On Mon, Sep 23, 2013 at 4:43 AM, Sameera Jayasoma wrote:
>>>
>>>> Hi Sagara,
>>>>
>>>> Can you please review this patch?
>>>>
>>>
>>>
>>> @Ravi,
>>>
>>> Why do you have take only part of the fix from AXIOM-443 ? This may
>>> solve only specific visible issue but as you can read from AXIOM-443
>>> comments we need complete fix to provide full support for IBM JRE. IMO if
>>> there is no specific reason then apply the full patch to local branch.
>>> (Generally when merging from Apache branch to out local branch don't merge
>>> part of a patch that may cause lot of incompatibilities in future)
>>>
>>> @Sameera
>>>
>>> Since we are merging from Apache trunk there can't be any technical
>>> issue with the fix let's just make sure we can pass test cases.
>>>
>>> Thanks !
>>>
>>> Thanks !
>>>
>>>>
>>>> Thanks,
>>>> Sameera.
>>>>
>>>>
>>>> On Mon, Sep 23, 2013 at 11:31 AM, Vanjikumaran Sivajothy <
>>>> va...@wso2.com> wrote:
>>>>
>>>>> @ravi
>>>>>
>>>>> Thank you for your patch.
>>>>>
>>>>> @sameera
>>>>> This is critical issue on IBM JRE 1.7!
>>>>>
>>>>> Please good enough to apply the patch to resolve this issue.
>>>>>
>>>>> Thank you,
>>>>> Best regards,
>>>>> vanji
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Sep 23, 2013 at 11:26 AM, Ravi Undupitiya wrote:
>>>>>
>>>>>> Hi Vanji,
>>>>>>
>>>>>>
>>>>>> I exported the patch from AXIOM-443 and it solved this issue. There's
>>>>>> a patch attached to [1].
>>>>>>
>>>>>> [1] https://wso2.org/jira/browse/ESBJAVA-2462
>>>>>>
>>>>>>
>>>>>> On Fri, Sep 20, 2013 at 9:25 AM, Vanjikumaran Sivajothy <
>>>>>> va...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Carbon team,
>>>>>>>
>>>>>>> Please assist us to resolve [1] by applying patch in [2]. This
>>>>>>> is pretty urgent, because esb is not starting at all in AIX 7.1,
>>>>>>> IBM JDK 1.7 environment.
>>>>>>>
>>>>>>>
>>>>>>> [1]https://wso2.org/jira/browse/ESBJAVA-2462
>>>>>>> [2]https://issues.apache.org/jira/browse/AXIOM-443
>>>>>>>
>>>>>>> Quick action highly appreciate to solve the problem and thank you in
>>>>>>> advance.
>>>>>>>
>>>>>>> --
>>>>>>> Sivajothy Vanjikumaran
>>>>>>>  *Senior Software Engineer*
>>>>>>> *Integration Technologies Team*
>>>>>>> *WSO2 Inc. http://wso2.com/*
>>>>>>> *Mobile:(+94)777219209**
>>>>>>> *[image: Facebook] <https://www.facebook.com/vanjikumaran> [image:
>>>>>>> Twitter] <https://twitter.com/vanjikumaran> [image: 
>>

Re: [Dev] [DEV][Blocker]StAX dialect detection fails on IBM JRE 1.7

[Ravi Undupitiya]

Hi Sagara,

It wasn't clear what the other two commits were, so I left those out. I'll
look into merging those.

What should we do if the code is too out of sync (since the version we are
patching is quite old), IIRC one of those commits was fixing a regression
issue and seemed to be out of sync with the version we're using.


Thanks


On Mon, Sep 23, 2013 at 11:13 PM, Sagara Gunathunga  wrote:

>
>
>
> On Mon, Sep 23, 2013 at 4:43 AM, Sameera Jayasoma wrote:
>
>> Hi Sagara,
>>
>> Can you please review this patch?
>>
>
>
> @Ravi,
>
> Why do you have take only part of the fix from AXIOM-443 ? This may solve
> only specific visible issue but as you can read from AXIOM-443 comments we
> need complete fix to provide full support for IBM JRE. IMO if there is no
> specific reason then apply the full patch to local branch. (Generally when
> merging from Apache branch to out local branch don't merge part of a patch
> that may cause lot of incompatibilities in future)
>
> @Sameera
>
> Since we are merging from Apache trunk there can't be any technical issue
> with the fix let's just make sure we can pass test cases.
>
> Thanks !
>
> Thanks !
>
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Mon, Sep 23, 2013 at 11:31 AM, Vanjikumaran Sivajothy 
>> wrote:
>>
>>> @ravi
>>>
>>> Thank you for your patch.
>>>
>>> @sameera
>>> This is critical issue on IBM JRE 1.7!
>>>
>>> Please good enough to apply the patch to resolve this issue.
>>>
>>> Thank you,
>>> Best regards,
>>> vanji
>>>
>>>
>>>
>>> On Mon, Sep 23, 2013 at 11:26 AM, Ravi Undupitiya  wrote:
>>>
>>>> Hi Vanji,
>>>>
>>>>
>>>> I exported the patch from AXIOM-443 and it solved this issue. There's a
>>>> patch attached to [1].
>>>>
>>>> [1] https://wso2.org/jira/browse/ESBJAVA-2462
>>>>
>>>>
>>>> On Fri, Sep 20, 2013 at 9:25 AM, Vanjikumaran Sivajothy >>> > wrote:
>>>>
>>>>> Hi Carbon team,
>>>>>
>>>>> Please assist us to resolve [1] by applying patch in [2]. This
>>>>> is pretty urgent, because esb is not starting at all in AIX 7.1, IBM
>>>>> JDK 1.7 environment.
>>>>>
>>>>>
>>>>> [1]https://wso2.org/jira/browse/ESBJAVA-2462
>>>>> [2]https://issues.apache.org/jira/browse/AXIOM-443
>>>>>
>>>>> Quick action highly appreciate to solve the problem and thank you in
>>>>> advance.
>>>>>
>>>>> --
>>>>> Sivajothy Vanjikumaran
>>>>>  *Senior Software Engineer*
>>>>> *Integration Technologies Team*
>>>>> *WSO2 Inc. http://wso2.com/*
>>>>> *Mobile:(+94)777219209**
>>>>> *[image: Facebook] <https://www.facebook.com/vanjikumaran> [image:
>>>>> Twitter] <https://twitter.com/vanjikumaran> [image: 
>>>>> LinkedIn]<http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293> 
>>>>> [image:
>>>>> Blogger] <http://vanjikumaran.blogspot.com/> [image: 
>>>>> SlideShare]<http://www.slideshare.net/vanjikumaran>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Ravi Undupitiya*
>>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>>> *
>>>> *
>>>> *E-mail: r...@wso2.com
>>>> **M: **+94 772 930 712*
>>>> *
>>>> *Lean . Enterprise . Middleware
>>>>
>>>
>>>
>>>
>>> --
>>> Sivajothy Vanjikumaran
>>> *Senior Software Engineer*
>>> *Integration Technologies Team*
>>> *WSO2 Inc. http://wso2.com/*
>>> *Mobile:(+94)777219209**
>>> *[image: Facebook] <https://www.facebook.com/vanjikumaran> [image:
>>> Twitter] <https://twitter.com/vanjikumaran> [image: 
>>> LinkedIn]<http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293> 
>>> [image:
>>> Blogger] <http://vanjikumaran.blogspot.com/> [image: 
>>> SlideShare]<http://www.slideshare.net/vanjikumaran>
>>>
>>
>>
>>
>> --
>> Sameera Jayasoma,
>> Architect,
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://sameera.adahas.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>> Mobile: 0094776364456
>>
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Fixing ESB Access Logs

[Ravi Undupitiya]

I've been looking into $subject. There were several formatting issues with
the current logs like incorrect time stamps and not recording bytes sent
when this information is available through HTTP Headers. I've managed to
fix these, but there's another issue with the current implementation:

The current implementation logs requests and responses independent of each
other. This causes additional response log's to print with only a time
stamp and a status code.

I think ideally the status code should be included as part of the
corresponding request log (AFAIU, this is how common log format is used in
squid proxy). But in order to do this, we have to map requests and
responses - and I think this might be an unnecessary use of memory.

Should we attempt to fix this?

Here's a sample of the current output:

localhost:9000 - - [23/Sep/2013:13:41:52 +0530] "POST
/services/SimpleStockQuoteService HTTP/1.1" - - "-"
"Synapse-PT-HttpComponents-NIO"
-  - [23/Sep/2013:13:41:52 +0530] "- - " 500 - "-" "-"




-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][Blocker]StAX dialect detection fails on IBM JRE 1.7

[Ravi Undupitiya]

Hi Vanji,


I exported the patch from AXIOM-443 and it solved this issue. There's a
patch attached to [1].

[1] https://wso2.org/jira/browse/ESBJAVA-2462


On Fri, Sep 20, 2013 at 9:25 AM, Vanjikumaran Sivajothy wrote:

> Hi Carbon team,
>
> Please assist us to resolve [1] by applying patch in [2]. This
> is pretty urgent, because esb is not starting at all in AIX 7.1, IBM JDK
> 1.7 environment.
>
>
> [1]https://wso2.org/jira/browse/ESBJAVA-2462
> [2]https://issues.apache.org/jira/browse/AXIOM-443
>
> Quick action highly appreciate to solve the problem and thank you in
> advance.
>
> --
> Sivajothy Vanjikumaran
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)777219209**
> *[image: Facebook] <https://www.facebook.com/vanjikumaran> [image:
> Twitter] <https://twitter.com/vanjikumaran> [image: 
> LinkedIn]<http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293> 
> [image:
> Blogger] <http://vanjikumaran.blogspot.com/> [image: 
> SlideShare]<http://www.slideshare.net/vanjikumaran>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need a latest ELB pack with the spinning issue fixed

[Ravi Undupitiya]

The changes have been made and committed, once the kernel changes are
committed, we should be able to build a pack.


On Wed, Sep 18, 2013 at 6:35 PM, Amila Maha Arachchi wrote:

> Hi Isuru,
>
> $Subject. Is it available?
>
> Regards,
> AmilaM.
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk-02 Nightly Build packs - 18/09/2013

[Ravi Undupitiya]

That pack won't contain any changes as we haven't downgraded yet, we just
finished discussing the downgrade, will commit the changes ASAP.

Could you please follow Isuru's instructions to downgrade the components in
the mean time.


On Wed, Sep 18, 2013 at 10:58 AM, Nuwan Silva  wrote:

> Hi Ravi,
>
> The given ELB 2.1.0 contains ;
>
> httpclient_4.2.5.wso2v1.jar
> httpcore_4.3.0.wso2v1.jar
> httpcore-nio_4.3.0.wso2v1.jar
>
> Does this pack contain any fixes for the Spinning issue?
> please advice.
>
> Thanks,
> NuwanS
>
>
> On Wed, Sep 18, 2013 at 1:47 AM, Sanjeewa Malalgoda wrote:
>
>> Hi Team,
>>
>> Packs built on 4.2.0 Branch/Chunk-02 are available at the following
>> location.
>>
>> http://builder3.us1.wso2.org/builds/chunk-02/N_18-09-13/
>>
>> Thanks,
>> Sanjeewa.
>>
>> --
>> *
>> *
>> *Sanjeewa Malalgoda*
>> Senior Software Engineer
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>>  <http://sanjeewamalalgoda.blogspot.com/>blog
>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *
> *
> *Nuwan Silva
> *
> *Senior Software Engineer - QA*
> Mobile: +94779804543
>
> WSO2 Inc.
> lean . enterprise . middlewear.
> http://www.wso2.com
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Preparing ELB 2.1.0 release

[Ravi Undupitiya]

Hi Nuwan,

I checked to see if the pack contained the spinning related fixes, and they
seem to be there. This might be due to another reason.

It would be helpful if you can give the steps to reproduce this.



On Sat, Sep 14, 2013 at 11:07 AM, Nuwan Silva  wrote:

> Hi All,
>
> We setup a GREG cluster with the 2 nodes and given ELB 2.1.0 [1]. After
> working with it for sometime (5-10 minutes) ELB spinning issue appears
> please refer the attache screen-shot.
>
> console logs:
> [2013-09-14 10:48:29,636]  WARN - SourceHandler Connection time out after
> request is read: http-incoming-1
> [2013-09-14 10:54:26,351]  WARN - SourceHandler I/O error (Probably the
> connection was closed by the remote party):Broken pipe
> [2013-09-14 10:54:29,755]  WARN - SourceHandler Connection time out while
> writing the response: http-incoming-49
> [2013-09-14 10:54:47,081]  WARN - SourceHandler Connection time out after
> request is read: http-incoming-47
> [2013-09-14 10:55:04,787]  WARN - SourceHandler Connection time out while
> writing the response: http-incoming-43
> [2013-09-14 10:55:27,036]  WARN - SourceHandler Connection time out after
> request is read: http-incoming-46
> [2013-09-14 10:56:27,102]  WARN - SourceHandler Connection time out after
> request is read: http-incoming-55
> [2013-09-14 10:56:28,099]  WARN - SourceHandler Connection time out after
> request is read: http-incoming-57
> [2013-09-14 10:57:45,575]  WARN - SourceHandler Connection time out after
> request is read: http-incoming-59
> [2013-09-14 10:57:48,592]  WARN - SourceHandler Connection time out after
> request is read: http-incoming-61
> [2013-09-14 10:58:48,645]  WARN - SourceHandler Connection time out after
> request is read: http-incoming-60
> [2013-09-14 10:59:48,706]  WARN - SourceHandler Connection time out after
> request is read: http-incoming-63
> [2013-09-14 10:59:59,677]  WARN - SourceHandler Connection time out after
> request is read: http-incoming-65
> [2013-09-14 11:01:04,820]  WARN - SourceHandler Connection time out after
> request is read: http-incoming-67
>
>
> [1] http://builder3.us1.wso2.org/builds/chunk-02/N_12-09-13/ELB/
>
>
> On Fri, Sep 13, 2013 at 5:45 PM, Isuru Perera  wrote:
>
>> Hi,
>>
>> I noticed some of the 
>> issues<https://wso2.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+10210+AND+labels+%3D+passthru-transport>were
>>  marked as fixed today. Thanks for looking in to those.
>>
>> There are few in open state still. For example,
>> https://wso2.org/jira/browse/LB-88. This is probably the same issue with
>> spinning?
>>
>> Please check the NPEs as well.
>>
>> https://wso2.org/jira/browse/LB-85
>> https://wso2.org/jira/browse/LB-105
>>
>> Thanks.
>>
>>
>> On Sun, Sep 8, 2013 at 8:34 PM, Isuru Perera  wrote:
>>
>>> Hi Ravi,
>>>
>>> Could you please go through the issues here:
>>> https://wso2.org/jira/browse/LB-106?jql=project%20%3D%2010210%20AND%20labels%20%3D%20passthru-transport
>>>
>>> I created a label for passthru transport related issues.
>>>
>>> Thanks!
>>>
>>>
>>> On Thu, Sep 5, 2013 at 5:30 PM, Ravi Undupitiya  wrote:
>>>
>>>> LB-97 <https://wso2.org/jira/browse/LB-97> - this has been fixed.
>>>>
>>>> LB-106 <https://wso2.org/jira/browse/LB-106>, 
>>>> LB-75<https://wso2.org/jira/browse/LB-75>
>>>> , LB-90 <https://wso2.org/jira/browse/LB-90> and 
>>>> LB-105<https://wso2.org/jira/browse/LB-105> - should
>>>> be due to the spinning issue, i'm re-testing these scenarios with the
>>>> spinning fix to see if they reoccur on RC8 pack.
>>>>
>>>>
>>>>
>>>> On Thu, Sep 5, 2013 at 12:05 PM, Isuru Perera  wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I have started working on fixing issues on ELB.
>>>>>
>>>>> Following are some synapse related issues that needs to be fixed.
>>>>>
>>>>> ESB Team, please check these issues and let me know whether those can
>>>>> be fixed.
>>>>>
>>>>> https://wso2.org/jira/browse/LB-74
>>>>> https://wso2.org/jira/browse/LB-97
>>>>> https://wso2.org/jira/browse/LB-106
>>>>> https://wso2.org/jira/browse/LB-75
>>>>> https://wso2.org/jira/browse/LB-90
>>>>> https://wso2.org/jira/browse/LB-105
>>>>>
>>>>> I will check on other issues and update this thread.
>>&g

Re: [Dev] Preparing ELB 2.1.0 release

[Ravi Undupitiya]

Turned out I was using RC5 App Server with RC8 ELB. Using latest AS has
fixed my problem.


On Tue, Sep 10, 2013 at 9:47 AM, Isuru Perera  wrote:

> Hi Ravi,
>
> Yes,  the ELB 2.1.0 product can be built from chunk 02. I will give you
> the pack.
>
> But RC8 should work fine.
>
> Thanks!
> On Sep 10, 2013 9:39 AM, "Ravi Undupitiya"  wrote:
>
>> Hi Isuru,
>>
>>
>> Is there a pack available after RC8? RC8 pack seems to have an issue with
>> worker node access.
>>
>>
>> On Sun, Sep 8, 2013 at 8:34 PM, Isuru Perera  wrote:
>>
>>> Hi Ravi,
>>>
>>> Could you please go through the issues here:
>>> https://wso2.org/jira/browse/LB-106?jql=project%20%3D%2010210%20AND%20labels%20%3D%20passthru-transport
>>>
>>> I created a label for passthru transport related issues.
>>>
>>> Thanks!
>>>
>>>
>>> On Thu, Sep 5, 2013 at 5:30 PM, Ravi Undupitiya  wrote:
>>>
>>>> LB-97 <https://wso2.org/jira/browse/LB-97> - this has been fixed.
>>>>
>>>> LB-106 <https://wso2.org/jira/browse/LB-106>, 
>>>> LB-75<https://wso2.org/jira/browse/LB-75>
>>>> , LB-90 <https://wso2.org/jira/browse/LB-90> and 
>>>> LB-105<https://wso2.org/jira/browse/LB-105> - should
>>>> be due to the spinning issue, i'm re-testing these scenarios with the
>>>> spinning fix to see if they reoccur on RC8 pack.
>>>>
>>>>
>>>>
>>>> On Thu, Sep 5, 2013 at 12:05 PM, Isuru Perera  wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I have started working on fixing issues on ELB.
>>>>>
>>>>> Following are some synapse related issues that needs to be fixed.
>>>>>
>>>>> ESB Team, please check these issues and let me know whether those can
>>>>> be fixed.
>>>>>
>>>>> https://wso2.org/jira/browse/LB-74
>>>>> https://wso2.org/jira/browse/LB-97
>>>>> https://wso2.org/jira/browse/LB-106
>>>>> https://wso2.org/jira/browse/LB-75
>>>>> https://wso2.org/jira/browse/LB-90
>>>>> https://wso2.org/jira/browse/LB-105
>>>>>
>>>>> I will check on other issues and update this thread.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> --
>>>>> Isuru Perera
>>>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>> about.me/chrishantha
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Ravi Undupitiya*
>>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>>> *
>>>> *
>>>>  *E-mail: r...@wso2.com
>>>> **M: **+94 772 930 712*
>>>>  *
>>>> *Lean . Enterprise . Middleware
>>>>
>>>
>>>
>>>
>>> --
>>> Isuru Perera
>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>>
>>
>>
>>
>> --
>> *Ravi Undupitiya*
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> *
>> *
>> *E-mail: r...@wso2.com
>> **M: **+94 772 930 712*
>> *
>> *Lean . Enterprise . Middleware
>>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Preparing ELB 2.1.0 release

[Ravi Undupitiya]

Hi Isuru,


Is there a pack available after RC8? RC8 pack seems to have an issue with
worker node access.


On Sun, Sep 8, 2013 at 8:34 PM, Isuru Perera  wrote:

> Hi Ravi,
>
> Could you please go through the issues here:
> https://wso2.org/jira/browse/LB-106?jql=project%20%3D%2010210%20AND%20labels%20%3D%20passthru-transport
>
> I created a label for passthru transport related issues.
>
> Thanks!
>
>
> On Thu, Sep 5, 2013 at 5:30 PM, Ravi Undupitiya  wrote:
>
>> LB-97 <https://wso2.org/jira/browse/LB-97> - this has been fixed.
>>
>> LB-106 <https://wso2.org/jira/browse/LB-106>, 
>> LB-75<https://wso2.org/jira/browse/LB-75>
>> , LB-90 <https://wso2.org/jira/browse/LB-90> and 
>> LB-105<https://wso2.org/jira/browse/LB-105> - should
>> be due to the spinning issue, i'm re-testing these scenarios with the
>> spinning fix to see if they reoccur on RC8 pack.
>>
>>
>>
>> On Thu, Sep 5, 2013 at 12:05 PM, Isuru Perera  wrote:
>>
>>> Hi all,
>>>
>>> I have started working on fixing issues on ELB.
>>>
>>> Following are some synapse related issues that needs to be fixed.
>>>
>>> ESB Team, please check these issues and let me know whether those can be
>>> fixed.
>>>
>>> https://wso2.org/jira/browse/LB-74
>>> https://wso2.org/jira/browse/LB-97
>>> https://wso2.org/jira/browse/LB-106
>>> https://wso2.org/jira/browse/LB-75
>>> https://wso2.org/jira/browse/LB-90
>>> https://wso2.org/jira/browse/LB-105
>>>
>>> I will check on other issues and update this thread.
>>>
>>> Thanks!
>>>
>>> --
>>> Isuru Perera
>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Ravi Undupitiya*
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> *
>> *
>>  *E-mail: r...@wso2.com
>> **M: **+94 772 930 712*
>>  *
>> *Lean . Enterprise . Middleware
>>
>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Preparing ELB 2.1.0 release

[Ravi Undupitiya]

LB-97 <https://wso2.org/jira/browse/LB-97> - this has been fixed.

LB-106 <https://wso2.org/jira/browse/LB-106>,
LB-75<https://wso2.org/jira/browse/LB-75>
, LB-90 <https://wso2.org/jira/browse/LB-90> and
LB-105<https://wso2.org/jira/browse/LB-105> - should
be due to the spinning issue, i'm re-testing these scenarios with the
spinning fix to see if they reoccur on RC8 pack.



On Thu, Sep 5, 2013 at 12:05 PM, Isuru Perera  wrote:

> Hi all,
>
> I have started working on fixing issues on ELB.
>
> Following are some synapse related issues that needs to be fixed.
>
> ESB Team, please check these issues and let me know whether those can be
> fixed.
>
> https://wso2.org/jira/browse/LB-74
> https://wso2.org/jira/browse/LB-97
> https://wso2.org/jira/browse/LB-106
> https://wso2.org/jira/browse/LB-75
> https://wso2.org/jira/browse/LB-90
> https://wso2.org/jira/browse/LB-105
>
> I will check on other issues and update this thread.
>
> Thanks!
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>
> _______
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] - Cannot access the Management console in worker/manager separated setup with latest packs

[Ravi Undupitiya]

This seems to have been fixed in RC8 (including the tenatn domain not set
issue).


On Wed, Aug 21, 2013 at 8:39 PM, Evanthika Amarasiri wrote:

> Related JIRA [1]
>
> [1]  - https://wso2.org/jira/browse/LB-97
>
> Evanthika Amarasiri
> Senior Technical Lead - Quality Assurance
> Mobile: +94773125935
> *
> *
> wso2.com Lean Enterprise Middleware
>
>
> On Wed, Aug 21, 2013 at 4:47 PM, Evanthika Amarasiri 
> wrote:
>
>> Hi All,
>>
>> In our worker/manager separated setup, we cannot access the management
>> console. I see the below exception at ELB side. Used the same configuration
>> we used before.
>>
>>
>> ***
>> [2013-08-21 16:15:39,133]  WARN - PassThroughHttpSSLListener System may
>> be unstable: HTTPS ListeningIOReactor encountered a runtime exception :
>> Null action
>> java.lang.IllegalArgumentException: Null action
>> at
>> java.nio.charset.CharsetDecoder.onMalformedInput(CharsetDecoder.java:368)
>>  at
>> org.apache.http.impl.nio.NHttpConnectionBase.(NHttpConnectionBase.java:162)
>>  at
>> org.apache.http.impl.nio.DefaultNHttpServerConnection.(DefaultNHttpServerConnection.java:100)
>>  at
>> org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection.(LoggingNHttpServerConnection.java:62)
>>  at
>> org.apache.synapse.transport.http.conn.LoggingUtils.createServerConnection(LoggingUtils.java:73)
>>  at
>> org.apache.synapse.transport.http.conn.ServerConnFactory.createConnection(ServerConnFactory.java:90)
>>  at
>> org.apache.synapse.transport.passthru.ServerIODispatch.createConnection(ServerIODispatch.java:58)
>>  at
>> org.apache.synapse.transport.passthru.ServerIODispatch.createConnection(ServerIODispatch.java:39)
>>  at
>> org.apache.http.impl.nio.reactor.AbstractIODispatch.connected(AbstractIODispatch.java:71)
>> at
>> org.apache.http.impl.nio.reactor.BaseIOReactor.sessionCreated(BaseIOReactor.java:240)
>>  at
>> org.apache.http.impl.nio.reactor.AbstractIOReactor.processNewChannels(AbstractIOReactor.java:426)
>>  at
>> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:288)
>>  at
>> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
>> at
>> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:584)
>>  at java.lang.Thread.run(Thread.java:722)
>>
>> Regards,
>> Evanthika Amarasiri
>> Senior Technical Lead - Quality Assurance
>> Mobile: +94773125935
>> *
>> *
>> wso2.com Lean Enterprise Middleware
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Response body getting dropped when invoking APIs

[Ravi Undupitiya]

Hi,

Even after including Kasun's fix the scenario was failing for GET requests.
We had a closer look at this and identified that the
MESSAGE_BUILDER_INVOKED property is always set to true when it is passed
via the tenant dispatcher, when it should be false (on the out path). I
verified this by comparing it with the same scenario on ESB 4.7.0 and
managed to find the cause:

In 4.1.0 org.wso2.carbon.core (patch0001 version) we have got:

tenantResponseMsgCtx.setProperty(MultitenantConstants.MESSAGE_BUILDER_INVOKED,Boolean.FALSE);

Set in line 151, this is missing in 4.2.0.

Putting this line back has fixed the issue - I think it may have been a
missed commit.

I've attached a patch for this, please apply it if this fix is ok.



Ravi


On Thu, Aug 29, 2013 at 8:40 AM, Isuru Udana  wrote:

> Hi Kasun,
>
> The fix you provided to enable Multitenant REST API support for Pass-Thru
> Transport is not there in kernel 4.2.0.
>
>
>
>
>
> On Thu, Aug 29, 2013 at 12:19 AM, Dinusha Senanayaka wrote:
>
>> Hi Kasun,
>>
>>
>> On Thu, Aug 29, 2013 at 12:02 AM, Kasun Indrasiri  wrote:
>>
>>> Hi Dinusha,
>>>
>>> I have added MT REST support for PT sometime back (refer @architecture
>>> 'Multitenant REST API support for Pass-Thru Transport') and
>>> included/verified in ESB 4.7 release.
>>> So, I guess API-M is also tested for these scenarios with PTT since
>>> then. If this is some thing that you observe in the latest packs, then it
>>> could be a regression in kernel or transport.
>>>
>>  yes, this is in latest AM pack, built on new kernel-4.2.0.. It works
>> fine in the AM-1.4.0 release.
>>
>> Regards,
>> Dinusha.
>>
>>> Will check this and get back to you.
>>>
>>>
>>>
>>>
>>> On Thu, Aug 29, 2013 at 12:00 AM, Dinusha Senanayaka 
>>> wrote:
>>>
>>>> Hi Isuru,
>>>>
>>>> Following are the steps to reproduce the issue;
>>>>
>>>> 1. By default in APIM, we have enabled PT.
>>>> 2. create/publish/subscribe an API using a tenant. (works for super
>>>> tenant mode)
>>>> 3. Do a HTTP GET request. Endpoint will send the response body as
>>>> follows [a], but when it comes to the client through APIM response body has
>>>> get dropped and received the empty response body as [b].
>>>> 4. No back-end errors are thrown. If we switch to nio instead of PT,
>>>> client is receiving the response as expected.
>>>>
>>>> [a]. 
>>>>  http://ws.wso2.org/dataservice/samples/rdbms_sample
>>>> ">Gifts4AllAges.comYoshido
>>>> 
>>>>
>>>>
>>>> [b].  http://www.w3.org/2003/05/soap-envelope";>
>>>>
>>>>
>>>>
>>>>
>>>> Regards,
>>>> Dinusha.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Aug 28, 2013 at 11:10 PM, Isuru Udana  wrote:
>>>>
>>>>> Hi Dinusha,
>>>>>
>>>>> Can you elaborate more on the scenario and issue with configs and logs
>>>>> ?
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Aug 28, 2013 at 11:06 PM, Dinusha Senanayaka >>>> > wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> When we do a HTTP GET request, response body getting dropped. This
>>>>>> issue happens only for tenants with the PT. If we switch to NIO, client
>>>>>> receive the response properly.
>>>>>> Appreciate any help/ideas to resolve this.
>>>>>>
>>>>>> Regards,
>>>>>> Dinusha.
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Dinusha Dilrukshi
>>>>>> Senior Software Engineer
>>>>>> WSO2 Inc.: http://wso2.com/
>>>>>> Mobile: +94725255071
>>>>>> Blog: http://dinushasblog.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Isuru Udana*
>>>>> *
>>>>>  *
>>>>> Senior *
>>>>> Software Engineer
>>>>> *
>>>>> WSO2 Inc.; http://wso2.com
>>>>> email: isu...@wso2.com cell: +94 77 3791887
>>>>> blog: http://mytecheye.blogspot.com/
>>>>> twitter: http://twitter.com/isudana
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Dinusha Dilrukshi
>>>> Senior Software Engineer
>>>> WSO2 Inc.: http://wso2.com/
>>>> Mobile: +94725255071
>>>> Blog: http://dinushasblog.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 71 536 4128
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>> Dinusha Dilrukshi
>> Senior Software Engineer
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
> *Isuru Udana*
> *
>  *
> Senior *
> Software Engineer
> *
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
> twitter: http://twitter.com/isudana
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware


mt-rest-issue.patch
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] wss4j 1.5.11.wso2v6 packing 2 bouncy castle's

[Ravi Undupitiya]

wss4j 1.5.11.wso2v6 is packing two bouncy castle's (one of which is
exposed).

This is causing an issue with ESB's axis2server as it places its own
bouncy-castle (bcprov-jdk15.jar) onto the class path.

I tried not including bcprov-jdk15.jar when starting axis2 server and it
didn't help. I think the required version of bcprov for axis2server is
different to the one exposed by wss4j.



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Commits] [Carbon-platform] svn commit r178674 - carbon/platform/trunk/dependencies/synapse/2.1.1-wso2v8/modules/core/src/main/java/org/apache/synapse/endpoints

[Ravi Undupitiya]

les) call will fill up a list of variables and since
>> uriTemplate
>> +// is not thread safe, this list won't be clearing.
>> +UriTemplate template = null;
>> +template = UriTemplate.fromTemplate(uriTemplate.getTemplate());
>> +
>> +if(template != null) {
>> +template.set(variables);
>> +}
>> +
>>  String evaluatedUri = "";
>>  try {
>> -evaluatedUri = uriTemplate.expand();
>> +evaluatedUri = new java.net.URI(template.expand()).getPath();
>>  } catch(ExpressionParseException e) {
>>  log.debug("No URI Template variables defined in HTTP
>> Endpoint: " + this.getName());
>> -evaluatedUri = uriTemplate.getTemplate();
>> +evaluatedUri = template.getTemplate();
>> +} catch (URISyntaxException e) {
>> +evaluatedUri = template.getTemplate();
>>  }
>>  if (evaluatedUri != null) {
>>  synCtx.setTo(new EndpointReference(evaluatedUri));
>> @@ -136,8 +146,6 @@
>>  super.getDefinition().setAddress(evaluatedUri);
>>  }
>>  }
>> -
>> -
>>  }
>>
>>  public String getHttpMethod() {
>> ___
>> Commits mailing list
>> comm...@wso2.org 
>> http://wso2.org/cgi-bin/mailman/listinfo/commits
>>
>
>
>
> --
> Miyuru Wanninayaka
> Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile : +94 77 209 9788
> Blog : http://miyurudw.blogspot.com
> Flickr : http://www.flickr.com/photos/miyuru_daminda



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Vanjikumaran Sivajothy

[Ravi Undupitiya]

Congrats Vanji! :)


On Fri, Jul 26, 2013 at 2:28 PM, Kasun Indrasiri  wrote:

> Hi Folks,
>
> Its my pleasure to welcome Vanjikumaran Sivajothy as a WSO2 Committer. He
> has contributed to the recent ESB release and has involved in bug
> fixes/features implementation the 4.7 release.
>
> Vanji, welcome aboard and keep up the good work.
>
> Thanks.
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Shafreen Anfar

[Ravi Undupitiya]

Congrats Shafreen! :)


On Wed, Jul 3, 2013 at 2:03 PM, Kasun Indrasiri  wrote:

> Hi Folks,
>
> Its my pleasure to welcome Shafreen Anfar as a WSO2 Committer. He is a key
> contributor in bug fixing of 4.7 release and done a good job in ESB
> performance testing too.
>
> Shafreen, welcome aboard and keep up the good work.
>
> Thanks.
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build error when building Orbit in Carbon 4.1.0 branch

[Ravi Undupitiya]

Hi,

I'm look into this.


Thanks


On Tue, Jul 2, 2013 at 9:40 AM, Ishara Premadasa  wrote:

> Hi Ravi,
>
> I am getting following build error [1] when trying to build orbit in
> https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.1.0/ branch. It
> seems that you have removed the 'bsf' module from orbit but the orbit pom
> file still refers to that. Can you pls have a look and fix the pom file
> accordingly.
>
> Thanks!
> Ishara
>
> [1].
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR]   The project org.wso2.carbon:orbit-parent:4.1.0
> (/home/isha/Documents/ideaprojs/carbon_4.1.0/orbit/pom.xml) has 1 error
> [ERROR] Child module /home/isha//carbon_4.1.0/orbit/bsf/3.0.0.wso2v3
> of /home/isha/carbon_4.1.0/orbit/pom.xml does not exist
> [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/ProjectBuildingException
>
>
>
> --
> Ishara Premasada
> Software Engineer,
> WSO2 Inc. http://wso2.com/
> *Blog   :  http://isharapremadasa.blogspot.com/
> Twitter   :  https://twitter.com/ishadil
> Mobile   : +94 714445832*
>
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 ESB 4.7.0 RC3

[Ravi Undupitiya]

Please find $subject at [1]

[1]
http://svn.wso2.org/repos/wso2/people/ravi/packs/2013-06-29-wso2esb-4.7.0-RC3.zip



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 ESB 4.7.0 - RC1 (2013-06-24)

[Ravi Undupitiya]

Hi Krishantha,

Its running the tests right now. I'll post the results here when it has
finished.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 ESB 4.7.0 - RC1 (2013-06-24)

[Ravi Undupitiya]

Please find $subject at [1].


[1]
https://svn.wso2.org/repos/wso2/people/ravi/packs/20130624-wso2esb-4.7.0.zip


Known Issues:
https://wso2.org/jira/issues/?filter=11088



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESB 4.7.0 Pack (18-06-2013)

[Ravi Undupitiya]

Please find $subject at [1].

[1]
https://svn.wso2.org/repos/wso2/people/ravi/packs/20130618-wso2esb-4.7.0.zip



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Compile error on Platform trunk - org.wso2.carbon.mediation.templates.ui

[Ravi Undupitiya]

Hi Geeth,


Can you take an svn up in service-stubs and
build service-stubs/org.wso2.carbon.mediation.templates.stub. We made some
changes there.



Thanks,
Ravi


On Tue, Jun 18, 2013 at 4:44 PM, Geeth Munasinghe  wrote:

> Hi
>
> I am getting following compilation error.
>
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/geeth/workspace/carbon/carbon/platform/trunk/components/mediation/template-editor/org.wso2.carbon.mediation.templates.ui/src/main/java/org/wso2/carbon/mediation/templates/ui/EndpointTemplateAdminClient.java:[238,43]
> cannot find symbol
> symbol  : method hasDuplicateTempleteEndpoint(java.lang.String)
> location: class
> org.wso2.carbon.mediation.templates.endpoint.stub.types.EndpointTemplateAdminServiceStub
>
>
>
>
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 2:27.926s
> [INFO] Finished at: Tue Jun 18 15:42:00 IST 2013
> [INFO] Final Memory: 958M/1513M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.mediation.templates.ui:
> Compilation failure
> [ERROR]
> /home/geeth/workspace/carbon/carbon/platform/trunk/components/mediation/template-editor/org.wso2.carbon.mediation.templates.ui/src/main/java/org/wso2/carbon/mediation/templates/ui/EndpointTemplateAdminClient.java:[238,43]
> cannot find symbol
> [ERROR] symbol  : method hasDuplicateTempleteEndpoint(java.lang.String)
> [ERROR] location: class
> org.wso2.carbon.mediation.templates.endpoint.stub.types.EndpointTemplateAdminServiceStub
> [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
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :org.wso2.carbon.mediation.templates.ui
>
>
> Thanks
> *G. K. S. Munasinghe
> *
> *Software Engineer,*
> *WSO2, Inc. http://wso2.com *
> *lean.enterprise.middleware.*
> *
> *
> email: ge...@wso2.com
> phone:(+94) 777911226
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Patch Release 4.1.3 Build Break JGIT

[Ravi Undupitiya]

Thanks Isuru, its working now.


On Tue, Jun 18, 2013 at 2:04 PM, Isuru Haththotuwa  wrote:

> fixed in r175461.
>
>
> On Tue, Jun 18, 2013 at 2:00 PM, Ravi Undupitiya  wrote:
>
>> Hello,
>>
>>
>> We've got following build error when trying to build JGIT.
>>
>> [ERROR] Two or more projects in the reactor have the same identifier,
>> please make sure that :: is unique for
>> each project: {org.eclipse.jgit:org.eclipse.jgit:2.3.1-wso2
>> v2=[/home/esb/carbon/platform/4.1.0/dependencies/jgit/2.3.1-
>> wso2v2/org.eclipse.jgit/pom.xml, /home/esb/carbon/platform/4.1.
>> 0/dependencies/orbit/jgit/2.3.1-wso2v2/pom.xml]} -> [Help 1]
>>
>>
>> Please fix.
>>
>>
>> Thanks,
>> Ravi
>>
>> --
>> *Ravi Undupitiya*
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> *
>> *
>> *E-mail: r...@wso2.com
>> **M: **+94 772 930 712*
>> *
>> *Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
>
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Patch Release 4.1.3 Build Break JGIT

[Ravi Undupitiya]

Hello,


We've got following build error when trying to build JGIT.

[ERROR] Two or more projects in the reactor have the same identifier,
please make sure that :: is unique for each
project: {org.eclipse.jgit:org.eclipse.jgit:2.3.1-wso2v2=[/home/esb/c
arbon/platform/4.1.0/dependencies/jgit/2.3.1-wso2v2/org.eclipse.jgit/pom.xml,
/home/esb/carbon/platform/4.1.0/dependencies/orbit/jgit/2.3.1-wso2v2/pom.xml]}
-> [Help 1]


Please fix.


Thanks,
Ravi

-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Latest ESB Pack (14-06-2013)

[Ravi Undupitiya]

Please fine $subject at [1].

[1]
https://svn.wso2.org/repos/wso2/people/ravi/packs/20130614-wso2esb-4.7.0.zip

-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB: RDF Message Builder

[Ravi Undupitiya]

Hi Sagara,


Thanks for the reply. There was another case where if the server does not
send the correct content type, it might select the SOAP builder - I had a
look at this with IsuruU, and we found that this case was fixed in NHTTP by
setting the content type to application/xml if doingREST is true, this
logic was not included in PTT.


Is it ok to add the application/rdf+xml builder/formatter pair into
axis2.xml by default?



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

[Dev] Latest ESB Pack (10-06-2013)

[Ravi Undupitiya]

Please find $subject below.

http://svn.wso2.org/repos/wso2/people/ravi/packs/20130610-wso2esb-4.7.0.zip


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB: RDF Message Builder

[Ravi Undupitiya]

I managed to fix this by adding the following to axis2.xml:





I think this is the right way around this since RDF is XML.

But this scenario works in HTTP-NIO transport without having to explicitly
define the content type.

Any advice on the proposed solution?



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

[Dev] ESB: RDF Message Builder

[Ravi Undupitiya]

Is it correct functionality for the MessageProcessorSelector (the class
responsible for selecting the message builder/formatter) to return the SOAP
builder for the application/rdf+xml message type?

How does this class return a builder based on the content type and message
context?

I think this is the case with the PTT and it's causing some parse errors
when dealing with RDF data (see ESBJAVA-1825).




Thanks,
Ravi

-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why do 4.1.3 patch-release has 4.1.2 ESB components?

[Ravi Undupitiya]

Hi Amila,


The reason we have 4.1.2 components is because we moved to 4.1.3 before
4.1.2 was released - we'll be removing them soon.

SynapseJsonPathFactory is found inside synapse - both 2.1.1-wso2v5 and
2.1.1-wso2v6 have this component.



Thanks,
Ravi



On Thu, Jun 6, 2013 at 10:35 AM, Amila Maha Arachchi wrote:

> Hi ESB team,
>
> $Subject?
>
> I am getting a build failure in payloadFactory.ui component due to a
> missing java class SynapseJsonPath.java.
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.mediator.payloadfactory.ui:
> Compilation failure: Compilation failure:
> [ERROR]
> /home/amila/development/branches/4.1.0/platform/components/mediators/payloadFactory/org.wso2.carbon.mediator.payloadfactory.ui/
> *4.1.2*/src/main/java/org/wso2/carbon/mediator/payloadfactory/PayloadFactoryMediator.java:[25,36]
> cannot find symbol
> [ERROR] symbol  : class SynapseJsonPathFactory
> [ERROR] location: package org.apache.synapse.config.xml
> [ERROR]
> /home/amila/development/branches/4.1.0/platform/components/mediators/payloadFactory/org.wso2.carbon.mediator.payloadfactory.ui/4.1.2/src/main/java/org/wso2/carbon/mediator/payloadfactory/PayloadFactoryMediator.java:[29,36]
> cannot find symbol
> [ERROR] symbol  : class SynapseJsonPath
> [ERROR] location: package org.apache.synapse.util.xpath
> [ERROR]
> /home/amila/development/branches/4.1.0/platform/components/mediators/payloadFactory/org.wso2.carbon.mediator.payloadfactory.ui/4.1.2/src/main/java/org/wso2/carbon/mediator/payloadfactory/PayloadFactoryMediator.java:[277,16]
> cannot find symbol
> [ERROR] symbol  : class SynapseJsonPath
> [ERROR] location: class
> org.wso2.carbon.mediator.payloadfactory.PayloadFactoryMediator.Argument
> [ERROR]
> /home/amila/development/branches/4.1.0/platform/components/mediators/payloadFactory/org.wso2.carbon.mediator.payloadfactory.ui/4.1.2/src/main/java/org/wso2/carbon/mediator/payloadfactory/PayloadFactoryMediator.java:[296,15]
> cannot find symbol
> [ERROR] symbol  : class SynapseJsonPath
> [ERROR] location: class
> org.wso2.carbon.mediator.payloadfactory.PayloadFactoryMediator.Argument
> [ERROR]
> /home/amila/development/branches/4.1.0/platform/components/mediators/payloadFactory/org.wso2.carbon.mediator.payloadfactory.ui/4.1.2/src/main/java/org/wso2/carbon/mediator/payloadfactory/PayloadFactoryMediator.java:[300,32]
> cannot find symbol
> [ERROR] symbol  : class SynapseJsonPath
> [ERROR] location: class
> org.wso2.carbon.mediator.payloadfactory.PayloadFactoryMediator.Argument
> [ERROR]
> /home/amila/development/branches/4.1.0/platform/components/mediators/payloadFactory/org.wso2.carbon.mediator.payloadfactory.ui/4.1.2/src/main/java/org/wso2/carbon/mediator/payloadfactory/PayloadFactoryMediator.java:[188,48]
> cannot find symbol
> [ERROR] symbol  : variable SynapseJsonPathFactory
> [ERROR] location: class
> org.wso2.carbon.mediator.payloadfactory.PayloadFactoryMediator
> [ERROR] -> [Help 1]
>
> Regards,
> AmilaM.
>
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Latest ESB 4.7.0 Pack 05-06-2013

[Ravi Undupitiya]

Please find $subject at [1].

[1]
http://svn.wso2.org/repos/wso2/people/ravi/packs/20130605-wso2esb-4.7.0.zip


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB: Integration test failure

[Ravi Undupitiya]

Hi Lahiru,


I'm not seeing this error on the latest build. Which pack did you use to
run this? It's possible this was fixed recently as there were some issues
resolved related to XSLT Transformation.



Thanks,
Ravi


On Fri, May 31, 2013 at 2:54 PM, Lahiru Sandaruwan  wrote:

> Hi,
>
> $subject for 1 out of 7 tests in XSLT tests.
>
> Results :
>
> Failed tests:
> xsltTransformationFromUrl(org.wso2.carbon.mediator.tests.xslt.XsltTransformationFromUrlTestCase):
> Unable to perform XSLT transformation using : Value {name ='null', keyValue
> ='transform.xslt'} against source XPath : s11:Body/child::*[position()=1] |
> s12:Body/child::*[position()=1]
>
> Tests run: 7, Failures: 1, Errors: 0, Skipped: 0
>
>
> Attached the surefire report.
>
> Thanks.
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahi...@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Build Error: JGIT 4.1.3 Patch Release

[Ravi Undupitiya]

Hi,


Getting the following build error:

ERROR] Failed to execute goal on project org.eclipse.jgit: Could not
resolve dependencies for project
org.eclipse.jgit:org.eclipse.jgit:jar:2.3.1-wso2v2: Could not find artifact
com.jcraft:jsch:jar:0.1.49.wso2v1 in jgit-repository (
http://download.eclipse.org/jgit/maven) -> [Help 1]




-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Isuru Perera

[Ravi Undupitiya]

Congratulations Isuru! :)


On Mon, Jun 3, 2013 at 5:27 PM, Susankha Nirmala  wrote:

> Congratz isuru!
>
>
> On Mon, Jun 3, 2013 at 5:21 PM, Piyum Fernando  wrote:
>
>> Congrads Isuru!
>>
>>
>> On Mon, Jun 3, 2013 at 5:18 PM, Supun Malinga  wrote:
>>
>>> Congrats!
>>>
>>>
>>> On Mon, Jun 3, 2013 at 5:13 PM, Lasantha Fernando wrote:
>>>
>>>> Congrats Isuru!... :-)
>>>>
>>>>
>>>> On 3 June 2013 17:10, Ramith Jayasinghe  wrote:
>>>>
>>>>> Contragrats Isuru!
>>>>>
>>>>>
>>>>> On Mon, Jun 3, 2013 at 5:08 PM, Nirmal Fernando wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jun 3, 2013 at 5:07 PM, Nirmal Fernando wrote:
>>>>>>
>>>>>>> Congratulations IsuruP!
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jun 3, 2013 at 5:04 PM, Lakmal Warusawithana <
>>>>>>> lak...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Its my pleasure to welcome Isuru Perera as a WSO2 Commiter.
>>>>>>>>
>>>>>>>> IsuruP has done excellent contribution in the areas of
>>>>>>>> Stratos2 specially new CLI and Stratos Controller UI.
>>>>>>>>
>>>>>>>> IsuruP, welcome aboard and keep up the good work.
>>>>>>>>
>>>>>>>> regards
>>>>>>>>
>>>>>>>> --
>>>>>>>> Lakmal Warusawithana
>>>>>>>> Software Architect; WSO2 Inc.
>>>>>>>> Mobile : +94714289692
>>>>>>>>
>>>>>>>>
>>>>>>>> ___
>>>>>>>> Dev mailing list
>>>>>>>> Dev@wso2.org
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Thanks & regards,
>>>>>>> Nirmal
>>>>>>>
>>>>>>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>>>>>>> Mobile: +94715779733
>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Thanks & regards,
>>>>>> Nirmal
>>>>>>
>>>>>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>>>>>> Mobile: +94715779733
>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ramith Jayasinghe
>>>>> Technical Lead
>>>>> WSO2 Inc., http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> E: ram...@wso2.com
>>>>> P: +94 776715671
>>>>>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Lasantha Fernando*
>>>> Software Engineer - Data Technologies Team
>>>> WSO2 Inc. http://wso2.com
>>>>
>>>> email: lasan...@wso2.com
>>>> mobile: (+94) 71 5247551
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Supun Malinga,
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>> email - sup...@wso2.com 
>>> mobile - 071 56 91 321
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Piyum Fernando
>> Software Engineer
>>
>> Mobile: +94 77 22 93 880
>> Home:  +94 31 22 75 715
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Susankha Nirmala
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] 4.1.2 Build Error am-p2-profile

[Ravi Undupitiya]

For some reason the feature
org.wso2.carbon.stratos.common.server.feature-2.1.2.zip file does not
contain
features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xml - I
manually replaced this and got it working.

The same thing was done for tenant-mgt.xml which was also missing from the
feature zip.


On Fri, May 31, 2013 at 6:42 PM, Ravi Undupitiya  wrote:

> I'm getting the same error on 4.1.3 now with wso2esb-p2-profile. The error
> is below.
>
>
> An error occurred while configuring the installed items
>  session context was:(profile=WSO2CarbonProfile,
> phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
> --> [R]org.wso2.carbon.stratos.common.server.feature.group 2.1.2,
> action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
>
> I/O Error while copying
> /home/esb/carbon/platform/4.1.0/products/esb/4.7.0/modules/p2-profile/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xml
> - see details.
> Caused by:  java.io.IOException: Source:
> /home/esb/carbon/platform/4.1.0/products/esb/4.7.0/modules/p2-profile/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xmldoes
> not exists
>
>
>
>
> On Fri, May 31, 2013 at 2:59 PM, Nuwan Dias  wrote:
>
>> On Fri, May 31, 2013 at 2:07 PM, Kasun Indrasiri  wrote:
>>
>>> Hi Ravi,
>>>
>>> Seems there are successful builds on the same patch release version on
>>> clean repo. Refer '[Dev] BAM 2.3.0 RC pack for testing'.
>>> @AM team : Are we building 4.1.2 based packs on clean repo?
>>>
>>
>> Yes, we moved to a clean repo about 3/4 days back.
>>
>>>
>>>
>>> On Fri, May 31, 2013 at 1:07 PM, Ravi Undupitiya  wrote:
>>>
>>>> I'm getting the following build error while trying to build 4.1.2
>>>> branch:
>>>>
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.wso2.maven:carbon-p2-plugin:1.5.2:p2-profile-gen
>>>> (4-p2-profile-generation) on project am-p2-profile: P2 publisher return
>>>> code was 13 -> [Help 1]
>>>>
>>>>
>>>> An error occurred while configuring the installed items
>>>>  session context was:(profile=WSO2CarbonProfile,
>>>> phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
>>>> --> [R]org.wso2.carbon.stratos.common.server.feature.group 2.1.2,
>>>> action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
>>>>  I/O Error while copying
>>>> /home/esb/carbon/platform/4.1.0/products/apimgt/1.4.0/modules/p2-profile/product/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xml
>>>> - see details.
>>>> Caused by:  java.io.IOException: Source:
>>>> /home/esb/carbon/platform/4.1.0/products/apimgt/1.4.0/modules/p2-profile/product/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xmldoes
>>>> not exists
>>>>
>>>>
>>>> --
>>>> *Ravi Undupitiya*
>>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>>> *
>>>> *
>>>> *E-mail: r...@wso2.com
>>>> **M: **+94 772 930 712*
>>>> *
>>>> *Lean . Enterprise . Middleware
>>>>
>>>
>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Associate Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 71 536 4128
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Member, Management Committee - Solutions Technology Group
>> Senior Software Engineer - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> *Ravi Undupitiya*
> Software Engineer; WSO2 Inc.; http://wso2.com
> *
> *
> *E-mail: r...@wso2.com
> **M: **+94 772 930 712*
> *
> *Lean . Enterprise . Middleware
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] 4.1.2 Build Error am-p2-profile

[Ravi Undupitiya]

I'm getting the same error on 4.1.3 now with wso2esb-p2-profile. The error
is below.


An error occurred while configuring the installed items
 session context was:(profile=WSO2CarbonProfile,
phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
--> [R]org.wso2.carbon.stratos.common.server.feature.group 2.1.2,
action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).

I/O Error while copying
/home/esb/carbon/platform/4.1.0/products/esb/4.7.0/modules/p2-profile/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xml
- see details.
Caused by:  java.io.IOException: Source:
/home/esb/carbon/platform/4.1.0/products/esb/4.7.0/modules/p2-profile/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xmldoes
not exists



On Fri, May 31, 2013 at 2:59 PM, Nuwan Dias  wrote:

> On Fri, May 31, 2013 at 2:07 PM, Kasun Indrasiri  wrote:
>
>> Hi Ravi,
>>
>> Seems there are successful builds on the same patch release version on
>> clean repo. Refer '[Dev] BAM 2.3.0 RC pack for testing'.
>> @AM team : Are we building 4.1.2 based packs on clean repo?
>>
>
> Yes, we moved to a clean repo about 3/4 days back.
>
>>
>>
>> On Fri, May 31, 2013 at 1:07 PM, Ravi Undupitiya  wrote:
>>
>>> I'm getting the following build error while trying to build 4.1.2
>>> branch:
>>>
>>>
>>> [ERROR] Failed to execute goal
>>> org.wso2.maven:carbon-p2-plugin:1.5.2:p2-profile-gen
>>> (4-p2-profile-generation) on project am-p2-profile: P2 publisher return
>>> code was 13 -> [Help 1]
>>>
>>>
>>> An error occurred while configuring the installed items
>>>  session context was:(profile=WSO2CarbonProfile,
>>> phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
>>> --> [R]org.wso2.carbon.stratos.common.server.feature.group 2.1.2,
>>> action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
>>>  I/O Error while copying
>>> /home/esb/carbon/platform/4.1.0/products/apimgt/1.4.0/modules/p2-profile/product/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xml
>>> - see details.
>>> Caused by:  java.io.IOException: Source:
>>> /home/esb/carbon/platform/4.1.0/products/apimgt/1.4.0/modules/p2-profile/product/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xmldoes
>>> not exists
>>>
>>>
>>> --
>>> *Ravi Undupitiya*
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> *
>>> *
>>> *E-mail: r...@wso2.com
>>> **M: **+94 772 930 712*
>>> *
>>> *Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> Kasun Indrasiri
>> Associate Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 71 536 4128
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> Nuwan Dias
>
> Member, Management Committee - Solutions Technology Group
> Senior Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] 4.1.3 Integration Test Failure: Jaggery Integration

[Ravi Undupitiya]

Hello,

I'm getting the following Integration Test failure on Jaggery. I'll comment
this bit out and build.

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on
project integration: There are test failures.
[ERROR]
[ERROR] Please refer to
/home/esb/carbon/platform/4.1.0/dependencies/jaggery/0.9.0.ALPHA3-wso2v6/server/integration/target/surefire-reports
for the individual test results.

Results :

Failed tests:
testGetEnvProcessParams(org.wso2.jaggery.integration.tests.hostObjects.ProcessObjectTestCase):
expected:<28> but was:<29>



Thanks,
Ravi

-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] 4.1.2 Build Error am-p2-profile

[Ravi Undupitiya]

Since that is a BAM build, maybe they commented out APIM??

As a workaround I commented out the product builds - since we only need
4.1.2 components/features. I hope this is ok.



Thanks,
Ravi


On Fri, May 31, 2013 at 2:07 PM, Kasun Indrasiri  wrote:

> Hi Ravi,
>
> Seems there are successful builds on the same patch release version on
> clean repo. Refer '[Dev] BAM 2.3.0 RC pack for testing'.
> @AM team : Are we building 4.1.2 based packs on clean repo?
>
>
> On Fri, May 31, 2013 at 1:07 PM, Ravi Undupitiya  wrote:
>
>> I'm getting the following build error while trying to build 4.1.2 branch:
>>
>>
>> [ERROR] Failed to execute goal
>> org.wso2.maven:carbon-p2-plugin:1.5.2:p2-profile-gen
>> (4-p2-profile-generation) on project am-p2-profile: P2 publisher return
>> code was 13 -> [Help 1]
>>
>>
>> An error occurred while configuring the installed items
>>  session context was:(profile=WSO2CarbonProfile,
>> phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
>> --> [R]org.wso2.carbon.stratos.common.server.feature.group 2.1.2,
>> action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
>>  I/O Error while copying
>> /home/esb/carbon/platform/4.1.0/products/apimgt/1.4.0/modules/p2-profile/product/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xml
>> - see details.
>> Caused by:  java.io.IOException: Source:
>> /home/esb/carbon/platform/4.1.0/products/apimgt/1.4.0/modules/p2-profile/product/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xmldoes
>> not exists
>>
>>
>> --
>> *Ravi Undupitiya*
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> *
>> *
>> *E-mail: r...@wso2.com
>> **M: **+94 772 930 712*
>> *
>> *Lean . Enterprise . Middleware
>>
>
>
>
> --
> Kasun Indrasiri
> Associate Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] 4.1.2 Build Error am-p2-profile

[Ravi Undupitiya]

I'm getting the following build error while trying to build 4.1.2 branch:


[ERROR] Failed to execute goal
org.wso2.maven:carbon-p2-plugin:1.5.2:p2-profile-gen
(4-p2-profile-generation) on project am-p2-profile: P2 publisher return
code was 13 -> [Help 1]


An error occurred while configuring the installed items
 session context was:(profile=WSO2CarbonProfile,
phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
--> [R]org.wso2.carbon.stratos.common.server.feature.group 2.1.2,
action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
 I/O Error while copying
/home/esb/carbon/platform/4.1.0/products/apimgt/1.4.0/modules/p2-profile/product/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xml
- see details.
Caused by:  java.io.IOException: Source:
/home/esb/carbon/platform/4.1.0/products/apimgt/1.4.0/modules/p2-profile/product/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xmldoes
not exists


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [URGENT] Need to add MultiValued header patch to APPLY

[Ravi Undupitiya]

Hi Dushan,


This patch is in both 2.1.1-wso2v5 and 2.1.1-wso2v6.

Was something not working?



Thanks,
Ravi


On Fri, May 24, 2013 at 10:35 PM, Dushan Abeyruwan  wrote:

> Hi Ravi
>
> Stratos ELB: Multiple Set-Cookie header in one response
> *multivalue-header-passthru.diff*
> 8K   
> Download<https://mail.google.com/mail/u/0/?ui=2&ik=d46cb1a626&view=att&th=13d598777d14f63c&attid=0.1&disp=safe&realattid=f_he5mzelc0&zw>
>
>
> we have missed all these patches for Synapse 2.1.1-wso2v5 please make sure
> this has been patched properly
>
>
>
>
>
> cheeers,
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)714408632*
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESB 4.7.0 Alpha Pack for Testing (28/05/2013)

[Ravi Undupitiya]

Please find $subject at [1] - feature complete alpha pack.

[1]
https://svn.wso2.org/repos/wso2/people/ravi/packs/20130528-wso2esb-4.7.0.zip



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Patch Release 4.1.3 Build Error

[Ravi Undupitiya]

Hi,

Getting the following when trying to build 4.1.3 patch release:

[ERROR]   The project org.apache.juddi:juddiv3-war:3.1.5.wso2v1
(/home/ravi/PACK/platform/4.1.0/products/greg/4.6.0/modules/juddiv3-war/pom.xml)
has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact
org.apache.juddi:juddi-parent:pom:3.1.5.wso2v1 in central (
http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
wrong local POM @ line 13, column 10 -> [Help 2]



Thanks,
Ravi

-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Ravi Undupitiya

[Ravi Undupitiya]

Thanks all. :)



Ravi


On Tue, May 14, 2013 at 12:30 PM, Sivajothy Vanjikumaran wrote:

> congrats ravi :)
>
>
> On Tue, May 14, 2013 at 11:48 AM, Miyuru Wanninayaka wrote:
>
>> Hi all,
>>
>> It's my pleasure to announce Ravi as a WSO2 committer. Ravi made a
>> excellent contribution to WSO2 ESB.
>>
>> @Ravi, welcome abroad and keep up the good work!
>>
>> Cheers!
>> --
>> Miyuru Wanninayaka
>> Senior Software Engineer
>> Member, Management Committee - Integration Technologies
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile : +94 77 209 9788
>> Blog : http://miyurudw.blogspot.com
>> Flickr : http://www.flickr.com/photos/miyuru_daminda
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sivajothy Vanjikumaran
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)777219209**
> *[image: Facebook] <https://www.facebook.com/vanjikumaran> [image:
> Twitter] <https://twitter.com/vanjikumaran> [image: 
> LinkedIn]<http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293> 
> [image:
> Blogger] <http://vanjikumaran.blogspot.com/> [image: 
> SlideShare]<http://www.slideshare.net/vanjikumaran>
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Security Component disableREST always set to true when a policy exists

[Ravi Undupitiya]

Hi,


The proposed hack for to fix this issue is to parse out the Security
Scenario wsuid ("WSO2ServiceThrottlingPolicy",
"RMPolicy", WSO2CachingPolicy"). And to check if one of these exist, and if
they do, not to disableREST.

But what if the user has asked for a particular service to have disableREST
set to true, each time the service restarts and the service has either
throttling, RM or caching, the opposite will now happen: disableREST will
be set to false.

IMHO, this is not a good solution.



Thanks,
Ravi


On Fri, May 10, 2013 at 11:20 AM, Asela Pathberiya  wrote:

> Issue may be related to this [1].  Because when you applied caching, RM
> and throttling policy,  there are also persist as security policies (with
> security policy name space).  Therefore security component would see this
> as security policy and try to process
>
> [1] https://wso2.org/jira/browse/CARBON-13927
>
> Thanks,
> Asela
>
>
> On Thu, May 9, 2013 at 5:26 PM, Ravi Undupitiya  wrote:
>
>> Copying below mail to dev.
>>
>>
>> On Thu, May 9, 2013 at 2:17 PM, Ravi Undupitiya  wrote:
>>
>>> Hello,
>>>
>>> I'm looking at ESBJAVA-1845. The problem is described below:
>>>
>>> Enabling throttling on a service causes this to be added to the service
>>> WSDL:
>>>
>>> http://schemas.xmlsoap.org/ws/2004/09/policy";
>>> xmlns:wsu="
>>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
>>> wsu:Id="WSO2ServiceThrottlingPolicy">
>>> 
>>> 
>>> 
>>> 
>>>
>>>
>>> This makes the security component call disableRESTCalls and
>>> applySecurityParameters which turns disableREST to true. This happens every
>>> time we start the server.
>>>
>>>
>>> What is the best way to handle this case?
>>>
>>>
>>>
>>> Thanks,
>>> Ravi
>>>
>>
>> --
>> *Ravi Undupitiya*
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> *
>> *
>> *E-mail: r...@wso2.com
>> **M: **+94 772 930 712*
>> *
>> *Lean . Enterprise . Middleware
>>
>
>
>
> --
> Thanks & Regards,
> Asela
>
> Mobile : +94 777 625 933
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Security Component disableREST always set to true when a policy exists

[Ravi Undupitiya]

Copying below mail to dev.


On Thu, May 9, 2013 at 2:17 PM, Ravi Undupitiya  wrote:

> Hello,
>
> I'm looking at ESBJAVA-1845. The problem is described below:
>
> Enabling throttling on a service causes this to be added to the service
> WSDL:
>
> http://schemas.xmlsoap.org/ws/2004/09/policy";
> xmlns:wsu="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
> wsu:Id="WSO2ServiceThrottlingPolicy">
> 
> 
> 
> 
>
>
> This makes the security component call disableRESTCalls and
> applySecurityParameters which turns disableREST to true. This happens every
> time we start the server.
>
>
> What is the best way to handle this case?
>
>
>
> Thanks,
> Ravi
>

-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Axis2 Multipart/Form-Data Builder

[Ravi Undupitiya]

Hi Charitha,


Not yet. I have to create a patch and pass it over to Sagara who is going
to commit it. I wanted to write a test case for it as well.



Thanks,
Ravi


On Tue, May 7, 2013 at 3:36 PM, Charitha Kankanamge wrote:

> Hi Ravi,
>
> On Tue, Apr 16, 2013 at 2:46 PM, Sagara Gunathunga wrote:
>
>>
>>
>>
>>
>> On Tue, Apr 16, 2013 at 1:08 PM, Ravi Undupitiya  wrote:
>>
>>> Hello,
>>>
>>>
>>> I'm trying to move the multipart/from-data builder to work without the
>>> use of Servlets so that this format can be used in the regular transports.
>>>
>>> To do this, I implemented a class of the apache commons-fileupload
>>> RequestContext which requires the following:
>>>
>>> 1.) Raw input stream.
>>> 2.) Content length.
>>> 3.) Charset encoding.
>>>
>>> I had an offline chat with Sagara regarding this and he recommended we
>>> set 2 and 3 inside the transports and that builders are meant to look up
>>> this information using the message context.
>>>
>>
>> Other than the issue you are trying fix there is another design problem
>> with above builder class, it use some HTTPServlet specific codes within the
>> builder class which result into builder only usable with Servlet transport
>> only. Basically Builders/Formatters are independent from any transport. As
>> I mentioned following should be the correct approach.
>>
>> 1. Remove those Servlet specific ( or any other transport specific) code
>> from above builder class instead builder methods should try to get above 3
>> properties from MC if not found them on MC throw an exception. You don't
>> need to introduce new class for this.
>>
>> 2. Underline transport should read above 2 or 3 values from transport
>> headers and should write to MC so that builder can use those values.
>>
>> You need to test your modifications for both NHTTP and Servlet
>> transports.  Also make sure to merge this change to current active branch
>> as well.
>>
>
> Have we committed these changes to current branch?
>
>
>>
>>
>> Thanks !
>>
>>
>>>
>>> So to start, I will add 2 and 3 to the message context inside the Axis2
>>> HTTP transport.
>>>
>>> Please advise if there are any problems with what is proposed above.
>>>
>>>
>>>
>>> Thanks,
>>> Ravi
>>>
>>> --
>>> *Ravi Undupitiya*
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> *
>>> *
>>> *E-mail: r...@wso2.com
>>> **M: **+94 772 930 712*
>>> *
>>> *Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Technical Lead; WSO2, Inc.;  http://wso2.com
>> V.P Apache Web Services;http://ws.apache.org/
>> Linkedin; http://www.linkedin.com/in/ssagara
>> Blog ;  http://ssagara.blogspot.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Axis2 Multipart/Form-Data Builder

[Ravi Undupitiya]

Hello,


I'm trying to move the multipart/from-data builder to work without the use
of Servlets so that this format can be used in the regular transports.

To do this, I implemented a class of the apache commons-fileupload
RequestContext which requires the following:

1.) Raw input stream.
2.) Content length.
3.) Charset encoding.

I had an offline chat with Sagara regarding this and he recommended we set
2 and 3 inside the transports and that builders are meant to look up this
information using the message context.

So to start, I will add 2 and 3 to the message context inside the Axis2
HTTP transport.

Please advise if there are any problems with what is proposed above.



Thanks,
Ravi

-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Pamod Sylvester

[Ravi Undupitiya]

Congrats Pamod! :)

On Thu, Mar 21, 2013 at 12:56 PM, Pamod Sylvester  wrote:

> Hi,
>
> Thank you very much for the great opportunity. Will keep contributing
> better.
>
> Thanks,
> Pamod
>
>
> On Thu, Mar 21, 2013 at 12:00 PM, Kasun Indrasiri  wrote:
>
>> Hi Folks,
>>
>> The All-MC has voted in Pamod Sylvester as a WSO2 committer. He has been
>> an excellent contributor for WSO2 ESB and other related projects over the
>> last few months and done an excellent job in EIP implementation space as
>> well.
>>
>> Pamod, welcome aboard and keep up the good work.
>>
>> Thanks,
>> Kasun
>>
>> --
>> Kasun Indrasiri
>> Associate Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 71 536 4128
>> Blog : http://kasunpanorama.blogspot.com/
>
>
>
>
> --
> *Pamod Sylvester *
> *
> *
> *
> Software Engineer
> *
> Integration Technologies Team, WSO2 Inc.; http://wso2.com
> email: pa...@wso2.com cell: +94 77 7779495
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.7.0 build admin login failure

[Ravi Undupitiya]

Hi,

Changes made to carbon kernel on r167864 seems to have fixed this issue.


Thanks,
Ravi

On Thu, Mar 14, 2013 at 12:39 PM, Ravi Undupitiya  wrote:

> Hi,
>
> I've built the latest ESB 4.7.0 pack and I'm trying to run integration
> tests but I get the following error:
>
>  WARN - CarbonAuthenticationUtil Failed Administrator login attempt
> 'admin[-1234]' at [2013-03-14 12:21:21,206+0530]
>
> I have checked by running the built pack and trying to login through the
> carbon web console with admin/admin and I get the same error.
>
> I checked user-mgt.xml and it has the following contents:
>
> 
> 
> true
> admin
> 
>  admin
>  admin
> 
> everyone 
> jdbc/WSO2CarbonDB
>  name="MultiTenantRealmConfigBuilder">org.wso2.carbon.user.core.config.multitenancy.SimpleRealmConfigBuilder
> 
>
>  class="org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager">
>  false
> 100
> false
>
> false
> default
> SHA-256
> true
> true
>  true
> false
> ^[\S]{5,30}$
>  name="PasswordJavaScriptRegEx">^[\\S]{5,30}$
>   name="UsernameJavaRegEx">^[^~!#$;%^*+={}\\|<>,\'\"]{3,30}$
>  ^[\\S]{3,30}$
>   name="RolenameJavaRegEx">^[^~!#$;%^*+={}\\|<>,\'\"]{3,30}$
>  ^[\\S]{3,30}$
> true
> 100
> 100
> 
>
> 
> class="org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager">
>  name="AdminRoleManagementPermissions">/permission
> true
> 
> 
>
>
>
>
> --
> *Ravi Undupitiya*
> Software Engineer; WSO2 Inc.; http://wso2.com
> *
> *
> *E-mail: r...@wso2.com
> **M: **+94 772 930 712*
> *
> *Lean . Enterprise . Middleware
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESB 4.7.0 build admin login failure

[Ravi Undupitiya]

Hi,

I've built the latest ESB 4.7.0 pack and I'm trying to run integration
tests but I get the following error:

 WARN - CarbonAuthenticationUtil Failed Administrator login attempt
'admin[-1234]' at [2013-03-14 12:21:21,206+0530]

I have checked by running the built pack and trying to login through the
carbon web console with admin/admin and I get the same error.

I checked user-mgt.xml and it has the following contents:



true
admin

 admin
 admin

everyone 
jdbc/WSO2CarbonDB
org.wso2.carbon.user.core.config.multitenancy.SimpleRealmConfigBuilder



 false
100
false

false
default
SHA-256
true
true
 true
false
^[\S]{5,30}$
^[\\S]{5,30}$
 ^[^~!#$;%^*+={}\\|<>,\'\"]{3,30}$
 ^[\\S]{3,30}$
 ^[^~!#$;%^*+={}\\|<>,\'\"]{3,30}$
 ^[\\S]{3,30}$
true
100
100



    /permission
true






-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stratos ELB: Multiple Set-Cookie header in one response

[Ravi Undupitiya]

Hi,

Thanks, will do the necessary testing.


Ravi

On Tue, Mar 12, 2013 at 10:28 AM, Dushan Abeyruwan  wrote:

> Hi
>Theoretically, if you replace headers with Mutivalue map, the areas
> which gonna impact are TargetResponse and SourceResponses (basically all
> the places where the headers getting consumed)
>
>FYI Ravi: Before me or Kasun apply this to synapse,* please make sure
> you have run all the Automation tests and integration tests, *make sure
> this modification does not introduced any new anomalies, so take your time
> and run AM and integration tests..and provide us the surefire test reports.
>
> *  "**I'm not sure what this may have broken. "* hope you got the answer
>
> cheers
> Dushan
>
>
> On Tue, Mar 12, 2013 at 9:45 AM, Nirmal Fernando  wrote:
>
>> Hi Ravi,
>>
>>
>> On Mon, Mar 11, 2013 at 8:58 AM, Ravi Undupitiya  wrote:
>>
>>> Hello,
>>>
>>> Adding ESBJAVA-1659 to passthru did the trick - took me a while to
>>> understand how the NIO patch worked and also how to add it to passthru.
>>>
>>
>> Nice to hear that fix worked. (I didn't get a chance to look at your
>> patch, but I know that the NIO patch, I created, is working :-))
>>
>>>
>>> I've attached the patch here. This should be applied to Synapse
>>> 2.1.1-wso2v2.
>>>
>>
>> I think it's better if you could merge this to trunk. Synapse
>> 2.1.1-wso2v2 is already released and you don't need to patch, since the bug
>> we're solving is of S2 and we gonna cut S2 from trunk.
>>
>>>
>>> I'm not sure what this may have broken.
>>>
>>
>> Well, get the help from Dushan, Kasun et al. and do a round of test,
>> please :-)
>>
>>
>>>
>>>
>>> Thanks,
>>> Ravi
>>>
>>> On Thu, Mar 7, 2013 at 6:06 AM, Nirmal Fernando  wrote:
>>>
>>>>
>>>> On Mar 6, 2013 9:15 PM, "Ravi Undupitiya"  wrote:
>>>> >
>>>> > Hello,
>>>> >
>>>> >
>>>> >
>>>> > When the Stratos ELB is proxying third party applications - some of
>>>> these applications send several Set-Cookie headers in one response.
>>>> >
>>>> > RFC2109 states:
>>>> >
>>>> > An origin server may include multiple Set-Cookie headers in a
>>>> >response.  Note that an intervening gateway could fold multiple
>>>> such
>>>> >headers into a single header.
>>>> >
>>>> >
>>>> > Which means we should be able to fold multiple cookies into one
>>>> Set-Cookie. However this specification is obsolete and the more
>>>> up-to-date version (RFC6265) states:
>>>> >
>>>> >
>>>> > Origin servers SHOULD NOT fold multiple Set-Cookie header fields into
>>>> >a single header field.  The usual mechanism for folding HTTP
>>>> headers
>>>> >fields (i.e., as defined in [RFC2616]) might change the semantics
>>>> of
>>>> >the Set-Cookie header field because the %x2C (",") character is
>>>> used
>>>> >by Set-Cookie in a way that conflicts with such folding.
>>>> >
>>>> >
>>>> >
>>>> > I suspect this to be the issue when proxying Wordpress via the ELB -
>>>> Multiple Set-Cookies are ignored by the current Synapse implementation.
>>>> >
>>>> > I tried, making the synapse implementation fold multiple cookies (as
>>>> per the older RFC2109) using "," but it didn't do anything different.
>>>> >
>>>> >
>>>> > Did the wordpress login work in previous versions?
>>>> >
>>>> > Also I have been implementing
>>>> https://wso2.org/jira/browse/ESBJAVA-1659 for the passthru transport -
>>>> but if I understand correctly this only solves the issue of a header having
>>>> multiple values and not multiple headers by the same name?
>>>>
>>>> If you read the test case there, you'll see that this is the exact
>>>> issue.
>>>> >
>>>> >
>>>> > Thanks,
>>>> >
>>>> > Ravi
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>>
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Software Engineer- Platform Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>> <http://nirmalfdo.blogspot.com/>
>>
>
>
>
> --
> Dushan Abeyruwan
> *Senior Software Engineer*
> *Integration Technologies Team*
> *Member of Integration MC*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)714408632*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stratos ELB: Multiple Set-Cookie header in one response

[Ravi Undupitiya]

Hello,

Adding ESBJAVA-1659 to passthru did the trick - took me a while to
understand how the NIO patch worked and also how to add it to passthru.

I've attached the patch here. This should be applied to Synapse
2.1.1-wso2v2.

I'm not sure what this may have broken.


Thanks,
Ravi

On Thu, Mar 7, 2013 at 6:06 AM, Nirmal Fernando  wrote:

>
> On Mar 6, 2013 9:15 PM, "Ravi Undupitiya"  wrote:
> >
> > Hello,
> >
> >
> >
> > When the Stratos ELB is proxying third party applications - some of
> these applications send several Set-Cookie headers in one response.
> >
> > RFC2109 states:
> >
> > An origin server may include multiple Set-Cookie headers in a
> >response.  Note that an intervening gateway could fold multiple such
> >headers into a single header.
> >
> >
> > Which means we should be able to fold multiple cookies into one
> Set-Cookie. However this specification is obsolete and the more
> up-to-date version (RFC6265) states:
> >
> >
> > Origin servers SHOULD NOT fold multiple Set-Cookie header fields into
> >a single header field.  The usual mechanism for folding HTTP headers
> >fields (i.e., as defined in [RFC2616]) might change the semantics of
> >the Set-Cookie header field because the %x2C (",") character is used
> >by Set-Cookie in a way that conflicts with such folding.
> >
> >
> >
> > I suspect this to be the issue when proxying Wordpress via the ELB -
> Multiple Set-Cookies are ignored by the current Synapse implementation.
> >
> > I tried, making the synapse implementation fold multiple cookies (as per
> the older RFC2109) using "," but it didn't do anything different.
> >
> >
> > Did the wordpress login work in previous versions?
> >
> > Also I have been implementing https://wso2.org/jira/browse/ESBJAVA-1659 for
> the passthru transport - but if I understand correctly this only solves the
> issue of a header having multiple values and not multiple headers by the
> same name?
>
> If you read the test case there, you'll see that this is the exact issue.
> >
> >
> > Thanks,
> >
> > Ravi
> >
> >
> >
> >
> >
>


multivalue-header-passthru.diff
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Stratos ELB: Multiple Set-Cookie header in one response

[Ravi Undupitiya]

Hello,



When the Stratos ELB is proxying third party applications - some of these
applications send several Set-Cookie headers in one response.

RFC2109 states:

An origin server may include multiple Set-Cookie headers in a
   response.  Note that an intervening gateway could fold multiple such
   headers into a single header.


Which means we should be able to fold multiple cookies into one
Set-Cookie. However this specification is obsolete and the more
up-to-date version (RFC6265) states:


Origin servers SHOULD NOT fold multiple Set-Cookie header fields into
   a single header field.  The usual mechanism for folding HTTP headers
   fields (i.e., as defined in [RFC2616
]) might change the semantics of
   the Set-Cookie header field because the %x2C (",") character is used
   by Set-Cookie in a way that conflicts with such folding.


I suspect this to be the issue when proxying Wordpress via the ELB -
Multiple Set-Cookies are ignored by the current Synapse
implementation.

I tried, making the synapse implementation fold multiple cookies (as
per the older RFC2109) using "," but it didn't do anything different.


Did the wordpress login work in previous versions?

Also I have been implementing
https://wso2.org/jira/browse/ESBJAVA-1659 for the passthru transport -
but if I understand correctly this only solves the issue of a header
having multiple values and not multiple headers by the same name?


Thanks,

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

[Dev] HTTP Endpoint UI Verification

[Ravi Undupitiya]

Hello,

I'm enhancing the HTTP EP verification in two ways:

   1. The UI will check the URI template to see if it is valid.
   2. Use the HTTP OPTIONS method to see what methods the endpoint supports
   and append this as part of the current success message that is displayed.


Also, the HTTP EP works fine with a SOAP BE (as long as the method is
POST).


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

Re: [Dev] ESB - HTTP Endpoint for Outbound HTTP Calls

[Ravi Undupitiya]

Hi,


I've worked on the HTTP Endpoint UI component - and have uploaded a patch
which can be found on https://wso2.org/jira/browse/ESBJAVA-1786.



Thanks,
Ravi

On Fri, Jan 4, 2013 at 3:38 PM, Kasun Indrasiri  wrote:

> Hi,
>
> - The first cut of the HTTP Endpoints for outbound REST integration (I
> have attached the diff and required esb config). Basically, this feature
> allows us to create a new endpoint type 'http' to facilitate outbound REST
> calls. The outbound uri is dynamically generated with the use of URI
> Templates and required http method can be selected.
>
> - Since the WSO2 URI-template doesn't support expanding, *
> https://github.com/damnhandy/Handy-URI-Templates* was used.
> - Also, this endpoint type allows us to dynamically construct the endpoint
> uri for SOAP services as well (i.e by method set to POST).
>
> *Sample Scenario:*
>
> The scenario is to send a outbound http call to an external RESTful
> service.
> SOAP () - > REST ()
>
> *GET*
>
> http://localhost:8080/PizzaShopServlet/restapi/PizzaWS/menu?category=pizza&type=pan
>
> *POST*
> http://localhost:8080/PizzaShopServlet/restapi/PizzaWS
>
> So we can have endpoint uri template as follows :
> *http://localhost:8080/{uri.var.servicepath}/restapi/{uri.var.servicename
> }/menu?category={uri.var.}&type={uri.var.pizzaType}*
>
> eg:
> http://ws.apache.org/ns/synapse"; name="TestEP">
>  http://localhost:8080/{uri.var.servicepath}/restapi/{uri.var.servicename}/menu?category={uri.var.category}&type={uri.var.pizzaType}
> "
>   method="GET">
> 
>
> The properties defined in the inSeq will get dynamically expanded during
> the outbound call.
>  
> 
> 
> 
> 
> 
> 
> 
> 
>
>
>
> Remaining stuff :
> - Payload Factory for other formats
> - HTTP Header mediator
> - HTTP EP UI
>
>
>
>
> -- Forwarded message --
> From: Kasun Indrasiri 
> Date: Thu, Nov 8, 2012 at 11:28 AM
> Subject: [Architecture]Outbound HTTP Calls in the ESB
> To: architecture 
>
>
> We had a discussion on the $subject.
>
> *Attendees: Kasun, Miyuru, Paul, Sanjiva, Shankar.
> Date: Wed Nov 7 2012
>
> 
>
> 
>
>  [method=”string or {property}”]
>
>[statistics="enable|disable"]
> [trace="enable|disable"]>
>
> expression=”xpath-expression”)/>*
>
>
>timeout duration in milliseconds
>discard|fault
>?
>
>
>[xxx,yyy]
>m
>d
>
>
>
>[xxx,yyy]
>n
>r
>l
>
> 
> 
>
> 
> 
>
> ONE OF:
>   {“a” : {{uri.var.user}}, “b” : “$1”}
>Hello there Mr. $1
>   

Re: [Dev] platform build error

[Ravi Undupitiya]

Hi,


I got the same error. Here's more output with the -e switch:

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 56.731s
[INFO] Finished at: Tue Dec 04 16:40:22 IST 2012
[INFO] Final Memory: 110M/1322M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project
hive-deploy: An Ant BuildException has occured: The following error
occurred while executing this line:
[ERROR]
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/build.xml:297:
The following error occurred while executing this line:
[ERROR]
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/build.xml:151:
The following error occurred while executing this line:
[ERROR]
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/metastore/build.xml:98:
Java returned: 1
[ERROR] around Ant part .. @ 4:137 in
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/deploy/target/antrun/build-main.xml
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on
project hive-deploy: An Ant BuildException has occured: The following error
occurred while executing this line:
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/build.xml:297:
The following error occurred while executing this line:
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/build.xml:151:
The following error occurred while executing this line:
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/metastore/build.xml:98:
Java returned: 1
around Ant part .. @ 4:137 in
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/deploy/target/antrun/build-main.xml
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: An Ant
BuildException has occured: The following error occurred while executing
this line:
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/build.xml:297:
The following error occurred while executing this line:
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/build.xml:151:
The following error occurred while executing this line:
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/metastore/build.xml:98:
Java returned: 1
around Ant part .. @ 4:137 in
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/deploy/target/antrun/build-main.xml
at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:355)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by:
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/deploy/target/antrun/build-main.xml:4:
The following error occurred while executing this line:
/home/ravi/Projects/carbon/platform/branches/4.0.0/dependencies/hive/0.8.1-wso2v5/build.xml:297:
The following error occurred while executing this line:
/home/ravi/Projects/carbon/platform/bran

[Dev] Compiling Carbon Platform 4.0.5 and Maven Repository Failure

[Ravi Undupitiya]

Hello,


I'm compiling carbon-platform 4.0.5 with -DskipTests and found this error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0:compile
(default-compile) on project synapse-samples:  Compilation failure:
Compilation failure:
[ERROR] error: error reading
/home/ravi/.m2/repository/bouncycastle/bcprov-jdk14/140/bcprov-jdk14-140.jar;
error in opening zip file

The bcprov-jdk14.-140.jar file turned out to be a default 404 error HTML
and not a JAR file. Seems like maven is being pointed at the wrong location
for this. I fixed this by downloading the correct file from
http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22bcprov-jdk14%22.


Also, I've written down a tutorial with solutions to some of the pitfalls I
came across (like setting maven_opts, skipping tests, etc) while building
orbit/kernel and platform. Is there something like a wiki I can put this
information on, as it might be helpful for others travelling down the same
path.



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