Re: [Dev] [ESB] Illegal key size exception from AxisEngine when sending an encrypted request
Hi, Thank you for the response. Previously I had both java 8 and java 7 in my machine, the problem was solved after making java 7 as the default java version. Thanks! Best Regards, On Fri, Jan 30, 2015 at 9:37 AM, Pavithra Madurangi pavit...@wso2.com wrote: Also please refer ESB Installation Prerequisites for more information https://docs.wso2.com/display/ESB481/Installation+Prerequisites On Fri, Jan 30, 2015 at 9:33 AM, Pavithra Madurangi pavit...@wso2.com wrote: As per [1], this happens when you've not installed JCE policy files properly. So please make sure whether - You've placed the two jar files @ $JAVA_HOME/jre/lib/security - As per the special note in [1], if you are running your client through an IDE - and you still gets the above error after applying the provided solution - double check the JAVA_HOME set in the corresponding IDE - and need to patch that corresponding JDK Or if you are running curl commands from terminal try reloading .bashrc [1] http://blog.rampartfaq.com/2009/08/faq-001-javasecurityinvalidkeyexception.html Regards, Pavithra On Wed, Jan 28, 2015 at 10:35 AM, Chathura Priyankara chathu...@wso2.com wrote: Hi, When I'm sending an encrypted request to the proxy service for the sample ESB configuration listed in [1], getting the following error from the AxisEngine. The java version I'm using is 1.7 so I used JCE for Java 7. Is this because of version mismatch of Java ? ERROR engine.AxisEngine: The signature or decryption was invalid; nested exception is: org.apache.xml.security.encryption.XMLEncryptionException: Illegal key size Original Exception was java.security.InvalidKeyException: Illegal key size org.apache.axis2.AxisFault: The signature or decryption was invalid; nested exception is: org.apache.xml.security.encryption.XMLEncryptionException: Illegal key size Original Exception was java.security.InvalidKeyException: Illegal key size at org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180) at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:95) at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340) at org.apache.axis2.engine.Phase.invoke(Phase.java:313) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172) at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:459) at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:279) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.apache.ws.security.WSSecurityException: The signature or decryption was invalid; nested exception is: org.apache.xml.security.encryption.XMLEncryptionException: Illegal key size Original Exception was java.security.InvalidKeyException: Illegal key size at org.apache.ws.security.processor.ReferenceListProcessor.decryptEncryptedData(ReferenceListProcessor.java:258) at org.apache.ws.security.processor.EncryptedKeyProcessor.decryptDataRef(EncryptedKeyProcessor.java:483) at org.apache.ws.security.processor.EncryptedKeyProcessor.handleEncryptedKey(EncryptedKeyProcessor.java:421) at org.apache.ws.security.processor.EncryptedKeyProcessor.handleEncryptedKey(EncryptedKeyProcessor.java:119) at org.apache.ws.security.processor.EncryptedKeyProcessor.handleToken(EncryptedKeyProcessor.java:95) at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:332) at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:249) at org.apache.rampart.RampartEngine.process(RampartEngine.java:214) at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92) ... 11 more [1] https://docs.wso2.com/display/ESB481/Sample+153%3A+Routing+Messages+that+Arrive+to+a+Proxy+Service+without+Processing+Security+Headers -- Chathura Priyankara Software Engineer | WSO2 Inc. Mobile : +94718795340 Blog : www.codeoncloud.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Pavithra Madurangi* Associate Technical Lead - QA. WSO2 Inc.: http://wso2.com/ Mobile: 0777207357 / 0112747089 -- *Pavithra Madurangi* Associate Technical Lead - QA. WSO2 Inc.: http://wso2.com/ Mobile: 0777207357 / 0112747089 -- Chathura Priyankara Software Engineer | WSO2 Inc. Mobile : +94718795340 Blog : www.codeoncloud.blogspot.com ___ Dev mailing list Dev@wso2.org
Re: [Dev] [ESB] Eror Setting up Deployment Synchronizer for Manager Node
Hi Jeewantha, I'll retry with your modifications and update here. Thanks, Maheeka Jayasuriya Software Engineer Mobile : +9450661 On Fri, Jan 30, 2015 at 7:14 PM, Jeewantha Dharmaparakrama jeewan...@wso2.com wrote: Hi Maheeka, I tested Dep synch functionality in ESB 4.9.0 M5 pack and it works fine. I followed the same Clustering guide but with few modifications. 1: Used the exact IP address of my local machine instead of localhost in clustering configs in both ESB nodes 2: In the Manager Node Members section looks like follows. members member hostName10.100.0.17/hostName port4010/port /member /members 4010 is the Group management port configured in ELB. In Worker node members member hostName10.100.0.17/hostName port4010/port /member member hostName10.100.0.17/hostName port4100/port /member /members 4100 is the LocalMemberPort in Manager node. Thanks, Jeewantha On Fri, Jan 30, 2015 at 2:03 PM, Jeewantha Dharmaparakrama jeewan...@wso2.com wrote: Sure will do. Thanks, Jeewantha On Fri, Jan 30, 2015 at 1:56 PM, Kasun Indrasiri ka...@wso2.com wrote: Hi Jeewantha, Seems like that the clustered deployment is not properly working in 4.9 M4. Can you please check. On Fri, Jan 30, 2015 at 8:05 AM, Harsha Thirimanna hars...@wso2.com wrote: Hi, Can you try with putting [1] to dropin ? [1] http://dist.wso2.org/tools/svnkit-1.3.9.wso2v1.jar *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * http://www.apache.org/* *email: **hars...@wso2.com* az...@wso2.com* cell: +94 71 5186770 , +94 * *774617784twitter: **http://twitter.com/ http://twitter.com/afkham_azeez* *harshathirimannlinked-in: **http: http://lk.linkedin.com/in/afkhamazeez**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122* *Lean . Enterprise . Middleware* On Thu, Jan 29, 2015 at 1:54 AM, Aruna Karunarathna ar...@wso2.com wrote: Hi Nirmal, On Thu, Jan 29, 2015 at 3:11 PM, Nirmal Fernando nir...@wso2.com wrote: SVN server has SSLv3 enabled? There was a bug in previous releases which is fixed by now AFAIK. Yesterday, for some testing, I did the same and connected to the intern svn without any issues. Regards, Aruna On Thu, Jan 29, 2015 at 2:49 PM, Maheeka Jayasuriya mahe...@wso2.com wrote: Hi, I am trying to setup an svn deployment synchronizer for ESB when creating a manager node. However when I enable the synchronizer, ESB does not start. I continuously get following warning message at [1]. The configurations in carbon.xml is : DeploymentSynchronizer Enabledtrue/Enabled AutoCommittrue/AutoCommit AutoCheckouttrue/AutoCheckout RepositoryTypesvn/RepositoryType SvnUrl https://svn.wso2.com/wso2/interns/2013/maheeka/esb_svn//SvnUrl SvnUsermahe...@wso2.com/SvnUser SvnPassword***/SvnPassword SvnUrlAppendTenantIdtrue/SvnUrlAppendTenantId /DeploymentSynchronizer I am trying to connect to the intern svn repo. How do I get this working? [1] [2015-01-29 14:20:57,525] INFO - PermissionUpdater Permission cache updated for tenant -1234 [2015-01-29 14:21:57,506] WARN - AppDeployerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService, [2015-01-29 14:21:57,517] WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.service.CappDeploymentService,org.wso2.carbon.server.admin.common.IServerAdmin,org.wso2.carbon.throttling.agent.ThrottlingAgent, [2015-01-29 14:22:57,506] WARN - AppDeployerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService, [2015-01-29 14:22:57,517] WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.service.CappDeploymentService,org.wso2.carbon.server.admin.common.IServerAdmin,org.wso2.carbon.throttling.agent.ThrottlingAgent, [2015-01-29 14:23:57,507] WARN - AppDeployerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService, Thanks, Maheeka Jayasuriya Software Engineer Mobile : +9450661 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team,
Re: [Dev] 'ws' module in jaggery not supported for WSO2 CEP 3.1
On Fri, Jan 30, 2015 at 5:46 PM, Sabra Ossen sa...@wso2.com wrote:
Hi,
Hi Sabra,
I am using wso2 cep 3.1 to deploy a jaggery app to follow the example
mentioned in [1] with a valid wsdl.
The code is as below.
%
var ws = require('ws');
var stub = new ws.WSStub('
http://10.224.112.16:9763/services/Version?wsdl');
%
I included the following jar [2] to the repository/components/dropins
folder to allow 'ws' module support to the cep.
But it gives me the below error.
This is a known issue.. You can see the workaround in jira [1]..
[1] https://wso2.org/jira/browse/CEP-870
Thanks,
Mohan
[2015-01-30 17:40:19,821] ERROR - {WebAppManager}
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
java.net.ConnectException: Connection timed out (/NewTest//index.jag#31)
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
java.net.ConnectException: Connection timed out (/NewTest//index.jag#31)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:571)
at org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
at
org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:536)
at org.jaggeryjs.jaggery.core.JaggeryServlet.doGet(JaggeryServlet.java:24)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
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
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(JaggeryFilter.java:21)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
org.wso2.carbon.tomcat.ext.valves.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:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
java.net.ConnectException: Connection timed out (/NewTest//index.jag#31)
at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:392)
at org.mozilla.javascript.BaseFunction.construct(BaseFunction.java:343)
at org.mozilla.javascript.ScriptRuntime.newObject(ScriptRuntime.java:2349)
at org.jaggeryjs.rhino.NewTest.c0._c_script_0(/NewTest//index.jag:31)
at org.jaggeryjs.rhino.NewTest.c0.call(/NewTest//index.jag)
at
[Dev] Filter user REST url -SCIM
Hi All The following REST invocation should be change to acceptable format. Why do we pass the username (adam) along with the userNameEq constant.? curl -v -k --user admin:admin https: //localhost:9443/wso2/scim/Users?filter=userNameEq*adam* Eg: curl -v -k --user admin:admin https://localhost:9443/wso2/scim/Users/filter?userName=value OR curl -v -k --user admin:admin https://localhost:9443/wso2/scim/Users/filter/username/value [1] https://docs.wso2.com/display/IS500/WSO2+Identity+Server+as+a+SCIM+Service+Provider -Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +1-812-360-5335 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Filter user REST url -SCIM
Hi Ajith, On Sat, Jan 31, 2015 at 2:05 AM, Ajith Vitharana aji...@wso2.com wrote: Hi All The following REST invocation should be change to acceptable format. Why do we pass the username (adam) along with the userNameEq constant.? Eq is the operator to check equal according to SCIM spec. See the 3.2.2.1 in [1] curl -v -k --user admin:admin https: //localhost:9443/wso2/scim/Users?filter=userNameEq*adam* Eg: curl -v -k --user admin:admin https://localhost:9443/wso2/scim/Users/filter?userName=value OR curl -v -k --user admin:admin https://localhost:9443/wso2/scim/Users/filter/username/value [1] https://docs.wso2.com/display/IS500/WSO2+Identity+Server+as+a+SCIM+Service+Provider -Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +1-812-360-5335 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev [1] http://www.simplecloud.info/specs/draft-scim-api-01.html Thanks Isura -- Isura Dilhara Karunaratne Software Engineer Mob +94 772 254 810 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS] Clarifying the code implementation
Hi Lasantha,
On Fri, Jan 30, 2015 at 1:42 AM, Lasitha Wattaladeniya lasit...@wso2.com
wrote:
I'm developing on IS version 5.0.0
On Fri, Jan 30, 2015 at 1:35 AM, Lasitha Wattaladeniya lasit...@wso2.com
wrote:
Hi all,
In the org.wso2.carbon.idp.mgt.ui component the update method in
idp-mgt-edit-local.jsp submits the form to idp-mgt-edit-finish-local.jsp ,
which eventually call the updateResidentIdP method in
org.wso2.carbon.idp.mgt.ui.client.IdentityProviderMgtServiceClient class.
public void updateResidentIdP(IdentityProvider identityProvider) throws
Exception {
try {
idPMgtStub.updateResidentIdP(identityProvider);
} catch (Exception e) {
log.error(e.getMessage(), e);
throw new Exception(Error occurred while retrieving list of
Identity Providers);
}
}
which calls the updateResidentIdP method
in org.wso2.carbon.idp.mgt.IdentityProviderManagementService through the
service stub.
public void updateResidentIdP(IdentityProvider identityProvider)
throws IdentityApplicationManagementException {
// invoking the listeners
ListIdentityProviderMgtLister listerns =
IdpMgtListenerServiceComponent.getListners();
for(IdentityProviderMgtLister listner : listerns) {
listner.updateResidentIdP(identityProvider);
}
String tenantDomain =
CarbonContext.getThreadLocalCarbonContext().getTenantDomain();
IdentityProviderManager.getInstance().updateResidentIdP(identityProvider,
tenantDomain);
}
as you can see , the update method calls each listener's
updateResidentIdp method. Listeners should have registered as an osgi
service with IdentityProviderMgtLister interface.
when I searched for the osgi services registered to that interface , I
could only get one service ,
osgi services (objectclass=*IdentityProviderMgtLister)
{org.wso2.carbon.idp.mgt.listener.IdentityProviderMgtLister}={service.id
=160}
Registered by bundle: org.wso2.carbon.identity.provisioning_4.2.0
[246]
Bundles using service
org.wso2.carbon.idp.mgt_4.2.2 [279]
in the org.wso2.carbon.identity.provisioning component , implementation
of IdentityProviderMgtLister interface is
the IdentityProviderMgtProvisioningListener class. which has the following
method ,
@Override
public void updateResidentIdP(IdentityProvider identityProvider) {
log.debug(update Resident Identity Provider event received);
}
which does nothing, so my question is,
aren't there any other implementations of IdentityProviderMgtLister ?
AFAIK there is no other implementations of IdentityProviderMgtListner
is it updating only through this method ,
IdentityProviderManager.getInstance().updateResidentIdP(identityProvider,
tenantDomain); ?
Yes. Resident service provider is currently updating through only
IdentityProviderManager.getInstance().updateResidentIdP(identityProvider,
tenantDomain) method.
--
Lasitha Wattaladeniya
Software Engineer
WSO2, Inc. | http://wso2.com
lean. enterprise. middleware
Mobile : +94719397528
Blog : techreadme.blogspot.com
--
Lasitha Wattaladeniya
Software Engineer
WSO2, Inc. | http://wso2.com
lean. enterprise. middleware
Mobile : +94719397528
Blog : techreadme.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Isura Dilhara Karunaratne
Software Engineer
Mob +94 772 254 810
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Filter user REST url -SCIM
On Fri, Jan 30, 2015 at 8:59 PM, Isura Karunaratne is...@wso2.com wrote: Hi Ajith, On Sat, Jan 31, 2015 at 2:05 AM, Ajith Vitharana aji...@wso2.com wrote: Hi All The following REST invocation should be change to acceptable format. Why do we pass the username (adam) along with the userNameEq constant.? Eq is the operator to check equal according to SCIM spec. See the 3.2.2.1 in [1] If so fine, but then do we need to append the value to that ? -Ajith curl -v -k --user admin:admin https: //localhost:9443/wso2/scim/Users?filter=userNameEq*adam* Eg: curl -v -k --user admin:admin https://localhost:9443/wso2/scim/Users/filter?userName=value OR curl -v -k --user admin:admin https://localhost:9443/wso2/scim/Users/filter/username/value [1] https://docs.wso2.com/display/IS500/WSO2+Identity+Server+as+a+SCIM+Service+Provider -Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +1-812-360-5335 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev [1] http://www.simplecloud.info/specs/draft-scim-api-01.html Thanks Isura -- Isura Dilhara Karunaratne Software Engineer Mob +94 772 254 810 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +1-812-360-5335 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error, build the connector external pom
Hi Sabashan, I think there's a issue with parent pom. can you please mention the steps you followed during the process ? +1 for suhan's recommendation. and make sure you have correctly version running in CLI/terminal with mvn -version. Regards, On Fri, Jan 30, 2015 at 12:29 PM, Suhan Dharmasuriya suh...@wso2.com wrote: Hi Sabashan, It is recommended to use Apache Maven versions *3.0.* * e.g.: [1]. [1] https://docs.wso2.com/display/AM180/Installation+Prerequisites Thanks, Suhan On Fri, Jan 30, 2015 at 12:04 PM, Shiva Balachandran sh...@wso2.com wrote: Hi Sabashan, This might be due to your java version being 1.7, try building with 1.6 version. Thank you. Regards Shiva Balachandran On Thu, Jan 29, 2015 at 5:15 PM, Sabashan Baladevan sabashan...@gmail.com wrote: Hi all, My environment is . Apache Maven *3.2.3* (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-12T02:28:10+05:30) Maven home: /home/sabashan/apache-maven-3.2.3 Java version: *1.7*.0_76, vendor: *Oracle Corporation* Java home: /usr/lib/jvm/java-7-oracle/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.13.0-44-generic, arch: amd64, family: unix - I got the following error while I build the *cloud connectors' external pom * but, I have built *integration-base* pom *successfully* Error logs: org.apache.maven.project.ProjectBuildingException:* Some problems* were encountered while processing the POMs: at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:416) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:663) at org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:654) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:243) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Thanks Regards, Sabashan ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Shiva Balachandran Software Engineer WSO2 Inc. Mobile - +94 774445788 Blog - https://shivabalachandran.wordpress.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Suhan Dharmasuriya Software Engineer - Test Automation *WSO2, Inc. * lean . enterprise . middleware Tel: +94 112 145345 Mob: +94 779 869138 Blog: http://suhan-opensource.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Applying new design to ES publisher app
@Shiva, it will be HTML5/css3 since we are developing on top of Bootstrap. I like this design and with the Open Sans font typology aspect seems to be good as well. There is a slight concern regarding the main blue colour. The logo colour use in the wso2.com is green. But current colour seems nice for the product rather than going for the logo green colour. We can leave out green and use the existing colour since we are not going to use that logo with the applications. We only use that logo in the Carbon web console. thanks, Chanaka On Fri, Jan 30, 2015 at 12:20 PM, Dhanuka De Silva dhanu...@wso2.com wrote: Thanks Shiva We will need to establish branding for ES first so then it can be applied as the theme. And Sharon, will be coming up with UXD/Visual Designs for ES Public facing part (At the moment its at the wireframing stage) and we will publish once they are available. Would like to hear options! and always appreciate your opinion and feedback. Cheers On Fri, Jan 30, 2015 at 12:10 PM, Shiva Balachandran sh...@wso2.com wrote: Its actually a brilliant mixture! :) Looks very sleek and trendy, Just an opinion, what about integrating a bit of wso2 colors or ES colors into the theme? On Fri, Jan 30, 2015 at 12:05 PM, Dhanuka De Silva dhanu...@wso2.com wrote: Hi Shiva Thanks for your feedback.. Well its a combination of both Windows 8 (formerly Metro) and MS Sharepoint 2013 adding slight variations into their guidelines improvising more on flat design (over skeuomorphic design) Cheers On Fri, Jan 30, 2015 at 11:57 AM, Shiva Balachandran sh...@wso2.com wrote: Hi Dhanuka, The New Design/Html looks good, Chanaka, out of curiosity, Are we going to be using HTML5/CSS3? Also, the UI/UX reminds me of Windows Metro or of Sharepoint 2013. Is there a specific design/theme we are adhering to? Any guidelines. Thank you Regards, Shiva Balachandran On Fri, Jan 30, 2015 at 11:27 AM, Chanaka Jayasena chan...@wso2.com wrote: Thanks Dhanuka for the designs, Will apply them. Cheers, Chanaka On Fri, Jan 30, 2015 at 11:21 AM, Dhanuka De Silva dhanu...@wso2.com wrote: Hi Chanaka Apologies for the delay!.. Here are the remaining set of designs to be integrated (Add/Edit and Overview of Assets). Feel free to talk to me if you need any help clarifying any of these. Cheers On Mon, Jan 26, 2015 at 12:02 PM, Chanaka Jayasena chan...@wso2.com wrote: Hi all, I have started working on applying the new design/html [1] provided by Dhanuka to Enterprise Store 2.0 replacing the current design [2]. This is to track the progress of it. thanks, Chanaka -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com -- Dhanuka De Silva m: +94 773 887816 e: dhanu...@wso2.com w: http://www.wso2.com -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Shiva Balachandran Software Engineer WSO2 Inc. Mobile - +94 774445788 Blog - https://shivabalachandran.wordpress.com/ -- Dhanuka De Silva m: +94 773 887816 e: dhanu...@wso2.com w: http://www.wso2.com -- Shiva Balachandran Software Engineer WSO2 Inc. Mobile - +94 774445788 Blog - https://shivabalachandran.wordpress.com/ -- Dhanuka De Silva m: +94 773 887816 e: dhanu...@wso2.com w: http://www.wso2.com -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] Eror Setting up Deployment Synchronizer for Manager Node
Hi Jeewantha, Seems like that the clustered deployment is not properly working in 4.9 M4. Can you please check. On Fri, Jan 30, 2015 at 8:05 AM, Harsha Thirimanna hars...@wso2.com wrote: Hi, Can you try with putting [1] to dropin ? [1] http://dist.wso2.org/tools/svnkit-1.3.9.wso2v1.jar *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * http://www.apache.org/* *email: **hars...@wso2.com* az...@wso2.com* cell: +94 71 5186770 , +94 * *774617784twitter: **http://twitter.com/ http://twitter.com/afkham_azeez* *harshathirimannlinked-in: **http: http://lk.linkedin.com/in/afkhamazeez**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122* *Lean . Enterprise . Middleware* On Thu, Jan 29, 2015 at 1:54 AM, Aruna Karunarathna ar...@wso2.com wrote: Hi Nirmal, On Thu, Jan 29, 2015 at 3:11 PM, Nirmal Fernando nir...@wso2.com wrote: SVN server has SSLv3 enabled? There was a bug in previous releases which is fixed by now AFAIK. Yesterday, for some testing, I did the same and connected to the intern svn without any issues. Regards, Aruna On Thu, Jan 29, 2015 at 2:49 PM, Maheeka Jayasuriya mahe...@wso2.com wrote: Hi, I am trying to setup an svn deployment synchronizer for ESB when creating a manager node. However when I enable the synchronizer, ESB does not start. I continuously get following warning message at [1]. The configurations in carbon.xml is : DeploymentSynchronizer Enabledtrue/Enabled AutoCommittrue/AutoCommit AutoCheckouttrue/AutoCheckout RepositoryTypesvn/RepositoryType SvnUrlhttps://svn.wso2.com/wso2/interns/2013/maheeka/esb_svn/ /SvnUrl SvnUsermahe...@wso2.com/SvnUser SvnPassword***/SvnPassword SvnUrlAppendTenantIdtrue/SvnUrlAppendTenantId /DeploymentSynchronizer I am trying to connect to the intern svn repo. How do I get this working? [1] [2015-01-29 14:20:57,525] INFO - PermissionUpdater Permission cache updated for tenant -1234 [2015-01-29 14:21:57,506] WARN - AppDeployerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService, [2015-01-29 14:21:57,517] WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.service.CappDeploymentService,org.wso2.carbon.server.admin.common.IServerAdmin,org.wso2.carbon.throttling.agent.ThrottlingAgent, [2015-01-29 14:22:57,506] WARN - AppDeployerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService, [2015-01-29 14:22:57,517] WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.service.CappDeploymentService,org.wso2.carbon.server.admin.common.IServerAdmin,org.wso2.carbon.throttling.agent.ThrottlingAgent, [2015-01-29 14:23:57,507] WARN - AppDeployerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService, Thanks, Maheeka Jayasuriya Software Engineer Mobile : +9450661 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Aruna Sujith Karunarathna* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 9040362 | Work: +94 112145345 Email: ar...@wso2.com | Web: www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] Eror Setting up Deployment Synchronizer for Manager Node
Sure will do. Thanks, Jeewantha On Fri, Jan 30, 2015 at 1:56 PM, Kasun Indrasiri ka...@wso2.com wrote: Hi Jeewantha, Seems like that the clustered deployment is not properly working in 4.9 M4. Can you please check. On Fri, Jan 30, 2015 at 8:05 AM, Harsha Thirimanna hars...@wso2.com wrote: Hi, Can you try with putting [1] to dropin ? [1] http://dist.wso2.org/tools/svnkit-1.3.9.wso2v1.jar *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * http://www.apache.org/* *email: **hars...@wso2.com* az...@wso2.com* cell: +94 71 5186770 , +94 * *774617784twitter: **http://twitter.com/ http://twitter.com/afkham_azeez* *harshathirimannlinked-in: **http: http://lk.linkedin.com/in/afkhamazeez**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122* *Lean . Enterprise . Middleware* On Thu, Jan 29, 2015 at 1:54 AM, Aruna Karunarathna ar...@wso2.com wrote: Hi Nirmal, On Thu, Jan 29, 2015 at 3:11 PM, Nirmal Fernando nir...@wso2.com wrote: SVN server has SSLv3 enabled? There was a bug in previous releases which is fixed by now AFAIK. Yesterday, for some testing, I did the same and connected to the intern svn without any issues. Regards, Aruna On Thu, Jan 29, 2015 at 2:49 PM, Maheeka Jayasuriya mahe...@wso2.com wrote: Hi, I am trying to setup an svn deployment synchronizer for ESB when creating a manager node. However when I enable the synchronizer, ESB does not start. I continuously get following warning message at [1]. The configurations in carbon.xml is : DeploymentSynchronizer Enabledtrue/Enabled AutoCommittrue/AutoCommit AutoCheckouttrue/AutoCheckout RepositoryTypesvn/RepositoryType SvnUrl https://svn.wso2.com/wso2/interns/2013/maheeka/esb_svn//SvnUrl SvnUsermahe...@wso2.com/SvnUser SvnPassword***/SvnPassword SvnUrlAppendTenantIdtrue/SvnUrlAppendTenantId /DeploymentSynchronizer I am trying to connect to the intern svn repo. How do I get this working? [1] [2015-01-29 14:20:57,525] INFO - PermissionUpdater Permission cache updated for tenant -1234 [2015-01-29 14:21:57,506] WARN - AppDeployerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService, [2015-01-29 14:21:57,517] WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.service.CappDeploymentService,org.wso2.carbon.server.admin.common.IServerAdmin,org.wso2.carbon.throttling.agent.ThrottlingAgent, [2015-01-29 14:22:57,506] WARN - AppDeployerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService, [2015-01-29 14:22:57,517] WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.service.CappDeploymentService,org.wso2.carbon.server.admin.common.IServerAdmin,org.wso2.carbon.throttling.agent.ThrottlingAgent, [2015-01-29 14:23:57,507] WARN - AppDeployerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService, Thanks, Maheeka Jayasuriya Software Engineer Mobile : +9450661 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Aruna Sujith Karunarathna* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 9040362 | Work: +94 112145345 Email: ar...@wso2.com | Web: www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/ -- Jeewantha Dharmaparakrama Software Engineer; WSO2, Inc.; http://wso2.com/ Phone : (+94) 778403757 Blog: http://jeewanthad.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] Eror Setting up Deployment Synchronizer for Manager Node
Hi Maheeka, I tested Dep synch functionality in ESB 4.9.0 M5 pack and it works fine. I followed the same Clustering guide but with few modifications. 1: Used the exact IP address of my local machine instead of localhost in clustering configs in both ESB nodes 2: In the Manager Node Members section looks like follows. members member hostName10.100.0.17/hostName port4010/port /member /members 4010 is the Group management port configured in ELB. In Worker node members member hostName10.100.0.17/hostName port4010/port /member member hostName10.100.0.17/hostName port4100/port /member /members 4100 is the LocalMemberPort in Manager node. Thanks, Jeewantha On Fri, Jan 30, 2015 at 2:03 PM, Jeewantha Dharmaparakrama jeewan...@wso2.com wrote: Sure will do. Thanks, Jeewantha On Fri, Jan 30, 2015 at 1:56 PM, Kasun Indrasiri ka...@wso2.com wrote: Hi Jeewantha, Seems like that the clustered deployment is not properly working in 4.9 M4. Can you please check. On Fri, Jan 30, 2015 at 8:05 AM, Harsha Thirimanna hars...@wso2.com wrote: Hi, Can you try with putting [1] to dropin ? [1] http://dist.wso2.org/tools/svnkit-1.3.9.wso2v1.jar *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * http://www.apache.org/* *email: **hars...@wso2.com* az...@wso2.com* cell: +94 71 5186770 , +94 * *774617784twitter: **http://twitter.com/ http://twitter.com/afkham_azeez* *harshathirimannlinked-in: **http: http://lk.linkedin.com/in/afkhamazeez**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122* *Lean . Enterprise . Middleware* On Thu, Jan 29, 2015 at 1:54 AM, Aruna Karunarathna ar...@wso2.com wrote: Hi Nirmal, On Thu, Jan 29, 2015 at 3:11 PM, Nirmal Fernando nir...@wso2.com wrote: SVN server has SSLv3 enabled? There was a bug in previous releases which is fixed by now AFAIK. Yesterday, for some testing, I did the same and connected to the intern svn without any issues. Regards, Aruna On Thu, Jan 29, 2015 at 2:49 PM, Maheeka Jayasuriya mahe...@wso2.com wrote: Hi, I am trying to setup an svn deployment synchronizer for ESB when creating a manager node. However when I enable the synchronizer, ESB does not start. I continuously get following warning message at [1]. The configurations in carbon.xml is : DeploymentSynchronizer Enabledtrue/Enabled AutoCommittrue/AutoCommit AutoCheckouttrue/AutoCheckout RepositoryTypesvn/RepositoryType SvnUrl https://svn.wso2.com/wso2/interns/2013/maheeka/esb_svn//SvnUrl SvnUsermahe...@wso2.com/SvnUser SvnPassword***/SvnPassword SvnUrlAppendTenantIdtrue/SvnUrlAppendTenantId /DeploymentSynchronizer I am trying to connect to the intern svn repo. How do I get this working? [1] [2015-01-29 14:20:57,525] INFO - PermissionUpdater Permission cache updated for tenant -1234 [2015-01-29 14:21:57,506] WARN - AppDeployerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService, [2015-01-29 14:21:57,517] WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.service.CappDeploymentService,org.wso2.carbon.server.admin.common.IServerAdmin,org.wso2.carbon.throttling.agent.ThrottlingAgent, [2015-01-29 14:22:57,506] WARN - AppDeployerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService, [2015-01-29 14:22:57,517] WARN - StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.service.CappDeploymentService,org.wso2.carbon.server.admin.common.IServerAdmin,org.wso2.carbon.throttling.agent.ThrottlingAgent, [2015-01-29 14:23:57,507] WARN - AppDeployerServiceComponent Waiting for required OSGi services: org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService, Thanks, Maheeka Jayasuriya Software Engineer Mobile : +9450661 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Aruna Sujith Karunarathna* | Software Engineer
[Dev] Inconsistent behavior of UserCoreUtil methods
Hi,
In UserCoreUtil [1] there are two methods to remove user store domain from
given name. Those two methods have Inconsistent behavior.
public static String removeDomainFromName(String name) {
int index;
if ((index = name.indexOf(CarbonConstants.DOMAIN_SEPARATOR)) = 0) {
// remove domain name if exist
name = name.substring(index + 1);
}
return name;
}
Here name which is having 'Internal/' is not treated as a special case and
just remove 'Internal/' from name.
public static String[] removeDomainFromNames(String[] names) {
ListString nameList = new ArrayListString();
int index;
if (names != null names.length != 0) {
for (String name : names) {
if ((index =
name.indexOf(UserCoreConstants.DOMAIN_SEPARATOR)) 0) {
String domain = name.substring(0, index);
if
(!UserCoreConstants.INTERNAL_DOMAIN.equalsIgnoreCase(domain)) {
// remove domain name if exist
nameList.add(name.substring(index + 1));
} else {
nameList.add(name);
}
}
}
}
if (nameList.size() != 0) {
return nameList.toArray(new String[nameList.size()]);
} else {
return names;
}
}
Here even though there is a consideration for 'Internal/' names which are
not having domain separator will be removed from return list.
IMO correct implementation should be removeDomainFromNames(String[] names)
invokes removeDomainFromName(String names) and inside
removeDomainFromName(String names) take 'Internal/' into consideration.
WDYT?
[1]
https://github.com/wso2/carbon4-kernel/blob/master/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/util/UserCoreUtil.java
--
Gayan Gunawardana
Software Engineer; WSO2 Inc.; http://wso2.com/
Email: ga...@wso2.com
Mobile: +94 (71) 8020933
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [G-Reg] Dependency Graph UI Implementation Summary
*Status Update, * - Dependency Graph UI implementation Phase 2 (Extra Features) - Research on D3 force directed graph zoom out to fit screen position center - Complete! - Develop function to zoom out graph fit to screen - Complete! - Improving zoom out graph to fit screen function to auto center - Complete! - Graph outer click, close detail view window - Complete! - Research on svg print methods - Working on - Implementing function to print generated svg graph - Working on - Other UI style tweaks - Complete! Thanks, Jerad On Tue, Jan 27, 2015 at 2:29 PM, Jerad Rutnam je...@wso2.com wrote: This is should be added to *Dependency Graph** UI implementation Phase 2* (Extra Features) - Graph outer click, close detail view window - Complete! On Tue, Jan 27, 2015 at 12:41 PM, Jerad Rutnam je...@wso2.com wrote: Hi, Please find below the tasks complete and pending on G-Reg dependency graph UI implementation, - UXD for Impact Analysis view (Dependency Graph) - Gathering requirements documentation - Complete! - Research on best practise to show dependency etc ... - Complete! - Fixing UI issues on current feature (which is developed already) - Complete! - Designing new interface - Complete! - Deciding on improvements features needs to add - Complete! - Understanding learning D3 library basics - Complete! - Dependency Graph UI implementation Phase 1 (Basic Features) - Implementing basic UI design - Complete! - Making the graph screen responsive - Complete! - Tweaking resource locate feature and styling - Complete! - Develop function to on resource single click detailed view - Complete! - Styling on resource double click highlighting resource closes connections - Complete! - Develop function to parent resource highlight - Complete! - Resource relationship tool-tip styling - Complete! - Implementing function: Icons for common resources with standard icon for phase 1 - Complete! - Dependency Graph UI implementation Phase 2 (Extra Features) - Research on D3 force directed graph zoom out to fit screen position center - Working on - Develop function to zoom out graph fit to screen - Complete! - Improving zoom out graph to fit screen function to auto center - Working on - Research on svg print methods - Working on - Implementing function to print generated svg graph - Pending - Other UI style tweaks - Working on - Dependency Graph UI implementation Phase 3 (Improve Features) - Deciding designing icon set for middleware resources - Pending - Making a glyph-icon font using the designed icon set - Pending - Dependency Graph UI implementation Phase 4 (Feature Issues Fixing) - Research for a workaround solution to fix text overlapping - Working on - Implementing function to fix text overlapping - Pending - Research on solution for svg z-indexing - Working on - Develop function to z-index (layer up) resources on double click highlight - Pending - Additional UI style tweaks - Pending I will update back if I missed anything to add here. Other than that, i'm planing on completing the task list on Phase 2 early as possible. Thinking it will take maximum 1 1/2 weeks in worst comes. As i'm still stuck with graph centering issue searching for a work-around for it. Thanks, Jerad -- *Jerad Rutnam* *Software Engineer - UI* WSO2 Inc. lean | enterprise | middleware M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com -- *Jerad Rutnam* *Software Engineer - UI* WSO2 Inc. lean | enterprise | middleware M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com -- *Jerad Rutnam* *Software Engineer* WSO2 Inc. lean | enterprise | middleware M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] 'ws' module in jaggery not supported for WSO2 CEP 3.1
Hi,
I am using wso2 cep 3.1 to deploy a jaggery app to follow the example
mentioned in [1] with a valid wsdl.
The code is as below.
%
var ws = require('ws');
var stub = new ws.WSStub('
http://10.224.112.16:9763/services/Version?wsdl');
%
I included the following jar [2] to the repository/components/dropins
folder to allow 'ws' module support to the cep.
But it gives me the below error.
[2015-01-30 17:40:19,821] ERROR - {WebAppManager}
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
java.net.ConnectException: Connection timed out (/NewTest//index.jag#31)
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
java.net.ConnectException: Connection timed out (/NewTest//index.jag#31)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:571)
at org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
at
org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:536)
at org.jaggeryjs.jaggery.core.JaggeryServlet.doGet(JaggeryServlet.java:24)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
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
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(JaggeryFilter.java:21)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
org.wso2.carbon.tomcat.ext.valves.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:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
java.net.ConnectException: Connection timed out (/NewTest//index.jag#31)
at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:392)
at org.mozilla.javascript.BaseFunction.construct(BaseFunction.java:343)
at org.mozilla.javascript.ScriptRuntime.newObject(ScriptRuntime.java:2349)
at org.jaggeryjs.rhino.NewTest.c0._c_script_0(/NewTest//index.jag:31)
at org.jaggeryjs.rhino.NewTest.c0.call(/NewTest//index.jag)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
at org.jaggeryjs.rhino.NewTest.c0.call(/NewTest//index.jag)
at org.jaggeryjs.rhino.NewTest.c0.exec(/NewTest//index.jag)
at
