Re: [Dev] Deploying a custom Axis2 handler in ELB
Okay so the issue was the use of the package name
*org.apache.axis2.handlers* for my Axis2 handler, apparently using this
package name can lead to conflicts. I used a different package name
*org.wso2.custom.handlers* as suggested by Isuru and this solved the issue,
Thanks Isuru.
On 5 September 2014 10:45, Uvindra Dias Jayasinha uvin...@wso2.com wrote:
Thanks Isuru,
okay I've made sure that the proxy handler is only in the lib folder,
uvindra@uvindra-ThinkPad-T530:~/SkyTV_Dev_Service/handler_elb_esb_cluster/ELB_1$
*find -iname EchoProxyHandler**
./repository/components/lib/EchoProxyHandler_1.0.0.jar
no other entries exist in the pack. But still I get the same exception
when I start,
TID: [0] [ELB] [2014-09-05 10:39:31,009] FATAL
{org.wso2.carbon.core.init.CarbonServerManager} - WSO2 Carbon
initialization Failed {org.wso2.carbon.core.init.CarbonServerManager}
org.apache.axis2.AxisFault: Exception occured while loading the Axis
configuration from
/home/uvindra/SkyTV_Dev_Service/handler_elb_esb_cluster/ELB_1/repository/conf/axis2/axis2.xml
at
org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:190)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at
org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
at
org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
at
org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
at
org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.
Hi Chathurika, There is a new resource migration-1.7.0_to_1.7.1 to modify the database. it creates the related column SUBS_CREATE_STATE (which is mentioned in the error log). Did you use that one? I think this might be the problem. On Fri, Sep 5, 2014 at 11:18 AM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All The migration cannot be tested in the 04/09/2014 due to the following issue, since none of the migrated APIs can be retrieved. Testing is currently blocking. https://wso2.org/jira/browse/APIMANAGER-2799 Thank You Erandi On Mon, Aug 18, 2014 at 1:45 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila I have reopened the issue APIMANAGER-2662 because this issue should be fixed and shipped in a newer revision or as a patch itself. Thank You On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake chami...@wso2.com wrote: I'll create a small java client to modify the apis in the synapse-config/default/api folder. Thanks, Chamila. On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias nuw...@wso2.com wrote: We should be able to write a simple script or java client to do this right? Thanks, NuwanD. On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila As i understand regarding APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 following are the two workarounds. 1. As mentioned in the readme.txt., edit *each* api xml in the APIM_1.7.0/repository/deployment/server/synapse-config/default/api directory. Replace handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/ with handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler 2. Manually go to implement tab in the edit mode of *each* of the APIs and click manage If a customer wants to migrate hundreds of APIs, is it a feasible solution from the customer's perspective? Ideally when a customer migrates from an older version, they should be able to work with their data as they worked before the migration. Since invoking an API is the core functionality of API Manager, is it really feasible in asking the customer to follow above 1st or 2nd method? From the customer/user perspective above given solution cannot be accepted. In my opinion this should be handled by our side without asking the customer/user to take extra effort in bringing his migrated data to work properly. Thank You Erandi On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, Issues mentioned in the previous mail are fixed in the latest 17/08/2014 pack[1]. There are some updates done to the migration tool readme.txt file as well. You can proceed with the migration testing. For the issue APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 please read the comments in the jira (these instructions are added to the readme.txt). [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/ Thanks, Chamila. On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As per the pack released on 05/08/2014 following is the status 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 - issue status - inprogress. This is the main scenario of the migration. Thus the fix for this is crucial to proceed with the proper user scenario based testing 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 - issue status - reopened. This issue corrupts the entire database. 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 - issue status - reopened. The resources added before the migration is not copied correctly 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 - issue status - reopened (due to APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot be verified until APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed. Since the above mentioned issues are blocking, the migration testing cannot be proceeded for the 05/08/2014 pack Thank You On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The ticket has been resolved, please continue with testing On 11 August 2014 12:49, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Seems the stack trace is different from what was originally reported for this ticket, can we have a closer look at this? Please ping me when you get back to your seat. Thanks On 11 August 2014 12:30, Chathurika De Silva chathuri...@wso2.com wrote: Hi We started to test the migration with the 05/08/2014 pack and APIMANAGER-2529 is reopened. This is currently blocking the testing Thank You On Tue, Aug 5, 2014 at 10:26 AM, Chalitha Waldeniyage chali...@wso2.com wrote: Hi, We have covered entire
Re: [Dev] {chunk-13 packs}
Hi Evanthika, DSS pack is also available now in the above location. Thanks On Fri, Sep 5, 2014 at 10:35 AM, Evanthika Amarasiri evanth...@wso2.com wrote: Thanks Ratha, Can we have a DSS pack as well? Regards, Evanthika On Fri, Sep 5, 2014 at 10:33 AM, Vijayaratha Vijayasingam rat...@wso2.com wrote: Hi Evanthika, Use this packs fro testing; https://svn.wso2.org/repos/wso2/scratch/chunk13-release/04-09-2014/ Thanks. -- -Ratha -- Best Regards.. Chanika Geeganage Software Engineer WSO2, Inc.; http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] chunk-13 packs 03/09/2014
Hi Evanthika, The DSS pack is committed to the same location Thanks On Fri, Sep 5, 2014 at 10:16 AM, Evanthika Amarasiri evanth...@wso2.com wrote: Hi Chanika, Can we get a DSS pack as well? We are planning to do a setup with API-M DSS. Regards, Evanthika On Wed, Sep 3, 2014 at 4:56 PM, Vijayaratha Vijayasingam rat...@wso2.com wrote: Hi all; Please find packs here https://svn.wso2.org/repos/wso2/scratch/chunk13-release/03-09-2014/ -- -Ratha -- Best Regards.. Chanika Geeganage Software Engineer WSO2, Inc.; http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] {chunk-13 packs}
Thanks Chanika Regards, Evanthika On Fri, Sep 5, 2014 at 12:01 PM, Chanika Geeganage chan...@wso2.com wrote: Hi Evanthika, DSS pack is also available now in the above location. Thanks On Fri, Sep 5, 2014 at 10:35 AM, Evanthika Amarasiri evanth...@wso2.com wrote: Thanks Ratha, Can we have a DSS pack as well? Regards, Evanthika On Fri, Sep 5, 2014 at 10:33 AM, Vijayaratha Vijayasingam rat...@wso2.com wrote: Hi Evanthika, Use this packs fro testing; https://svn.wso2.org/repos/wso2/scratch/chunk13-release/04-09-2014/ Thanks. -- -Ratha -- Best Regards.. Chanika Geeganage Software Engineer WSO2, Inc.; http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.
Hi Chamila I cannot find the mentioned resource in the 04/09/2014 pack. I followed the steps given in the README.txt to migrate the database. Thank You Erandi On Fri, Sep 5, 2014 at 11:57 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, There is a new resource migration-1.7.0_to_1.7.1 to modify the database. it creates the related column SUBS_CREATE_STATE (which is mentioned in the error log). Did you use that one? I think this might be the problem. On Fri, Sep 5, 2014 at 11:18 AM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All The migration cannot be tested in the 04/09/2014 due to the following issue, since none of the migrated APIs can be retrieved. Testing is currently blocking. https://wso2.org/jira/browse/APIMANAGER-2799 Thank You Erandi On Mon, Aug 18, 2014 at 1:45 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila I have reopened the issue APIMANAGER-2662 because this issue should be fixed and shipped in a newer revision or as a patch itself. Thank You On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake chami...@wso2.com wrote: I'll create a small java client to modify the apis in the synapse-config/default/api folder. Thanks, Chamila. On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias nuw...@wso2.com wrote: We should be able to write a simple script or java client to do this right? Thanks, NuwanD. On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila As i understand regarding APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 following are the two workarounds. 1. As mentioned in the readme.txt., edit *each* api xml in the APIM_1.7.0/repository/deployment/server/synapse-config/default/api directory. Replace handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/ with handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler 2. Manually go to implement tab in the edit mode of *each* of the APIs and click manage If a customer wants to migrate hundreds of APIs, is it a feasible solution from the customer's perspective? Ideally when a customer migrates from an older version, they should be able to work with their data as they worked before the migration. Since invoking an API is the core functionality of API Manager, is it really feasible in asking the customer to follow above 1st or 2nd method? From the customer/user perspective above given solution cannot be accepted. In my opinion this should be handled by our side without asking the customer/user to take extra effort in bringing his migrated data to work properly. Thank You Erandi On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, Issues mentioned in the previous mail are fixed in the latest 17/08/2014 pack[1]. There are some updates done to the migration tool readme.txt file as well. You can proceed with the migration testing. For the issue APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 please read the comments in the jira (these instructions are added to the readme.txt). [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/ Thanks, Chamila. On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As per the pack released on 05/08/2014 following is the status 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 - issue status - inprogress. This is the main scenario of the migration. Thus the fix for this is crucial to proceed with the proper user scenario based testing 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 - issue status - reopened. This issue corrupts the entire database. 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 - issue status - reopened. The resources added before the migration is not copied correctly 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 - issue status - reopened (due to APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot be verified until APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed. Since the above mentioned issues are blocking, the migration testing cannot be proceeded for the 05/08/2014 pack Thank You On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The ticket has been resolved, please continue with testing On 11 August 2014 12:49, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Seems the stack trace is different from what was originally reported for this ticket, can we have a closer look at this? Please ping me when you get back to your seat. Thanks On 11 August 2014 12:30, Chathurika De Silva chathuri...@wso2.com wrote: Hi
Re: [Dev] [APPFAC] Appfactory plugin build failures due to corrupted poms in nexus repo
Hi Rumesh, Still getting the old corrupted pom files from the above links. Thanks, Samith On Thu, Sep 4, 2014 at 9:44 AM, Rumesh Bandara rum...@wso2.com wrote: Uploaded the given pom. Please check now. Regards, Rumesh On Wed, Sep 3, 2014 at 3:05 PM, Samith Dassanayake sam...@wso2.com wrote: Hi Rumesh, Following pom file is also corrupted. I have attached the corrected pom file. Could you please commit it as well. wstx-asl-3.1.0: http://maven.wso2.org/nexus/content/groups/wso2-public/woodstox/wstx-asl/3.1.0/wstx-asl-3.1.0.pom Thanks, Samith. On Tue, Sep 2, 2014 at 10:55 AM, Rumesh Bandara rum...@wso2.com wrote: Hi Anuruddha, Please re-check after some time because there is an ongoing syncing process with maven. Thanks, Rumesh On Tue, Sep 2, 2014 at 10:43 AM, Anuruddha Premalal anurud...@wso2.com wrote: Hi Rumesh, I'm still getting the old pom files from the previous links. Regards, Anuruddha. On Tue, Sep 2, 2014 at 10:35 AM, Rumesh Bandara rum...@wso2.com wrote: Uploaded the given pom files. Please check now. Thanks, Rumesh On Wed, Aug 20, 2014 at 10:24 AM, Anuruddha Premalal anurud...@wso2.com wrote: Hi, We are facing build failures due to the following corrupted pom files. Can some authorized person commit the following corrected poms to wso2 nexus repo?. uddi4j : http://maven.wso2.org/nexus/content/groups/wso2-public/uddi/uddi4j/1.0.1/uddi4j-1.0.1.pom org.eclipse.core.runtime : http://maven.wso2.org/nexus/content/groups/wso2-public/org/eclipse/core/org.eclipse.core.runtime/3.5.0.v20090429-1800/org.eclipse.core.runtime-3.5.0.v20090429-1800.pom Thanks Regards, -- *Anuruddha Premalal* Software Eng. | WSO2 Inc. Mobile : +94710461070 Web site : www.regilandvalley.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Anuruddha Premalal* Software Eng. | WSO2 Inc. Mobile : +94710461070 Web site : www.regilandvalley.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards Samith Dassanayake Software Engineer, WSO2 Inc. -- Best Regards Samith Dassanayake Software Engineer, WSO2 Inc. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.
this can be found in the svn location[1] but is missing in the pack [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/apimgt/1.7.1/modules/distribution/resources/migration-1.7.0_to_1.7.1/ On Fri, Sep 5, 2014 at 12:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila I cannot find the mentioned resource in the 04/09/2014 pack. I followed the steps given in the README.txt to migrate the database. Thank You Erandi On Fri, Sep 5, 2014 at 11:57 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, There is a new resource migration-1.7.0_to_1.7.1 to modify the database. it creates the related column SUBS_CREATE_STATE (which is mentioned in the error log). Did you use that one? I think this might be the problem. On Fri, Sep 5, 2014 at 11:18 AM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All The migration cannot be tested in the 04/09/2014 due to the following issue, since none of the migrated APIs can be retrieved. Testing is currently blocking. https://wso2.org/jira/browse/APIMANAGER-2799 Thank You Erandi On Mon, Aug 18, 2014 at 1:45 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila I have reopened the issue APIMANAGER-2662 because this issue should be fixed and shipped in a newer revision or as a patch itself. Thank You On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake chami...@wso2.com wrote: I'll create a small java client to modify the apis in the synapse-config/default/api folder. Thanks, Chamila. On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias nuw...@wso2.com wrote: We should be able to write a simple script or java client to do this right? Thanks, NuwanD. On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila As i understand regarding APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 following are the two workarounds. 1. As mentioned in the readme.txt., edit *each* api xml in the APIM_1.7.0/repository/deployment/server/synapse-config/default/api directory. Replace handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/ with handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler 2. Manually go to implement tab in the edit mode of *each* of the APIs and click manage If a customer wants to migrate hundreds of APIs, is it a feasible solution from the customer's perspective? Ideally when a customer migrates from an older version, they should be able to work with their data as they worked before the migration. Since invoking an API is the core functionality of API Manager, is it really feasible in asking the customer to follow above 1st or 2nd method? From the customer/user perspective above given solution cannot be accepted. In my opinion this should be handled by our side without asking the customer/user to take extra effort in bringing his migrated data to work properly. Thank You Erandi On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, Issues mentioned in the previous mail are fixed in the latest 17/08/2014 pack[1]. There are some updates done to the migration tool readme.txt file as well. You can proceed with the migration testing. For the issue APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 please read the comments in the jira (these instructions are added to the readme.txt). [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/ Thanks, Chamila. On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As per the pack released on 05/08/2014 following is the status 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 - issue status - inprogress. This is the main scenario of the migration. Thus the fix for this is crucial to proceed with the proper user scenario based testing 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 - issue status - reopened. This issue corrupts the entire database. 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 - issue status - reopened. The resources added before the migration is not copied correctly 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 - issue status - reopened (due to APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot be verified until APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed. Since the above mentioned issues are blocking, the migration testing cannot be proceeded for the 05/08/2014 pack Thank You On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The ticket has been resolved, please continue with testing On 11 August 2014 12:49,
[Dev] Jenkins gives an error in Appfactory when deploying the built artifacts
Hi,
I have made changes in org.wso2.carbon.appfactory.deployers component which
is in the wso2as (used by jenkins) that it uses methods in
org.wso2.carbon.appfactory.s4.integration component which in wso2appfactory.
So I have put the org.wso2.carbon.appfactory.s4.integration bundle inside
the wso2as dropins. Additionally have put org.wso2.carbon.appfactory.core
and org.wso2.carbon.appfactory.common
into the dropins to resolve dependencies.
But when deploying an artifact it throws the following error[1]. What would
be the issue here?
[1] -
TID: [0] [AS] [2014-09-05 12:26:35,483] ERROR
{org.wso2.carbon.appfactory.deployers.AbstractDeployer} - Error when
calling deployLatestSuccessArtifact null
{org.wso2.carbon.appfactory.deployers.AbstractDeployer}
java.lang.NullPointerException
at
org.wso2.carbon.appfactory.deployers.AbstractStratosDeployer.addToGitRepo(AbstractStratosDeployer.java:102)
at
org.wso2.carbon.appfactory.deployers.AbstractStratosDeployer.deploy(AbstractStratosDeployer.java:60)
at
org.wso2.carbon.appfactory.deployers.AbstractDeployer.deployLatestSuccessArtifact(AbstractDeployer.java:100)
at
org.wso2.carbon.appfactory.jenkins.deploy.JenkinsArtifactDeployer.deployLatestSuccessArtifact(JenkinsArtifactDeployer.java:101)
at
org.wso2.carbon.appfactory.jenkins.artifact.storage.AppfactoryArtifactStoragePlugin.doDynamic(AppfactoryArtifactStoragePlugin.java:95)
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.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:370)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.
As we are shipping the final pack to the customer, any inclusions should be in the released pack. So until this is included in the pack itself, the migration cannot be tested and will remain in the status blocked. On Fri, Sep 5, 2014 at 12:35 PM, Chamila Adhikarinayake chami...@wso2.com wrote: this can be found in the svn location[1] but is missing in the pack [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/apimgt/1.7.1/modules/distribution/resources/migration-1.7.0_to_1.7.1/ On Fri, Sep 5, 2014 at 12:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila I cannot find the mentioned resource in the 04/09/2014 pack. I followed the steps given in the README.txt to migrate the database. Thank You Erandi On Fri, Sep 5, 2014 at 11:57 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, There is a new resource migration-1.7.0_to_1.7.1 to modify the database. it creates the related column SUBS_CREATE_STATE (which is mentioned in the error log). Did you use that one? I think this might be the problem. On Fri, Sep 5, 2014 at 11:18 AM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All The migration cannot be tested in the 04/09/2014 due to the following issue, since none of the migrated APIs can be retrieved. Testing is currently blocking. https://wso2.org/jira/browse/APIMANAGER-2799 Thank You Erandi On Mon, Aug 18, 2014 at 1:45 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila I have reopened the issue APIMANAGER-2662 because this issue should be fixed and shipped in a newer revision or as a patch itself. Thank You On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake chami...@wso2.com wrote: I'll create a small java client to modify the apis in the synapse-config/default/api folder. Thanks, Chamila. On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias nuw...@wso2.com wrote: We should be able to write a simple script or java client to do this right? Thanks, NuwanD. On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila As i understand regarding APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 following are the two workarounds. 1. As mentioned in the readme.txt., edit *each* api xml in the APIM_1.7.0/repository/deployment/server/synapse-config/default/api directory. Replace handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/ with handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler 2. Manually go to implement tab in the edit mode of *each* of the APIs and click manage If a customer wants to migrate hundreds of APIs, is it a feasible solution from the customer's perspective? Ideally when a customer migrates from an older version, they should be able to work with their data as they worked before the migration. Since invoking an API is the core functionality of API Manager, is it really feasible in asking the customer to follow above 1st or 2nd method? From the customer/user perspective above given solution cannot be accepted. In my opinion this should be handled by our side without asking the customer/user to take extra effort in bringing his migrated data to work properly. Thank You Erandi On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, Issues mentioned in the previous mail are fixed in the latest 17/08/2014 pack[1]. There are some updates done to the migration tool readme.txt file as well. You can proceed with the migration testing. For the issue APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 please read the comments in the jira (these instructions are added to the readme.txt). [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/ Thanks, Chamila. On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As per the pack released on 05/08/2014 following is the status 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 - issue status - inprogress. This is the main scenario of the migration. Thus the fix for this is crucial to proceed with the proper user scenario based testing 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 - issue status - reopened. This issue corrupts the entire database. 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 - issue status - reopened. The resources added before the migration is not copied correctly 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 - issue status - reopened (due to APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot be verified until APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed.
Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.
It will be included in the next pack. On Fri, Sep 5, 2014 at 12:39 PM, Chathurika De Silva chathuri...@wso2.com wrote: As we are shipping the final pack to the customer, any inclusions should be in the released pack. So until this is included in the pack itself, the migration cannot be tested and will remain in the status blocked. On Fri, Sep 5, 2014 at 12:35 PM, Chamila Adhikarinayake chami...@wso2.com wrote: this can be found in the svn location[1] but is missing in the pack [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/apimgt/1.7.1/modules/distribution/resources/migration-1.7.0_to_1.7.1/ On Fri, Sep 5, 2014 at 12:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila I cannot find the mentioned resource in the 04/09/2014 pack. I followed the steps given in the README.txt to migrate the database. Thank You Erandi On Fri, Sep 5, 2014 at 11:57 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, There is a new resource migration-1.7.0_to_1.7.1 to modify the database. it creates the related column SUBS_CREATE_STATE (which is mentioned in the error log). Did you use that one? I think this might be the problem. On Fri, Sep 5, 2014 at 11:18 AM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All The migration cannot be tested in the 04/09/2014 due to the following issue, since none of the migrated APIs can be retrieved. Testing is currently blocking. https://wso2.org/jira/browse/APIMANAGER-2799 Thank You Erandi On Mon, Aug 18, 2014 at 1:45 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila I have reopened the issue APIMANAGER-2662 because this issue should be fixed and shipped in a newer revision or as a patch itself. Thank You On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake chami...@wso2.com wrote: I'll create a small java client to modify the apis in the synapse-config/default/api folder. Thanks, Chamila. On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias nuw...@wso2.com wrote: We should be able to write a simple script or java client to do this right? Thanks, NuwanD. On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila As i understand regarding APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 following are the two workarounds. 1. As mentioned in the readme.txt., edit *each* api xml in the APIM_1.7.0/repository/deployment/server/synapse-config/default/api directory. Replace handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/ with handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler 2. Manually go to implement tab in the edit mode of *each* of the APIs and click manage If a customer wants to migrate hundreds of APIs, is it a feasible solution from the customer's perspective? Ideally when a customer migrates from an older version, they should be able to work with their data as they worked before the migration. Since invoking an API is the core functionality of API Manager, is it really feasible in asking the customer to follow above 1st or 2nd method? From the customer/user perspective above given solution cannot be accepted. In my opinion this should be handled by our side without asking the customer/user to take extra effort in bringing his migrated data to work properly. Thank You Erandi On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, Issues mentioned in the previous mail are fixed in the latest 17/08/2014 pack[1]. There are some updates done to the migration tool readme.txt file as well. You can proceed with the migration testing. For the issue APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 please read the comments in the jira (these instructions are added to the readme.txt). [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/ Thanks, Chamila. On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As per the pack released on 05/08/2014 following is the status 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 - issue status - inprogress. This is the main scenario of the migration. Thus the fix for this is crucial to proceed with the proper user scenario based testing 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 - issue status - reopened. This issue corrupts the entire database. 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 - issue status - reopened. The resources added before the migration is not copied correctly 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 - issue status - reopened (due to APIMANAGER-2669
[Dev] Cannot proceed with testing of API-M 1.7.1 testing with MSSQL
Hi All I connected the pack released on 04/09 to the MSSQL database i used with a previous 1.7.1 pack and the following error occurred. https://wso2.org/jira/browse/APIMANAGER-2802 Please provide directives in proceeding. Thank You Erandi -- *Chathurika Erandi* Software Engineer, WSO2 Inc. *E-mail:* chathuri...@wso2.com *Mobile: *+94714 328 612 *Blog*: chathurikaerandi.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Cannot proceed with testing of API-M 1.7.1 testing with MSSQL
There has been a database change. Hence the reason for the error. The change is reflected correctly in the new DB scripts that are shipped with the product. The error is the exact same as you have reported in thread [1]. Therefore the solution is also the same as what ChamilaA has provided in the same thread. You can follow the instructions he has given to proceed. [1] - [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0. Thanks, NuwanD. On Fri, Sep 5, 2014 at 12:48 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All I connected the pack released on 04/09 to the MSSQL database i used with a previous 1.7.1 pack and the following error occurred. https://wso2.org/jira/browse/APIMANAGER-2802 Please provide directives in proceeding. Thank You Erandi -- *Chathurika Erandi* Software Engineer, WSO2 Inc. *E-mail:* chathuri...@wso2.com *Mobile: *+94714 328 612 *Blog*: chathurikaerandi.blogspot.com -- Nuwan Dias Associate Tech Lead - 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] CSS and DIV Structure
Thanks Jerad, There was a css file overiding the styles, got it sorted! :) On Thu, Sep 4, 2014 at 4:53 PM, Lahiru Cooray lahi...@wso2.com wrote: Hi Shiva, I checked the HTML structure and seems like nothing wrong with it. Please check this with another browser. I guess this may be a issue with the CSS file. On Thu, Sep 4, 2014 at 2:59 PM, Shiva Balachandran sh...@wso2.com wrote: Hi All, As you all may understand the amount of typo we come across when we develop a HTML site, I am facing a issue where one DIV is overlaying another. As shown in the attachment screenshot. Does anyone has any clue on why this might happen, i checked the div structure and the css files but i am unable to spot the issue or the error in the structure. I have attached the div structure and the screenshot of the error. Thank you. -- Shiva Balachandran Software Engineer WSO2 Inc. Mobile - +94 774445788 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lahiru Cooray* Software Engineer WSO2, Inc.;http://wso2.com/ lean.enterprise.middleware Mobile: +94 715 654154 -- Shiva Balachandran Software Engineer WSO2 Inc. Mobile - +94 774445788 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] BAM 4.2.2 build failed [Failure to find org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009]
Hi, While building BAM 2.4.2 (in turing branch) I overcome a build failure. Kindly find the mvn error log Im getting below. I googled this error and found a resource in wso2 oxygen tank[1]. as per that solution I cant find Kernel patch 0009 (org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009). Where could i find it?. Can someone help me? [1] http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-BAM-4-2-1-build-failed-td93488.html Thanx [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack (2-unpack-kernel-patch) on project wso2bam-p2-profile-gen: Unable to find artifact. Failure to find org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009 in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced [ERROR] [ERROR] Try downloading the file manually from the project website. [ERROR] [ERROR] Then, install it using the command: [ERROR] mvn install:install-file -DgroupId=org.wso2.carbon -DartifactId=WSO2-CARBON-PATCH-4.2.0 -Dversion=0009 -Dpackaging=zip -Dfile=/path/to/file [ERROR] [ERROR] Alternatively, if you host your own repository you can deploy the file there: [ERROR] mvn deploy:deploy-file -DgroupId=org.wso2.carbon -DartifactId=WSO2-CARBON-PATCH-4.2.0 -Dversion=0009 -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] [ERROR] [ERROR] [ERROR] org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009 [ERROR] [ERROR] from the specified remote repositories: [ERROR] wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/, releases=true, snapshots=true), [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false) [ERROR] - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack (2-unpack-kernel-patch) on project wso2bam-p2-profile-gen: Unable to find artifact. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to find artifact. at org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.getArtifact(AbstractFromConfigurationMojo.java:250) at org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.getProcessedArtifactItems(AbstractFromConfigurationMojo.java:146) at org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:67) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Failure to find org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009 in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.wso2.carbon -DartifactId=WSO2-CARBON-PATCH-4.2.0 -Dversion=0009 -Dpackaging=zip -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file
Re: [Dev] Error while building the SAML testcase in WSO2 EAM
Hi Waruna,
@Test(groups = { wso2.appmanager }, description = test SAML tokens send
to the backend)
public void samlToBackendTestCase() throws Exception {
String appId = ;
// publisher creates an app
String username = userInfo.getUserName();
String password = userInfo.getPassword();
appmPublisher.login(username, password);
AppCreateRequest appRequest = new AppCreateRequest();
int port = 9988; // used to create a wiremonitor server and get the
// requst
String webappUrl = http://localhost:; + port;
String appName = samltestapp;
String version = 1.0.0;
appRequest.setOverview_webAppUrl(webappUrl);
appRequest.setOverview_transports(https);
appRequest.setOverview_name(appName);
appRequest.setOverview_version(version);
appRequest.setOverview_context(/ + appName);
appRequest.setEntitlementPolicies([]);
// for IS autoconfig to get SSO feature
appRequest.setAutoConfig(on);
appRequest.setProviders(wso2is-5.0.0);
appRequest.setSso_ssoProvider(wso2is-5.0.0);
appRequest.setSso_singleSignOn(Enabled);
appRequest.setClaims(http://wso2.org/claims/role;);
appRequest.setClaimPropertyCounter(1);
appRequest.setSso_idpProviderUrl(https://localhost:9443/samlsso/;);
log.info(Waiting for the test application to be
created..);
HttpResponse response = appmPublisher.createApp(appRequest);
JSONObject jsonObject = new JSONObject(response.getData());
appId = (String) jsonObject.get(id);
try {
Thread.sleep(4000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
log.info(Publishing the test application..);
appmPublisher.publishApp(appId);
try {
Thread.sleep(1);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
// client subscribe to that app
log.info(Subscribe to the test application..);
appmStore.login(username, password);
// try {
// Thread.sleep(5000);
// } catch (InterruptedException e) {
// // TODO Auto-generated catch block
// e.printStackTrace();
// }
SubscriptionRequest subscriptionRequest = new SubscriptionRequest(
appName, username, version);
HttpResponse subscriptionResponse = appmStore
.subscribeForApplication(subscriptionRequest);
Thread.sleep(2);
// Assert.assertTrue((Boolean) subscriptionJsonObject.get(status),
// Application is already subscribed);
// do the selenium login and app selection
//FirefoxDriver driver = new FirefoxDriver();
log.info(sso profiver--
++appRequest.getSso_ssoProvider());
// wire monitor server to get the request from the appmanager
WireMonitorServer server = new WireMonitorServer(port);
server.start();
driver = BrowserManager.getWebDriver();
APPMStoreUIClient.login(driver, storeURLHttp, username, password);
//String baseWindow = driver.getWindowHandle();
//driver.manage().timeouts().pageLoadTimeout(30, TimeUnit.SECONDS);
//driver.manage().timeouts().implicitlyWait(4000,
TimeUnit.MILLISECONDS);
try {
Thread.sleep(5000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
APPMStoreUIClient.selectApplication(driver, storeURLHttp, appId,
username, password);
try {
Thread.sleep(3000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
System.out.println(the backend sent saml message :
+server.getCapturedMessage());
boolean hasSAML = false;
if (server.getCapturedMessage().contains(AppMgtSAML2Response)) {
hasSAML = true;
}
Assert.assertEquals(hasSAML, true,
SAML token cannot be found in the request sent to the
backend);
server = null;
driver.close();
}
Cheers
On Fri, Sep 5, 2014 at 1:41 PM, Waruna Perera waru...@wso2.com wrote:
Hi,
Can you please share your test case code?
Thanks
On Fri, Sep 5, 2014 at 1:37 PM, Kasun Dissanayake kas...@wso2.com wrote:
Hi all,
I'm working on [1] and getting following error
[1] https://wso2.org/jira/browse/APPM-161
samlToBackendTestCase(org.wso2.carbon.appmanager.tests.sample.SAMLtoBackendTest)
Time elapsed: 51.699 sec FAILURE!
org.openqa.selenium.remote.UnreachableBrowserException: Error
communicating with the remote browser. It may have died.
Build info: version: '2.37.0', revision:
[Dev] Error while building the SAML testcase in WSO2 EAM
Hi all, I'm working on [1] and getting following error [1] https://wso2.org/jira/browse/APPM-161 samlToBackendTestCase(org.wso2.carbon.appmanager.tests.sample.SAMLtoBackendTest) Time elapsed: 51.699 sec FAILURE! org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the remote browser. It may have died. Build info: version: '2.37.0', revision: 'a7c61cbd68657e133ae96672cf995890bad2ee42', time: '2013-10-18 09:51:02' System info: host: 'puppet.kasun.org', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-35-generic', java.version: '1.6.0_45' Driver info: driver.version: RemoteWebDriver at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:548) at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:268) at org.openqa.selenium.remote.RemoteWebElement.sendKeys(RemoteWebElement.java:89) at org.wso2.carbon.appmanager.tests.util.APPMStoreUIClient.selectApplication(APPMStoreUIClient.java:93) at org.wso2.carbon.appmanager.tests.sample.SAMLtoBackendTest.samlToBackendTestCase(SAMLtoBackendTest.java:141) Caused by: org.apache.http.conn.HttpHostConnectException: Connection to http://127.0.0.1:7056 refused at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:158) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:561) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:337) at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:298) at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:145) at org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:366) at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:527) ... 38 more Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148) ... 48 more Any idea ? -- Kasun Dissanayake Software Engineer WSO2 Inc. Lean | Enterprise | Middleware Tel - +94 77 086 2860 Skype - kasun.dissanayake4 LinkedIn - lk.linkedin.com/in/kasundis/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while building the SAML testcase in WSO2 EAM
HI,
Can you try adding following code segment and try.
On Fri, Sep 5, 2014 at 1:43 PM, Kasun Dissanayake kas...@wso2.com wrote:
Hi Waruna,
@Test(groups = { wso2.appmanager }, description = test SAML tokens send
to the backend)
public void samlToBackendTestCase() throws Exception {
String appId = ;
// publisher creates an app
String username = userInfo.getUserName();
String password = userInfo.getPassword();
appmPublisher.login(username, password);
AppCreateRequest appRequest = new AppCreateRequest();
int port = 9988; // used to create a wiremonitor server and get the
// requst
String webappUrl = http://localhost:; + port;
String appName = samltestapp;
String version = 1.0.0;
appRequest.setOverview_webAppUrl(webappUrl);
appRequest.setOverview_transports(https);
appRequest.setOverview_name(appName);
appRequest.setOverview_version(version);
appRequest.setOverview_context(/ + appName);
appRequest.setEntitlementPolicies([]);
// for IS autoconfig to get SSO feature
appRequest.setAutoConfig(on);
appRequest.setProviders(wso2is-5.0.0);
appRequest.setSso_ssoProvider(wso2is-5.0.0);
appRequest.setSso_singleSignOn(Enabled);
appRequest.setClaims(http://wso2.org/claims/role;);
appRequest.setClaimPropertyCounter(1);
appRequest.setSso_idpProviderUrl(https://localhost:9443/samlsso/
);
log.info(Waiting for the test application to be
created..);
HttpResponse response = appmPublisher.createApp(appRequest);
JSONObject jsonObject = new JSONObject(response.getData());
appId = (String) jsonObject.get(id);
try {
Thread.sleep(4000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
log.info(Publishing the test application..);
appmPublisher.publishApp(appId);
try {
Thread.sleep(1);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
// client subscribe to that app
log.info(Subscribe to the test
application..);
appmStore.login(username, password);
// try {
// Thread.sleep(5000);
// } catch (InterruptedException e) {
// // TODO Auto-generated catch block
// e.printStackTrace();
// }
SubscriptionRequest subscriptionRequest = new SubscriptionRequest(
appName, username, version);
HttpResponse subscriptionResponse = appmStore
.subscribeForApplication(subscriptionRequest);
Thread.sleep(2);
// Assert.assertTrue((Boolean)
subscriptionJsonObject.get(status),
// Application is already subscribed);
// do the selenium login and app selection
//FirefoxDriver driver = new FirefoxDriver();
log.info(sso profiver--
++appRequest.getSso_ssoProvider());
// wire monitor server to get the request from the appmanager
WireMonitorServer server = new WireMonitorServer(port);
server.start();
driver = BrowserManager.getWebDriver();
APPMStoreUIClient.login(driver, storeURLHttp, username, password);
//String baseWindow = driver.getWindowHandle();
//driver.manage().timeouts().pageLoadTimeout(30, TimeUnit.SECONDS);
//driver.manage().timeouts().implicitlyWait(4000,
TimeUnit.MILLISECONDS);
try {
Thread.sleep(5000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
APPMStoreUIClient.selectApplication(driver, storeURLHttp, appId,
username, password);
try {
Thread.sleep(3000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
System.out.println(the backend sent saml message :
+server.getCapturedMessage());
boolean hasSAML = false;
if (server.getCapturedMessage().contains(AppMgtSAML2Response)) {
hasSAML = true;
}
Assert.assertEquals(hasSAML, true,
SAML token cannot be found in the request sent to the
backend);
server = null;
driver.close();
}
Cheers
On Fri, Sep 5, 2014 at 1:41 PM, Waruna Perera waru...@wso2.com wrote:
Hi,
Can you please share your test case code?
Thanks
On Fri, Sep 5, 2014 at 1:37 PM, Kasun Dissanayake kas...@wso2.com
wrote:
Hi all,
I'm working on [1] and getting following error
[1] https://wso2.org/jira/browse/APPM-161
Re: [Dev] CSS and DIV Structure
No problem Shiva. Glad you got it fixed. Regards, Jerad On Fri, Sep 5, 2014 at 12:57 PM, Shiva Balachandran sh...@wso2.com wrote: Thanks Jerad, There was a css file overiding the styles, got it sorted! :) On Thu, Sep 4, 2014 at 4:53 PM, Lahiru Cooray lahi...@wso2.com wrote: Hi Shiva, I checked the HTML structure and seems like nothing wrong with it. Please check this with another browser. I guess this may be a issue with the CSS file. On Thu, Sep 4, 2014 at 2:59 PM, Shiva Balachandran sh...@wso2.com wrote: Hi All, As you all may understand the amount of typo we come across when we develop a HTML site, I am facing a issue where one DIV is overlaying another. As shown in the attachment screenshot. Does anyone has any clue on why this might happen, i checked the div structure and the css files but i am unable to spot the issue or the error in the structure. I have attached the div structure and the screenshot of the error. Thank you. -- Shiva Balachandran Software Engineer WSO2 Inc. Mobile - +94 774445788 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lahiru Cooray* Software Engineer WSO2, Inc.;http://wso2.com/ lean.enterprise.middleware Mobile: +94 715 654154 -- Shiva Balachandran Software Engineer WSO2 Inc. Mobile - +94 774445788 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Jerad Rutnam | **Software Engineer - UI* WSO2, Inc. www.wso2.com *Email: je...@wso2.com je...@wso2.com* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while building the SAML testcase in WSO2 EAM
Hi waruna,
You have submitted your WSO2 IS certificate in a different pack right?
But our pack contains the IS too.
How can I manage this file path ?
On Fri, Sep 5, 2014 at 1:47 PM, Waruna Perera waru...@wso2.com wrote:
Hi,
This sets the trust store in client. Set it to your paths
System.setProperty(javax.net.ssl.trustStore,
/home/waruna/Products/wso2is-4.7.0/repository/resources/security/wso2carbon.jks);
System.setProperty(javax.net.ssl.trustStorePassword,
wso2carbon);
System.setProperty(javax.net.ssl.trustStoreType, JKS);
On Fri, Sep 5, 2014 at 1:45 PM, Waruna Perera waru...@wso2.com wrote:
HI,
Can you try adding following code segment and try.
On Fri, Sep 5, 2014 at 1:43 PM, Kasun Dissanayake kas...@wso2.com
wrote:
Hi Waruna,
@Test(groups = { wso2.appmanager }, description = test SAML tokens
send to the backend)
public void samlToBackendTestCase() throws Exception {
String appId = ;
// publisher creates an app
String username = userInfo.getUserName();
String password = userInfo.getPassword();
appmPublisher.login(username, password);
AppCreateRequest appRequest = new AppCreateRequest();
int port = 9988; // used to create a wiremonitor server and get
the
// requst
String webappUrl = http://localhost:; + port;
String appName = samltestapp;
String version = 1.0.0;
appRequest.setOverview_webAppUrl(webappUrl);
appRequest.setOverview_transports(https);
appRequest.setOverview_name(appName);
appRequest.setOverview_version(version);
appRequest.setOverview_context(/ + appName);
appRequest.setEntitlementPolicies([]);
// for IS autoconfig to get SSO feature
appRequest.setAutoConfig(on);
appRequest.setProviders(wso2is-5.0.0);
appRequest.setSso_ssoProvider(wso2is-5.0.0);
appRequest.setSso_singleSignOn(Enabled);
appRequest.setClaims(http://wso2.org/claims/role;);
appRequest.setClaimPropertyCounter(1);
appRequest.setSso_idpProviderUrl(
https://localhost:9443/samlsso/;);
log.info(Waiting for the test application to be
created..);
HttpResponse response = appmPublisher.createApp(appRequest);
JSONObject jsonObject = new JSONObject(response.getData());
appId = (String) jsonObject.get(id);
try {
Thread.sleep(4000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
log.info(Publishing the test
application..);
appmPublisher.publishApp(appId);
try {
Thread.sleep(1);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
// client subscribe to that app
log.info(Subscribe to the test
application..);
appmStore.login(username, password);
// try {
// Thread.sleep(5000);
// } catch (InterruptedException e) {
// // TODO Auto-generated catch block
// e.printStackTrace();
// }
SubscriptionRequest subscriptionRequest = new
SubscriptionRequest(
appName, username, version);
HttpResponse subscriptionResponse = appmStore
.subscribeForApplication(subscriptionRequest);
Thread.sleep(2);
// Assert.assertTrue((Boolean)
subscriptionJsonObject.get(status),
// Application is already subscribed);
// do the selenium login and app selection
//FirefoxDriver driver = new FirefoxDriver();
log.info(sso profiver--
++appRequest.getSso_ssoProvider());
// wire monitor server to get the request from the appmanager
WireMonitorServer server = new WireMonitorServer(port);
server.start();
driver = BrowserManager.getWebDriver();
APPMStoreUIClient.login(driver, storeURLHttp, username,
password);
//String baseWindow = driver.getWindowHandle();
//driver.manage().timeouts().pageLoadTimeout(30,
TimeUnit.SECONDS);
//driver.manage().timeouts().implicitlyWait(4000,
TimeUnit.MILLISECONDS);
try {
Thread.sleep(5000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
APPMStoreUIClient.selectApplication(driver, storeURLHttp, appId,
username, password);
try {
Thread.sleep(3000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
System.out.println(the backend sent saml message :
+server.getCapturedMessage());
boolean hasSAML = false;
if
Re: [Dev] Error while building the SAML testcase in WSO2 EAM
Hi,
Use the trust store in IS which is within your pack.
On Fri, Sep 5, 2014 at 1:51 PM, Kasun Dissanayake kas...@wso2.com wrote:
Hi waruna,
You have submitted your WSO2 IS certificate in a different pack right?
But our pack contains the IS too.
How can I manage this file path ?
On Fri, Sep 5, 2014 at 1:47 PM, Waruna Perera waru...@wso2.com wrote:
Hi,
This sets the trust store in client. Set it to your paths
System.setProperty(javax.net.ssl.trustStore,
/home/waruna/Products/wso2is-4.7.0/repository/resources/security/wso2carbon.jks);
System.setProperty(javax.net.ssl.trustStorePassword,
wso2carbon);
System.setProperty(javax.net.ssl.trustStoreType, JKS);
On Fri, Sep 5, 2014 at 1:45 PM, Waruna Perera waru...@wso2.com wrote:
HI,
Can you try adding following code segment and try.
On Fri, Sep 5, 2014 at 1:43 PM, Kasun Dissanayake kas...@wso2.com
wrote:
Hi Waruna,
@Test(groups = { wso2.appmanager }, description = test SAML tokens
send to the backend)
public void samlToBackendTestCase() throws Exception {
String appId = ;
// publisher creates an app
String username = userInfo.getUserName();
String password = userInfo.getPassword();
appmPublisher.login(username, password);
AppCreateRequest appRequest = new AppCreateRequest();
int port = 9988; // used to create a wiremonitor server and get
the
// requst
String webappUrl = http://localhost:; + port;
String appName = samltestapp;
String version = 1.0.0;
appRequest.setOverview_webAppUrl(webappUrl);
appRequest.setOverview_transports(https);
appRequest.setOverview_name(appName);
appRequest.setOverview_version(version);
appRequest.setOverview_context(/ + appName);
appRequest.setEntitlementPolicies([]);
// for IS autoconfig to get SSO feature
appRequest.setAutoConfig(on);
appRequest.setProviders(wso2is-5.0.0);
appRequest.setSso_ssoProvider(wso2is-5.0.0);
appRequest.setSso_singleSignOn(Enabled);
appRequest.setClaims(http://wso2.org/claims/role;);
appRequest.setClaimPropertyCounter(1);
appRequest.setSso_idpProviderUrl(
https://localhost:9443/samlsso/;);
log.info(Waiting for the test application to be
created..);
HttpResponse response = appmPublisher.createApp(appRequest);
JSONObject jsonObject = new JSONObject(response.getData());
appId = (String) jsonObject.get(id);
try {
Thread.sleep(4000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
log.info(Publishing the test
application..);
appmPublisher.publishApp(appId);
try {
Thread.sleep(1);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
// client subscribe to that app
log.info(Subscribe to the test
application..);
appmStore.login(username, password);
// try {
// Thread.sleep(5000);
// } catch (InterruptedException e) {
// // TODO Auto-generated catch block
// e.printStackTrace();
// }
SubscriptionRequest subscriptionRequest = new
SubscriptionRequest(
appName, username, version);
HttpResponse subscriptionResponse = appmStore
.subscribeForApplication(subscriptionRequest);
Thread.sleep(2);
// Assert.assertTrue((Boolean)
subscriptionJsonObject.get(status),
// Application is already subscribed);
// do the selenium login and app selection
//FirefoxDriver driver = new FirefoxDriver();
log.info(sso profiver--
++appRequest.getSso_ssoProvider());
// wire monitor server to get the request from the appmanager
WireMonitorServer server = new WireMonitorServer(port);
server.start();
driver = BrowserManager.getWebDriver();
APPMStoreUIClient.login(driver, storeURLHttp, username,
password);
//String baseWindow = driver.getWindowHandle();
//driver.manage().timeouts().pageLoadTimeout(30,
TimeUnit.SECONDS);
//driver.manage().timeouts().implicitlyWait(4000,
TimeUnit.MILLISECONDS);
try {
Thread.sleep(5000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
APPMStoreUIClient.selectApplication(driver, storeURLHttp, appId,
username, password);
try {
Thread.sleep(3000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
Re: [Dev] Error while building the SAML testcase in WSO2 EAM
Hi,
This sets the trust store in client. Set it to your paths
System.setProperty(javax.net.ssl.trustStore,
/home/waruna/Products/wso2is-4.7.0/repository/resources/security/wso2carbon.jks);
System.setProperty(javax.net.ssl.trustStorePassword,
wso2carbon);
System.setProperty(javax.net.ssl.trustStoreType, JKS);
On Fri, Sep 5, 2014 at 1:45 PM, Waruna Perera waru...@wso2.com wrote:
HI,
Can you try adding following code segment and try.
On Fri, Sep 5, 2014 at 1:43 PM, Kasun Dissanayake kas...@wso2.com wrote:
Hi Waruna,
@Test(groups = { wso2.appmanager }, description = test SAML tokens
send to the backend)
public void samlToBackendTestCase() throws Exception {
String appId = ;
// publisher creates an app
String username = userInfo.getUserName();
String password = userInfo.getPassword();
appmPublisher.login(username, password);
AppCreateRequest appRequest = new AppCreateRequest();
int port = 9988; // used to create a wiremonitor server and get
the
// requst
String webappUrl = http://localhost:; + port;
String appName = samltestapp;
String version = 1.0.0;
appRequest.setOverview_webAppUrl(webappUrl);
appRequest.setOverview_transports(https);
appRequest.setOverview_name(appName);
appRequest.setOverview_version(version);
appRequest.setOverview_context(/ + appName);
appRequest.setEntitlementPolicies([]);
// for IS autoconfig to get SSO feature
appRequest.setAutoConfig(on);
appRequest.setProviders(wso2is-5.0.0);
appRequest.setSso_ssoProvider(wso2is-5.0.0);
appRequest.setSso_singleSignOn(Enabled);
appRequest.setClaims(http://wso2.org/claims/role;);
appRequest.setClaimPropertyCounter(1);
appRequest.setSso_idpProviderUrl(https://localhost:9443/samlsso/
);
log.info(Waiting for the test application to be
created..);
HttpResponse response = appmPublisher.createApp(appRequest);
JSONObject jsonObject = new JSONObject(response.getData());
appId = (String) jsonObject.get(id);
try {
Thread.sleep(4000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
log.info(Publishing the test
application..);
appmPublisher.publishApp(appId);
try {
Thread.sleep(1);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
// client subscribe to that app
log.info(Subscribe to the test
application..);
appmStore.login(username, password);
// try {
// Thread.sleep(5000);
// } catch (InterruptedException e) {
// // TODO Auto-generated catch block
// e.printStackTrace();
// }
SubscriptionRequest subscriptionRequest = new SubscriptionRequest(
appName, username, version);
HttpResponse subscriptionResponse = appmStore
.subscribeForApplication(subscriptionRequest);
Thread.sleep(2);
// Assert.assertTrue((Boolean)
subscriptionJsonObject.get(status),
// Application is already subscribed);
// do the selenium login and app selection
//FirefoxDriver driver = new FirefoxDriver();
log.info(sso profiver--
++appRequest.getSso_ssoProvider());
// wire monitor server to get the request from the appmanager
WireMonitorServer server = new WireMonitorServer(port);
server.start();
driver = BrowserManager.getWebDriver();
APPMStoreUIClient.login(driver, storeURLHttp, username, password);
//String baseWindow = driver.getWindowHandle();
//driver.manage().timeouts().pageLoadTimeout(30,
TimeUnit.SECONDS);
//driver.manage().timeouts().implicitlyWait(4000,
TimeUnit.MILLISECONDS);
try {
Thread.sleep(5000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
APPMStoreUIClient.selectApplication(driver, storeURLHttp, appId,
username, password);
try {
Thread.sleep(3000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
System.out.println(the backend sent saml message :
+server.getCapturedMessage());
boolean hasSAML = false;
if (server.getCapturedMessage().contains(AppMgtSAML2Response)) {
hasSAML = true;
}
Assert.assertEquals(hasSAML, true,
SAML token cannot be found in the request sent to the
backend);
Re: [Dev] Error while building the SAML testcase in WSO2 EAM
Hi Kasun, According to the error message, test are depending on remote webdriver, you have to disable remote webdriver in automation.xml. This property should be enabled if you want to run the tests on browser hosted in remote server. Set the remote webdriver enabled property to false. You can find configuration details at [1]. remoteDriverUrl enable=falsewww://xx.xxx.xx.xx:/zz//remoteDriverUrl [1]https://docs.wso2.com/display/TA430/Automation.xml+File Thanks, Krishantha. On Fri, Sep 5, 2014 at 1:37 PM, Kasun Dissanayake kas...@wso2.com wrote: Hi all, I'm working on [1] and getting following error [1] https://wso2.org/jira/browse/APPM-161 samlToBackendTestCase(org.wso2.carbon.appmanager.tests.sample.SAMLtoBackendTest) Time elapsed: 51.699 sec FAILURE! org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the remote browser. It may have died. Build info: version: '2.37.0', revision: 'a7c61cbd68657e133ae96672cf995890bad2ee42', time: '2013-10-18 09:51:02' System info: host: 'puppet.kasun.org', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-35-generic', java.version: '1.6.0_45' Driver info: driver.version: RemoteWebDriver at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:548) at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:268) at org.openqa.selenium.remote.RemoteWebElement.sendKeys(RemoteWebElement.java:89) at org.wso2.carbon.appmanager.tests.util.APPMStoreUIClient.selectApplication(APPMStoreUIClient.java:93) at org.wso2.carbon.appmanager.tests.sample.SAMLtoBackendTest.samlToBackendTestCase(SAMLtoBackendTest.java:141) Caused by: org.apache.http.conn.HttpHostConnectException: Connection to http://127.0.0.1:7056 refused at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:158) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:561) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:337) at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:298) at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:145) at org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:366) at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:527) ... 38 more Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148) ... 48 more Any idea ? -- Kasun Dissanayake Software Engineer WSO2 Inc. Lean | Enterprise | Middleware Tel - +94 77 086 2860 Skype - kasun.dissanayake4 LinkedIn - lk.linkedin.com/in/kasundis/ -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [APIM] Access-Control-Allow-Methods header not getting set for CORS requests.
Hi In AM 1.7.1 Access-Control-Allow-Methods header is not getting set by the handler. When trouble shooting I found that particular line is commented. was there a reason to remove it ? If Access-Control-Allow-Methods is not present PUT and DELETE requests will not work in swagger console + other web clients. Thanks Jo -- -- *Joseph Fonseka* WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 772 512 430 skype: jpfonseka * http://lk.linkedin.com/in/rumeshbandara* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ESB] Extract attachment from incoming REST request
Hi,
We are sending a request to a through an ESB connector as follows:
{
AddFiles:[{ DocumentName:sick.txt, File: aSBhbSBzaWNr ,
Description:sick }]
}
The File value is the Base64-encoded content of the file.
However, rather than asking the client to send a Base64-encoded string, we
would prefer to get the file along with the REST request sent to the ESB and
then extract it, Base64-encode it, and add it to the outgoing request to the
backend.
Is there any way to accomplish this? Or is it advisable to ask the client to
send a Base64-encoded string?
Thanks.
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-Extract-attachment-from-incoming-REST-request-tp102449.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Adding new tests-UI module to BRS
Completed. (https://github.com/wso2-dev/product-brs/pull/3) Regards On Thu, Sep 4, 2014 at 11:03 AM, Dimuthu De Lanerolle dimut...@wso2.com wrote: Hi, I have started the $subject and will update the progress soon. Regards -- Dimuthu De Lanerolle Software Engineer WSO2 Inc. lean . enterprise . middlewear. http://wso2.com/ Tel. : +94 11 2145345 Fax : +94 11 2145300 email : dimut...@wso2.com -- Dimuthu De Lanerolle Software Engineer WSO2 Inc. lean . enterprise . middlewear. http://wso2.com/ Tel. : +94 11 2145345 Fax : +94 11 2145300 email : dimut...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Pls merge pull request
Pls merge the pull request added for new tests-ui-integration module , https://github.com/wso2-dev/product-brs/pull/3 -- Dimuthu De Lanerolle Software Engineer WSO2 Inc. lean . enterprise . middlewear. http://wso2.com/ Tel. : +94 11 2145345 Fax : +94 11 2145300 email : dimut...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Exception occurs when trying to update an existing tenant
Hi, When adding a new tenant with an invalid email validates the input, but updating an existing tenant with an invalid email throws the below exception ERROR - TenantMgtUtil Failed to update the tenant config. tenant-domain: test.com, tenant-admin: test. org.wso2.carbon.tenant.mgt.stub.TenantMgtAdminServiceExceptionException: TenantMgtAdminServiceExceptionException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at java.lang.Class.newInstance0(Class.java:374) at java.lang.Class.newInstance(Class.java:327) at org.wso2.carbon.tenant.mgt.stub.TenantMgtAdminServiceStub.updateTenant(TenantMgtAdminServiceStub.java:364) at org.wso2.carbon.tenant.mgt.ui.clients.TenantServiceClient.updateTenant(TenantServiceClient.java:110) at org.wso2.carbon.tenant.mgt.ui.utils.TenantMgtUtil.updateTenantConfigBean(TenantMgtUtil.java:115) at org.apache.jsp.tenant_002dmgt.submit_005ftenant_005fajaxprocessor_jsp._jspService(org.apache.jsp.tenant_002dmgt.submit_005ftenant_005fajaxprocessor_jsp:120) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155) at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68) at javax.servlet.http.HttpServlet.service(HttpServlet.java: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.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) 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.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Thanks, Sohani Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] API Changes in WSO2 EAM
Hi All, I'm working with test automation in newest WSO2 EAM pack and getting errors in test cases. So I did change the framework according to that. And followings are the errors generated APIs I've changed 1) App create API. 2) APP Publish API. 3) IS configurations. 4) Selenium configurations according to new EAM pack. So because of this I was taking much time for completing the test cases. But I'm now stuck with Subscription API. It is mentioned as follow. backEndUrl+/store/resources/webapp/v1/subscription/app Is this the latest backend API or is it changed ? Cheers -- Kasun Dissanayake Software Engineer WSO2 Inc. Lean | Enterprise | Middleware Tel - +94 77 086 2860 Skype - kasun.dissanayake4 LinkedIn - lk.linkedin.com/in/kasundis/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Exception occurs when trying to update an existing tenant
Hi Sohani I think you haven't posted the full error log. According to the exception trace this was thrown from at org.wso2.carbon.tenant.mgt.ui.utils.TenantMgtUtil.updateTenantConfigBean( TenantMgtUtil.java:115) If you check the code you could find the exact error Failed to update the tenant config. But this exception alone will not help to identify from where it fails. Can you post full exception log? Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Fri, Sep 5, 2014 at 5:51 PM, Sohani Weerasinghe soh...@wso2.com wrote: Hi, When adding a new tenant with an invalid email validates the input, but updating an existing tenant with an invalid email throws the below exception ERROR - TenantMgtUtil Failed to update the tenant config. tenant-domain: test.com, tenant-admin: test. org.wso2.carbon.tenant.mgt.stub.TenantMgtAdminServiceExceptionException: TenantMgtAdminServiceExceptionException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at java.lang.Class.newInstance0(Class.java:374) at java.lang.Class.newInstance(Class.java:327) at org.wso2.carbon.tenant.mgt.stub.TenantMgtAdminServiceStub.updateTenant(TenantMgtAdminServiceStub.java:364) at org.wso2.carbon.tenant.mgt.ui.clients.TenantServiceClient.updateTenant(TenantServiceClient.java:110) at org.wso2.carbon.tenant.mgt.ui.utils.TenantMgtUtil.updateTenantConfigBean(TenantMgtUtil.java:115) at org.apache.jsp.tenant_002dmgt.submit_005ftenant_005fajaxprocessor_jsp._jspService(org.apache.jsp.tenant_002dmgt.submit_005ftenant_005fajaxprocessor_jsp:120) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155) at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68) at javax.servlet.http.HttpServlet.service(HttpServlet.java: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.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) 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.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at
Re: [Dev] BAM 4.2.2 build failed [Failure to find org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009]
Hi, You can find patch0009 in https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0009 . And also please note that BAM 2.4.2 has been renamed to BAM 2.5.0. BAM 2.4.2 has been removed. *Maninda Edirisooriya* Senior Software Engineer *WSO2, Inc.*lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *E-mail* : mani...@wso2.com *Skype* : @manindae *Twitter* : @maninda On Fri, Sep 5, 2014 at 1:27 PM, Thushara Ranawaka thusha...@wso2.com wrote: Hi, While building BAM 2.4.2 (in turing branch) I overcome a build failure. Kindly find the mvn error log Im getting below. I googled this error and found a resource in wso2 oxygen tank[1]. as per that solution I cant find Kernel patch 0009 (org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009). Where could i find it?. Can someone help me? [1] http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-BAM-4-2-1-build-failed-td93488.html Thanx [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack (2-unpack-kernel-patch) on project wso2bam-p2-profile-gen: Unable to find artifact. Failure to find org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009 in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced [ERROR] [ERROR] Try downloading the file manually from the project website. [ERROR] [ERROR] Then, install it using the command: [ERROR] mvn install:install-file -DgroupId=org.wso2.carbon -DartifactId=WSO2-CARBON-PATCH-4.2.0 -Dversion=0009 -Dpackaging=zip -Dfile=/path/to/file [ERROR] [ERROR] Alternatively, if you host your own repository you can deploy the file there: [ERROR] mvn deploy:deploy-file -DgroupId=org.wso2.carbon -DartifactId=WSO2-CARBON-PATCH-4.2.0 -Dversion=0009 -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] [ERROR] [ERROR] [ERROR] org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009 [ERROR] [ERROR] from the specified remote repositories: [ERROR] wso2-nexus ( http://maven.wso2.org/nexus/content/groups/wso2-public/, releases=true, snapshots=true), [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false) [ERROR] - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack (2-unpack-kernel-patch) on project wso2bam-p2-profile-gen: Unable to find artifact. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to find artifact. at org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.getArtifact(AbstractFromConfigurationMojo.java:250) at org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.getProcessedArtifactItems(AbstractFromConfigurationMojo.java:146) at org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:67) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Failure to find
Re: [Dev] API Changes in WSO2 EAM
you can find the actual api by subscribing to an app manually and monitor through wireshark or firebug where the http post goes. On Fri, Sep 5, 2014 at 5:44 PM, Kasun Dissanayake kas...@wso2.com wrote: Hi All, I'm working with test automation in newest WSO2 EAM pack and getting errors in test cases. So I did change the framework according to that. And followings are the errors generated APIs I've changed 1) App create API. 2) APP Publish API. 3) IS configurations. 4) Selenium configurations according to new EAM pack. So because of this I was taking much time for completing the test cases. But I'm now stuck with Subscription API. It is mentioned as follow. backEndUrl+/store/resources/webapp/v1/subscription/app Is this the latest backend API or is it changed ? Cheers -- Kasun Dissanayake Software Engineer WSO2 Inc. Lean | Enterprise | Middleware Tel - +94 77 086 2860 Skype - kasun.dissanayake4 LinkedIn - lk.linkedin.com/in/kasundis/ -- Jenananthan Yogendran *Software Engineer,* *WSO2 inc., http://wso2.com http://wso2.com* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] BAM 4.2.2 build failed [Failure to find org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009]
Hi Thushara, Since patch0009 is not yet released it is not deployed to nexus repo. Due to that reason you may need to build it locally. Thanks, Manoj *Manoj Kumara* Software Engineer WSO2 Inc. http://wso2.com/ *lean.enterprise.middleware* Mobile: +94713448188 On Fri, Sep 5, 2014 at 3:57 AM, Thushara Ranawaka thusha...@wso2.com wrote: Hi, While building BAM 2.4.2 (in turing branch) I overcome a build failure. Kindly find the mvn error log Im getting below. I googled this error and found a resource in wso2 oxygen tank[1]. as per that solution I cant find Kernel patch 0009 (org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009). Where could i find it?. Can someone help me? [1] http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-BAM-4-2-1-build-failed-td93488.html Thanx [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack (2-unpack-kernel-patch) on project wso2bam-p2-profile-gen: Unable to find artifact. Failure to find org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009 in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced [ERROR] [ERROR] Try downloading the file manually from the project website. [ERROR] [ERROR] Then, install it using the command: [ERROR] mvn install:install-file -DgroupId=org.wso2.carbon -DartifactId=WSO2-CARBON-PATCH-4.2.0 -Dversion=0009 -Dpackaging=zip -Dfile=/path/to/file [ERROR] [ERROR] Alternatively, if you host your own repository you can deploy the file there: [ERROR] mvn deploy:deploy-file -DgroupId=org.wso2.carbon -DartifactId=WSO2-CARBON-PATCH-4.2.0 -Dversion=0009 -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] [ERROR] [ERROR] [ERROR] org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009 [ERROR] [ERROR] from the specified remote repositories: [ERROR] wso2-nexus ( http://maven.wso2.org/nexus/content/groups/wso2-public/, releases=true, snapshots=true), [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false) [ERROR] - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack (2-unpack-kernel-patch) on project wso2bam-p2-profile-gen: Unable to find artifact. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to find artifact. at org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.getArtifact(AbstractFromConfigurationMojo.java:250) at org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.getProcessedArtifactItems(AbstractFromConfigurationMojo.java:146) at org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:67) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Failure to find org.wso2.carbon:WSO2-CARBON-PATCH-4.2.0:zip:0009 in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be
Re: [Dev] API Changes in WSO2 EAM
Hi Jenananthan, Yep I've done that. Now API seems to be correct. But still getting that error On Fri, Sep 5, 2014 at 7:02 PM, Jenananthan Yogendran jenanant...@wso2.com wrote: you can find the actual api by subscribing to an app manually and monitor through wireshark or firebug where the http post goes. On Fri, Sep 5, 2014 at 5:44 PM, Kasun Dissanayake kas...@wso2.com wrote: Hi All, I'm working with test automation in newest WSO2 EAM pack and getting errors in test cases. So I did change the framework according to that. And followings are the errors generated APIs I've changed 1) App create API. 2) APP Publish API. 3) IS configurations. 4) Selenium configurations according to new EAM pack. So because of this I was taking much time for completing the test cases. But I'm now stuck with Subscription API. It is mentioned as follow. backEndUrl+/store/resources/webapp/v1/subscription/app Is this the latest backend API or is it changed ? Cheers -- Kasun Dissanayake Software Engineer WSO2 Inc. Lean | Enterprise | Middleware Tel - +94 77 086 2860 Skype - kasun.dissanayake4 LinkedIn - lk.linkedin.com/in/kasundis/ -- Jenananthan Yogendran *Software Engineer,* *WSO2 inc., http://wso2.com http://wso2.com* -- Kasun Dissanayake Software Engineer WSO2 Inc. Lean | Enterprise | Middleware Tel - +94 77 086 2860 Skype - kasun.dissanayake4 LinkedIn - lk.linkedin.com/in/kasundis/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] chunk-13 packs 03/09/2014
Do we have the report? On Thu, Sep 4, 2014 at 10:40 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Ratha, Can you share the integration test result report as well. Thanks, Krishantha. On Wed, Sep 3, 2014 at 4:56 PM, Vijayaratha Vijayasingam rat...@wso2.com wrote: Hi all; Please find packs here https://svn.wso2.org/repos/wso2/scratch/chunk13-release/03-09-2014/ -- -Ratha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- S.Uthaiyashankar VP Engineering WSO2 Inc. http://wso2.com/ - lean . enterprise . middleware Phone: +94 714897591 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Adding new tests-UI module to BRS
What are the test cases we are automating? Can you point to the test case document? On Thu, Sep 4, 2014 at 11:03 AM, Dimuthu De Lanerolle dimut...@wso2.com wrote: Hi, I have started the $subject and will update the progress soon. Regards -- Dimuthu De Lanerolle Software Engineer WSO2 Inc. lean . enterprise . middlewear. http://wso2.com/ Tel. : +94 11 2145345 Fax : +94 11 2145300 email : dimut...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- S.Uthaiyashankar VP Engineering WSO2 Inc. http://wso2.com/ - lean . enterprise . middleware Phone: +94 714897591 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Changes in WSO2 EAM
It seems api has been modified. check the parameters of current api and the parameters used in the subscription test case(we used old pack when we wrote the test cases) they might differ. On Fri, Sep 5, 2014 at 7:40 PM, Kasun Dissanayake kas...@wso2.com wrote: Hi Jenananthan, Yep I've done that. Now API seems to be correct. But still getting that error On Fri, Sep 5, 2014 at 7:02 PM, Jenananthan Yogendran jenanant...@wso2.com wrote: you can find the actual api by subscribing to an app manually and monitor through wireshark or firebug where the http post goes. On Fri, Sep 5, 2014 at 5:44 PM, Kasun Dissanayake kas...@wso2.com wrote: Hi All, I'm working with test automation in newest WSO2 EAM pack and getting errors in test cases. So I did change the framework according to that. And followings are the errors generated APIs I've changed 1) App create API. 2) APP Publish API. 3) IS configurations. 4) Selenium configurations according to new EAM pack. So because of this I was taking much time for completing the test cases. But I'm now stuck with Subscription API. It is mentioned as follow. backEndUrl+/store/resources/webapp/v1/subscription/app Is this the latest backend API or is it changed ? Cheers -- Kasun Dissanayake Software Engineer WSO2 Inc. Lean | Enterprise | Middleware Tel - +94 77 086 2860 Skype - kasun.dissanayake4 LinkedIn - lk.linkedin.com/in/kasundis/ -- Jenananthan Yogendran *Software Engineer,* *WSO2 inc., http://wso2.com http://wso2.com* -- Kasun Dissanayake Software Engineer WSO2 Inc. Lean | Enterprise | Middleware Tel - +94 77 086 2860 Skype - kasun.dissanayake4 LinkedIn - lk.linkedin.com/in/kasundis/ -- Jenananthan Yogendran *Software Engineer,* *WSO2 inc., http://wso2.com http://wso2.com* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] Extract attachment from incoming REST request
Hi,
You can use script mediator or class mediator to implement encoding
mechanism.
Thanks,
Milinda
On Fri, Sep 5, 2014 at 4:43 PM, Ramindu Deshapriya rasad...@gmail.com
wrote:
Hi,
We are sending a request to a through an ESB connector as follows:
{
AddFiles:[{ DocumentName:sick.txt, File: aSBhbSBzaWNr ,
Description:sick }]
}
The File value is the Base64-encoded content of the file.
However, rather than asking the client to send a Base64-encoded string, we
would prefer to get the file along with the REST request sent to the ESB
and
then extract it, Base64-encode it, and add it to the outgoing request to
the
backend.
Is there any way to accomplish this? Or is it advisable to ask the client
to
send a Base64-encoded string?
Thanks.
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-Extract-attachment-from-incoming-REST-request-tp102449.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Milinda Perera
Software Engineer;
WSO2 Inc. http://wso2.com ,
Mobile: (+94) 714 115 032
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Changes in WSO2 EAM
Hi Kasun, On Fri, Sep 5, 2014 at 7:40 PM, Kasun Dissanayake kas...@wso2.com wrote: Yep I've done that. Now API seems to be correct. But still getting that error Post your errors here -- Roshan Wijesena. Senior Software Engineer-WSO2 Inc. Mobile: *+94752126789* Email: ros...@wso2.com *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] chunk-13 packs 03/09/2014
Sure fire reports are committed with build packs. https://svn.wso2.org/repos/wso2/scratch/chunk13-release/04-09-2014/ Thanks. On 5 September 2014 19:58, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Do we have the report? On Thu, Sep 4, 2014 at 10:40 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Ratha, Can you share the integration test result report as well. Thanks, Krishantha. On Wed, Sep 3, 2014 at 4:56 PM, Vijayaratha Vijayasingam rat...@wso2.com wrote: Hi all; Please find packs here https://svn.wso2.org/repos/wso2/scratch/chunk13-release/03-09-2014/ -- -Ratha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- S.Uthaiyashankar VP Engineering WSO2 Inc. http://wso2.com/ - lean . enterprise . middleware Phone: +94 714897591 -- -Ratha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Changes in WSO2 EAM
I suppose you will have to input loggers step by step to figure out the exact point of failure as this is all jaggery code. On 5 Sep 2014 22:01, Roshan Wijesena ros...@wso2.com wrote: Hi Kasun, On Fri, Sep 5, 2014 at 7:40 PM, Kasun Dissanayake kas...@wso2.com wrote: Yep I've done that. Now API seems to be correct. But still getting that error Post your errors here -- Roshan Wijesena. Senior Software Engineer-WSO2 Inc. Mobile: *+94752126789* Email: ros...@wso2.com *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Access-Control-Allow-Methods header not getting set for CORS requests.
Hi Jo, On 5 September 2014 15:19, Joseph Fonseka jos...@wso2.com wrote: Hi In AM 1.7.1 Access-Control-Allow-Methods header is not getting set by the handler. When trouble shooting I found that particular line is commented. was there a reason to remove it ? Yes. When we had this, the configured Access-Control-Allow-Methods header value was completely overriding the actual value sent in the response for that header. As a result if someone checks the Methods supported by the API (with Max-Forwards:0) or the back-end service by sending an OPTIONS call to the API, the value is not correct. Therefore we decided to remove this header and only depend on the Access-Control-Allow-Methods value sent from the back-end service for Swagger call [1]. [1]https://wso2.org/jira/browse/APIMANAGER-2128 If Access-Control-Allow-Methods is not present PUT and DELETE requests will not work in swagger console + other web clients. May be we can check whether actual response contains this header and if not add the header with the methods only exposed by the API's resources. Thanks, Lakmali Thanks Jo -- -- *Joseph Fonseka* WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 772 512 430 skype: jpfonseka * http://lk.linkedin.com/in/rumeshbandara* -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
