On Tue, Apr 19, 2011 at 7:58 PM, Hiranya Jayathilaka <hira...@wso2.com>wrote:
> Hi Amila, > > It seems we cannot add hierarchical subscriptions for registry collections. > I get the following exception from the event component. My topic > is /registry/notifications/_system/config/repository/deployment/server/#. > The '#' at the end was added because I need to receive events related to all > child resources. > I added regular expression to validate topic names, so This is caused by that, I will correct it. Thank you. > > org.wso2.carbon.event.core.exception.EBRuntimeException: Topic name > /registry/notifications/_system/config/repository/deployment/server/# is not > a valid topic name. Only alphanumeric characters, hyphens (-), and > underscores (_) are allowed. > at > org.wso2.carbon.event.core.internal.topic.registry.RegistryTopicManager.addTopic(RegistryTopicManager.java:96) > at > org.wso2.carbon.event.core.internal.CarbonEventBroker.subscribe(CarbonEventBroker.java:89) > at > org.wso2.carbon.registry.eventing.services.EventingServiceImpl.subscribe(EventingServiceImpl.java:215) > at > org.wso2.carbon.deployment.synchronizer.util.Utils.subscribeForRegistryEventing(Utils.java:110) > at > org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizer.start(DeploymentSynchronizer.java:95) > at > org.wso2.carbon.deployment.synchronizer.services.DeploymentSynchronizerAdmin.enableSynchronizerForCarbonRepository(DeploymentSynchronizerAdmin.java:48) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212) > at > org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66) > at > org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181) > at > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172) > at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146) > at > org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:206) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:641) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) > at > org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) > at > org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) > at > org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) > at org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:155) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164) > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:498) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) > at org.wso2.carbon.server.TomcatServer$1.invoke(TomcatServer.java:242) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:562) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:394) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:391) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:357) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1531) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > > Thanks, > Hiranya > > > On Tue, Apr 19, 2011 at 4:37 PM, Hiranya Jayathilaka <hira...@wso2.com>wrote: > >> >> >> On Tue, Apr 19, 2011 at 12:23 AM, Senaka Fernando <sen...@wso2.com>wrote: >> >>> Hi Hiranya, >>> >>> On Mon, Apr 18, 2011 at 8:53 PM, Hiranya Jayathilaka >>> <hira...@wso2.com>wrote: >>> >>>> Hi Amila, Senaka, >>>> >>>> Is $subject available in the trunk? I'd like to get on with the rest of >>>> the deployment-synchronizer impl. >>>> >>> >>> This has been partially available, for SOAP and XML/REST notifications. >>> >> >> That's good enough for my requirement. I'll be subscribing through a piece >> of Java code. Can you please provide me a sample code segment which shows >> how to subscribe to a particular collection? I want to get notified on all >> possible changes in the given collection, its child resources, child >> collections and their children as well. >> >> Thanks, >> Hiranya >> >> >>> There was limitation for E-mail based notifications, where it was not >>> possible to identify the exact topic to which the event was published, since >>> a hierarchical subscription would match multiple topics. With the most >>> recent improvements done to the event component, where we can store >>> key-value pairs against messages, this too can be fixed. >>> >>> However, these are not yet available at the UI-level and these have not >>> been tested. Let's have a look tomorrow. >>> >>> Thanks, >>> Senaka. >>> >>>> >>>> Thanks >>>> -- >>>> Hiranya Jayathilaka >>>> Senior Software Engineer; >>>> WSO2 Inc.; http://wso2.org >>>> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >>>> Blog: http://techfeast-hiranya.blogspot.com >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> Carbon-dev@wso2.org >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> >>> -- >>> *Senaka Fernando* >>> Product Manager - WSO2 Governance Registry; >>> Associate Technical Lead; WSO2, Inc.; http://wso2.com* >>> Member; Apache Software Foundation; http://apache.org >>> >>> E-mail: senaka AT wso2.com >>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>> Linked-In: http://www.linkedin.com/in/senakafernando >>> >>> *Lean . Enterprise . Middleware >>> >>> >> >> >> -- >> Hiranya Jayathilaka >> Senior Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> > > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
