[Dev] WSO2 Committers += Pranavan Somaskandhan
Hi all, It's my pleasure to announce Pranavan Somaskandhan as a WSO2 Committer. He has been a valuable contributor to WSO2. Congratulations Pranavan and keep up the good work...! Thanks, Anupama -- *Anupama Pathirage *| Senior Technical Lead | WSO2 Inc. (m) +94 718 273 979 | (e) anup...@wso2.com | (b) https://medium.com/@anupama.pathirage [image: http://wso2.com/signature] <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Chanaka Lakmal
Hi all, It's my pleasure to announce Chanaka Lakmal as a WSO2 Committer. He has been a valuable contributor to WSO2. Congratulations Chanaka and keep up the good work...! Thanks, Anupama -- *Anupama Pathirage *| Technical Lead | WSO2 Inc. (m) +94 718 273 979 | (e) anup...@wso2.com | (b) https://medium.com/@anupama.pathirage [image: http://wso2.com/signature] <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Pubudu Fernando
Hi All, It's my pleasure to announce Pubudu Fernando as a WSO2 Committer. He has been valuable contributor to the Ballerina team. In recognition of his contribution, dedication and commitment he has been voted as a WSO2 committer. Congratulations Pubudu and keep up the good work...! Thanks, Anupama -- Anupama Pathirage Technical Lead WSO2, Inc. http://wso2.com/ Email: anup...@wso2.com Blog: http://mycodeideas.blogspot.com Mobile:+94 71 8273 979 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] String to JSON in Ballerina 0.89
Hi,
In earlier versions of ballerina following should work for string to json
and json to string conversions.
import ballerina.lang.system;
import ballerina.lang.jsons;
function main(string[] args) {
string s1 = "{'ab':'ddd'}";
json jsonVal = s1;
system:println(jsonVal);
string s2 = jsons:toString(jsonVal);
system:println(s2);
}
Thanks,
Anupama
On Mon, Oct 30, 2017 at 5:07 PM, Gayan Chamara <gaya...@wso2.com> wrote:
> Hi Rajith & Suthagar,
> I tried the suggested method, but no luck. It gives the following error
> message,
>
> *incompatible types: 'string' cannot be converted to 'json'*
>
>
> I'm restricted to ballerina 0.89 because API Manager has not moved to a
> newer version yet.
>
> Regards,
> Gayan.
>
> On Mon, Oct 30, 2017 at 4:57 PM, Suthagar Kailayapathy <sutha...@wso2.com>
> wrote:
>
>> Hi Gayan,
>>
>> Can you please take a look at here(last one),
>> https://groups.google.com/forum/#!topic/ballerina-dev/DIWQIULUvSw
>>
>> string s = "somejson";
>> json j;
>> Error e;
>> j, err = s;
>>
>> Thanks.
>>
>> On Mon, Oct 30, 2017 at 4:39 PM, Gayan Chamara <gaya...@wso2.com> wrote:
>>
>>> Hi,
>>> Is there a way to convert JSON string into ballerina json type in
>>> ballerina 0.89? I couldn't find a suitable method in the docs.
>>>
>>> Thanks,
>>> Gayan.
>>>
>>> --
>>> Regards,
>>>
>>> *Gayan Chamara*
>>>
>>> *Software Engineering Intern*
>>> *WSO2 Inc.*
>>>
>>>
>>> *Email: gaya...@wso2.com <gaya...@wso2.com> *
>>> *Mobile : **+94 71 728 5827 <+94%2071%20728%205827>*
>>> <http://wso2.com/signature>
>>>
>>
>>
>>
>> --
>>
>> *K.Suthagar*
>> Software Engineering Intern | WSO2
>> LinkedIn: https://www.linkedin.com/in/ksuthagar
>> <http://suthagar.inncaps.com/>
>>
>> Email: sutha...@wso2.com
>> Mobile : +94779543968 <+94%2077%20954%203968>
>> Web: http://wso2.com
>>
>>
>
>
> --
> Regards,
>
> *Gayan Chamara*
>
> *Software Engineering Intern*
> *WSO2 Inc.*
>
>
> *Email: gaya...@wso2.com <gaya...@wso2.com> *
> *Mobile : **+94 71 728 5827 <+94%2071%20728%205827>*
> <http://wso2.com/signature>
>
--
Anupama Pathirage
Technical Lead
WSO2, Inc. http://wso2.com/
Email: anup...@wso2.com
Blog: http://mycodeideas.blogspot.com
Mobile:+94 71 8273 979
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Chathurika De Silva
Congratulations Chathurika :) On Tue, Jun 13, 2017 at 11:34 AM, Aparna Karunarathna <apa...@wso2.com> wrote: > Hi All, > > It's my pleasure to announce Chathurika De Silva as a WSO2 Committer. She is > an active member of EE team and has given a great contribution to ESB, BPS, > BRS, App Factory product releases. > > Congratulations Chathurika and keep up the good work...! > > -- > *Regards,* > > *Aparna Karunarathna.* > > > *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* > > * <http://wso2.com/signature>* > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Anupama Pathirage Associate Technical Lead WSO2, Inc. http://wso2.com/ Email: anup...@wso2.com Mobile:+94 71 8273 979 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Exception related to eclipse BIRT when connecting DAS data using DAS JDBC driver
on DAS report generation stuff. So I have tried to connect >>> eclipse BIRT reporting tool with WSO2 DAS using DAS JDBC driver. but >>> I'm getting an exception after giving the connection properties.That >>> exception is related to connection properties. >>> >>> >>> -- >>> org.eclipse.datatools.connectivity.oda.OdaException: Failed to create a >>> connection. Please verify the connection properties. >>> at org.eclipse.birt.report.data.oda.jdbc.ui.profile.JDBCSelecti >>> onPageHelper$TestInProcessDialog$TestConnectionJob$1.run(JDB >>> CSelectionPageHelper.java:218) >>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) >>> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr >>> onizer.java:182) >>> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav >>> a:4528) >>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java >>> :4146) >>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) >>> at org.eclipse.jface.window.Window.open(Window.java:794) >>> at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.j >>> ava:396) >>> at org.eclipse.birt.report.data.oda.jdbc.ui.profile.JDBCSelecti >>> onPageHelper$8.widgetSelected(JDBCSelectionPageHelper.java:1036) >>> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe >>> ner.java:249) >>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) >>> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) >>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) >>> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja >>> va:4553) >>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java >>> :4143) >>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) >>> at org.eclipse.jface.window.Window.open(Window.java:794) >>> at org.eclipse.birt.report.designer.data.ui.actions.NewDataSour >>> ceAction.run(NewDataSourceAction.java:127) >>> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) >>> at org.eclipse.jface.action.ActionContributionItem.handleWidget >>> Selection(ActionContributionItem.java:565) >>> at org.eclipse.jface.action.ActionContributionItem.lambda$4(Act >>> ionContributionItem.java:397) >>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) >>> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) >>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) >>> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja >>> va:4553) >>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java >>> :4143) >>> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine >>> $4.run(PartRenderingEngine.java:1121) >>> at org.eclipse.core.databinding.observable.Realm.runWithDefault >>> (Realm.java:336) >>> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine >>> .run(PartRenderingEngine.java:1022) >>> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRu >>> nUI(E4Workbench.java:150) >>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) >>> at org.eclipse.core.databinding.observable.Realm.runWithDefault >>> (Realm.java:336) >>> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work >>> bench.java:604) >>> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j >>> ava:148) >>> at org.eclipse.ui.internal.ide.application.IDEApplication.start >>> (IDEApplication.java:138) >>> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips >>> eAppHandle.java:196) >>> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher >>> .runApplication(EclipseAppLauncher.java:134) >>> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher >>> .start(EclipseAppLauncher.java:104) >>> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS >>> tarter.java:388) >>> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS >>> tarter.java:243) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce >>> ssorImpl.java:62) >>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe >>> thodAccessorImpl.java:43) >>> at java.lang.reflect.Method.invoke(Method.java:498) >>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) >>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) >>> at org.eclipse.equinox.launcher.Main.run(Main.java:1519) >>> at org.eclipse.equinox.launcher.Main.main(Main.java:1492) >>> >>> >>> -- >>> >>> Here I have attached a screenshot of connection properties also*. *So >>> need any kind of help to fix this issue. >>> >>> Thanks, >>> Pawan >>> >>> >>> -- >>> *Pawan Gunaratne* >>> Software Engineering Intern >>> *WSO2* >>> *Mob : 0770373556* >>> >> >> >> >> -- >> *Pawan Gunaratne* >> Software Engineering Intern >> *WSO2* >> *Mob : 0770373556* >> > > > > -- > *Pawan Gunaratne* > Software Engineering Intern > *WSO2* > *Mob : 0770373556* > -- Anupama Pathirage Associate Technical Lead WSO2, Inc. http://wso2.com/ Email: anup...@wso2.com Mobile:+94 71 8273 979 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Anupama Pathirage
Hi, Thanks a lot Malli... :) And also thanks a lot for all the support you have given during the past period. It helped me a lot :) On Mon, Oct 17, 2016 at 3:33 AM, Rajith Vitharana <raji...@wso2.com> wrote: > Congrats akke :) :) > > On 17 October 2016 at 14:01, Dilshani Subasinghe <dilsh...@wso2.com> > wrote: > >> Congrats :) :) >> >> On Mon, Oct 17, 2016 at 1:35 PM, Anjana Fernando <anj...@wso2.com> wrote: >> >>> Hi everyone, >>> >>> It's my pleasure to announce Anupama as a WSO2 committer. Anupama has >>> made great contributions to WSO2 DSS/DAS in improving the products. In >>> recognizing the work that has been done, she has been voted in as a WSO2 >>> committer. Anupama, welcome aboard and all the best! .. >>> >>> Cheers, >>> Anjana. >>> -- >>> *Anjana Fernando* >>> Associate Director / Architect >>> WSO2 Inc. | http://wso2.com >>> lean . enterprise . middleware >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Best Regards, >> >> Dilshani Subasinghe >> Software Engineer - QA *|* WSO2 >> lean *|* enterprise *|* middleware >> >> Mobile : +94773375185 >> Blog: dilshani.me >> >> <https://wso2.com/signature> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Rajith Vitharana > > Senior Software Engineer, > WSO2 Inc. : wso2.com > Mobile : +94715883223 > Blog : http://lankavitharana.blogspot.com/ > <http://wso2.com/signature> > -- Anupama Pathirage Associate Technical Lead WSO2, Inc. http://wso2.com/ Email: anup...@wso2.com Mobile:+94 71 8273 979 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Carbon-Registry 4.5.5 is Staged
Hi, I have tested Carbon registry 4.5.5 with WSO2 DSS 3.5.1-SNAPSHOT and didn't find any issue. Regards, Anupama On Sat, Jul 2, 2016 at 8:45 AM, Rajith Roshan <raji...@wso2.com> wrote: > Hi all, > > Carbon registry 4.5.5 is staged at > https://maven.wso2.org/nexus/content/repositories/orgwso2carbonregistry-1005/ > > This release is with kernel version 4.4.6. Please test and verify staging > repo with products. > > *Note : *In order to access the remote registry please exclude the sub > context URL [1] in the "Owasp.CsrfGuard.Carbon.properties" file in > $SERVER_HOME/repository/conf/security directory. > > [1] - org.owasp.csrfguard.unprotected.Registry=%servletContext%/registry/* > > Thanks! > Rajith > > -- > Rajith Roshan > Software Engineer, WSO2 Inc. > Mobile: +94-72-642-8350 <%2B94-71-554-8430> > -- Anupama Pathirage Associate Technical Lead WSO2, Inc. http://wso2.com/ Email: anup...@wso2.com Mobile:+94 71 8273 979 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.7 RC1
Hi, I tested DSS 3.5.1 Snapshot with kernel 4.4.7 RC1 and didn't find any issue related to this RC. *Note :* Feature repo not shown issue [1], introduced with kernel 4.4.6 is observed. Hope this will be fixed in a future release. [1] https://wso2.org/jira/browse/CARBON-15973 Regards, Anupama On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne <shash...@wso2.com> wrote: > Hi, > > I tested the kernal with following databases and no issues observed. > > Test Area: > Add/ Delete resource (inline text) and collection > Add/Remove user and role > > Databases: > mysql 5.5. > mysql 5.7 > postgres 9.3 > oracle 12c > > Regards, > Shashika > > Shashika Ubhayaratne > Associate Technical Lead - QA > WSO2 Inc: http://www.wso2.com/ > Mobile: *+94773383831* > > On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna <ar...@wso2.com> wrote: > >> Hi all, >> >> I've tested the kernel with following databases and found no issues. >> 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl >> 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1 >> >> [x] Stable - go ahead and release. >> >> Regards, >> Aruna >> On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake <jaya...@wso2.com> >> wrote: >> >>> Hi Devs, >>> >>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7. >>> >>> This release fixes the following issues: >>> https://wso2.org/jira/issues/?filter=13113 >>> >>> Please download and test your products with kernel 4.4.7 RC1 and vote. >>> Vote will be open for 72 hours or as longer as needed. >>> >>> Source and binary distribution files: >>> https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip >>> >>> http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip >>> >>> Maven staging repository >>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025 >>> >>> The tag to be voted upon : >>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1 >>> >>> [ ] Broken - do not release (explain why) >>> [ ] Stable - go ahead and release >>> >>> Thank you >>> Carbon Team >>> >>> >>> *Jayanga Dissanayake* >>> Associate Technical Lead >>> WSO2 Inc. - http://wso2.com/ >>> lean . enterprise . middleware >>> email: jaya...@wso2.com >>> mobile: +94772207259 >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> *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 >> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Anupama Pathirage Associate Technical Lead WSO2, Inc. http://wso2.com/ Email: anup...@wso2.com Mobile:+94 71 8273 979 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] DSS Tryit Page issue
Hi,
When we build the product DSS [1] with the latest Kernel Release (4.4.6),
we have observed following issues in "Try it" page. Appreciate any clue on
this to get them resolved.
*1) *In Https mode, Try it requests gives following error on send [2][3].
WARN {org.owasp.csrfguard.log.JavaLogger} - potential cross-site request
forgery (CSRF) attack thwarted (user:, ip:10.100.7.118,
method:POST, uri:/carbon/admin/jsp/WSRequestXSSproxy_ajaxprocessor.jsp,
error:required token is missing from the request)
Private proxy protocol will be attempted as cross-domain browser
restrictions might be enforced for this endpoint.
http://tryit.carbon.wso2.org;>
Error connecting to the Tryit ajax proxy
*2)* Try it page does not load properly in Chrome. It loads correctly in
Firefox. It gives the following error on chrome [4].
Refused to execute script from '
https://localhost:9443/services/echo?wsdl2form=editarea/edit_area_full.js'
<https://www.google.com/url?q=https%3A%2F%2Flocalhost%3A9443%2Fservices%2Fecho%3Fwsdl2form%26resource%3Deditarea%2Fedit_area_full.js%27=D=1=AFQjCNGL0XVRd6yRXPkx_0JirC6kv1p-4A>
because its MIME type ('text/html') is not executable, and strict MIME type
checking is enabled.
Uncaught ReferenceError: editAreaLoader is not defined.
[1] https://github.com/wso2/product-dss/
[2] https://drive.google.com/open?id=0B16LG8jdYeP8ZEpyV1F5cmRsTDA
[3] https://drive.google.com/open?id=0B16LG8jdYeP8LWF2elVTbzFQOWs
[4] https://drive.google.com/open?id=0B16LG8jdYeP8VmtlWXEtdmRJUjQ
Regards,
--
Anupama Pathirage
Associate Technical Lead
WSO2, Inc. http://wso2.com/
Email: anup...@wso2.com
Mobile:+94 71 8273 979
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.6 RC2
Hi Kalpa,
Thanks for the update. Please update us with the solution for CSRF
security issue. We get the same issue for the DSS try it as well.
[2016-06-08 11:55:28,396] WARN {org.owasp.csrfguard.log.JavaLogger} -
potential cross-site request forgery (CSRF) attack thwarted
(user:, ip:10.100.7.118, method:POST,
uri:/carbon/admin/jsp/WSRequestXSSproxy_ajaxprocessor.jsp, error:required
token is missing from the request)
Private proxy protocol will be attempted as cross-domain browser
restrictions might be enforced for this endpoint.
http://tryit.carbon.wso2.org;>
Error connecting to the Tryit ajax proxy
Regards,
On Wed, Jun 8, 2016 at 8:45 AM, Kasun Bandara <kas...@wso2.com> wrote:
> Hi All,
>
> We have done the fix for L1 reported in [1] yesterday.
>
> Thanks,
> Kasun.
>
> [1] https://wso2.org/jira/browse/IDENTITY-4656
>
> On Wed, Jun 8, 2016 at 7:00 AM, Kalpa Welivitigoda <kal...@wso2.com>
> wrote:
>
>> Hi Anupama,
>>
>> On Tue, Jun 7, 2016 at 8:45 PM, Anupama Pathirage <anup...@wso2.com>
>> wrote:
>>
>>> Hi Kalpa,
>>>
>>> Checked the suggested approaches and those two issues were resolved
>>> after applying both changes. We will further test the service with the
>>> Carbon RC2.
>>>
>>> On Tue, Jun 7, 2016 at 6:15 PM, Kalpa Welivitigoda <kal...@wso2.com>
>>> wrote:
>>>
>>>> Hi Anupama,
>>>>
>>>> On Tue, Jun 7, 2016 at 5:50 PM, Anupama Pathirage <anup...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> We got the following issues when testing WSO2 DSS with the Kernel RC2
>>>>> Release.
>>>>>
>>>>> *1) *Any action on management console gives the following error. It
>>>>> seems to be related with the tomcat upgrade and appreciate your input on
>>>>> this.
>>>>>
>>>>> [2016-06-07 17:21:16,905] ERROR
>>>>> {org.apache.coyote.AbstractProtocol$AbstractConnectionHandler} - Error
>>>>> reading request, ignored
>>>>> java.lang.NoSuchMethodError: org.apache.coyote.Request.getBytesRead()I
>>>>> at
>>>>> org.apache.coyote.RequestInfo.updateCounters(RequestInfo.java:143)
>>>>> at org.apache.coyote.Request.updateCounters(Request.java:533)
>>>>> at
>>>>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1140)
>>>>> at
>>>>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
>>>>> at
>>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1749)
>>>>> at
>>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1708)
>>>>> 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)
>>>>>
>>>>
>>>> Yes, it is due to the tomcat upgrade in kernel, relevant fixes for
>>>> carbon-deployment are already there in 4.6.2-SNAPSHOT. We have to do a
>>>> deployment release once we release 4.4.6-SNAPSHOT. For the moment, for
>>>> testing purpose, is it possible you try with 4.6.2-SNAPSHOT?
>>>>
>>>
>>> Could you please do the needful to release the carbon-deployment 4.6.2
>>> as DSS 3.5.1 release will be on hold until it is done.
>>>
>>
>> Yes, we will be doing component released once we are done with kernel
>> 4.4.6.
>>
>>
>>>
>>>
>>>>
>>>>
>>>>>
>>>>> *2) *DBS file uploads gives the following error which returns Error
>>>>> 403 - Forbidden
>>>>>
>>>>> [2016-06-07 17:21:16,904] WARN {org.owasp.csrfguard.log.JavaLogger}
>>>>> - potential cross-site request forgery (CSRF) attack thwarted
>>>>> (user:, ip:10.100.7.118, method:POST,
>>>>> uri:/carbon/admin/jsp/WSRequestXSSproxy_ajaxprocessor.jsp, error:required
>>>>> token is missing from the request)
>>>>>
>>>>>
>>>> For this would you please try with adding the fol
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.6 RC2
Hi Kalpa,
Checked the suggested approaches and those two issues were resolved after
applying both changes. We will further test the service with the Carbon RC2.
On Tue, Jun 7, 2016 at 6:15 PM, Kalpa Welivitigoda <kal...@wso2.com> wrote:
> Hi Anupama,
>
> On Tue, Jun 7, 2016 at 5:50 PM, Anupama Pathirage <anup...@wso2.com>
> wrote:
>
>> Hi,
>>
>> We got the following issues when testing WSO2 DSS with the Kernel RC2
>> Release.
>>
>> *1) *Any action on management console gives the following error. It
>> seems to be related with the tomcat upgrade and appreciate your input on
>> this.
>>
>> [2016-06-07 17:21:16,905] ERROR
>> {org.apache.coyote.AbstractProtocol$AbstractConnectionHandler} - Error
>> reading request, ignored
>> java.lang.NoSuchMethodError: org.apache.coyote.Request.getBytesRead()I
>> at org.apache.coyote.RequestInfo.updateCounters(RequestInfo.java:143)
>> at org.apache.coyote.Request.updateCounters(Request.java:533)
>> at
>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1140)
>> at
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
>> at
>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1749)
>> at
>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1708)
>> 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)
>>
>
> Yes, it is due to the tomcat upgrade in kernel, relevant fixes for
> carbon-deployment are already there in 4.6.2-SNAPSHOT. We have to do a
> deployment release once we release 4.4.6-SNAPSHOT. For the moment, for
> testing purpose, is it possible you try with 4.6.2-SNAPSHOT?
>
Could you please do the needful to release the carbon-deployment 4.6.2 as
DSS 3.5.1 release will be on hold until it is done.
>
>
>>
>> *2) *DBS file uploads gives the following error which returns Error 403
>> - Forbidden
>>
>> [2016-06-07 17:21:16,904] WARN {org.owasp.csrfguard.log.JavaLogger} -
>> potential cross-site request forgery (CSRF) attack thwarted
>> (user:, ip:10.100.7.118, method:POST,
>> uri:/carbon/admin/jsp/WSRequestXSSproxy_ajaxprocessor.jsp, error:required
>> token is missing from the request)
>>
>>
> For this would you please try with adding the following line to
> repository/conf/security/Owasp.CsrfGuard.Carbon.properties,
>
> org.owasp.csrfguard.unprotected.FileUpload=%servletContext%/fileupload/*
>
Is excluding these patterns from CSRF protection recommended ?
Regards,
Anupama
>
>
>
>> Regards,
>>
>> On Tue, Jun 7, 2016 at 4:46 PM, KasunG Gajasinghe <kas...@wso2.com>
>> wrote:
>>
>>>
>>> Others, please continue to testing the pack and report all the issues so
>>> we can check and fix.
>>>
>>> On Tue, Jun 7, 2016 at 2:31 PM, Kasun Bandara <kas...@wso2.com> wrote:
>>>
>>>> Hi Niranjan,
>>>>
>>>> Created [1] to track the equivalent Carbon JIRA.
>>>>
>>>> [1] https://wso2.org/jira/browse/CARBON-15938
>>>>
>>>> Thanks,
>>>> Kasun.
>>>>
>>>> On Tue, Jun 7, 2016 at 2:23 PM, Niranjan Karunanandham <
>>>> niran...@wso2.com> wrote:
>>>>
>>>>> Hi KasunB,
>>>>>
>>>>> Please create an equivalent JIRA in Kernel in-order to track this.
>>>>>
>>>>> Regards,
>>>>> Nira
>>>>>
>>>>> On Tue, Jun 7, 2016 at 2:11 PM, Kasun Bandara <kas...@wso2.com> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> We are having L1 reported in [1] and will be a blocker for IS.
>>>>>> Please hold off the vote proceedings until we find out the root cause of
>>>>>> the issue. Most probably this issue must be originated from user core.
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Kasun.
>>>>>>
>>>>>> [1] https://wso2.org/jira/browse/IDENTITY-4656
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Jun 7, 2016 at 11:45 AM, KasunG Gajasinghe &l
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.6 RC2
clipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1465274241567.log* >>>>>> >>>>>> How can we overcome this? >>>>>> >>>>> >>>>> To fix security vulnerabilities, we have upgraded the opensaml orbit >>>>> bundle to the latest. In that process, IS folks have fixed issues in the >>>>> old opensaml orbit to conform to the new orbit guidelines. In that >>>>> process, >>>>> the org.apache.velocity packages were removed from opensaml. If you need >>>>> opensaml, then you should include this feature [1]. >>>>> >>>>> You shouldn't be using velocity packages directly that is coming from >>>>> opensaml. If you only need velocity, then your feature need to include >>>>> velocity orbit. >>>>> >>>>> [1] >>>>> https://github.com/wso2-extensions/identity-inbound-auth-saml/blob/master/features/org.wso2.carbon.identity.sso.saml.server.feature/pom.xml >>>>> >>>>> >>>>> >>>>>> >>>>>> Thank You, >>>>>> >>>>>> On Tue, Jun 7, 2016 at 8:32 AM, Kalpa Welivitigoda <kal...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Devs, >>>>>>> >>>>>>> This is the 2nd release candidate of WSO2 Carbon Kernel 4.4.6. >>>>>>> >>>>>>> This release fixes the following issues: >>>>>>> https://wso2.org/jira/issues/?filter=13090 >>>>>>> >>>>>>> Please download and test your products with kernel 4.4.6 RC1 and >>>>>>> vote. Vote will be open for 72 hours or as longer as needed. >>>>>>> >>>>>>> Source and binary distribution files: >>>>>>> >>>>>>> http://svn.wso2.org/repos/wso2/people/kalpaw/wso2carbon-4.4.6/wso2carbon-4.4.6-rc2.zip >>>>>>> >>>>>>> Maven staging repository: >>>>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1023/ >>>>>>> >>>>>>> The tag to be voted upon: >>>>>>> https://github.com/wso2/carbon-kernel/tree/v4.4.6-rc2 >>>>>>> >>>>>>> >>>>>>> [ ] Broken - do not release (explain why) >>>>>>> [ ] Stable - go ahead and release >>>>>>> >>>>>>> Thank you >>>>>>> Carbon Team >>>>>>> >>>>>>> -- >>>>>>> Best Regards, >>>>>>> >>>>>>> Kalpa Welivitigoda >>>>>>> Software Engineer, WSO2 Inc. http://wso2.com >>>>>>> Email: kal...@wso2.com >>>>>>> Mobile: +94776509215 >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Viraj Senevirathne >>>>>> Software Engineer; WSO2, Inc. >>>>>> >>>>>> Mobile : +94 71 958 0269 >>>>>> Email : vir...@wso2.com >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. >>>>> email: kasung AT spamfree wso2.com >>>>> linked-in: http://lk.linkedin.com/in/gajasinghe >>>>> blog: http://kasunbg.org >>>>> >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Kasun Bandara >>>> *Software Engineer* >>>> Mobile : +94 (0) 718 338 360 >>>> <%2B94%20%280%29%20773%20451194> >>>> kas...@wso2.com <thili...@wso2.com> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> >>> >>> *Niranjan Karunanandham* >>> Associate Technical Lead - WSO2 Inc. >>> WSO2 Inc.: http://www.wso2.com >>> >> >> >> >> -- >> Kasun Bandara >> *Software Engineer* >> Mobile : +94 (0) 718 338 360 >> <%2B94%20%280%29%20773%20451194> >> kas...@wso2.com <thili...@wso2.com> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. > email: kasung AT spamfree wso2.com > linked-in: http://lk.linkedin.com/in/gajasinghe > blog: http://kasunbg.org > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Anupama Pathirage Associate Technical Lead WSO2, Inc. http://wso2.com/ Email: anup...@wso2.com Mobile:+94 71 8273 979 Blog:http://mycodeideas.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][Vote] Release WSO2 Puppet Modules 2.0.0
Hi, *[X] Stable* - go ahead and release Tested the default deployment for WSO2 DSS and verified README Files & configs. Regards, Anupama Pathirage On Tue, May 24, 2016 at 11:50 AM, Dharshana Warusavitharana < dharsha...@wso2.com> wrote: > Tested with WSO2 APIM > > [X] Stable - Go ahead and release > > Thank you, > Dharshana. > > On Tue, May 24, 2016 at 11:29 AM, Dimuthu De Lanerolle <dimut...@wso2.com> > wrote: > >> Tested & verified following products for the deployment on below >> mentioned platforms. >> >> [1] WSO2 AS - K8S >> [2] WSO2 ESB - K8S >> [3] WSO2 APIM - default >> >> [X] Stable - Go ahead and release >> >> Regards >> >> On Tue, May 24, 2016 at 11:01 AM, Thushara Ranawaka <thusha...@wso2.com> >> wrote: >> >>> Hi Everyone, >>> >>> Tested the default deployment for G-Reg 5.1.0 and went through >>> configuration and found no blocking issues. >>> >>> [X] Stable - Go ahead and release >>> >>> Thanks, >>> Thushara. >>> >>> >>> On Tue, May 24, 2016 at 9:48 AM, Anuruddha Liyanarachchi < >>> anurudd...@wso2.com> wrote: >>> >>>> Hi >>>> >>>> *[X] Stable* - go ahead and release >>>> >>>> verified the following. >>>> >>>>- README Files >>>>- License Headers >>>> >>>> Tested the default and kubernetes deployment for the following products >>>> puppet modules. >>>> >>>>- WSO2 BPS >>>>- WSO2 ESB >>>>- WSO2 AS >>>> >>>> >>>> On Wed, May 18, 2016 at 10:24 PM, Chamila De Alwis <chami...@wso2.com> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> >>>>> This is the first release candidate (RC1) for WSO2 Puppet Modules >>>>> 2.0.0. Please download, verify, and vote. Voting will be open for 72 >>>>> hours. >>>>> >>>>> [ ] Broken - Do not release (explain why) >>>>> >>>>> [ ] Stable - Go ahead and release >>>>> >>>>> Main features and fixes released with this release: >>>>> >>>>>- >>>>> >>>>>Updated Hiera data hierarchy to include deployment Platform >>>>>- >>>>> >>>>>Kubernetes based workflow supported, based on >>>>>wso2/kubernetes-artifacts >>>>>- >>>>> >>>>>system_file_list to copy files with scope outside of CARBON_HOME >>>>>- >>>>> >>>>>Platform specific configuration data sets for Kubernetes >>>>>- >>>>> >>>>> Kubernetes deployment-ready Puppet modules >>>>> - >>>>> >>>>> Data sources matching a distributed set of Kubernetes MySQL >>>>> Services >>>>> - >>>>> >>>>>Streamlined Default platform YAML configuration data >>>>>- >>>>> >>>>>Optional update flags to control product pack and JDK cleanup >>>>>- >>>>> >>>>>Minor fixes on the Hiera data >>>>>- >>>>> >>>>> Issues in YAML file formatting >>>>> - >>>>> >>>>> Puppet templates for identity.xml added to relevant products >>>>> - >>>>> >>>>> Proxy Port values assigned to different products are streamlined >>>>> - >>>>> >>>>> Hostname entries streamlined in default deployment platform >>>>> data set >>>>> - >>>>> >>>>> Pass Through Port Mapping for WSO2 ESB >>>>> - >>>>> >>>>> Fixing Thrift Server IP configuration for WSO2 MB >>>>> - >>>>> >>>>> SecureVault parameters made optional >>>>> - >>>>> >>>>> Reusing Data Source related fields in YAML by inheriting from >>>>> wso2/common.yaml >>>>> - >>>>> >>>>> Fix Symbolic Link creation in WSO2 DAS >>>>> - >>
[Dev] Streaming capabilities in the GW framework
Hi All, When implementing the Data Integration Server (DIS) which is based on the GW framework, Streaming functionality is identified as one of the core feature which is already there in the DSS as well. The streaming functionality should make sure that the full result set is not built completely at the server side before sending the response, but the records are streamed to the client side as they are made available. This will help to avoid, data getting piled up at the server side which can possibly cause OOM issues etc specially in the presence of a large data set [1] . Since this is a core feature required for DIS, appreciate input on followings, so we can make a decision on how to move forward. 1) What is the current status of streaming aspects in the gateway framework? 2) If it is not supported yet, what are the suggestions to start on that. [1] http://wso2.com/library/knowledge-base/large-scale-data-transfer-data-services-streaming/ Regards. -- Anupama Pathirage Associate Technical Lead WSO2, Inc. http://wso2.com/ Email: anup...@wso2.com Mobile:+94 71 8273 979 Blog:http://mycodeideas.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] One or more certificates rejected Issue on product Build
Hi All, Thanks a lot for the support and as mentioned in [1] downloading a fresh jdk and replacing the all the certificates in the installation folder resolved the issue. [1] - Mail Subject: "[Dev] P2 Profile Generation Fails - One or more certificates rejected." Regards, On Mon, Apr 25, 2016 at 8:10 PM, Niranjan Karunanandham <niran...@wso2.com> wrote: > Hi all, > > This issue is because the certificates is not trusted are not trusted by > the JVM. This issue was mentioned in [1] and was solved by downloading a > fresh JDK and replacing all the certificates in that. > > [1] - Mail Subject: "[Dev] P2 Profile Generation Fails - One or more > certificates rejected." > > Regards, > Nira > > On Mon, Apr 25, 2016 at 5:26 PM, Aruna Karunarathna <ar...@wso2.com> > wrote: > >> Experienced the same issue and was able to resolve by using a different >> JDK version. Haven't dig further though, since it resolved after the JDK >> version change. >> >> On Mon, Apr 25, 2016 at 5:11 PM, Anupama Pathirage <anup...@wso2.com> >> wrote: >> >>> Hi, >>> >>> When building wso2-products (Ex: DSS ,ESB) [1], I encountered the error >>> of "One or more certificates rejected. Cannot proceed with installation." >>> during the profile generation. Error log for DSS build is as follows. >>> Checked with java 1.7.0_80 with maven 3.0.5 and 3.3.3. Seems it may due to >>> recent change in my local setup since I was able to build them earlier. >>> >>> Any help on this issue is appreciated. >>> >>> >>> *Error Log:* >>> >>> [INFO] Running Equinox P2 Category Publisher Application for the >>> Generated Repository >>> [INFO] >>> [INFO] --- carbon-p2-plugin:1.5.3:publish-product (publishing product) @ >>> wso2dataservices-profile-gen --- >>> [INFO] Command line: >>> /bin/sh -c cd >>> /home/anupama/Anupama/SRC/product-dss/modules/p2-profile-gen && >>> /usr/lib/jvm/java-7-oracle/jre/bin/java -jar >>> /home/anupama/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar >>> -nosplash -application org.eclipse.equinox.p2.publisher.ProductPublisher >>> -metadataRepository >>> file:/home/anupama/Anupama/SRC/product-dss/modules/p2-profile-gen/target/p2-repo >>> -artifactRepository >>> file:/home/anupama/Anupama/SRC/product-dss/modules/p2-profile-gen/target/p2-repo >>> -productFile >>> /home/anupama/Anupama/SRC/product-dss/modules/p2-profile-gen/carbon.product >>> -executables >>> /home/anupama/Anupama/SRC/product-dss/modules/p2-profile-gen/target/org.eclipse.equinox.executable_3.5.0.v20110530-7P7NFUFFLWUl76mart >>> -publishArtifacts -configs gtk.linux.x86 -flavor tooling -append >>> Generating metadata for .. >>> Generation completed with success [0 seconds]. >>> [INFO] >>> [INFO] --- carbon-p2-plugin:1.5.3:materialize-product >>> (creating-worker-profile) @ wso2dataservices-profile-gen --- >>> [INFO] Command line: >>> /bin/sh -c cd >>> /home/anupama/Anupama/SRC/product-dss/modules/p2-profile-gen && >>> /usr/lib/jvm/java-7-oracle/jre/bin/java -jar >>> /home/anupama/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar >>> -nosplash -application org.eclipse.equinox.p2.director -metadataRepository >>> file:/home/anupama/Anupama/SRC/product-dss/modules/p2-profile-gen/target/p2-repo >>> -artifactRepository >>> file:/home/anupama/Anupama/SRC/product-dss/modules/p2-profile-gen/target/p2-repo >>> -installIU carbon.product.id -profileProperties >>> org.eclipse.update.install.features=true -profile worker -bundlepool >>> file:/home/anupama/Anupama/SRC/product-dss/modules/p2-profile-gen/target/wso2carbon-core-4.4.2/repository/components >>> -shared >>> file:/home/anupama/Anupama/SRC/product-dss/modules/p2-profile-gen/target/wso2carbon-core-4.4.2/repository/components/p2 >>> -destination >>> file:/home/anupama/Anupama/SRC/product-dss/modules/p2-profile-gen/target/wso2carbon-core-4.4.2/repository/components/worker >>> -p2.os linux -p2.ws gtk -p2.arch x86 -roaming >>> >>> *Installing carbon.product.id <http://carbon.product.id> >>> 4.4.2.Installation failed.One or more certificates rejected. Cannot proceed >>> with installation.* >>> >>> Application failed, log file location: >&g
[Dev] One or more certificates rejected Issue on product Build
UI module . SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 01:03 min [INFO] Finished at: 2016-04-25T16:41:06+05:30 [INFO] Final Memory: 59M/750M [INFO] *[ERROR] Failed to execute goal org.wso2.maven:carbon-p2-plugin:1.5.3:materialize-product (creating-worker-profile) on project wso2dataservices-profile-gen: Cannot generate P2 metadata: P2 publisher return code was 13 -> [Help 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wso2.maven:carbon-p2-plugin:1.5.3:materialize-product (creating-worker-profile) on project wso2dataservices-profile-gen: Cannot generate P2 metadata* at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) 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:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286) at org.apache.maven.cli.MavenCli.main(MavenCli.java:197) 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:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot generate P2 metadata at org.wso2.maven.p2.MaterializeProductMojo.execute(MaterializeProductMojo.java:89) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 20 more Caused by: org.apache.maven.plugin.MojoFailureException: P2 publisher return code was 13 at org.wso2.maven.p2.MaterializeProductMojo.deployRepository(MaterializeProductMojo.java:165) at org.wso2.maven.p2.MaterializeProductMojo.execute(MaterializeProductMojo.java:84) ... 22 more [1]https://github.com/anupama-pathirage/product-dss Thank you. -- Anupama Pathirage Associate Technical Lead WSO2, Inc. http://wso2.com/ Email: anup...@wso2.com Mobile:+94 71 8273 979 Blog:http://mycodeideas.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error on loading external OSGI bundles with Carbon 5
Hi Aruna,
Thanks a lot. That solved the problem. :) and thanks Thusitha and Kalpa for
the support.
On Tue, Mar 1, 2016 at 4:39 PM, Aruna Karunarathna <ar...@wso2.com> wrote:
> * is defined wrong.
>
> Try adding
>
> *
>
> Refer this [1] for more details.
>
> [1]. https://docs.wso2.com/display/Carbon500/Using+the+Maven+Bundle+Plugin
>
> On Tue, Mar 1, 2016 at 4:24 PM, Anupama Pathirage <anup...@wso2.com>
> wrote:
>
>> Hi,
>>
>> Thanks for the suggestions.
>>
>> I already tried with followings. May be something is wrong in the way I
>> specified them.
>>
>> 1) import the com.mysql.jdbc pacakage
>>
>> [5.1.35, 5.1.38)
>> com.mysql.jdbc.*;version="${mysql.import.version.range}"
>>
>> 2) Adding dynamic import
>>
>> *
>>
>> I have attached my pom.xml file herewith.
>>
>>
>>
>> On Tue, Mar 1, 2016 at 3:45 PM, Aruna Karunarathna <ar...@wso2.com>
>> wrote:
>>
>>> Hi Anupama,
>>>
>>> Since you are doing a class.forName();, you have to do dynamic import
>>> package.
>>>
>>> Can you try adding that to your pom.xml?
>>>
>>> Regards,
>>> Aruna
>>>
>>> On Tue, Mar 1, 2016 at 2:54 PM, Thusitha Thilina Dayaratne <
>>> thusit...@wso2.com> wrote:
>>>
>>>> Hi Anupama,
>>>>
>>>> Are you importing the com.mysql.jdbc package inside your bundle which
>>>> uses mysql?
>>>>
>>>> Thanks
>>>> Thusitha
>>>>
>>>> On Tue, Mar 1, 2016 at 2:49 PM, Anupama Pathirage <anup...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I need to query MySQL database with Carbon 5 based product and I added
>>>>> the mysql-connector-java-5.1.35.jar [1] file to the osgi/droppings
>>>>> directory. Since the jar file is already an osgi bundle I copied it
>>>>> directly to osgi/droppings folder.
>>>>>
>>>>> But when I load the class as below it gives the
>>>>> java.lang.ClassNotFoundException.
>>>>>
>>>>> Class.forName("com.mysql.jdbc.Driver");
>>>>>
>>>>> Is there any missing step I followed which can cause this error?
>>>>>
>>>>>
>>>>> java.lang.ClassNotFoundException: com.mysql.jdbc.Driver cannot be
>>>>> found by org.wso2.carbon.ibus_1.0.0.SNAPSHOT
>>>>> at
>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
>>>>> at
>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
>>>>> at
>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
>>>>> at
>>>>> org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
>>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>>>>> at java.lang.Class.forName0(Native Method)
>>>>> at java.lang.Class.forName(Class.java:264)
>>>>> at org.wso2.carbon.ibus.Activator.start(Activator.java:55)
>>>>> at
>>>>> org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
>>>>> at
>>>>> org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
>>>>> at java.security.AccessController.doPrivileged(Native Method)
>>>>> at
>>>>> org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
>>>>> at
>>>>> org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
>>>>> at
>>>>> org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:936)
>>>>> at
>>>>> org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:319)
>>>>> at org.eclipse.osgi.container.Module.doStart(Module.java:571)
>>>>> at org.eclipse.osgi.container.Module.start(Module.java:439)
>>>>> at
>>>>> org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:393)
>>>>> at
>>>>> org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:412)
>>>>> at
>
Re: [Dev] Error on loading external OSGI bundles with Carbon 5
Hi,
Thanks for the suggestions.
I already tried with followings. May be something is wrong in the way I
specified them.
1) import the com.mysql.jdbc pacakage
[5.1.35, 5.1.38)
com.mysql.jdbc.*;version="${mysql.import.version.range}"
2) Adding dynamic import
*
I have attached my pom.xml file herewith.
On Tue, Mar 1, 2016 at 3:45 PM, Aruna Karunarathna <ar...@wso2.com> wrote:
> Hi Anupama,
>
> Since you are doing a class.forName();, you have to do dynamic import
> package.
>
> Can you try adding that to your pom.xml?
>
> Regards,
> Aruna
>
> On Tue, Mar 1, 2016 at 2:54 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Anupama,
>>
>> Are you importing the com.mysql.jdbc package inside your bundle which
>> uses mysql?
>>
>> Thanks
>> Thusitha
>>
>> On Tue, Mar 1, 2016 at 2:49 PM, Anupama Pathirage <anup...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I need to query MySQL database with Carbon 5 based product and I added
>>> the mysql-connector-java-5.1.35.jar [1] file to the osgi/droppings
>>> directory. Since the jar file is already an osgi bundle I copied it
>>> directly to osgi/droppings folder.
>>>
>>> But when I load the class as below it gives the
>>> java.lang.ClassNotFoundException.
>>>
>>> Class.forName("com.mysql.jdbc.Driver");
>>>
>>> Is there any missing step I followed which can cause this error?
>>>
>>>
>>> java.lang.ClassNotFoundException: com.mysql.jdbc.Driver cannot be found
>>> by org.wso2.carbon.ibus_1.0.0.SNAPSHOT
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
>>> at
>>> org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>>> at java.lang.Class.forName0(Native Method)
>>> at java.lang.Class.forName(Class.java:264)
>>> at org.wso2.carbon.ibus.Activator.start(Activator.java:55)
>>> at
>>> org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
>>> at
>>> org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> at
>>> org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
>>> at
>>> org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
>>> at
>>> org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:936)
>>> at
>>> org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:319)
>>> at org.eclipse.osgi.container.Module.doStart(Module.java:571)
>>> at org.eclipse.osgi.container.Module.start(Module.java:439)
>>> at
>>> org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:393)
>>> at
>>> org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:412)
>>> at
>>> org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:438)
>>> at
>>> org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:111)
>>> at
>>> org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:191)
>>> at
>>> org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:205)
>>> at
>>> org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:60)
>>> at
>>> org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
>>> at
>>> org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> at
>>> org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
>>> at
>>> org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
>>>
[Dev] Error on loading external OSGI bundles with Carbon 5
Hi,
I need to query MySQL database with Carbon 5 based product and I added the
mysql-connector-java-5.1.35.jar [1] file to the osgi/droppings directory.
Since the jar file is already an osgi bundle I copied it directly to
osgi/droppings folder.
But when I load the class as below it gives the
java.lang.ClassNotFoundException.
Class.forName("com.mysql.jdbc.Driver");
Is there any missing step I followed which can cause this error?
java.lang.ClassNotFoundException: com.mysql.jdbc.Driver cannot be found by
org.wso2.carbon.ibus_1.0.0.SNAPSHOT
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
at
org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at org.wso2.carbon.ibus.Activator.start(Activator.java:55)
at
org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
at
org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
at
org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:936)
at
org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:319)
at org.eclipse.osgi.container.Module.doStart(Module.java:571)
at org.eclipse.osgi.container.Module.start(Module.java:439)
at
org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:393)
at
org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:412)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:438)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:111)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:191)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:205)
at
org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:60)
at
org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
at
org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
at
org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:936)
at
org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:319)
at org.eclipse.osgi.container.Module.doStart(Module.java:571)
at org.eclipse.osgi.container.Module.start(Module.java:439)
at
org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:393)
at
org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:412)
at
org.wso2.carbon.launcher.CarbonServer.loadInitialBundles(CarbonServer.java:243)
at org.wso2.carbon.launcher.CarbonServer.start(CarbonServer.java:84)
at org.wso2.carbon.launcher.Main.main(Main.java:83)
[1] http://mvnrepository.com/artifact/mysql/mysql-connector-java/5.1.35
Thanks.
--
Anupama Pathirage
Associate Technical Lead
WSO2, Inc. http://wso2.com/
Email: anup...@wso2.com
Mobile:+94 71 8273 979
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Missing DB Scripts in Identity Server
Hi,
When Setting up MySQL with Identity Server(wso2is-5.1.0) as described in
[1], it gives the following error on server startup. This error occurs only
when we create the database tables using the scripts located at
"/dbscripts/mysql.sql" using the following command as
mentioned in the documentation.[1]
*Command:*
mysql -u regadmin -p -Dregdb < '/dbscripts/mysql.sql';
*Error:*
[2016-01-07 18:07:10,230] ERROR
{org.wso2.carbon.idp.mgt.internal.IdPManagementServiceComponent} - Error
while activating Identity Provider Management bundle
org.wso2.carbon.idp.mgt.IdentityProviderManagementE xception: Error
occurred while retrieving Identity Provider information for tenant :
carbon.super and Identity Provider name : LOCAL
...
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
'regdb.IDP' doesn't exist.
That /dbscripts/mysql.sql script in the Identity server
bundle doesn't contain the scripts for tables IDN_*, IDP_*, SP_*, and WF_*.
Even though table creation can be done by -Dsetup option at runtime without
any issue, when following the documentation users gets this error.
Thought to mention this since I found several forum posts regarding the
same issue. So my suggestion is to either,
- update /dbscripts/mysql.sql (and scripts for other
dbs as well ) with all the required tables OR
- update the documentation to work with -Dsetup option only instead
of using script based method
because the users who follows the steps in the document gets this error for
the first time.
*[1] *https://docs.wso2.com/display/IS510/Setting+up+MySQL
Thank You,
--
Anupama Pathirage
Associate Technical Lead
WSO2, Inc. http://wso2.com/
Email: anup...@wso2.com
Mobile:+94 71 8273 979
Blog:http://mycodeideas.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Clarification on OUT_ONLY ESB proxy service scenario
Hi Vijitha, Thanks a lot for the clear explanation. On Fri, Dec 18, 2015 at 11:43 PM, Vijitha Ekanayake <vijit...@wso2.com> wrote: > Hi Anupama, > > We set *OUT_ONLY *property to "true" on a message to indicate that no > response message is expected for it once it is forwarded from the ESB. This > prevents the ESB from registering unnecessary callbacks for response > handling. > > One possible option to get sample working for client modes, We can check > the header value and change synapse configuration accordingly. We can > support for both types of operations by using config[1]. > > > [1]. > > xmlns="http://ws.apache.org/ns/synapse; name="StockQuoteProxy" > transports="https,http" statistics="disable" trace="disable" > startOnLoad="true"> > > > http://www.w3.org/2005/08/addressing; > source="$header/wsa:Action" regex="urn:placeOrder"> > > type="STRING" /> > > > > > > > > uri="http://localhost:9000/services/SimpleStockQuoteService; /> > > > uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl" /> > > > > Thanks, > > Vijitha. > > > On Fri, Dec 18, 2015 at 6:00 PM, Anupama Pathirage <anup...@wso2.com> > wrote: > >> >> Hi team, >> >> I get the following exception when I run the Sample 150 (Introduction to >> Proxy Services) in the WSO2 ESB 4.9.0 as mentioned in the [1 >> <https://docs.wso2.com/display/ESB490/Sample+150%3A+Introduction+to+Proxy+Services>] >> with the client mode "placeorder" even though the order is placed correctly >> in the back end service. >> >> *Client Command used:* >> ant stockquote -Daddurl=http://localhost:8280/services/StockQuoteProxy >> -Dmode=placeorder -Dsymbol=MSFT >> >> *ESB Exception:* >> [2015-12-18 17:00:04,072] ERROR - NativeWorkerPool Uncaught exception >> java.lang.UnsupportedOperationException: An access occurred that is not >> valid. >> at >> org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:117) >> at >> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:299) >> at >> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172) >> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) >> at >> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247) >> at >> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >> at java.lang.Thread.run(Thread.java:745) >> >> Since “PlaceOrder” is a method which does not return anything as a >> response for a request, it was possible to avoid this exception by setting >> the property OUT_ONLY for the in sequence as follows [2 >> <https://docs.wso2.com/display/ESB403/Generic+Properties>]. >> >> >> >> >> >> But this make the other client modes such as "quote" not working because >> it is trying to send a request which expects a response through an OUT_ONLY >> proxy which must be wrong in theoretically. So can you please let me know >> the proper way of handling above ESB exception while providing the support >> for both types of operations. >> >> >> [1] >> https://docs.wso2.com/display/ESB490/Sample+150%3A+Introduction+to+Proxy+Services >> [2] https://docs.wso2.com/display/ESB403/Generic+Properties >> >> Thanks and Regards, >> -- >> Anupama Pathirage >> Associate Technical Lead >> WSO2, Inc. http://wso2.com/ >> Email: anup...@wso2.com >> Mobile:+94 71 8273 979 >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Vijitha Ekanayake > Software Engineer*, *WSO2, Inc.; http://wso2.com/ > Mobile : +94 777 24 73 39 | +94 718 74 44 08 > lean.enterprise.middleware > -- Anupama Pathirage Associate Technical Lead WSO2, Inc. http://wso2.com/ Email: anup...@wso2.com Mobile:+94 71 8273 979 Blog:http://mycodeideas.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Clarification on OUT_ONLY ESB proxy service scenario
Hi team, I get the following exception when I run the Sample 150 (Introduction to Proxy Services) in the WSO2 ESB 4.9.0 as mentioned in the [1 <https://docs.wso2.com/display/ESB490/Sample+150%3A+Introduction+to+Proxy+Services>] with the client mode "placeorder" even though the order is placed correctly in the back end service. *Client Command used:* ant stockquote -Daddurl=http://localhost:8280/services/StockQuoteProxy -Dmode=placeorder -Dsymbol=MSFT *ESB Exception:* [2015-12-18 17:00:04,072] ERROR - NativeWorkerPool Uncaught exception java.lang.UnsupportedOperationException: An access occurred that is not valid. at org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:117) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:299) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Since “PlaceOrder” is a method which does not return anything as a response for a request, it was possible to avoid this exception by setting the property OUT_ONLY for the in sequence as follows [2 <https://docs.wso2.com/display/ESB403/Generic+Properties>]. But this make the other client modes such as "quote" not working because it is trying to send a request which expects a response through an OUT_ONLY proxy which must be wrong in theoretically. So can you please let me know the proper way of handling above ESB exception while providing the support for both types of operations. [1] https://docs.wso2.com/display/ESB490/Sample+150%3A+Introduction+to+Proxy+Services [2] https://docs.wso2.com/display/ESB403/Generic+Properties Thanks and Regards, -- Anupama Pathirage Associate Technical Lead WSO2, Inc. http://wso2.com/ Email: anup...@wso2.com Mobile:+94 71 8273 979 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
