Re: [Dev] Datamapper Build pack errors

[Lali Devamanthri]

Hi,
Seems it wired properly.

osgi> packages  org.codehaus.jackson
org.codehaus.jackson;
version="0.0.0"
  org.wso2.developerstudio.visualdatamapper.diagram_1.0.0.201312091117
[1004] imports






On Tue, Dec 10, 2013 at 12:45 PM, Harshana Martin  wrote:

> Hi Lali,
>
> Can you confirm that package org.codehaus.jackson is exported by someone
> and it is bound by the data mapprt bundle proery. You can start Eclipse
> with -console switch and try out the OSGI commands to find them out.
>
> Thanks and Regards,
> Harshana
>
>
> On Tue, Dec 10, 2013 at 12:23 PM, Lali Devamanthri  wrote:
>
>> Hi Harshana,
>> Build pack for Datamapper have been install in fresh eclipse and tested.
>> It gave following errors in log. Though I have add relevant .jars and
>> exported in *eclipse.library plugins project, this errors occur. Do I have
>> missed anything ?
>>
>>
>> j*ava.lang.NoClassDefFoundError: Could not initialize class
>> org.apache.avro.generic.GenericData*
>> at
>> org.apache.avro.generic.GenericDatumReader.(GenericDatumReader.java:49)
>>  at
>> dataMapper.diagram.tree.generator.TreeFromAvro.generateInputTree(TreeFromAvro.java:33)
>> at
>> dataMapper.diagram.edit.parts.InputEditPart.activate(InputEditPart.java:99)
>>  at
>> org.eclipse.gef.editparts.AbstractEditPart.activate(AbstractEditPart.java:160)
>> at
>> org.eclipse.gef.editparts.AbstractGraphicalEditPart.activate(AbstractGraphicalEditPart.java:195)
>>  at
>> org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart.access$0(GraphicalEditPart.java:1)
>> at
>> org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart.activate(GraphicalEditPart.java:205)
>>  at
>> org.eclipse.gef.editparts.AbstractEditPart.addChild(AbstractEditPart.java:215)
>> at
>> org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart.addChild(GraphicalEditPart.java:1319)
>>  at
>> org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:781)
>> ...
>>
>>
>>
>> *java.lang.NoClassDefFoundError: org/codehaus/jackson/JsonNode* at
>> org.apache.avro.generic.GenericData.(GenericData.java:901) at
>> org.apache.avro.generic.GenericDatumReader.(GenericDatumReader.java:49)
>> at
>> dataMapper.diagram.tree.generator.TreeFromAvro.generateInputTree(TreeFromAvro.java:33)
>> at
>> dataMapper.diagram.edit.parts.InputEditPart.activate(InputEditPart.java:99)
>> at
>> org.eclipse.gef.editparts.AbstractEditPart.addChild(AbstractEditPart.java:215)
>> at
>> org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart.addChild(GraphicalEditPart.java:1319)
>> at
>> org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:781)
>> at
>> org.eclipse.gef.editparts.AbstractEditPart.refresh(AbstractEditPart.java:726)
>> at
>> org.eclipse.gef.editparts.AbstractGraphicalEditPart.refresh(AbstractGraphicalEditPart.java:644)
>> at
>> org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart.access$3(GraphicalEditPart.java:1)
>> ...
>>
>> java.lang.NullPointerException
>> at
>> org.eclipse.gmf.runtime.diagram.ui.internal.services.decorator.DecoratorService$ProviderDescriptor.provides(DecoratorService.java:72)
>>  at
>> org.eclipse.gmf.runtime.common.core.service.Service.safeProvides(Service.java:859)
>> at
>> org.eclipse.gmf.runtime.common.core.service.ExecutionStrategy.getUncachedProviders(ExecutionStrategy.java:254)
>>  at
>> org.eclipse.gmf.runtime.common.core.service.Service.getProviders(Service.java:537)
>> at
>> org.eclipse.gmf.runtime.common.core.service.ExecutionStrategy$4.execute(ExecutionStrategy.java:178)
>>  at
>> org.eclipse.gmf.runtime.common.core.service.Service.execute(Service.java:651)
>> at
>> org.eclipse.gmf.runtime.diagram.ui.internal.services.decorator.DecoratorService.createDecorators(DecoratorService.java:121)
>>  ...
>>
>>
>>
>> java.lang.ClassNotFoundException:
>> org.eclipse.gmf.examples.runtime.diagram.decorator.provider.ReviewDecoratorProvider
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
>> ...
>>
>> --
>> *Lali Sudaththa Devamanthri*
>>  Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 71 895 4922
>>
>>
>
>
> --
>
> Harshana Martin
> Associate Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 775 998 115
> Profile: https://www.google.com/profiles/harshana05
> Blog: http://harshana05.blogspot.com
> Twitter: http://twitter.com/harshana05
>
>


-- 
*Lali Sudaththa Devamanthri*
 Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 71 895 4922
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/list

[Dev] API Manager nightly build pack - 09/12/2013

[Dinusha Senanayaka]

Hi All,

Please find the $subject in [1].

[1]. http://builder1.us1.wso2.org/~apim/09-12-2013/wso2am-1.6.0.zip


Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Senior Software Engineer
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API Manager nightly build pack - 09/12/2013

[Pavithra Madurangi]

Observed following error when trying to publish an API which was created
with caching enabled. Issue reported at [1]

[2013-12-10 15:03:37,703] ERROR - CacheMediatorFactory Unable to load the
hash generator class
java.lang.ClassNotFoundException:
org.wso2.caching.digest.REQUESTHASHGenerator
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:455)
 at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
 at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:169)
at
org.apache.synapse.config.xml.CacheMediatorFactory.createSpecificMediator(CacheMediatorFactory.java:99)
 at
org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:91)
 at
org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:223)
 at
org.apache.synapse.config.xml.AbstractListMediatorFactory.addChildren(AbstractListMediatorFactory.java:41)
 at
org.apache.synapse.config.xml.SequenceMediatorFactory.createAnonymousSequence(SequenceMediatorFactory.java:70)
 at
org.apache.synapse.config.xml.rest.ResourceFactory.configureSequences(ResourceFactory.java:103)
 at
org.apache.synapse.config.xml.rest.ResourceFactory.createResource(ResourceFactory.java:46)
 at
org.apache.synapse.config.xml.rest.APIFactory.createAPI(APIFactory.java:81)
 at
org.wso2.carbon.rest.api.service.RestApiAdmin.addApi(RestApiAdmin.java:606)
at
org.wso2.carbon.rest.api.service.RestApiAdmin.addApiFromString(RestApiAdmin.java:75)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
 at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
 at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
 at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
 at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
 at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
 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:848)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
 at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
 at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
 at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
 at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
 at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
 at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorVa

Re: [Dev] API Manager nightly build pack - 09/12/2013

[Lakmali Baminiwatta]

Hi Pavithra,

Fixed in r192914.
Occured due to older caching jar has gone in the pack. Updated to
org.wso2.caching_4.0.3.jar.

Thanks,
Lakmali


On 10 December 2013 15:13, Pavithra Madurangi  wrote:

> Observed following error when trying to publish an API which was created
> with caching enabled. Issue reported at [1]
>
> [2013-12-10 15:03:37,703] ERROR - CacheMediatorFactory Unable to load the
> hash generator class
> java.lang.ClassNotFoundException:
> org.wso2.caching.digest.REQUESTHASHGenerator
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:455)
>  at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>  at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>  at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> at java.lang.Class.forName0(Native Method)
>  at java.lang.Class.forName(Class.java:169)
> at
> org.apache.synapse.config.xml.CacheMediatorFactory.createSpecificMediator(CacheMediatorFactory.java:99)
>  at
> org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:91)
>  at
> org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:223)
>  at
> org.apache.synapse.config.xml.AbstractListMediatorFactory.addChildren(AbstractListMediatorFactory.java:41)
>  at
> org.apache.synapse.config.xml.SequenceMediatorFactory.createAnonymousSequence(SequenceMediatorFactory.java:70)
>  at
> org.apache.synapse.config.xml.rest.ResourceFactory.configureSequences(ResourceFactory.java:103)
>  at
> org.apache.synapse.config.xml.rest.ResourceFactory.createResource(ResourceFactory.java:46)
>  at
> org.apache.synapse.config.xml.rest.APIFactory.createAPI(APIFactory.java:81)
>  at
> org.wso2.carbon.rest.api.service.RestApiAdmin.addApi(RestApiAdmin.java:606)
> at
> org.wso2.carbon.rest.api.service.RestApiAdmin.addApiFromString(RestApiAdmin.java:75)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>  at
> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>  at
> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>  at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>  at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>  at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
> at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>  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:848)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>  at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>  at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  at
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>  at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>  at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>  at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>  at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>  at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>  at
> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>  at
> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
> at
> org.wso2.carbon.tomcat.ext.valves.TomcatValv

[Dev] Mutual SSL authentication not working with ESB enpoints.

[Janis Jansons]

Hi!

When trying to connect to endpoint that requires client SSL certificate,
the request just hangs and times out.

I tried to use the HttpCoreNIOSSLSender with custom SSL profiles (
http://pastebin.com/h8ee5bys), I tried to replace the default keystore but
it doesn't work.

Seems like it is not possible to connect to an endpoint with a client
certificate in WSO2 ESB.
Also wouldn't it require some additional parameter to force the client
certificate usage in case the client certificate is optional?

There have been some other discussions about mutual SSL authentication but
the developers always start talking about the listener, not the sender. The
sender has the problem.

Basically I spent days looking for ways to do it and it seems like it's not
possible. Then I tried it with Mule (had never used it before) and did it
in 5 minutes. WSO2 either lacks features that are important to serious
companies or they are not documented. I hope this gets better in time.

I'm using WSO2 ESB 4.8.0 (about week old).

Best regards,
Janis
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Installing Features on ESB 4.8 fails

[Kambiz Darabi]

Hi Kasun,

thank you for your quick reply.

With some additional problems, I now could install.

This is what I get when I try to install AS ONLY:

> Cannot complete the install because of a conflicting dependency.
>
> Software being installed:
>
> WSO2 Carbon - Reporting Feature 4.2.0
> (org.wso2.carbon.reporting.feature.group 4.2.0)
>
> Software currently installed:
>
> WSO2 Carbon - Reporting Core Feature 4.2.1
> (org.wso2.carbon.reporting.server.feature.group 4.2.1)
>

then I uncheck 'Reporting' and get

> Cannot complete the install because of a conflicting dependency.
>
> Software being installed:
>
> SAML2 based Single Sign-On authenticator Feature 4.2.0
> (org.wso2.carbon.identity.authenticator.saml2.sso.feature.group 4.2.0)
>
> Software currently installed:
>
> SAML2 based authenticator UI Feature 4.2.1
> (org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.group
> 4.2.1)

then I uncheck  'Single Sign On(SAML2)' which seems to be the problem and
can install Application Server.

Afterwards, I could install DSS and IS.

What would be necessary to avoid the conflicts? Is the reason the fact
that the ESB download contains features in newer versions that those in
the p2 repo at http://dist.wso2.org/p2/carbon/releases/4.2.0/ ?

If the p2 repo contained the 'Reporting Feature 4.2.1' and 'Single Sign
On(SAML2) 4.2.1', the conflicts would not arise?

Why does the AS depend on 'Reporting Feature' 4.2.1 and not [4.2,4.3) ?

Thank you


Kambiz

Kasun Gajasinghe  wrote:
> 
> Hi,
>
> Due to some limitations in P2, you have first install Application
> Server features. Then, you have install Application Server Runtimes
> feature after a server restart. If you install both at once following
> error will occur -
>
> 1 
>   Error while executing AddXMLElementAction touchpoint
> 2 
>   
> /opt/wso2/wso2esb-4.8.0/repository/components/default/../../../repository/conf/tomcat/webapp-
>   classloading-environments.xml (No such file or directory)
> 3 
>
> On Tue, Dec 10, 2013 at 12:01 PM, Kambiz Darabi
>  wrote:
>
> Hello,
> 
> I would like to install the available Features in
> 
> http://dist.wso2.org/p2/carbon/releases/4.2.0/
> 
> on top a fresh download of ESB 4.8.
> 
> First problem: if I check all
> 
> - Application Server
> - Application Server Runtimes (Optional)
> - Data Services Server
> - Identity Server
> 
> the installation is not possible because of missing dependencies.
> 
> 
> Second problem: after unchecking some of the features
> (incrementally,
> with trial and error), e.g. Reporting, Identity Provider, SAML2,
> the
> installation starts, but leads to an error. I have pasted the log
> at
> 
> http://pastebin.com/ftEExnes
> 
> Can someone please shed some light on this issue?
> 
> Thank you
> 
> 
> Kambiz Darabi
> --
> m-creations gmbh
> Acker 2
> 55116 Mainz
> Germany
> 
> W: http://www.m-creations.com
> E: dar...@m-creations.com
> T: +49 6131 6224417
> F: +49 6131 6224418
> --
> Registered Office: Mainz, HRB Mainz 7382
> Managing Directors: Frank Pacholak, Kambiz Darabi
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
> 
>
> -- 
> Kasun Gajasinghe
> Software Engineer; 
> WSO2 Inc.; http://wso2.com
> ,
> email: kasung AT spamfree wso2.com
> cell: +94 (77) 678-0813
> linked-in: http://lk.linkedin.com/in/gajasinghe
>
> blog: http://kasunbg.org
>
> twitter: http://twitter.com/kasunbg
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Identity Server 4.6.0 release

[Shavantha Weerasinghe]

Hi ishara

Hope we can get a new pack tomorrow
Regards,shavantha
On 10 Dec 2013 10:23, "Ishara Karunarathna"  wrote:

> [Moving to dev list]
>
>
> On Tue, Dec 10, 2013 at 10:18 AM, Suneth Ranasinghe wrote:
>
>> Hi Johann,
>>
>> Please apply Asela's patch attached to JIRA [1], which is a UI fixed for
>> "write Policy in XML".
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-1939
>>
>> Regards,
>>
>>
>> On Tue, Dec 10, 2013 at 9:56 AM, Shavantha Weerasinghe <
>> shavan...@wso2.com> wrote:
>>
>>> hi all
>>>
>>> below are a list of jira reported upto now
>>>
>>> IDENTITY-1938
>>>
>>> when a tenant attempts to add a keystore such as the wso2carbon.jks
>>> the system informs that the keystore already exist but that is only
>>> for super tenant and not the tenant i created
>>>
>>> IDENTITY-1937
>>>
>>> on some occations the IS throws an error when a tenant tries to create
>>> an SSO client
>>>
>>> IDENTITY-1931
>>>
>>> Open ID login flow fails when attempting to login with the system
>>> generated open id
>>>
>>> IDENTITY-1930
>>>
>>> OAuth implicit flow works even after a user removes that grat type
>>> from the registered OA
>>>
>>> IDENTITY-1929
>>>
>>> tenants are shown the domain in the certificate aliasdropdown
>>>
>>> IDENTITY-1928
>>>
>>> secondary user stores cannot be created by a tenant
>>>
>>> IDENTITY-1923
>>>
>>> secondary domain is not visible for the tenant when a tenant clicks on
>>> the domain dropdown
>>>
>>> IDENTITY-1922
>>>
>>> unable to configure SSO as a dead page is loaded
>>> 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, Dec 5, 2013 at 6:19 PM, Johann Nallathamby 
>>> wrote:
>>> > Hi Shavantha,
>>> >
>>> > Please try with this jar. I have fixed some issues.
>>> >
>>> >
>>> > On Thu, Dec 5, 2013 at 3:11 PM, Johann Nallathamby 
>>> wrote:
>>> >>
>>> >> Hi Shavantha,
>>> >>
>>> >> Please test with attached jar. Add it as a patch.
>>> >>
>>> >>
>>> >> On Thu, Dec 5, 2013 at 1:17 PM, Shavantha Weerasinghe <
>>> shavan...@wso2.com>
>>> >> wrote:
>>> >>>
>>> >>> thanks, started testing
>>> >>> 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, Dec 5, 2013 at 1:09 PM, Chamath Gunawardana <
>>> chama...@wso2.com>
>>> >>> wrote:
>>> >>> > Hi Shavantha,
>>> >>> >
>>> >>> > The pack is available in
>>> >>> >
>>> >>> >
>>> https://svn.wso2.org/repos/wso2/scratch/IS-4.5.1/5-12-13/wso2is-4.6.0.zip
>>> >>> >
>>> >>> >
>>> >>> > Thanks,
>>> >>> >
>>> >>> >
>>> >>> > On Thu, Dec 5, 2013 at 11:19 AM, Shavantha Weerasinghe
>>> >>> > 
>>> >>> > wrote:
>>> >>> >>
>>> >>> >> hi guys
>>> >>> >>
>>> >>> >> any update on a pack for testing
>>> >>> >>
>>> >>> >> 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 Wed, Dec 4, 2013 at 9:58 AM, Shavantha Weerasinghe
>>> >>> >>  wrote:
>>> >>> >> > Hi Venura
>>> >>> >> >
>>> >>> >> > Thanks for the update
>>> >>> >> >
>>> >>> >> > 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 Wed, Dec 4, 2013 at 9:55 AM, Venura Kahawala <
>>> ven...@wso2.com>
>>> >>> >> > wrote:
>>> >>> >> >> Hi Shavantha,
>>> >>> >> >>
>>> >>> >> >> Ishara has encountered some integration test failures, which
>>> will
>>> >>> >> >> be
>>> >>> >> >> fixed
>>> >>> >> >> ASAP. Then a pack can be released for QA testing.
>>> >>> >> >>
>>> >>> >> >> Regards,
>>> >>> >> >> Venura
>>> >>> >> >>
>>> >>> >> >>
>>> >>> >> >> On Wed, Dec 4, 2013 at 9:53 AM, Shavantha Weerasinghe
>>> >>> >> >> 
>>> >>> >> >> wrote:
>>> >>> >> >>>
>>> >>> >> >>> Hi Asela
>>> >>> >> >>>
>>> >>> >> >>> When will the pack be released for QA
>>> >>> >> >>>
>>> >>> >> >>> 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 Tue, Dec 3, 2013 at 5:41 PM, Asela Pathberiya <
>>> as...@wso2.com>
>>> >>> >> >>> wrote:
>>> >>> >> >>> >
>>> >>> >> >>> >
>>> >>> >> >>> >
>>> >>> >> >>> > On Tue, Dec 3, 2013 at 4:33 PM, Sumedha Rubasinghe
>>> >>> >> >>> > 
>>>

[Dev] NPE while hazelcast initializing, in the 10th December Storage Server build

[Chamara Ariyarathne]

https://wso2.org/jira/browse/CARBON-14580

This is a blocker at the moment. I'm not using any new configuration here.
This exact configuration worked with the 3rd december build.

Please look asap.

-- 
*Chamara Ariyarathne*
Senior Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; *+94772786766*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] NPE while hazelcast initializing, in the 10th December Storage Server build

[Afkham Azeez]

If you can remember, this is the issue Peter mentioned that has been in
Hazelcast 3.0.3 onwards


On Tue, Dec 10, 2013 at 6:30 PM, Chamara Ariyarathne wrote:

> https://wso2.org/jira/browse/CARBON-14580
>
> This is a blocker at the moment. I'm not using any new configuration here.
> This exact configuration worked with the 3rd december build.
>
> Please look asap.
>
> --
> *Chamara Ariyarathne*
> Senior Software Engineer - QA;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; *+94772786766 <%2B94772786766>*
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919 blog: **http://blog.afkham.org*
*twitter: **http://twitter.com/afkham_azeez*
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

Re: [Dev] NPE while hazelcast initializing, in the 10th December Storage Server build

[Chamara Ariyarathne]

But I'm only seeing this in the latest SS build. With the same
configuration I've been used.

Have we changed the hazelcast version for this build. 10-12-2013


On Tue, Dec 10, 2013 at 6:35 PM, Afkham Azeez  wrote:

> If you can remember, this is the issue Peter mentioned that has been in
> Hazelcast 3.0.3 onwards
>
>
> On Tue, Dec 10, 2013 at 6:30 PM, Chamara Ariyarathne wrote:
>
>> https://wso2.org/jira/browse/CARBON-14580
>>
>> This is a blocker at the moment. I'm not using any new configuration
>> here. This exact configuration worked with the 3rd december build.
>>
>> Please look asap.
>>
>> --
>> *Chamara Ariyarathne*
>> Senior Software Engineer - QA;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; *+94772786766 <%2B94772786766>*
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
*Chamara Ariyarathne*
Senior Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; *+94772786766*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] NPE while hazelcast initializing, in the 10th December Storage Server build

[Prabath Abeysekera]

Hi Azeez,

Do we already have any interim fix that we can probably use till we do the
Hazelcast version upgrade?

Cheers,
Prabath


On Tue, Dec 10, 2013 at 2:05 PM, Afkham Azeez  wrote:

> If you can remember, this is the issue Peter mentioned that has been in
> Hazelcast 3.0.3 onwards
>
>
> On Tue, Dec 10, 2013 at 6:30 PM, Chamara Ariyarathne wrote:
>
>> https://wso2.org/jira/browse/CARBON-14580
>>
>> This is a blocker at the moment. I'm not using any new configuration
>> here. This exact configuration worked with the 3rd december build.
>>
>> Please look asap.
>>
>> --
>> *Chamara Ariyarathne*
>> Senior Software Engineer - QA;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; *+94772786766 <%2B94772786766>*
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Prabath Abeysekara
Associate Technical Lead, Data TG.
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Architecture][ANN] WSO2 Business Process Server (WSO2 BPS) 3.1.0 Released

[Nandika Jayawardana]

WSO2 Business Process Server (WSO2 BPS) 3.1.0 Release Notes December 2013

WSO2 Business Process Server (BPS) is an easy-to-use Open Source Business
Process Server that executes business processes written following WS-BPEL
and WS-Human Task standards. WS-BPEL is the defacto standard for composing
multiple synchronous and asynchronous web services into collaborative and
transactional process flows which increase the flexibility and agility of
your Service Oriented Architecture. WS-Human Task allows people activities
to be integrated with business processes.. WSO2 BPS is powered by
Apache ODE and
available underApache Software License
v2.0.
WSO2 BPS provides a complete Web based graphical console to deploy, manage
and monitor business process and process instances.

WSO2 BPS is developed on top of the revolutionary Carbon platform
(Middleware a' la carte), and is based on the OSGi framework to achieve the
better modularity for you SOA. Carbon platform contains lots of new
features and many other optional components that can be used to customize
or enhance the functionalities provided by BPS to suits you SOA needs. In
addition to installing optional components you can uninstall unwanted
features without any trouble.

WSO2 BPS is an opensource product available under the Apache Software
License (v2.0)  . This
includes all of the extra integration and management functionality as well.
Key Features

   - Deploying Business Processes written in compliance with WS-BPEL 2.0
   Standard and BPEL4WS 1.1 standard.
   - Support for Human Interactions in BPEL Processes with WS-Human Task
   and BPEL4People.
   - Managing BPEL packages, processes and process instances.
   - BPEL Extensions and XPath extensions support
   - Instance recovery(Only supports 'Invoke' activity) support through
   management console
   - OpenJPA based Data Access Layer For BPEL and Human Tasks
   - WS-Security support for business processes.
   - Support for invoking secured(Using WS-Security) partner services.
   - Support for HumanTask Coordination
   - BPEL Package hot update which facilitate Versioning of BPEL Packages
   - BPEL deployment descriptor editor
   - E4X based data manipulation support for BPEL assignments
   - Configure external data base system as the BPEL engine's persistence
   storage
   - Caching support for business processes.
   - Throttling support for business processes.
   - Transport management.
   - Internationalized web based management console.
   - System monitoring.
   - Try-it for business processes.
   - SOAP Message Tracing.
   - End-point configuration mechanism based on WSO2 Unified Endpoints.
   - Customizable server - You can customize the BPS to fit into your exact
   requirements, by removing certain features or by adding new optional
   features.
   - Performance improvements in XPath evaluations
   - Clustering support for BPEL engine.
   - Process monitoring with WSO2 Business Activity Monitor
   - JMX monitoring support

New Features In This Release

   - WS-Human Task Coordination Support
   - Literal based and Expression based user assignment support for Human
   Tasks
   - Hazelcast based clustering improvements for ODE

Issues Fixed for this release

   - WSO2 BPS related components of the WSO2 Carbon Platform -
   https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=11673

XML & WS-* Standards Support

   - BPEL4WS 1.1
   - WS-BPEL 2.0
   - WS-Human Task 1.1
   - BPEL4People 1.1
   - SOAP 1.1/1.2
   - WSDL 1.1
   - WSDL 2.0
   - MTOM, XOP & SOAP with Attachments
   - WS-Addressing
   - WS-Security 1.0/1.1
   - WS-Trust
   - WS-SecureConversation
   - WS-SecurityPolicy
   - WS-ReliableMessaging
   - WS-Policy
   - WS-PolicyAttachment
   - WS-MetadataExchange
   - WS-Transfer
   - XKMS

Open Source components included in WSO2 BPS/Java

   - Apache ODE (BPEL)
   - Apache Axis2 (SOAP)
   - Apache Axiom (High performance XML Object Model)
   - Apache Rampart/Apache WSS4J (WS-Security)
   - Apache Rahas(WS-SecureConversation)
   - Apache Sandesha2 (WS-ReliableMessaging)
   - Apache Batik
   - WS-Addressing implementation in Axis2
   - Apache Neethi (WS-Policy)
   - WS-SecurityPolicy implementation in Axis2
   - Apache XML Schema
   - Apache Derby (Database)
   - Apache OpenJPA
   - Embedded Apache Tomcat
   - Spring Framework

Apache Axis2 modules included with WSO2 BPS

   - Apache Rampart: Supporting WS-Security & WS-Trust
   - Apache Rahas: Supporting WS-SecureConversation
   - Apache Sandesha2: Supporting WS-Reliable Messaging
   - Mex: Supporting WS-MetaDataExchange
   - Throttle: For throttling requests
   - Statistics: For gathering & monitoring statistics
   - SOAP Tracer: For tracing SOAP requests & responses
   - XFer: Supporting WS-Transfer
   - XKMS: Supporting XML Key Management Specification

Known Issues

   - WS-Human Task implementation does not su

[Dev] Jaggery - How to process a SOAP request

[Nuwan Dias]

Hi,

I have a restful jaggery endpoint and I now want to make this serve SOAP
requests as well. My idea is to look at the Content-Type header and
determine whether the request is REST or SOAP.

I need to know how I can process a SOAP request from jaggery. When I try
'request.getContent()', it gives me a null value. Is there a way to process
a SOAP Body from jaggery?

Thanks,
NuwanD.

-- 
Nuwan Dias

Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Developer Studio 3.3.0 Alpha 3 Released!

[Krishantha Samaraweera]

Hi Harshana,

On Thu, Nov 21, 2013 at 2:37 PM, Harshana Martin  wrote:

> Hi Samisa,
>
>
> On Thu, Nov 21, 2013 at 2:31 PM, Samisa Abeysinghe wrote:
>
>> Given there is no auto test help, to guard against slips, lets at least
>> use a checklist of all mediators to be tested.
>>
>
> Yes.. That's a good idea.. we did such cross check when we did DevS 3.0.0
> release. So we will reuse the same set to make sure no slip ups.
>
>>
>> I was looking for auto tests, becuase, it is hard to test them all
>> manually.
>>
>> Alternatively, we can see if we can use ESB auto tests in here, where we
>> develop the artifacts for all mediators using DevS and test those artifacts
>> with ESB auto test framework. That could work.
>>
>
> Yes.. +1
>
> We can produce CAR files with all mediator scenarios and provide them to
> ESB Testing Framework which could show us the error in configurations. Also
> once we are done with it, the same CAR files can be used for future ESB
> testing as well.
>

When can we get CAR files to cover all mediators?  we can add some base
tests to cover deploy, undeploy and re-deployment of CAR files and allow
ESB team to complete the rest.

Thanks,
Krishantha.


> We will execute that plan for the release. Thanks for the valuable input
> Samisa.
>
> Best Regards,
> Harshana
>
>>
>>
>> Thanks,
>> Samisa...
>>
>>
>> Samisa Abeysinghe
>>
>> Vice President Training
>>
>> WSO2 Inc.
>> http://wso2.com
>>
>>
>>
>> On Thu, Nov 21, 2013 at 2:27 PM, Harshana Martin wrote:
>>
>>> Hi Samisa,
>>>
>>>
>>> On Thu, Nov 21, 2013 at 6:50 AM, Samisa Abeysinghe wrote:
>>>
 What is the plan to test all mediators for basic functionality for
 3.3.0?

>>>
>>> At the moment we are planning to test the mediators using the samples
>>> mainly and some known use cases.
>>>

 I understand that some mediators were badly broken in 3.2.0 release
 e.g. XACML.

>>>
>>> Although Entitlement mediator was a specific mediator only, we fixed but
>>> there could be some other mediators like that. So we are going to cover all
>>> most all mediators during the testing.
>>>

 Can we make use of the auto test framework to ensure that there are no
 absolute blockers in any mediator out of the full mediator lot.

>>>
>>> Test framework is still not developed to support that level of
>>> requirements. We will try to improve it while testing the 3.3.0. But most
>>> of the testing will happen manually for this release. We are planning to
>>> assign someone full-time basis to improve the test framework to support
>>> complete automated testing.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>


 Thanks,
 Samisa...


 Samisa Abeysinghe

 Vice President Training

 WSO2 Inc.
 http://wso2.com



 On Mon, Nov 18, 2013 at 3:49 PM, Asanka Sanjeewa wrote:

> Hi All,
>
> We have WSO2 Developer Studio 3.3.0 Alpha 3 version  ready to be
> downloaded at [1]. Installed eclipse distributions available at [2].
>
> This release includes following new feature, improvements and bug
> fixes.
>
> New Feature
>
>- [TOOLS-1855 ] - Cloud
>connector support
>
> Improvements
>
>- [TOOLS-1870 ] -
>Enabling Jaggery Editor Auto-Complete even without typing a character
>- [TOOLS-2085 ] - There
>is no way to rename a GReg artifact.
>- [TOOLS-2106 ] - Adding
>perspective login change icon into toolbar
>- [TOOLS-2107 ] - Login
>window should not pop-up when resetting the perspective and should 
> pop-up
>for new perspective Only
>
> Bug Fixes
>
>- [TOOLS-1337 ] - There
>is no way to add "include" block inside Script Mediator
>- [TOOLS-1694 ] - AF
>perspective detais view not filling all the feilds
>- [TOOLS-1719 ] - [Dev
>Studio-3.2] - Logging not consistent with WSO2 Standards
>- [TOOLS-1722 ] - Dev
>Studio fails to create Registry resource without file extension
>- [TOOLS-1731 ] - Dev
>Studio fails to rename a resource correctly.
>- [TOOLS-1737 ] - [Dev
>Studio 3.2] End Point Connection Issues
>- [TOOLS-1738 ] - [Dev
>Studio 3.2] - Null Argument error for Clone Mediator
>- [TOOLS-1743 ] - [Dev
>Studio 3.2] - Exceptions Creating EndPoint (JMS)
>- [TOOLS-1746 

Re: [Dev] [ESB] Creating a secure client using axiom

[Dulanja Liyanage]

Hi,

You need to have bouncycastle jar in your classpath [1].

You can find one at ESB_HOME/repository/axis2/client/lib/bcprov-jdk15.jar.

[1]
http://blog.rampartfaq.com/2009/08/orgapachewssecuritywssecurityexception.html

Thanks
Dulanja


On Tue, Dec 10, 2013 at 12:57 PM, Maduranga Siriwardena
wrote:

> I added the relevant path to the client repo and the axis2.xml and I added
> all the jars mentioned in the build file of the sample client in ESB to
>  the project I was able to engage the rampart module. Now I get the bellow
> error stack. It is encryption error. Can someone figure out how to fix the
> problem
>
> org.apache.axis2.AxisFault: Error in encryption
> at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:76)
> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>  at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:426)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:398)
>  at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>  at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:554)
> at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:530)
>  at client.OrderProcessClient.createOrder(OrderProcessClient.java:231)
> at client.OrderProcessClient.main(OrderProcessClient.java:57)
> Caused by: org.apache.rampart.RampartException: Error in encryption
> at
> org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:612)
>  at
> org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:97)
> at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
>  at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
> ... 11 more
> Caused by: org.apache.ws.security.WSSecurityException: An unsupported
> signature or encryption algorithm was used (unsupported key transport
> encryption algorithm: No such algorithm:
> http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p); nested exception is:
>  java.security.NoSuchAlgorithmException: Cannot find any provider
> supporting RSA/ECB/OAEPPadding
> at
> org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:785)
>  at
> org.apache.ws.security.message.WSSecEncryptedKey.prepareInternal(WSSecEncryptedKey.java:205)
> at
> org.apache.ws.security.message.WSSecEncrypt.prepare(WSSecEncrypt.java:259)
>  at
> org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:578)
> ... 14 more
> Caused by: java.security.NoSuchAlgorithmException: Cannot find any
> provider supporting RSA/ECB/OAEPPadding
> at javax.crypto.Cipher.getInstance(Cipher.java:524)
>  at
> org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:777)
> ... 17 more
>
>
> On Fri, Dec 6, 2013 at 8:07 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>>
>>
>>
>> On Fri, Dec 6, 2013 at 4:50 PM, Maduranga Siriwardena > > wrote:
>>
>>> Path to what file should I add to classpath? Isn't that enough to add
>>> bellow lines?
>>>
>>> ConfigurationContext configContext =   ConfigurationContextFactory.
>>> createConfigurationContextFromFileSystem("CARBON_HOME\\
>>> repository\\deployment\\client", "CARBON_HOME\\repository\\
>>> conf\\axis2_client.xml");
>>>
>>
>> The above should be enough as long as you have the rampart module under
>> client_repo_path/modules directory and rampart libraries
>> (rampart-core_1.6.1.wso2v12.jar, rampart-policy_1.6.1.wso2v12.jar,
>> rampart-trust_1.6.1.wso2v12.jar) in your classpath. The "classpath" is the
>> place you tell jvm to look for required classes for you client application.
>>
>> You are also giving the axis2.xml as well to create configuration
>> context. This is where you get the error java.lang.ClassNotFoundException:
>> org.apache.axis2.transport.tcp.TCPTransportSender. This is because when the
>> creating the ConfigrationContext it will initialize the axis config using
>> the given axis2.xml. And those missing classes reside in some other axis2
>> libraries, which are not yet available your classpath. Either you can add
>> that lib (axis2_1.6.1.wso2v10.jar) to you classpath or try the following.
>>
>> In a normal case you will not need to provide an axis2.xml when creating
>> ConfigrationContext. So first try giving it as null and only give the repo
>> location.
>> Ex:
>> ConfigurationContext configContext =
>> ConfigurationContextFactory.createConfigurationContextFromFileSystem("client_repo_path",
>> null);
>>
>> This will initialize axis2 client side with default axisConfig and make
>> those modules (and services) available at client side.
>>
>> You can find all the above mentioned libraries in ESB distribution

Re: [Dev] Jaggery - How to process a SOAP request

[Madhuka Udantha]

Hi, Nuwan

Yap, trying is correct, Jaggery Web hostobject had bug regard
to 'request.getContent()' and it is be fixed in github master.
Thinking you try some old jaggery version.

Here I will attaching patch (0.9.0.ALPHA4_wso2v1) for you and sample
jaggery file for you to test.


On Tue, Dec 10, 2013 at 8:30 PM, Nuwan Dias  wrote:

> Hi,
>
> I have a restful jaggery endpoint and I now want to make this serve SOAP
> requests as well. My idea is to look at the Content-Type header and
> determine whether the request is REST or SOAP.
>
> I need to know how I can process a SOAP request from jaggery. When I try
> 'request.getContent()', it gives me a null value.
>
Yap, it was bug in jaggery.
It is fixed. Try this and let us know.

Thanks

> Is there a way to process a SOAP Body from jaggery?
>
> Thanks,
> NuwanD.
>
> --
> Nuwan Dias
>
> Senior Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com

*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/


org.jaggeryjs.hostobjects.web_0.9.0.ALPHA4_wso2v1.jar
Description: application/java-archive


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

Re: [Dev] Identity Server 4.6.0 release

[Ishara Karunarathna]

Hi Shavantha,

Now we are fixing some issues in the pack and will try to give you
a new pack tomorrow.
Until please test with the given pack.

Thanks,


On Tue, Dec 10, 2013 at 6:29 PM, Shavantha Weerasinghe
wrote:

> Hi ishara
>
> Hope we can get a new pack tomorrow
> Regards,shavantha
> On 10 Dec 2013 10:23, "Ishara Karunarathna"  wrote:
>
>> [Moving to dev list]
>>
>>
>> On Tue, Dec 10, 2013 at 10:18 AM, Suneth Ranasinghe wrote:
>>
>>> Hi Johann,
>>>
>>> Please apply Asela's patch attached to JIRA [1], which is a UI fixed for
>>> "write Policy in XML".
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY-1939
>>>
>>> Regards,
>>>
>>>
>>> On Tue, Dec 10, 2013 at 9:56 AM, Shavantha Weerasinghe <
>>> shavan...@wso2.com> wrote:
>>>
 hi all

 below are a list of jira reported upto now

 IDENTITY-1938

 when a tenant attempts to add a keystore such as the wso2carbon.jks
 the system informs that the keystore already exist but that is only
 for super tenant and not the tenant i created

 IDENTITY-1937

 on some occations the IS throws an error when a tenant tries to create
 an SSO client

 IDENTITY-1931

 Open ID login flow fails when attempting to login with the system
 generated open id

 IDENTITY-1930

 OAuth implicit flow works even after a user removes that grat type
 from the registered OA

 IDENTITY-1929

 tenants are shown the domain in the certificate aliasdropdown

 IDENTITY-1928

 secondary user stores cannot be created by a tenant

 IDENTITY-1923

 secondary domain is not visible for the tenant when a tenant clicks on
 the domain dropdown

 IDENTITY-1922

 unable to configure SSO as a dead page is loaded
 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, Dec 5, 2013 at 6:19 PM, Johann Nallathamby 
 wrote:
 > Hi Shavantha,
 >
 > Please try with this jar. I have fixed some issues.
 >
 >
 > On Thu, Dec 5, 2013 at 3:11 PM, Johann Nallathamby 
 wrote:
 >>
 >> Hi Shavantha,
 >>
 >> Please test with attached jar. Add it as a patch.
 >>
 >>
 >> On Thu, Dec 5, 2013 at 1:17 PM, Shavantha Weerasinghe <
 shavan...@wso2.com>
 >> wrote:
 >>>
 >>> thanks, started testing
 >>> 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, Dec 5, 2013 at 1:09 PM, Chamath Gunawardana <
 chama...@wso2.com>
 >>> wrote:
 >>> > Hi Shavantha,
 >>> >
 >>> > The pack is available in
 >>> >
 >>> >
 https://svn.wso2.org/repos/wso2/scratch/IS-4.5.1/5-12-13/wso2is-4.6.0.zip
 >>> >
 >>> >
 >>> > Thanks,
 >>> >
 >>> >
 >>> > On Thu, Dec 5, 2013 at 11:19 AM, Shavantha Weerasinghe
 >>> > 
 >>> > wrote:
 >>> >>
 >>> >> hi guys
 >>> >>
 >>> >> any update on a pack for testing
 >>> >>
 >>> >> 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 Wed, Dec 4, 2013 at 9:58 AM, Shavantha Weerasinghe
 >>> >>  wrote:
 >>> >> > Hi Venura
 >>> >> >
 >>> >> > Thanks for the update
 >>> >> >
 >>> >> > 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 Wed, Dec 4, 2013 at 9:55 AM, Venura Kahawala <
 ven...@wso2.com>
 >>> >> > wrote:
 >>> >> >> Hi Shavantha,
 >>> >> >>
 >>> >> >> Ishara has encountered some integration test failures, which
 will
 >>> >> >> be
 >>> >> >> fixed
 >>> >> >> ASAP. Then a pack can be released for QA testing.
 >>> >> >>
 >>> >> >> Regards,
 >>> >> >> Venura
 >>> >> >>
 >>> >> >>
 >>> >> >> On Wed, Dec 4, 2013 at 9:53 AM, Shavantha Weerasinghe
 >>> >> >> 
 >>> >> >> wrote:
 >>> >> >>>
 >>> >> >>> Hi Asela
 >>> >> >>>
 >>> >> >>> When will the pack be released for QA
 >>> >> >>>
 >>> >> >>> Regards,
 >>> >> >>> Shavantha Weerasinghe
 >>> >> >>> Senior Software Engineer QA
 >>> >> >>> WSO2, Inc.
 >>> >> >>> lean.enterprise.middleware.
 >>> >> >>> ht

Re: [Dev] Identity Server 4.6.0 release

[Ishara Karunarathna]

Hi Shavantha,

Now we are fixing some issues in the pack and will try to give you
a new pack tomorrow.
Until please test with the given pack.

Thanks,


On Tue, Dec 10, 2013 at 6:29 PM, Shavantha Weerasinghe
wrote:

> Hi ishara
>
> Hope we can get a new pack tomorrow
> Regards,shavantha
> On 10 Dec 2013 10:23, "Ishara Karunarathna"  wrote:
>
>> [Moving to dev list]
>>
>>
>> On Tue, Dec 10, 2013 at 10:18 AM, Suneth Ranasinghe wrote:
>>
>>> Hi Johann,
>>>
>>> Please apply Asela's patch attached to JIRA [1], which is a UI fixed for
>>> "write Policy in XML".
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY-1939
>>>
>>> Regards,
>>>
>>>
>>> On Tue, Dec 10, 2013 at 9:56 AM, Shavantha Weerasinghe <
>>> shavan...@wso2.com> wrote:
>>>
 hi all

 below are a list of jira reported upto now

 IDENTITY-1938

 when a tenant attempts to add a keystore such as the wso2carbon.jks
 the system informs that the keystore already exist but that is only
 for super tenant and not the tenant i created

 IDENTITY-1937

 on some occations the IS throws an error when a tenant tries to create
 an SSO client

 IDENTITY-1931

 Open ID login flow fails when attempting to login with the system
 generated open id

 IDENTITY-1930

 OAuth implicit flow works even after a user removes that grat type
 from the registered OA

 IDENTITY-1929

 tenants are shown the domain in the certificate aliasdropdown

 IDENTITY-1928

 secondary user stores cannot be created by a tenant

 IDENTITY-1923

 secondary domain is not visible for the tenant when a tenant clicks on
 the domain dropdown

 IDENTITY-1922

 unable to configure SSO as a dead page is loaded
 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, Dec 5, 2013 at 6:19 PM, Johann Nallathamby 
 wrote:
 > Hi Shavantha,
 >
 > Please try with this jar. I have fixed some issues.
 >
 >
 > On Thu, Dec 5, 2013 at 3:11 PM, Johann Nallathamby 
 wrote:
 >>
 >> Hi Shavantha,
 >>
 >> Please test with attached jar. Add it as a patch.
 >>
 >>
 >> On Thu, Dec 5, 2013 at 1:17 PM, Shavantha Weerasinghe <
 shavan...@wso2.com>
 >> wrote:
 >>>
 >>> thanks, started testing
 >>> 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, Dec 5, 2013 at 1:09 PM, Chamath Gunawardana <
 chama...@wso2.com>
 >>> wrote:
 >>> > Hi Shavantha,
 >>> >
 >>> > The pack is available in
 >>> >
 >>> >
 https://svn.wso2.org/repos/wso2/scratch/IS-4.5.1/5-12-13/wso2is-4.6.0.zip
 >>> >
 >>> >
 >>> > Thanks,
 >>> >
 >>> >
 >>> > On Thu, Dec 5, 2013 at 11:19 AM, Shavantha Weerasinghe
 >>> > 
 >>> > wrote:
 >>> >>
 >>> >> hi guys
 >>> >>
 >>> >> any update on a pack for testing
 >>> >>
 >>> >> 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 Wed, Dec 4, 2013 at 9:58 AM, Shavantha Weerasinghe
 >>> >>  wrote:
 >>> >> > Hi Venura
 >>> >> >
 >>> >> > Thanks for the update
 >>> >> >
 >>> >> > 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 Wed, Dec 4, 2013 at 9:55 AM, Venura Kahawala <
 ven...@wso2.com>
 >>> >> > wrote:
 >>> >> >> Hi Shavantha,
 >>> >> >>
 >>> >> >> Ishara has encountered some integration test failures, which
 will
 >>> >> >> be
 >>> >> >> fixed
 >>> >> >> ASAP. Then a pack can be released for QA testing.
 >>> >> >>
 >>> >> >> Regards,
 >>> >> >> Venura
 >>> >> >>
 >>> >> >>
 >>> >> >> On Wed, Dec 4, 2013 at 9:53 AM, Shavantha Weerasinghe
 >>> >> >> 
 >>> >> >> wrote:
 >>> >> >>>
 >>> >> >>> Hi Asela
 >>> >> >>>
 >>> >> >>> When will the pack be released for QA
 >>> >> >>>
 >>> >> >>> Regards,
 >>> >> >>> Shavantha Weerasinghe
 >>> >> >>> Senior Software Engineer QA
 >>> >> >>> WSO2, Inc.
 >>> >> >>> lean.enterprise.middleware.
 >>> >> >>> ht

Re: [Dev] How do I get connectors to work with DevS?

[Isabelle Mauny]

But I am still able to have different configs / connector right ? for example 
use one set of credentials for connector1 in proxy1 and another set of 
credentials for connector1 in proxy2 ..

Thanks.
__

Isabelle Mauny
Director, Product Management; WSO2, Inc.;  http://wso2.com/

On Dec 7, 2013, at 7:14 AM, Asanka Sanjeewa  wrote:

> Hi,
> 
> Imported connectors maintained within the Workspace improvement [1] also 
> completed and it will be available in Developer Studio 3.3.0 Alpha 4 release. 
> 
> With this improvement all the imported connectors will be visible to all the 
> ESB Configuration Projects within the Workspace (in previous model they were 
> specific only to the particular project into which connectors were imported). 
> 
> [1] https://wso2.org/jira/browse/TOOLS-2161
> 
> Thanks and Regards,
> AsankaS. 
> 
> 
> On Sat, Dec 7, 2013 at 11:17 AM, Samisa Abeysinghe  wrote:
> Excellent!
> 
> Thanks,
> Samisa...
> 
> 
> 
> Samisa Abeysinghe
> 
> Vice President Training 
> 
> WSO2 Inc. 
> http://wso2.com
> 
> 
> 
> 
> On Sat, Dec 7, 2013 at 9:31 AM, Asanka Sanjeewa  wrote:
> Hi Samisa,
> 
> Arranging connector operations in alphabetical order [1] related changes 
> already done and this will be available in Developer Studio Alpha 4 release. 
> 
> [1] https://wso2.org/jira/browse/TOOLS-2159
> 
> Thanks and Regards,
> AsankaS. 
> 
> 
> On Sat, Dec 7, 2013 at 6:11 AM, Samisa Abeysinghe  wrote:
> That is great. Thanks. The other improvement that I think is a must is the 
> alphabetical ordering of the connector operations. Are we looking into that 
> too? It would be great to have that fix too before we ship, as otherwise, it 
> is hard to locate the proper operations. 
> 
> 
> Thanks,
> Samisa...
> 
> 
> 
> Samisa Abeysinghe
> 
> Vice President Training 
> 
> WSO2 Inc. 
> http://wso2.com
> 
> 
> 
> 
> On Fri, Dec 6, 2013 at 5:11 PM, Harshana Martin  wrote:
> Hi Samisa,
> 
> Asanka has accommodated this change now. We will ship the Alpha 4 release 
> with this fix.
> 
> Thanks and Regards,
> Harshana
> 
> 
> On Wed, Dec 4, 2013 at 12:04 PM, Samisa Abeysinghe  wrote:
> 
> 
> On Wed, Dec 4, 2013 at 11:02 AM, Harshana Martin  wrote:
> Hi Samisa,
> 
> The current design of DevS connector import is incorrect!.
> 
> It does not make sense user importing same connector over and over again just 
> because the configurations are in 2 different ESB config projects.
> 
> The connectors should be imported and maintained per Workspace not per 
> Project.
> 
> +1
> 
> That is exactly what I meant too!
>  
> So we will make this design change [1].
> 
> [1]. https://wso2.org/jira/browse/TOOLS-2161 
> 
> Thanks and Regards,
> Harshana
> 
> 
> On Tue, Dec 3, 2013 at 1:39 PM, Samisa Abeysinghe  wrote:
> In this model, is it correct to import a connector for every "project" that I 
> want to use connectors for? 
> 
> Can I not import per DevS instance? Say I have multiple projects, why do I 
> have to import project wise? 
> 
> 
> Thanks,
> Samisa...
> 
> 
> 
> Samisa Abeysinghe
> 
> Vice President Training 
> 
> WSO2 Inc. 
> http://wso2.com
> 
> 
> 
> 
> On Tue, Dec 3, 2013 at 1:31 PM, Samisa Abeysinghe  wrote:
> Created a Jira https://wso2.org/jira/browse/DOCUMENTATION-495
> 
> Thanks,
> Samisa...
> 
> 
> 
> Samisa Abeysinghe
> 
> Vice President Training 
> 
> WSO2 Inc. 
> http://wso2.com
> 
> 
> 
> 
> On Tue, Dec 3, 2013 at 12:59 PM, Asanka Sanjeewa  wrote:
> Hi,
> 
> Seems like Developer Studio 3.3.0 Documentations has not been updated with 
> tooling aspect in connectors. 
> 
> Viraj's blog at [1] will helpful in creating connector contents in Developer 
> Studio 3.3.0 document. 
> 
> [1] 
> http://sumuditha-viraj.blogspot.com/2013/10/how-to-use-wso2-developer-studio-cloud.html
> 
> Thanks and Regards,
> AsankaS.
> 
> 
> On Tue, Dec 3, 2013 at 12:56 PM, Isuru Udana  wrote:
> Hi Samisa,
> 
> You can right-click on the ESB project and then select "Import Cloud 
> Connector". 
> There is a blog post[1] written by Viraj on this but I am not sure whether 
> this is documented in the wiki. 
> 
> [1] 
> http://sumuditha-viraj.blogspot.com/2013/10/how-to-use-wso2-developer-studio-cloud.html
>  
> 
> Thanks.
> 
> 
> On Tue, Dec 3, 2013 at 12:42 PM, Samisa Abeysinghe  wrote:
> For $subject, do I have to drop connectors to DevS? If yes, where is the doc 
> on that? 
> 
> 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
> 
> 
> 
> 
> -- 
> 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
> 
> 
> 
> -- 
> Asanka Sanjeewa
> Senior Software Engineer
> Mobile: +94772532924
> WSO2 Inc. http://wso2.com/
> Blog: http://asanka-tech-blog.blogspot.com/

Re: [Dev] How do I get connectors to work with DevS?

[Harshana Martin]

HI Isabelle,

Yes.. Even-though we moved the connector maintenance over to global across
workspace, we maintain the configurations (the local entry with connector
specific metadata) as we used to do previously within the project itself.

Thus you can achieve the aforesaid use case without any issue with the
modifications.

Thanks and Regards,
Harshana


On Tue, Dec 10, 2013 at 11:14 PM, Isabelle Mauny  wrote:

> But I am still able to have different configs / connector right ? for
> example use one set of credentials for connector1 in proxy1 and another set
> of credentials for connector1 in proxy2 ..
>
> Thanks.
>  __
>
>
> *Isabelle Mauny *Director, Product Management; WSO2, Inc.;
> http://wso2.com/
>
> On Dec 7, 2013, at 7:14 AM, Asanka Sanjeewa  wrote:
>
> Hi,
>
> Imported connectors maintained within the Workspace improvement [1] also
> completed and it will be available in Developer Studio 3.3.0 Alpha 4
> release.
>
> With this improvement all the imported connectors will be visible to all
> the ESB Configuration Projects within the Workspace (in previous model they
> were specific only to the particular project into which connectors were
> imported).
>
> [1] https://wso2.org/jira/browse/TOOLS-2161
>
> Thanks and Regards,
> AsankaS.
>
>
> On Sat, Dec 7, 2013 at 11:17 AM, Samisa Abeysinghe wrote:
>
>> Excellent!
>>
>> Thanks,
>> Samisa...
>>
>>
>> Samisa Abeysinghe
>>
>> Vice President Training
>>
>> WSO2 Inc.
>> http://wso2.com
>>
>>
>>
>> On Sat, Dec 7, 2013 at 9:31 AM, Asanka Sanjeewa  wrote:
>>
>>> Hi Samisa,
>>>
>>> Arranging connector operations in alphabetical order [1] related changes
>>> already done and this will be available in Developer Studio Alpha 4
>>> release.
>>>
>>> [1] https://wso2.org/jira/browse/TOOLS-2159
>>>
>>> Thanks and Regards,
>>> AsankaS.
>>>
>>>
>>> On Sat, Dec 7, 2013 at 6:11 AM, Samisa Abeysinghe wrote:
>>>
 That is great. Thanks. The other improvement that I think is a must is
 the alphabetical ordering of the connector operations. Are we looking into
 that too? It would be great to have that fix too before we ship, as
 otherwise, it is hard to locate the proper operations.


 Thanks,
 Samisa...


 Samisa Abeysinghe

 Vice President Training

 WSO2 Inc.
 http://wso2.com



 On Fri, Dec 6, 2013 at 5:11 PM, Harshana Martin wrote:

> Hi Samisa,
>
> Asanka has accommodated this change now. We will ship the Alpha 4
> release with this fix.
>
> Thanks and Regards,
> Harshana
>
>
> On Wed, Dec 4, 2013 at 12:04 PM, Samisa Abeysinghe wrote:
>
>>
>>
>> On Wed, Dec 4, 2013 at 11:02 AM, Harshana Martin 
>> wrote:
>>
>>> Hi Samisa,
>>>
>>> The current design of DevS connector import is incorrect!.
>>>
>>>  It does not make sense user importing same connector over and over
>>> again just because the configurations are in 2 different ESB config
>>> projects.
>>>
>>> The connectors should be imported and maintained per Workspace not
>>> per Project.
>>>
>>
>> +1
>>
>> That is exactly what I meant too!
>>
>>
>>> So we will make this design change [1].
>>>
>>> [1]. https://wso2.org/jira/browse/TOOLS-2161
>>>
>>> Thanks and Regards,
>>> Harshana
>>>
>>>
>>> On Tue, Dec 3, 2013 at 1:39 PM, Samisa Abeysinghe 
>>> wrote:
>>>
 In this model, is it correct to import a connector for every
 "project" that I want to use connectors for?

 Can I not import per DevS instance? Say I have multiple projects,
 why do I have to import project wise?


 Thanks,
 Samisa...


 Samisa Abeysinghe

 Vice President Training

 WSO2 Inc.
 http://wso2.com



 On Tue, Dec 3, 2013 at 1:31 PM, Samisa Abeysinghe 
 wrote:

> Created a Jira https://wso2.org/jira/browse/DOCUMENTATION-495
>
>  Thanks,
> Samisa...
>
>
> Samisa Abeysinghe
>
> Vice President Training
>
> WSO2 Inc.
> http://wso2.com
>
>
>
> On Tue, Dec 3, 2013 at 12:59 PM, Asanka Sanjeewa  > wrote:
>
>> Hi,
>>
>> Seems like Developer Studio 3.3.0 Documentations has not been
>> updated with tooling aspect in connectors.
>>
>> Viraj's blog at [1] will helpful in creating connector contents
>> in Developer Studio 3.3.0 document.
>>
>> [1]
>> http://sumuditha-viraj.blogspot.com/2013/10/how-to-use-wso2-developer-studio-cloud.html
>>
>> Thanks and Regards,
>> AsankaS.
>>
>>
>> On Tue, Dec 3, 2013 at 12:56 PM, Isuru 

Re: [Dev] [ESB] Creating a secure client using axiom

[Maduranga Siriwardena]

Hi,
I have already added that to Java Build Path of the eclipse project.


On Tue, Dec 10, 2013 at 9:53 PM, Dulanja Liyanage  wrote:

> Hi,
>
> You need to have bouncycastle jar in your classpath [1].
>
> You can find one at ESB_HOME/repository/axis2/client/lib/bcprov-jdk15.jar.
>
> [1]
> http://blog.rampartfaq.com/2009/08/orgapachewssecuritywssecurityexception.html
>
> Thanks
> Dulanja
>
>
> On Tue, Dec 10, 2013 at 12:57 PM, Maduranga Siriwardena <
> madura...@wso2.com> wrote:
>
>> I added the relevant path to the client repo and the axis2.xml and I
>> added all the jars mentioned in the build file of the sample client in ESB
>> to  the project I was able to engage the rampart module. Now I get the
>> bellow error stack. It is encryption error. Can someone figure out how to
>> fix the problem
>>
>> org.apache.axis2.AxisFault: Error in encryption
>> at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:76)
>> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>>  at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:426)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:398)
>>  at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
>> at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>>  at
>> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:554)
>> at
>> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:530)
>>  at client.OrderProcessClient.createOrder(OrderProcessClient.java:231)
>> at client.OrderProcessClient.main(OrderProcessClient.java:57)
>> Caused by: org.apache.rampart.RampartException: Error in encryption
>> at
>> org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:612)
>>  at
>> org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:97)
>> at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
>>  at
>> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
>> ... 11 more
>> Caused by: org.apache.ws.security.WSSecurityException: An unsupported
>> signature or encryption algorithm was used (unsupported key transport
>> encryption algorithm: No such algorithm:
>> http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p); nested exception is:
>>  java.security.NoSuchAlgorithmException: Cannot find any provider
>> supporting RSA/ECB/OAEPPadding
>> at
>> org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:785)
>>  at
>> org.apache.ws.security.message.WSSecEncryptedKey.prepareInternal(WSSecEncryptedKey.java:205)
>> at
>> org.apache.ws.security.message.WSSecEncrypt.prepare(WSSecEncrypt.java:259)
>>  at
>> org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:578)
>> ... 14 more
>> Caused by: java.security.NoSuchAlgorithmException: Cannot find any
>> provider supporting RSA/ECB/OAEPPadding
>> at javax.crypto.Cipher.getInstance(Cipher.java:524)
>>  at
>> org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:777)
>> ... 17 more
>>
>>
>> On Fri, Dec 6, 2013 at 8:07 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>>
>>>
>>>
>>> On Fri, Dec 6, 2013 at 4:50 PM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Path to what file should I add to classpath? Isn't that enough to add
 bellow lines?

 ConfigurationContext configContext =   ConfigurationContextFactory.
 createConfigurationContextFromFileSystem("CARBON_HOME\\
 repository\\deployment\\client", "CARBON_HOME\\repository\\
 conf\\axis2_client.xml");

>>>
>>> The above should be enough as long as you have the rampart module under
>>> client_repo_path/modules directory and rampart libraries
>>> (rampart-core_1.6.1.wso2v12.jar, rampart-policy_1.6.1.wso2v12.jar,
>>> rampart-trust_1.6.1.wso2v12.jar) in your classpath. The "classpath" is the
>>> place you tell jvm to look for required classes for you client application.
>>>
>>> You are also giving the axis2.xml as well to create configuration
>>> context. This is where you get the error java.lang.ClassNotFoundException:
>>> org.apache.axis2.transport.tcp.TCPTransportSender. This is because when the
>>> creating the ConfigrationContext it will initialize the axis config using
>>> the given axis2.xml. And those missing classes reside in some other axis2
>>> libraries, which are not yet available your classpath. Either you can add
>>> that lib (axis2_1.6.1.wso2v10.jar) to you classpath or try the following.
>>>
>>> In a normal case you will not need to provide an axis2.xml when creating
>>> ConfigrationContext. So first try giving it as null and only give the repo
>>> location.
>>> Ex:
>>> ConfigurationContext configContext =
>>> Configura

Re: [Dev] Jaggery - How to process a SOAP request

[Nuwan Dias]

Hi Madhuka,

Thanks for the info.

Thanks,
NuwanD.


On Tue, Dec 10, 2013 at 10:09 PM, Madhuka Udantha  wrote:

> Hi, Nuwan
>
> Yap, trying is correct, Jaggery Web hostobject had bug regard
> to 'request.getContent()' and it is be fixed in github master.
> Thinking you try some old jaggery version.
>
> Here I will attaching patch (0.9.0.ALPHA4_wso2v1) for you and sample
> jaggery file for you to test.
>
>
> On Tue, Dec 10, 2013 at 8:30 PM, Nuwan Dias  wrote:
>
>> Hi,
>>
>> I have a restful jaggery endpoint and I now want to make this serve SOAP
>> requests as well. My idea is to look at the Content-Type header and
>> determine whether the request is REST or SOAP.
>>
>> I need to know how I can process a SOAP request from jaggery. When I try
>> 'request.getContent()', it gives me a null value.
>>
> Yap, it was bug in jaggery.
> It is fixed. Try this and let us know.
>
> Thanks
>
>> Is there a way to process a SOAP Body from jaggery?
>>
>> Thanks,
>> NuwanD.
>>
>> --
>> Nuwan Dias
>>
>> Senior Software Engineer - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> *Madhuka* Udantha
> Senior Software Engineer
> Development Technologies
> WSO2 Inc. : http://wso2.com
>
> *Mobile*: +94774066336
> *Blog*: http://madhukaudantha.blogspot.com/
>



-- 
Nuwan Dias

Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] OAuthServerConfiguration Error when instantiating the TokenPersistencePreprocessor

[Dinusha Senanayaka]

Hi Johan,

We encountered ClassNotFoundException when generating the user tokens with
the latest API-Manager nightly build pack. Seems like
TokenPersistencePreprocessor class has been re-factored as
'DefaultPersistenceProcessor'. Issue got resolved once we changed the
 defined in identity.xml as '
org.wso2.carbon.identity.oauth.tokenprocessor.DefaultPersistenceProcessor'.
Could you confirm is this the correct fix ?

[2013-12-11 09:38:02,974] ERROR - OAuthServerConfiguration Error when
instantiating the TokenPersistencePreprocessor :
org.wso2.carbon.identity.oauth.tokenprocessor.PlainTextProcessor.
Defaulting to PlainTextProcessor
java.lang.ClassNotFoundException:
org.wso2.carbon.identity.oauth.tokenprocessor.PlainTextProcessor
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at
org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.getPersistenceProcessor(OAuthServerConfiguration.java:474)
at
org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.(TokenMgtDAO.java:54)
at
org.wso2.carbon.identity.oauth2.token.handlers.grant.AbstractAuthorizationGrantHandler.init(AbstractAuthorizationGrantHandler.java:59)
at
org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.getSupportedGrantTypes(OAuthServerConfiguration.java:327)
at
org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.(AccessTokenIssuer.java:75)
at
org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.getInstance(AccessTokenIssuer.java:66)
at
org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:171)
at
org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:238)
at
org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:119)


Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Senior Software Engineer
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] OAuthServerConfiguration Error when instantiating the TokenPersistencePreprocessor

[Sumedha Rubasinghe]

On Wed, Dec 11, 2013 at 10:05 AM, Dinusha Senanayaka wrote:

> Hi Johan,
>
Johann !!!


>
> We encountered ClassNotFoundException when generating the user tokens with
> the latest API-Manager nightly build pack. Seems like
> TokenPersistencePreprocessor class has been re-factored as
> 'DefaultPersistenceProcessor'. Issue got resolved once we changed the
>  defined in identity.xml as '
> org.wso2.carbon.identity.oauth.tokenprocessor.DefaultPersistenceProcessor'.
> Could you confirm is this the correct fix ?
>
> [2013-12-11 09:38:02,974] ERROR - OAuthServerConfiguration Error when
> instantiating the TokenPersistencePreprocessor :
> org.wso2.carbon.identity.oauth.tokenprocessor.PlainTextProcessor.
> Defaulting to PlainTextProcessor
> java.lang.ClassNotFoundException:
> org.wso2.carbon.identity.oauth.tokenprocessor.PlainTextProcessor
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> at
> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.getPersistenceProcessor(OAuthServerConfiguration.java:474)
> at
> org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.(TokenMgtDAO.java:54)
> at
> org.wso2.carbon.identity.oauth2.token.handlers.grant.AbstractAuthorizationGrantHandler.init(AbstractAuthorizationGrantHandler.java:59)
> at
> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.getSupportedGrantTypes(OAuthServerConfiguration.java:327)
> at
> org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.(AccessTokenIssuer.java:75)
> at
> org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.getInstance(AccessTokenIssuer.java:66)
> at
> org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:171)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:238)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:119)
>
>
> Regards,
> Dinusha.
>
> --
> Dinusha Dilrukshi
> Senior Software Engineer
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Exception occurs when running ESB sample 200

[Sajith Ravindra]

Hi,

I'm a new joinee whose under going the training. I'm trying to run sample
200 of ESB (
http://docs.wso2.org/display/ESB480/Sample+200%3A+Using+WS-Security+with+policy+attachments+for+proxy+services
)
When i'm running the client of  it gives an  exception with following stack
trace.

 [java] Using WS-Security
 [java] org.apache.axis2.AxisFault: Error in encryption
 [java] at org.apache.rampart.handler.
RampartSender.invoke(RampartSender.java:76)
 [java] at
org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
 [java] at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
 [java] at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
 [java] at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:426)
 [java] at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
 [java] at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
 [java] at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
 [java] at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:554)
 [java] at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:530)
 [java] at samples.userguide.StockQuoteClient.executeClient(Unknown
Source)
 [java] at samples.userguide.StockQuoteClient.main(Unknown Source)
 [java] Caused by: org.apache.rampart.RampartException: Error in
encryption
 [java] at
org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:612)
 [java] at
org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:97)
 [java] at
org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
 [java] at
org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
 [java] ... 11 more
 [java] Caused by: org.apache.ws.security.WSSecurityException: An
unsupported signature or encryption algorithm was used (unsupported key
transport encryption algorithm: No such algorithm:
http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p); nested exception is:
 [java] java.security.NoSuchAlgorithmException: Cannot find any
provider supporting RSA/ECB/OAEPPadding
 [java] at
org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:785)
 [java] at
org.apache.ws.security.message.WSSecEncryptedKey.prepareInternal(WSSecEncryptedKey.java:205)
 [java] at
org.apache.ws.security.message.WSSecEncrypt.prepare(WSSecEncrypt.java:259)
 [java] at
org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:578)
 [java] ... 14 more
 [java] Caused by: java.security.NoSuchAlgorithmException: Cannot find
any provider supporting RSA/ECB/OAEPPadding
 [java] at javax.crypto.Cipher.getInstance(DashoA13*..)
 [java] at
org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:777)
 [java] ... 17 more

I tired what's being explain in
http://blog.rampartfaq.com/2009/08/faq-001-javasecurityinvalidkeyexception.htmlbut
it didn't work.

Can someone please explain the cause of this problem
-- 
Thanks
*,Sajith Ravindra*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 77 2273550

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

Re: [Dev] Exception occurs when running ESB sample 200

[Malaka Silva]

Usually this exception comes when BouncyCastle jar is not in the classpath.
(bcprov-jdk15.jar)

By default the BouncyCastle jar file is in
ESB_HOME/repository/axis2/client/lib folder. But when it is their, looks
like that file is not loaded in to axis2Client. But when I copy the
BouncyCastle jar file into ESB_HOME/repository/components/plugins folder,
issue get resolved.

The issue is resolved. However I am not sure whether this is the correct
resolution for this issue?

Best Regards,
Malaka



On Wed, Dec 11, 2013 at 11:06 AM, Sajith Ravindra  wrote:

> Hi,
>
> I'm a new joinee whose under going the training. I'm trying to run sample
> 200 of ESB (
> http://docs.wso2.org/display/ESB480/Sample+200%3A+Using+WS-Security+with+policy+attachments+for+proxy+services
> )
> When i'm running the client of  it gives an  exception with following
> stack trace.
>
>  [java] Using WS-Security
>  [java] org.apache.axis2.AxisFault: Error in encryption
>  [java] at org.apache.rampart.handler.
> RampartSender.invoke(RampartSender.java:76)
>  [java] at
> org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>  [java] at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>  [java] at
> org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>  [java] at
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:426)
>  [java] at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>  [java] at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>  [java] at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>  [java] at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:554)
>  [java] at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:530)
>  [java] at
> samples.userguide.StockQuoteClient.executeClient(Unknown Source)
>  [java] at samples.userguide.StockQuoteClient.main(Unknown Source)
>  [java] Caused by: org.apache.rampart.RampartException: Error in
> encryption
>  [java] at
> org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:612)
>  [java] at
> org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:97)
>  [java] at
> org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
>  [java] at
> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
>  [java] ... 11 more
>  [java] Caused by: org.apache.ws.security.WSSecurityException: An
> unsupported signature or encryption algorithm was used (unsupported key
> transport encryption algorithm: No such algorithm:
> http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p); nested exception is:
>  [java] java.security.NoSuchAlgorithmException: Cannot find any
> provider supporting RSA/ECB/OAEPPadding
>  [java] at
> org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:785)
>  [java] at
> org.apache.ws.security.message.WSSecEncryptedKey.prepareInternal(WSSecEncryptedKey.java:205)
>  [java] at
> org.apache.ws.security.message.WSSecEncrypt.prepare(WSSecEncrypt.java:259)
>  [java] at
> org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:578)
>  [java] ... 14 more
>  [java] Caused by: java.security.NoSuchAlgorithmException: Cannot find
> any provider supporting RSA/ECB/OAEPPadding
>  [java] at javax.crypto.Cipher.getInstance(DashoA13*..)
>  [java] at
> org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:777)
>  [java] ... 17 more
>
> I tired what's being explain in
> http://blog.rampartfaq.com/2009/08/faq-001-javasecurityinvalidkeyexception.htmlbut
>  it didn't work.
>
> Can someone please explain the cause of this problem
> --
> Thanks
> *,Sajith Ravindra*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 2273550
>  
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

Re: [Dev] [ESB] Creating a secure client using axiom

[Dulanja Liyanage]

Hi, could you please try running the program outside of Eclipse by
explicitly giving the classpath?


On Wed, Dec 11, 2013 at 9:00 AM, Maduranga Siriwardena
wrote:

> Hi,
> I have already added that to Java Build Path of the eclipse project.
>
>
> On Tue, Dec 10, 2013 at 9:53 PM, Dulanja Liyanage wrote:
>
>> Hi,
>>
>> You need to have bouncycastle jar in your classpath [1].
>>
>> You can find one at ESB_HOME/repository/axis2/client/lib/bcprov-jdk15.jar.
>>
>> [1]
>> http://blog.rampartfaq.com/2009/08/orgapachewssecuritywssecurityexception.html
>>
>> Thanks
>> Dulanja
>>
>>
>> On Tue, Dec 10, 2013 at 12:57 PM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> I added the relevant path to the client repo and the axis2.xml and I
>>> added all the jars mentioned in the build file of the sample client in ESB
>>> to  the project I was able to engage the rampart module. Now I get the
>>> bellow error stack. It is encryption error. Can someone figure out how to
>>> fix the problem
>>>
>>> org.apache.axis2.AxisFault: Error in encryption
>>> at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:76)
>>> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>>>  at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>>  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:426)
>>> at
>>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:398)
>>>  at
>>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
>>> at
>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>>>  at
>>> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:554)
>>> at
>>> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:530)
>>>  at client.OrderProcessClient.createOrder(OrderProcessClient.java:231)
>>> at client.OrderProcessClient.main(OrderProcessClient.java:57)
>>> Caused by: org.apache.rampart.RampartException: Error in encryption
>>> at
>>> org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:612)
>>>  at
>>> org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:97)
>>> at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
>>>  at
>>> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
>>> ... 11 more
>>> Caused by: org.apache.ws.security.WSSecurityException: An unsupported
>>> signature or encryption algorithm was used (unsupported key transport
>>> encryption algorithm: No such algorithm:
>>> http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p); nested exception is:
>>>  java.security.NoSuchAlgorithmException: Cannot find any provider
>>> supporting RSA/ECB/OAEPPadding
>>> at
>>> org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:785)
>>>  at
>>> org.apache.ws.security.message.WSSecEncryptedKey.prepareInternal(WSSecEncryptedKey.java:205)
>>> at
>>> org.apache.ws.security.message.WSSecEncrypt.prepare(WSSecEncrypt.java:259)
>>>  at
>>> org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:578)
>>> ... 14 more
>>> Caused by: java.security.NoSuchAlgorithmException: Cannot find any
>>> provider supporting RSA/ECB/OAEPPadding
>>> at javax.crypto.Cipher.getInstance(Cipher.java:524)
>>>  at
>>> org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:777)
>>> ... 17 more
>>>
>>>
>>> On Fri, Dec 6, 2013 at 8:07 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>



 On Fri, Dec 6, 2013 at 4:50 PM, Maduranga Siriwardena <
 madura...@wso2.com> wrote:

> Path to what file should I add to classpath? Isn't that enough to add
> bellow lines?
>
> ConfigurationContext configContext =   ConfigurationContextFactory.
> createConfigurationContextFromFileSystem("CARBON_HOME\\
> repository\\deployment\\client", "CARBON_HOME\\repository\\
> conf\\axis2_client.xml");
>

 The above should be enough as long as you have the rampart module under
 client_repo_path/modules directory and rampart libraries
 (rampart-core_1.6.1.wso2v12.jar, rampart-policy_1.6.1.wso2v12.jar,
 rampart-trust_1.6.1.wso2v12.jar) in your classpath. The "classpath" is the
 place you tell jvm to look for required classes for you client application.

 You are also giving the axis2.xml as well to create configuration
 context. This is where you get the error java.lang.ClassNotFoundException:
 org.apache.axis2.transport.tcp.TCPTransportSender. This is because when the
 creating the ConfigrationContext it will initialize the axis config using
 the given axis2.xml. And those missing classes reside in some other axis2
 libraries, which are not yet available your classpath. Either you can add
 that lib (axis2_1.6.1.wso2v10.jar)

Re: [Dev] Exception occurs when running ESB sample 200

[Sajith Ravindra]

Hi Malaka,

It fixed the issue. Thank you very much for the help.



On Wed, Dec 11, 2013 at 11:22 AM, Malaka Silva  wrote:

> Usually this exception comes when BouncyCastle jar is not in the
> classpath. (bcprov-jdk15.jar)
>
> By default the BouncyCastle jar file is in
> ESB_HOME/repository/axis2/client/lib folder. But when it is their, looks
> like that file is not loaded in to axis2Client. But when I copy the
> BouncyCastle jar file into ESB_HOME/repository/components/plugins folder,
> issue get resolved.
>
> The issue is resolved. However I am not sure whether this is the correct
> resolution for this issue?
>
> Best Regards,
> Malaka
>
>
>
> On Wed, Dec 11, 2013 at 11:06 AM, Sajith Ravindra wrote:
>
>> Hi,
>>
>> I'm a new joinee whose under going the training. I'm trying to run sample
>> 200 of ESB (
>> http://docs.wso2.org/display/ESB480/Sample+200%3A+Using+WS-Security+with+policy+attachments+for+proxy+services
>> )
>> When i'm running the client of  it gives an  exception with following
>> stack trace.
>>
>>  [java] Using WS-Security
>>  [java] org.apache.axis2.AxisFault: Error in encryption
>>  [java] at org.apache.rampart.handler.
>> RampartSender.invoke(RampartSender.java:76)
>>  [java] at
>> org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>>  [java] at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>>  [java] at
>> org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>  [java] at
>> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:426)
>>  [java] at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>>  [java] at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>>  [java] at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>>  [java] at
>> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:554)
>>  [java] at
>> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:530)
>>  [java] at
>> samples.userguide.StockQuoteClient.executeClient(Unknown Source)
>>  [java] at samples.userguide.StockQuoteClient.main(Unknown Source)
>>  [java] Caused by: org.apache.rampart.RampartException: Error in
>> encryption
>>  [java] at
>> org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:612)
>>  [java] at
>> org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:97)
>>  [java] at
>> org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
>>  [java] at
>> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
>>  [java] ... 11 more
>>  [java] Caused by: org.apache.ws.security.WSSecurityException: An
>> unsupported signature or encryption algorithm was used (unsupported key
>> transport encryption algorithm: No such algorithm:
>> http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p); nested exception is:
>>  [java] java.security.NoSuchAlgorithmException: Cannot find any
>> provider supporting RSA/ECB/OAEPPadding
>>  [java] at
>> org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:785)
>>  [java] at
>> org.apache.ws.security.message.WSSecEncryptedKey.prepareInternal(WSSecEncryptedKey.java:205)
>>  [java] at
>> org.apache.ws.security.message.WSSecEncrypt.prepare(WSSecEncrypt.java:259)
>>  [java] at
>> org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:578)
>>  [java] ... 14 more
>>  [java] Caused by: java.security.NoSuchAlgorithmException: Cannot
>> find any provider supporting RSA/ECB/OAEPPadding
>>  [java] at javax.crypto.Cipher.getInstance(DashoA13*..)
>>  [java] at
>> org.apache.ws.security.util.WSSecurityUtil.getCipherInstance(WSSecurityUtil.java:777)
>>  [java] ... 17 more
>>
>> I tired what's being explain in
>> http://blog.rampartfaq.com/2009/08/faq-001-javasecurityinvalidkeyexception.htmlbut
>>  it didn't work.
>>
>> Can someone please explain the cause of this problem
>> --
>> Thanks
>> *,Sajith Ravindra*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 77 2273550
>>  
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> 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 -C

[Dev] API Manager-1.6.0 nightly build pack - 10/12/2013

[Dinusha Senanayaka]

Hi All,

Please find the $subject in [1].

[1]. http://builder1.us1.wso2.org/~apim/10-12-2013/wso2am-1.6.0.zip

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Senior Software Engineer
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] OAuthServerConfiguration Error when instantiating the TokenPersistencePreprocessor

[Johann Nallathamby]

This is the correct fix.


On Wed, Dec 11, 2013 at 10:05 AM, Dinusha Senanayaka wrote:

> Hi Johan,
>
> We encountered ClassNotFoundException when generating the user tokens with
> the latest API-Manager nightly build pack. Seems like
> TokenPersistencePreprocessor class has been re-factored as
> 'DefaultPersistenceProcessor'. Issue got resolved once we changed the
>  defined in identity.xml as '
> org.wso2.carbon.identity.oauth.tokenprocessor.DefaultPersistenceProcessor'.
> Could you confirm is this the correct fix ?
>
> [2013-12-11 09:38:02,974] ERROR - OAuthServerConfiguration Error when
> instantiating the TokenPersistencePreprocessor :
> org.wso2.carbon.identity.oauth.tokenprocessor.PlainTextProcessor.
> Defaulting to PlainTextProcessor
> java.lang.ClassNotFoundException:
> org.wso2.carbon.identity.oauth.tokenprocessor.PlainTextProcessor
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> at
> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.getPersistenceProcessor(OAuthServerConfiguration.java:474)
> at
> org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.(TokenMgtDAO.java:54)
> at
> org.wso2.carbon.identity.oauth2.token.handlers.grant.AbstractAuthorizationGrantHandler.init(AbstractAuthorizationGrantHandler.java:59)
> at
> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.getSupportedGrantTypes(OAuthServerConfiguration.java:327)
> at
> org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.(AccessTokenIssuer.java:75)
> at
> org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.getInstance(AccessTokenIssuer.java:66)
> at
> org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:171)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:238)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:119)
>
>
> Regards,
> Dinusha.
>
> --
> Dinusha Dilrukshi
> Senior Software Engineer
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Senior Software Engineer
Integration Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Chunk-06 build failure while building features

[Dinusha Senanayaka]

Hi,

Seems org.wso2.carbon:org.wso2.carbon.identity.entitlement.ui/4.2.1 has not
added to chunk-06/component pom.

[ERROR] Failed to execute goal on project
org.wso2.carbon.identity.xacml.ui.feature: Could not resolve dependencies
for project
org.wso2.carbon:org.wso2.carbon.identity.xacml.ui.feature:pom:4.2.1: Could
not find artifact
org.wso2.carbon:org.wso2.carbon.identity.entitlement.ui:jar:4.2.1 in
wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
[Help 1]

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Senior Software Engineer
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk-06 build failure while building features

[Ishara Karunarathna]

Hi,

Fixed in chink component pom

Thanks



On Wed, Dec 11, 2013 at 12:21 PM, Dinusha Senanayaka wrote:

> Hi,
>
> Seems org.wso2.carbon:org.wso2.carbon.identity.entitlement.ui/4.2.1 has
> not added to chunk-06/component pom.
>
> [ERROR] Failed to execute goal on project
> org.wso2.carbon.identity.xacml.ui.feature: Could not resolve dependencies
> for project
> org.wso2.carbon:org.wso2.carbon.identity.xacml.ui.feature:pom:4.2.1: Could
> not find artifact
> org.wso2.carbon:org.wso2.carbon.identity.entitlement.ui:jar:4.2.1 in
> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
> [Help 1]
>
> Regards,
> Dinusha.
>
> --
> Dinusha Dilrukshi
> Senior Software Engineer
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Karunarathna
Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile: +94
718211678
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev