Re: [Carbon-dev] Compilation failure in RegistryBasedSynapseConfigBuilder.java
Supun Kamburugamuwa wrote: > Fixed in the trunk. This is due to another API change in Synapse. Hhmmm... Yeah. I did it purposely, forgot to fix the ESB bit :-( thanks Supun for fixing it. Ruwan > > Supun.. > > On Thu, Aug 27, 2009 at 10:46 PM, Chamara Silva <mailto:cham...@wso2.com>> wrote: > > There is any compilation failure in carbon component > RegistryBasedSynapseConfigBuilder.java class > > http://builder.wso2.org/browse/CARBONTRNK-CARBONCOMPONENTS-4/log > > Thank you, > Regards, > Chamara > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Allowing capability of editing sequences inside eclipse
Sanjiva Weerawarana wrote: > On Thu, Sep 10, 2009 at 8:50 AM, Saminda Wijeratne <mailto:samin...@wso2.com>> wrote: > > Also, you're bringing up a UI bundle right? Where does the > HTTP communication come in (sorry for the dumb question!). > > > All the requests go through handleSecurity method in the ui > bundle. One operation in this handleSecurity method is, if the > request isn't secure then decide if we should continue allowing > http access or redirect to https access. (There was a policy to > have only https access with a few exceptions for http access. the > few exceptions are defined in this method) > > > I think we're doing this the wrong way. If we're bringing up the > bundle, why aren't we using OSGi to talk to it directly without going > thru HTTP? Basically, use the same technique we've used to avoid > making HTTP calls when the frondend and backend servers are in the > same JVM. Yes... exactly the tooling team should be using a different back end OSGi service for this (eclipse tools), and that shouldn't go through any of these... am I missing anything? If you remember we implemented a different OSGi service and registered that with the ISequenceAdmin interface so that the Eclipse editor UI should directly call that OSGi service in-vm. Thanks, Ruwan > > Sanjiva. > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com <mailto:sanj...@wso2.com>; cell: +1 650 265 > 8311 | +94 77 787 6880 > blog: http://sanjiva.weerawarana.org/ > > The Open Source SOA Company > > > _______ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Allowing capability of editing sequences inside eclipse
Saminda Wijeratne wrote: > > > On Thu, Sep 10, 2009 at 8:53 AM, Sanjiva Weerawarana <mailto:sanj...@wso2.com>> wrote: > > On Thu, Sep 10, 2009 at 8:50 AM, Saminda Wijeratne > mailto:samin...@wso2.com>> wrote: > > Also, you're bringing up a UI bundle right? Where does the > HTTP communication come in (sorry for the dumb question!). > > > All the requests go through handleSecurity method in the ui > bundle. One operation in this handleSecurity method is, if the > request isn't secure then decide if we should continue > allowing http access or redirect to https access. (There was a > policy to have only https access with a few exceptions for > http access. the few exceptions are defined in this method) > > > I think we're doing this the wrong way. If we're bringing up the > bundle, why aren't we using OSGi to talk to it directly without > going thru HTTP? Basically, use the same technique we've used to > avoid making HTTP calls when the frondend and backend servers are > in the same JVM. > > > Bit confused here. The sequence/proxy/endpoint editors are web editors > right? They can only be accessed through the web browser control > AFAIK. Am I missing something here? OK... this is about rendering the UI not the back end call right??. So this is basically an issue in rendering the front end :-) Thanks, Ruwan > > Saminda > > > Sanjiva. > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com <mailto:sanj...@wso2.com>; cell: +1 650 > 265 8311 | +94 77 787 6880 > blog: http://sanjiva.weerawarana.org/ > > The Open Source SOA Company > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > -------- > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Allowing capability of editing sequences inside eclipse
Saminda Wijeratne wrote: > > > On Thu, Sep 10, 2009 at 9:43 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Saminda Wijeratne wrote: > > > > > > On Thu, Sep 10, 2009 at 8:53 AM, Sanjiva Weerawarana > mailto:sanj...@wso2.com> > > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com>>> wrote: > > > > On Thu, Sep 10, 2009 at 8:50 AM, Saminda Wijeratne > > mailto:samin...@wso2.com> > <mailto:samin...@wso2.com <mailto:samin...@wso2.com>>> wrote: > > > > Also, you're bringing up a UI bundle right? Where > does the > > HTTP communication come in (sorry for the dumb > question!). > > > > > > All the requests go through handleSecurity method in the ui > > bundle. One operation in this handleSecurity method is, > if the > > request isn't secure then decide if we should continue > > allowing http access or redirect to https access. (There > was a > > policy to have only https access with a few exceptions for > > http access. the few exceptions are defined in this method) > > > > > > I think we're doing this the wrong way. If we're bringing up the > > bundle, why aren't we using OSGi to talk to it directly without > > going thru HTTP? Basically, use the same technique we've used to > > avoid making HTTP calls when the frondend and backend > servers are > > in the same JVM. > > > > > > Bit confused here. The sequence/proxy/endpoint editors are web > editors > > right? They can only be accessed through the web browser control > > AFAIK. Am I missing something here? > OK... this is about rendering the UI not the back end call right??. So > this is basically an issue in rendering the front end :-) > > Yes. Our tooling requirements from front-end for now is only for the > web editors. > Rather than having a single parameter in carbon.xml it would be useful > in the long run if we allow to specify url patterns (most probably > like regular expressions) so that if for someone wants to allow http > access only to specific set of urls it is possible to do so without > allowing http access to everything. WDYT? +1, ideally we should have done that with the earlier releases as well. For example /registry like paths are skipped by hard coding them in the source code. So by making this configurable we can remove that hard coded set of URLs and make them configurations. BTW: on Eclipse, I don't see any security risk... and you should be skipping everything. If you are going to implement this, please make sure you allow regular expressions for the URL patterns. Thanks, Ruwan > > Saminda > > > Thanks, > Ruwan > > > > Saminda > > > > > > Sanjiva. > > -- > > Sanjiva Weerawarana, Ph.D. > > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > > email: sanj...@wso2.com <mailto:sanj...@wso2.com> > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com>>; cell: +1 650 > > 265 8311 | +94 77 787 6880 > > blog: http://sanjiva.weerawarana.org/ > > > > The Open Source SOA Company > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 341 3097 > blog: http://blog.ruwan.org > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] RegistryEventingService exception - unable to send
ansportSender.java:222) > > at > > > > org.apache.axis2.engine.AxisEngine$TransportNonBlockingInvocationWorker.run(AxisEngine.java:624) > > at > > > > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) > > at > > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) > > at java.lang.Thread.run(Thread.java:595) > > [2009-09-11 22:32:54,625] INFO - > [MessageContext: > > logID=urn:uuid:6E78D86FEE9218F7051252733627649] > > Connection refused: > > connect > > [2009-09-11 22:32:54,671] INFO - > [MessageContext: > > logID=urn:uuid:6E78D86FEE9218F7051252733627696] > > Connection refused: > > connect > > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> > > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > > -- > > Sanjiva Weerawarana, Ph.D. > > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > > email: sanj...@wso2.com <mailto:sanj...@wso2.com> > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com>>; cell: +1 > > 650 265 8311 | +94 77 787 6880 > > blog: http://sanjiva.weerawarana.org/ > > > > The Open Source SOA Company > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> > > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > > -- > > Samisa Abeysinghe > > Director, Engineering - WSO2 Inc. > > > > http://www.wso2.com/ - "The Open Source SOA Company" > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com <mailto:hira...@wso2.com>; Mobile: +94 > 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon 2.0.2 release plan
+1 Ruwan Afkham Azeez wrote: > Hi Folks, > For Carbon 2.0.2 I think we need to focus on the following items along > with a few selected bug fixes. > > 1. Fix all failing interop tests/write new interop tests for the new > scenarios > 2. Make OSGi (almost) completely transparent from the user > 2.1 Make Axis2 artifact deployment completely independent from OSGi > 2.2 Make Synapse artifact deployment completely independent from OSGi > > 3. Component manager - P2 UI Carbon component > > 4. Documentation > - Deployment guide > - Troubleshooting guide > > The main focus of the release will be to make artifact deployment easy > for the user, without having to work with OSGi. We should plan to do > the release close to the end of next month. Thoughts welcome. > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] MTOM Broken on Carbon Trunk
Senaka, It seems like the issue is with the Coyote transport, or may be the carbon Servlet. The best way to isolate the problem is to deploy axis2 on tomcat and test the exact same scenario and see the response. Can you do this and attach the response? Basically take the axis2.war and deploy that on a tomcat instance and do the same test. Thanks, Ruwan Senaka Fernando wrote: > Hi all, > > It seems that MTOM is no longer working properly on the Carbon trunk. > But, there doesn't seem to be any issues on the axis2 trunk. Here are > the responses that we receive, from the simple axis server, and from > carbon. > > > HTTP/1.1 200 OK > Date: Mon, 21 Sep 2009 19:03:14 GMT > Server: Simple-Server/1.1 > Transfer-Encoding: chunked > Content-Type: multipart/related; > boundary=MIMEBoundaryurn_uuid_9645FCE52FDC6F4D931253559793956; > type="application/xop+xml"; > start="<0.urn:uuid:9645fce52fdc6f4d931253559793...@apache.org > <mailto:0.urn%3auuid%3a9645fce52fdc6f4d931253559793...@apache.org>>"; > start-info="text/xml" > > 202 > --MIMEBoundaryurn_uuid_9645FCE52FDC6F4D931253559793956 > Content-Type: application/xop+xml; charset=UTF-8; type="text/xml" > Content-Transfer-Encoding: binary > Content-ID: <0.urn:uuid:9645fce52fdc6f4d931253559793...@apache.org > <mailto:0.urn%3auuid%3a9645fce52fdc6f4d931253559793...@apache.org>> > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> xmlns:ns2="http://ws.apache.org/axis2/mtomsample/";>File saved > succesfully. > 3c > > --MIMEBoundaryurn_uuid_9645FCE52FDC6F4D931253559793956-- > > 0 > > > HTTP/1.1 200 OK > Server: Apache-Coyote/1.1 > Set-Cookie: JSESSIONID=530BBD82AFE9DE49D72047D3DE3E6D10; Path=/ > Content-Type: multipart/related; > boundary=MIMEBoundaryurn_uuid_AF6ADACAB1DC99F4FE1253559608760; > type="application/xop+xml"; > start="<0.urn:uuid:af6adacab1dc99f4fe1253559608...@apache.org > <mailto:0.urn%3auuid%3aaf6adacab1dc99f4fe1253559608...@apache.org>>"; > start-info="text/xml" > Transfer-Encoding: chunked > Date: Mon, 21 Sep 2009 19:00:07 GMT > > 202 > --MIMEBoundaryurn_uuid_AF6ADACAB1DC99F4FE1253559608760 > Content-Type: application/xop+xml; charset=UTF-8; type="text/xml" > Content-Transfer-Encoding: binary > Content-ID: <0.urn:uuid:af6adacab1dc99f4fe1253559608...@apache.org > <mailto:0.urn%3auuid%3aaf6adacab1dc99f4fe1253559608...@apache.org>> > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> xmlns:ns2="http://ws.apache.org/axis2/mtomsample/";>File saved > succesfully. > 0 > > > As you can see, in the first response, which is from the simple axis > server, there is a mime boundary which the second (from carbon) > doesn't have. > > Thanks, > Senaka. > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Content types for Endpoints and Sequences
https://www.wso2.org/jira/browse/CARBON-5147 Have a look at this, I think we need a Wiki for Media-Types in the same way as for the namespaces. That way it is easy to track them. Thanks, Ruwan Senaka Fernando wrote: > IIRC they are not, but I do remember seeing these in our code. Perhaps > a grep would help finding it. > > Thanks, > Senaka. > > On Wed, Sep 30, 2009 at 4:56 PM, Supun Kamburugamuwa <mailto:su...@wso2.com>> wrote: > > BTW are these content types defined in registry? > > Supun.. > > > On Tue, Sep 29, 2009 at 9:17 PM, Senaka Fernando <mailto:sen...@wso2.com>> wrote: > > > > On Tue, Sep 29, 2009 at 9:37 PM, Sanjiva Weerawarana > mailto:sanj...@wso2.com>> wrote: > > Are these correct? That is, is this the proper use of the > application/vnd space? Can someone please check the spec? > I suspect you need to have the vendor name somewhere? > > > +1. Yes, this should be, > > EPR - "application/vnd.wso2.epr" > Sequence - "application/vnd.wso2.sequence" > > May be we need to go through other such uses and fix them as well. > > Thanks, > Senaka. > > > > Sanjiva. > > > On Tue, Sep 29, 2009 at 7:25 PM, Senaka Fernando > mailto:sen...@wso2.com>> wrote: > > Hi Supun, > > We do have content types for EPR and Sequences already. > > EPR - "application/vnd.epr" > Sequence - "application/vnd.sequence" > > But, they don't seem to be used. > > Thanks, > Senaka. > > On Tue, Sep 29, 2009 at 5:21 PM, Supun Kamburugamuwa > mailto:su...@wso2.com>> wrote: > > Hi all, > > At the moment we are saving the ESB endpoint and > sequences to the registry with the 'text/xml' > content type. We are hoping to give them specific > content types so that a user can search for > endpoints and sequences easily. What should be the > content types for sequences and endpoints? > > Thanks, > Supun.. > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com <mailto:sanj...@wso2.com>; cell: > +1 650 265 8311 | +94 77 787 6880 > blog: http://sanjiva.weerawarana.org/ > > The Open Source SOA Company > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] AxisFault : SOAPEnvelope must contain a body element which is either first or second child element of the SOAPEnvelope.!!!!
have a body. >> > >> nope...body presents there.. >> -Ratha. >> > Supun.. >> > >> > On Wed, Sep 30, 2009 at 5:43 AM, ratha > <mailto:rat...@wso2.com> >> > <mailto:rat...@wso2.com <mailto:rat...@wso2.com>>> wrote: >> > >> > Hi all, >> > In Axis Handler, when process the soap message i get the >> following >> > error.. what would be the reason? >> > >> > / >> > [2009-09-30 18:08:40,828] ERROR - error occurred while login >> > *org.apache.axis2.*//*AxisFault*//*: SOAPEnvelope must >> contain a body >> > element which is ei >> > ther first or second child element of the SOAPEnvelope.* >> >at >> > >> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.j >> > ava:518) >> >at >> > >> org.apache.axis2.description.OutInAxisOperationClient.handleResponse( >> > OutInAxisOperation.java:371) >> >at >> > >> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisO >> > peration.java:417) >> >at >> > >> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(Out >> > InAxisOperation.java:229) >> >at >> > >> org.apache.axis2.client.OperationClient.execute(OperationClient.java: >> > 165) >> >at >> > >> org.wso2.carbon.ui.authentication.AuthenticationAdminServiceStub.getS >> > ystemPermissionOfUser(AuthenticationAdminServiceStub.java:341) >> >at >> > >> org.wso2.carbon.ui.DefaultCarbonAuthenticator.setUserPermissions(Defa >> > ultCarbonAuthenticator.java:148) >> >at >> > >> org.wso2.carbon.ui.DefaultCarbonAuthenticator.authenticate(DefaultCar >> > bonAuthenticator.java:120) >> >at >> > >> org.wso2.carbon.ui.DefaultCarbonAuthenticator.authenticate(DefaultCar >> > bonAuthenticator.java:44) >> >at >> > >> org.wso2.carbon.ui.CarbonSecuredHttpContext.handleSecurity(CarbonSecu >> > redHttpContext.java:210) >> >at >> > >> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleR >> > equest(ServletRegistration.java:86) >> >at >> > >> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(P >> > >> > >> > /Thnaks. >> > -Ratha. >> > / >> > / >> > >> > ___ >> > Carbon-dev mailing list >> > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> >> <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> > >> >> > >> > ___ >> > Carbon-dev mailing list >> > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> >> >> -- >> Sanjiva Weerawarana, Ph.D. >> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ >> email: sanj...@wso2.com <mailto:sanj...@wso2.com>; cell: +1 650 265 >> 8311 | +94 77 787 6880 >> blog: http://sanjiva.weerawarana.org/ >> >> The Open Source SOA Company >> >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry
Senaka Fernando wrote: > > > On Thu, Oct 1, 2009 at 9:02 AM, Sanjiva Weerawarana <mailto:sanj...@wso2.com>> wrote: > > On Wed, Sep 30, 2009 at 8:56 PM, Senaka Fernando <mailto:sen...@wso2.com>> wrote: > > Hi Jonathan, > > I have fixed the spelling mistake and the session timeout not > being reflected when adding/editing properties through the UI. > > However, regarding the pop-up, I believe that coming up with a > non-modal alert, would be better but would be inconsistent > with the remainder of the UI alerts as we display pop-up > messages elsewhere. > > Therefore, what we can do is re-direct the user to the added > resource/collection which sounds logical, as 95% of the people > would be interested to see what gets added soon after adding > something. But, this would be an issue for someone who keeps > on adding several resources one after the other as he needs to > go back-and-forth. > > > Senaka, IMO in most cases you're not adding lots of collections .. > and if you add one you want to add stuff into that collection > next. So I think we should do what Jonathan suggested as the default. > > > OK, I will try to get this done for 2.0.1 if possible. 2.0.1 Aren't we let this release go out :-( Ruwan > > Thanks, > Senaka. > > > Sanjiva. > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com <mailto:sanj...@wso2.com>; cell: +1 650 > 265 8311 | +94 77 787 6880 > blog: http://sanjiva.weerawarana.org/ > > The Open Source SOA Company > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > ---- > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] is it a normal scenario at Clustering ?
Srinath Perera wrote: > yes, we talked about in detail. I think Ruwan and co are working on > hot deployment support across cluster (via registry subscriptions). We > have to wait to that to be done. > Correct!, for the moment, you do not have hot deployment for synapse artifacts, so you need to restart the other ESB nodes in the cluster. Guys, don't be hurry... please wait... :-) Thanks, Ruwan > --Srinath > > On Mon, Oct 5, 2009 at 7:08 PM, Sanjiva Weerawarana wrote: > >> Isn't this what we've been talking about (a customer wanted this) and I >> thought we agreed to do it by each node subscribing to changes in the >> registry? >> >> Sanjiva. >> >> On Mon, Oct 5, 2009 at 6:55 PM, Afkham Azeez wrote: >> >>> However, this can be done, but we should a distributed transactional >>> method to deploy the proxy service on all nodes of the cluster consistently. >>> Azeez >>> >>> On Mon, Oct 5, 2009 at 6:50 AM, Ajith Vitharana wrote: >>> >>>> Hi, >>>> >>>> I have ESB cluster (3 nodes) . >>>> then I create a proxy service from node1. But that proxy don't display at >>>> services list of node2 and node3. >>>> finally I restart the node2 and node3 , now that proxy show at service >>>> list of node2 and node3. >>>> >>>> why can't see that proxy without restarting? >>>> Is it a normal scenario at Clustering ? >>>> >>>> >>>> Ajith >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> ___ >>>> Carbon-dev mailing list >>>> Carbon-dev@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> -- >>> -- >>> Afkham Azeez >>> az...@wso2.com >>> WSO2 Inc. http://wso2.com >>> Blog: http://afkham.org >>> >>> _______ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> -- >> Sanjiva Weerawarana, Ph.D. >> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ >> email: sanj...@wso2.com; cell: +1 650 265 8311 | +94 77 787 6880 >> blog: http://sanjiva.weerawarana.org/ >> >> The Open Source SOA Company >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> > > > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Random error - too many open files
rbon.ui.JspServlet.service(JspServlet.java:117) > at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:64) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36) > > 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:802) > at org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:138) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) > > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691) > > at > org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:469) > > at > org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403) > > at > org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) > > at > org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30) > > at > org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:258) > > at > org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(ServletTilesRequestContext.java:198) > > at > org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(ServletTilesRequestContext.java:185) > > at > org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419) > > at > org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:370) > > at org.wso2.carbon.ui.action.ActionHelper.render(ActionHelper.java:53) > at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:86) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36) > > 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:802) > at org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:138) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) > > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) > > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) > > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) > > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) > > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) > > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) > > at > org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) > > at > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) > > at > org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) > > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) > > at java.lang.Thread.run(Thread.java:619) > Resource tree loading please wait .. > Resource tree loading please wait .. > > > > > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Is there a way to turn off registry eventing
omcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) > at java.lang.Thread.run(Thread.java:595) > Caused by: java.lang.IllegalStateException: Bundle > "reference:file:plugins/org.wso2.carbon.registry.ui.info-2.0.0.jar" > has been uninstalled > at > > org.eclipse.osgi.framework.internal.core.AbstractBundle.checkValid(AbstractBundle.java:1160) > at > > org.eclipse.osgi.framework.internal.core.AbstractBundle.getEntry0(AbstractBundle.java:1231) > at > > org.eclipse.osgi.framework.internal.core.AbstractBundle$6.getNextElement(AbstractBundle.java:1435) > at > > org.eclipse.osgi.framework.internal.core.AbstractBundle$6.nextElement(AbstractBundle.java:1418) > at > > org.wso2.carbon.ui.JspServlet$ServletContextAdaptor.getResource(JspServlet.java:177) > at > > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301) > at > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > at > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.wso2.carbon.ui.JspServlet.service(JspServlet.java:115) > at > org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:35) > at > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > > org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36) > 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:802) > at > org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:132) > at > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) > at > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at > > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691) > at > > org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:469) > at > > org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403) > at > > org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) > at > > org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30) > at > > org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:258) > at > > org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(ServletTilesRequestContext.java:198) > at > > org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(ServletTilesRequestContext.java:185) > at > > org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419) > ... 25 more > > > On Tue, Oct 6, 2009 at 10:36 PM, Senaka Fernando > mailto:sen...@wso2.com>> wrote: > > > > On Wed, Oct 7, 2009 at 11:02 AM, Supun Kamburugamuwa > mailto:su...@wso2.com>> wrote: > > Hi Senaka, > > What is the community feature and what we are going to > loose if we remove it? > > > You will loose Rating, Tagging, and Comments. > > Thanks, > Senaka. > > > Supun.. > > > On Tue, Oct 6, 2009 at 10:23 PM, Senaka Fernando > mailto:sen...@wso2.com>> wrote: > > Hi Supun, > > On Wed, Oct 7, 2009 at 10:45 AM, Supun > Kamburugamuwa <mailto:su...@wso2.com>> wrote: > > Hi $Subject. >
Re: [Carbon-dev] Removing XKMS and STS services from the ESB
dev > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Removing XKMS and STS services from the ESB
Prabath Siriwardena wrote: > Ruwan Linton wrote: > >> Charitha Kankanamge wrote: >> >> >>> FYI: I have already raised a bug regarding this in 2009 January and >>> its priority/severity had been reduced [1] >>> >>> [1]https://wso2.org/jira/browse/CARBON-2781 -STS and XKMS services are >>> allowed to delete, however those reappeared in the service list once >>> server is restarted >>> >>> >> Can we make them special services and not list in the normal service >> list and present a different custom UI for each of these? For example we >> will have a STS as a different menu item and the Ui can share most of >> the code from service management. >> >> > We already have both of these services [STS and XKMS] present in IS as > menu items. > So do we hide those services in IS, or we do not have service management in IS?? In any case I think we should make them hidden services and show them on the Configure menu as different menu items, if we need to keep them with other products. If we do not want to we can just get rid of those :-) from the other products. Thanks, Ruwan > Thanks & regards. > -Prabath > >> I agree with Supun this is not a service it is part of the product, if >> it reappears after the restart we shouldn't allow the user to delete it >> :-) at least. >> >> Thanks, >> Ruwan >> >> >>> Charitha Kankanamge >>> WSO2 Inc. >>> http://wso2.org >>> email: chari...@wso2.com <mailto:chari...@wso2.com> >>> cell: +94 718 359 265 >>> blog: http://charithaka.blogspot.com >>> >>> >>> On Thu, Oct 8, 2009 at 6:27 AM, Supun Kamburugamuwa >> <mailto:su...@wso2.com>> wrote: >>> >>> But my point is if we cannot remove them they are not services in >>> the normal sense. They are part of the product. >>> >>> Supun.. >>> >>> >>> On Wed, Oct 7, 2009 at 5:22 PM, Afkham Azeez >> <mailto:az...@wso2.com>> wrote: >>> >>> Those services can be removed, but they will be available once >>> you restart the server since they are supplied through OSGi >>> bundles. These are non-admin, non-hidden services, which can >>> be configured through the Mgt Console, so we cannot hide them. >>> >>> Azeez >>> >>> >>> On Wed, Oct 7, 2009 at 6:34 PM, Supun Kamburugamuwa >>> mailto:su...@wso2.com>> wrote: >>> >>> I would like to bring another point. These services like >>> XKMS, STS, RegistryEventing all are shown in the Service >>> management page. If they are shown there they should obey >>> the rules that other services do. For example a user >>> should be able to remove them from the UI (because that >>> option is available through the UI). >>> >>> Thanks, >>> Supun.. >>> >>> >>> On Wed, Oct 7, 2009 at 1:28 AM, Sameera Jayasoma >>> mailto:same...@wso2.com>> wrote: >>> >>> >>> >>> On Wed, Oct 7, 2009 at 12:56 PM, Prabath Siriwardena >>> mailto:prab...@wso2.com>> wrote: >>> >>> Hi Supun; >>> >>> The issue here is - the same bundle which exposes >>> the XKMS service out >>> is the one which exports the org.wso2.xkms2 - >>> which is consumed by the >>> security management bundle. >>> >>> I guess ideally org.wso2.xkms2 should be exported >>> by an orbit bundle. >>> >>> >>> +1. The service and the library should be separated. >>> This same scenario occurs even when you remove the >>> xkms feature from the system. P2 does not remove the >>> org.wso2.xkms bundle, since there are dependent >>> bundles on it. >>> >>> Sameera >>> >>> >>> So - with the current setup we have to keep the >>> org.wso2.carbon.xkms-2.0.0 bundle - but we can >>> try with an workaround >>>
Re: [Carbon-dev] Removing XKMS and STS services from the ESB
sumedha wrote: > Prabath Siriwardena wrote: > >> Hi Supun; >> >> The issue here is - the same bundle which exposes the XKMS service out >> is the one which exports the org.wso2.xkms2 - which is consumed by the >> security management bundle. >> >> I guess ideally org.wso2.xkms2 should be exported by an orbit bundle. >> >> So - with the current setup we have to keep the >> org.wso2.carbon.xkms-2.0.0 bundle - but we can try with an workaround >> to hide the XKMS service from the UI? >> > A simple & dirty hack would be to set the following parameters in the > services.xml for XKMS service. > > true > true > > I tried setting these parameters from the UI. But even after server > restart, they don't seem to be taking any effect. But modifying > services.xml should definitely work. > Sumedha they are not admin services, it is wrong to categorize them as admin services, they are just hidden services. Also, Supun the above hack will just hide the service but will not remove it :-) Also, shall we consider hiding them from the service management page and having them there own UIs as in the IS?? Thanks, Ruwan > /sumedha > > >> Also - we can create a patch to fix this in the correct way. >> >> What do you suggest ? >> >> Thanks & regards. >> -Prabath >> >> > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon Code Reviews!
sumedha wrote: > Afkham Azeez wrote: > >> We reviewed the Carbon HTTP session handling code & also had a session >> on Carbon implementation conventions & design. >> > Azeez, > This[1] is the HTTPSession Listener I mentioned yesterday. > +1, this way we can get the session wrapper cleared once the session gets invalidated. Thanks, Ruwan > /sumedha > > [1] > http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/servlet/http/HttpSessionListener.html > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Sending a fault for an invalid GET request URL
Supun Kamburugamuwa wrote: > Hi, > > There is a service which is invoked using HTTP GET. Is it > possible/reasonable to send a soap fault to this GET request? If you are using the ESB this is possible :-), you need to change the messageType axis2 message context property and the ContentType property. Also you may use a defaukt endpoint on the response delivery to force SOAP12. Thanks, Ruwan > > Thanks, > Supun.. > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] WSO2 Enterprise Service Bus (ESB) 2.1.1 Released!
ntitlement mediator * Reliable-Messaging specification 1.1 support * Enhanced WS-Eventing support and Event Sources making it an even broker * Enhanced AJAX based sequence, endpoint and proxy service editors * Enhanced transport configuration management through the graphical console * Enhanced integrated registry and search functionalities with versionning, notifications, rating of resources, and commenting * Enhanced remote registry support * Default persistence to the registry for the configuration elements * Enhanced permission model with the user management * Enhanced REST/GET and other HTTP method support * P2 based OSGi feature support, for optional features like service management, runtime governance and so on.. Bug Fixes and Enhancements * Endpoint management issues in clustered environments have been fixed (CARBON-5108) * Defects in DBReport, DBLookup mediator UIs have been corrected (CARBON-5084) * Script mediator UI has been improved to handle some exceptional scenarios (CARBON-5080) * XQuery mediator UI has been enhanced to handle some exceptional scenarios (CARBON-5078) * ESB management console has been enhanced to work properly on WebLogic application server * UI enhancements to support WebSphere application server * Sequence management UI has undergone some minor enhancements * Enhancements to support front end - back end separation of the server * Reported issues related to transaction mediator have been fixed (CARBON-4225) * Issues releated to task creation and management have been rectified * Many documentation updates and enhancements How You Can Contribute Mailing Lists Join our mailing list and correspond with the developers directly. * Developer List : esb-java-...@wso2.org <mailto:esb-java-...@wso2.org> | Subscribe <mailto:esb-java-dev-requ...@wso2.org?subject=subscribe> | Mail Archive <http://wso2.org/mailarchive/esb-java-dev/> * User List : esb-java-u...@wso2.org <mailto:esb-java-u...@wso2.org> | Subscribe <mailto:esb-java-user-requ...@wso2.org?subject=subscribe> | Mail Archive <http://wso2.org/mailarchive/esb-java-user/> Reporting Issues WSO2 encourages you to report issues and your enhancement requests for the WSO2 ESB using the public JIRA <http://www.wso2.org/jira/browse/ESBJAVA>. You can also watch how they are resolved, and comment on the progress.. Discussion Forums Alternatively, questions could be raised using the forums available. WSO2 ESB Forum <http://wso2.org/forum/187> : Discussion forum for WSO2 ESB developers/users Training WSO2 Inc. offers a variety of professional Training Programs, including training on general Web services as well as WSO2 ESB, Apache Synapse, Apache Axis2 and number of other products. For additional support information please refer to http://wso2.com/training/course-catalog/ Support WSO2 Inc. offers a variety of development and production support programs, ranging from Web-based support up through normal business hours, to premium 24x7 phone support. For additional support information please refer to http://wso2.com/support/ For more information on WSO2 ESB, visit the WSO2 Oxygen Tank (http://wso2.org) We welcome your feedback on this implementation. Thank you for your interest in WSO2 ESB. /-- The WSO2 ESB Team --/ -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Memory leak analysis
Azeez, Does this mean that none of the changes that we have done on the branch has not been committed into the trunk?? :-( Thanks, Ruwan Afkham Azeez wrote: > I have been trying to build the trunk for a few days without any > success. So, I was not able to commit this to the trunk, but > definitely did not forget it. I thought the snapshot repo was getting > updated; what is happening with the snapshot repo? > > Azeez > > On Tue, Oct 13, 2009 at 5:46 PM, Sanjiva Weerawarana <mailto:sanj...@wso2.com>> wrote: > > Folks, ALL fixes on any branch must always be committed to trunk > immediately. Otherwise we'll simply forget :(. > > Sanjiva. > > > On Tue, Oct 13, 2009 at 1:03 PM, Sameera Jayasoma > mailto:same...@wso2.com>> wrote: > > > > On Tue, Oct 13, 2009 at 7:11 PM, Samisa Abeysinghe > mailto:sam...@wso2.com>> wrote: > > We need to do a memory leak analysis on > > 1. Data services > 2. Gadgets and dashboard > 3. BAM component > > I ran a continuous test for about 20 minutes and I see > that BAM server memory consumption grow a great deal. And > did not notice memory dropping down even when there were > no requests coming in. > > > Are you testing on trunk? If the fix for the memory leak > ndiscovered recently is not applied to the trunk, you may have > experienced the same issue. > > Thanks > Sameera > > > > Samisa... > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com <mailto:sanj...@wso2.com>; cell: +1 650 > 265 8311 | +94 77 787 6880 > blog: http://sanjiva.weerawarana.org/ > > > The Open Source SOA Company > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Memory leak analysis
Afkham Azeez wrote: > No, all my changes have been committed except for this so no need to be :( I had a look at the svn logs and I cannot see the respective trunk commits for the following revisions for the branch from you; 46032 46199 46664 46668 46686 46712 46713 46714 and Dimuthu has done a set of fixes (see the following revision numbers) to branch including symlink and various other stuff which seems to be critical but those have not been committed to trunk as well :-( also I did a careful look at the trunk commits on the period these commits were made to branch but I don't see bulk commits containing these fixes on to trunk as well... 46406 46407 46408 46420 46396 46397 46399 46400 There are many more form different people :-( Thanks, Ruwan > > Since recently, I cannot build due to multiple build > failures/dependency problems > > Azeez > > On Wed, Oct 14, 2009 at 1:15 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Azeez, > > Does this mean that none of the changes that we have done on the > branch > has not been committed into the trunk?? :-( > > Thanks, > Ruwan > > Afkham Azeez wrote: > > I have been trying to build the trunk for a few days without any > > success. So, I was not able to commit this to the trunk, but > > definitely did not forget it. I thought the snapshot repo was > getting > > updated; what is happening with the snapshot repo? > > > > Azeez > > > > On Tue, Oct 13, 2009 at 5:46 PM, Sanjiva Weerawarana > mailto:sanj...@wso2.com> > > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com>>> wrote: > > > > Folks, ALL fixes on any branch must always be committed to trunk > > immediately. Otherwise we'll simply forget :(. > > > > Sanjiva. > > > > > > On Tue, Oct 13, 2009 at 1:03 PM, Sameera Jayasoma > > mailto:same...@wso2.com> > <mailto:same...@wso2.com <mailto:same...@wso2.com>>> wrote: > > > > > > > > On Tue, Oct 13, 2009 at 7:11 PM, Samisa Abeysinghe > > mailto:sam...@wso2.com> > <mailto:sam...@wso2.com <mailto:sam...@wso2.com>>> wrote: > > > > We need to do a memory leak analysis on > > > > 1. Data services > > 2. Gadgets and dashboard > > 3. BAM component > > > > I ran a continuous test for about 20 minutes and I see > > that BAM server memory consumption grow a great > deal. And > > did not notice memory dropping down even when there were > > no requests coming in. > > > > > > Are you testing on trunk? If the fix for the memory leak > > ndiscovered recently is not applied to the trunk, you > may have > > experienced the same issue. > > > > Thanks > > Sameera > > > > > > > > Samisa... > > > > -- > > Samisa Abeysinghe > > Director, Engineering - WSO2 Inc. > > > > http://www.wso2.com/ - "The Open Source SOA Company" > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> > > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > > -- > > Sanjiva Weerawarana, Ph.D. > > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > > email: sanj...@wso2.com <mailto:sanj...@wso2.com> > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com>>; cell: +1 650 > > 265 8311 | +94 77 787 6880 > > blog: http://sanjiva.weerawarana.org/ > > > > > > The Open Source SOA Company > > &g
Re: [Carbon-dev] Memory leak analysis
We should have the habit of maintaining the trunk stability, but when you are in a release branch we tend to neglect the trunk and focus on the release branch, which is a side effect of maintaining a branch as well as the trunk. It is really hard to get the changes back to trunk after few weeks. Thanks, Ruwan Senaka Fernando wrote: > Hi Ruwan, > > Thanks for the list of commits in question. The Registry team has > started committing the fixes done on the branch to the trunk. > Intermittent build issues and release deadlines have kept many people > from committing to the trunk during the latter stage of the release. > We are in the process of incorporating all of the missing commits to > the trunk, which we hope to complete in a few days. > > Thanks, > Senaka. > > On Wed, Oct 14, 2009 at 7:10 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Afkham Azeez wrote: > > No, all my changes have been committed except for this so no > need to be :( > I had a look at the svn logs and I cannot see the respective trunk > commits for the following revisions for the branch from you; > > 46032 > 46199 > 46664 > 46668 > 46686 > 46712 > 46713 > 46714 > > and Dimuthu has done a set of fixes (see the following revision > numbers) > to branch including symlink and various other stuff which seems to be > critical but those have not been committed to trunk as well :-( also I > did a careful look at the trunk commits on the period these > commits were > made to branch but I don't see bulk commits containing these fixes > on to > trunk as well... > > 46406 > 46407 > 46408 > 46420 > 46396 > 46397 > 46399 > 46400 > > There are many more form different people :-( > > Thanks, > Ruwan > > > > Since recently, I cannot build due to multiple build > > failures/dependency problems > > > > Azeez > > > > On Wed, Oct 14, 2009 at 1:15 AM, Ruwan Linton <mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>> wrote: > > > > Azeez, > > > > Does this mean that none of the changes that we have done on the > > branch > > has not been committed into the trunk?? :-( > > > > Thanks, > > Ruwan > > > > Afkham Azeez wrote: > > > I have been trying to build the trunk for a few days > without any > > > success. So, I was not able to commit this to the trunk, but > > > definitely did not forget it. I thought the snapshot repo was > > getting > > > updated; what is happening with the snapshot repo? > > > > > > Azeez > > > > > > On Tue, Oct 13, 2009 at 5:46 PM, Sanjiva Weerawarana > > mailto:sanj...@wso2.com> > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com>> > > > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com> > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com>>>> wrote: > > > > > > Folks, ALL fixes on any branch must always be > committed to trunk > > > immediately. Otherwise we'll simply forget :(. > > > > > > Sanjiva. > > > > > > > > > On Tue, Oct 13, 2009 at 1:03 PM, Sameera Jayasoma > > > mailto:same...@wso2.com> > <mailto:same...@wso2.com <mailto:same...@wso2.com>> > > <mailto:same...@wso2.com <mailto:same...@wso2.com> > <mailto:same...@wso2.com <mailto:same...@wso2.com>>>> wrote: > > > > > > > > > > > > On Tue, Oct 13, 2009 at 7:11 PM, Samisa Abeysinghe > > > mailto:sam...@wso2.com> > <mailto:sam...@wso2.com <mailto:sam...@wso2.com>> > > <mailto:sam...@wso2.com <mailto:sam...@wso2.com> > <mailto:sam...@wso2.com <mailto:sam...@wso2.com>>>> wrote: > > > > > > We need to do a memory leak analysis on > > > > > > 1. Data services > > > 2. Gadgets and dashboard > > > 3. BAM component > > > > > > I ran a continuous test for
Re: [Carbon-dev] Commits verification [was Re: Memory leak analysis]
Samisa Abeysinghe wrote: > Ruwan, can you let us know how you are doing this trunk vs branch > commit verification, so that others could do those checks on a regualr > basis? First of all I am using a different folder (filter) for commit messages for different projects, for example I have a folder in my thunderbird mail client which just has commits for the carbon project both trunk and branch. Then you sort them with the time and go through the commit notification list to see whether the commits to the branch and do a comparison with the commits to the trunk on the same period. Note that you can clearly differentiate the branch commits from the trunk commits from the notification mail subject. It is a manual process :-) and this is why I always ask all to commit to the trunk as and when they commit to the branch with the same commit log, so that the comparison is easier. Thanks, Ruwan > > Thanks, > Samisa... > > > On Wed, Oct 14, 2009 at 7:10 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Afkham Azeez wrote: > > No, all my changes have been committed except for this so no > need to be :( > I had a look at the svn logs and I cannot see the respective trunk > commits for the following revisions for the branch from you; > > 46032 > 46199 > 46664 > 46668 > 46686 > 46712 > 46713 > 46714 > > and Dimuthu has done a set of fixes (see the following revision > numbers) > to branch including symlink and various other stuff which seems to be > critical but those have not been committed to trunk as well :-( also I > did a careful look at the trunk commits on the period these > commits were > made to branch but I don't see bulk commits containing these fixes > on to > trunk as well... > > 46406 > 46407 > 46408 > 46420 > 46396 > 46397 > 46399 > 46400 > > There are many more form different people :-( > > Thanks, > Ruwan > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Memory leak analysis
Samisa Abeysinghe wrote: > > > On Wed, Oct 14, 2009 at 8:29 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > We should have the habit of maintaining the trunk stability, but when > you are in a release branch we tend to neglect the trunk and focus on > the release branch, which is a side effect of maintaining a branch as > well as the trunk. It is really hard to get the changes back to trunk > after few weeks. > > > There is NO WAY we can ALL can work on a single branch or trunk. So > people must have to learn to live with it, no matter how hard it is. +1, I meant to say that we need to keep both branch and the trunk in a stable state, but we shouldn't neglect the trunk and we need to commit the changes to the trunk then and there we do the changes to the branch. Thanks, Ruwan > > Samisa... > > > Thanks, > Ruwan > > Senaka Fernando wrote: > > Hi Ruwan, > > > > Thanks for the list of commits in question. The Registry team has > > started committing the fixes done on the branch to the trunk. > > Intermittent build issues and release deadlines have kept many > people > > from committing to the trunk during the latter stage of the release. > > We are in the process of incorporating all of the missing commits to > > the trunk, which we hope to complete in a few days. > > > > Thanks, > > Senaka. > > > > On Wed, Oct 14, 2009 at 7:10 AM, Ruwan Linton <mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>> wrote: > > > > Afkham Azeez wrote: > > > No, all my changes have been committed except for this so no > > need to be :( > > I had a look at the svn logs and I cannot see the respective > trunk > > commits for the following revisions for the branch from you; > > > > 46032 > > 46199 > > 46664 > > 46668 > > 46686 > > 46712 > > 46713 > > 46714 > > > > and Dimuthu has done a set of fixes (see the following revision > > numbers) > > to branch including symlink and various other stuff which > seems to be > > critical but those have not been committed to trunk as well > :-( also I > > did a careful look at the trunk commits on the period these > > commits were > > made to branch but I don't see bulk commits containing these > fixes > > on to > > trunk as well... > > > > 46406 > > 46407 > > 46408 > > 46420 > > 46396 > > 46397 > > 46399 > > 46400 > > > > There are many more form different people :-( > > > > Thanks, > > Ruwan > > > > > > Since recently, I cannot build due to multiple build > > > failures/dependency problems > > > > > > Azeez > > > > > > On Wed, Oct 14, 2009 at 1:15 AM, Ruwan Linton > mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>> > > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com> > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>>> wrote: > > > > > > Azeez, > > > > > > Does this mean that none of the changes that we have > done on the > > > branch > > > has not been committed into the trunk?? :-( > > > > > > Thanks, > > > Ruwan > > > > > > Afkham Azeez wrote: > > > > I have been trying to build the trunk for a few days > > without any > > > > success. So, I was not able to commit this to the > trunk, but > > > > definitely did not forget it. I thought the snapshot > repo was > > > getting > > > > updated; what is happening with the snapshot repo? > > > > > > > > Azeez > > > > > > > > On Tue, Oct 13, 2009 at 5:46 PM, Sanjiva Weerawarana > > > mailto:sanj...@wso2.com> > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com>> >
Re: [Carbon-dev] Memory leak analysis
Don't worry, I am not :-(, when I am going to be back in November after my leaves I am sure you will get these fixes somehow on to the trunk, I just wanted to point that there are stuff that we have not committed to the trunk which are there in the branch. :-) Thanks, Ruwan Afkham Azeez wrote: > Correction: I should have said, ALL of those commits were consciously > not committed to the trunk. > > > On Wed, Oct 14, 2009 at 4:28 AM, Afkham Azeez <mailto:az...@wso2.com>> wrote: > > Ruwan, > ALL of those commits were not consciously committed to the trunk. > Have you looked at the commit logs? All of them are related to the > session handling stuff, and one of them is related to the chroot > fix. The registry code in the trunk has changed in the trunk to > support multitenancy, hence the chroot fix should be done properly > by taking those changes into consideration, hence cannot be simply > committed to the trunk. > > So still, you need not be :( about my commits. But thanks for > taking your time to dig into this. > > Azeez > > On Wed, Oct 14, 2009 at 1:40 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Afkham Azeez wrote: > > No, all my changes have been committed except for this so no > need to be :( > I had a look at the svn logs and I cannot see the respective trunk > commits for the following revisions for the branch from you; > > 46032 > 46199 > 46664 > 46668 > 46686 > 46712 > 46713 > 46714 > > and Dimuthu has done a set of fixes (see the following > revision numbers) > to branch including symlink and various other stuff which > seems to be > critical but those have not been committed to trunk as well > :-( also I > did a careful look at the trunk commits on the period these > commits were > made to branch but I don't see bulk commits containing these > fixes on to > trunk as well... > > 46406 > 46407 > 46408 > 46420 > 46396 > 46397 > 46399 > 46400 > > There are many more form different people :-( > > Thanks, > Ruwan > > > > Since recently, I cannot build due to multiple build > > failures/dependency problems > > > > Azeez > > > > On Wed, Oct 14, 2009 at 1:15 AM, Ruwan Linton > mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>> wrote: > > > > Azeez, > > > > Does this mean that none of the changes that we have > done on the > > branch > > has not been committed into the trunk?? :-( > > > > Thanks, > > Ruwan > > > > Afkham Azeez wrote: > > > I have been trying to build the trunk for a few days > without any > > > success. So, I was not able to commit this to the > trunk, but > > > definitely did not forget it. I thought the snapshot > repo was > > getting > > > updated; what is happening with the snapshot repo? > > > > > > Azeez > > > > > > On Tue, Oct 13, 2009 at 5:46 PM, Sanjiva Weerawarana > > mailto:sanj...@wso2.com> > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com>> > > > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com> > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com>>>> wrote: > > > > > > Folks, ALL fixes on any branch must always be > committed to trunk > > > immediately. Otherwise we'll simply forget :(. > > > > > > Sanjiva. > > > > > > > > > On Tue, Oct 13, 2009 at 1:03 PM, Sameera Jayasoma > > > mailto:same...@wso2.com> > <mailto:same...@wso2.com <mailto:same...@wso2.com>> > > <mailto:same...@wso2.com <mailto:same...@wso2.com> > <mailto:same...@wso2.com <mailto:same...@wso2.com>>>> wrote: > > > > > > >
Re: [Carbon-dev] Selenium - how to use test framework
I think we should integrate the test framework with the product builds. This is a very good automation test framework and hence we need to make use of that. So what I suggest is that if a particular developer did some fixes he/she need to run the product build with the automation test enabled, for that particular component you have done the fix for, and the nightly build will make sure that the entire test framework runs before producing the artifacts. So if a particular developer breaks a test framework test case, for example with some UI changes, it is the responsibility of that developer to fix the test case. Also if you fix an issue reported by someone else, which means that the test framework didn't have a test case to cover that scenario and hence you should add a test case to cover that issue. We can do this by taking a svn:external to the respective product test framework from the product svn location and including the test framework as an integration test module in the product build. This is easy since the test framework is also running with maven. Thoughts?? Thanks, Ruwan Sameera Jayasoma wrote: > Hi Charitha, > > Followed the steps that you've given and it worked on my machine > without any issue. > > Thanks > Sameera > > On Fri, Oct 16, 2009 at 11:26 AM, Charitha Kankanamge > mailto:chari...@wso2.com>> wrote: > > Hi all, > > In case you still do not know how to run automated tests against > your product, here are the steps to run Selenium automated test > framework in your machines. > > 1. Checkout test framework from > https://wso2.org/repos/wso2/trunk/commons/qa/web-test-framework > > 2. Go to web_test_framework_root/commons/src/resources directory > and open framework.properties file > > Update the global properties section > > #Global properties > > host.name <http://host.name>=localhost > http.port=9763 > https.port=9443 > carbon.home=D:/wsas/wso2wsas-3.1.1 > context.root=/wsas > browser.version=firefox > > If you run standalone carbon product, make sure to keep > context.root empty. You can change browser type by changing > browser.version (if you need to run on IE, change browser.version > to *iexplore*) > > 3. Go to web_test_framework_root/product = esb, wsas, > is, mashup or registry > > Issue 'mvn idea:idea' to import the framework project to IDEA > > OR > > Issue 'mvn clean install' to run the framework directly. > > At the moment, you can select the tests which are required to be > run in AllTests.java test suite. We hope to pass a system property > and select test through that in soon. > > > If you face any issues, please report them at > https://wso2.org/jira/browse/QA > > > We use self-signed certificates in carbon therefore you will get > FF security popup when logging in to management UI. You can > eliminate it by specifying a custom FF profile as mentioned in > "Avoiding FF3 invalid certificate error when running selenium > tests" mail thread @arch list. > > Happy testing! > > > Charitha Kankanamge > WSO2 Inc. > http://wso2.org > email: chari...@wso2.com <mailto:chari...@wso2.com> > cell: +94 718 359 265 > blog: http://charithaka.blogspot.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Mediation stats - fault counts
Samisa Abeysinghe wrote: > It looks to me that faults counts from ESB stas are always zero. Even > through an endpoint or a proxy sends me a SOAP fault, it does not seem > that the fault stat gets updated properly. Have we tested this > scenario??? I just want to make sure that I am not mistaken here. I guess we have tested this, Evanthika?? Is this fault coming from the actual service, or generated by the ESB?? Thanks, Ruwan > > Thanks, > Samisa... > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Mediation stats - need for clearing - confilicts
Samisa Abeysinghe wrote: > When the mediation stat component collect data, it clears the lists > using Synapse API. > > When the BAM publisher module collect the data, if it does not clear > the data, then it happens to recount some of the records that is > already counted. So I also have to clear the lists. Which means, if > BAM publisher is present, the mediation stat module would not function > as expected. Didn't we already discussed this :-) and Hiranya is working on a solution. Thanks, Ruwan > > Samisa... > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Mediation stats - fault counts
Samisa Abeysinghe wrote: > > > On Wed, Oct 21, 2009 at 11:14 AM, Evanthika Amarasiri > mailto:evanth...@wso2.com>> wrote: > > Hi Samisa, > > I think there is an issue with the fault count. When the service > is deployed on WSAS and when a SOAP fault is thrown from the > service, the fault count is not increased. > > As you said when a single request is being sent, the total count > gets increased by 2. This as per Indika is the expected behavior. > He once told me that since the message is being sent from the > Proxy Service/sequence twice (in/out) the count is being displayed > like this. > > > In Synapse stat API, there are two separate calls to get In count and > Out count. When you add those, you get the 2x count. However, I am > looking at only the in count, and when the client only has sent, say > 17 requests, the in count appears to be 20. I wonder why? Can you please point to the exact methods that you are calling??? Thanks, Ruwan > > Samisa... > > > > > Thanks, > Evanthika > > > On Wed, Oct 21, 2009 at 10:51 AM, Samisa Abeysinghe > mailto:sam...@wso2.com>> wrote: > > > > On Wed, Oct 21, 2009 at 10:45 AM, Samisa Abeysinghe > mailto:sam...@wso2.com>> wrote: > > Evanthika, > I notice that there seem to be an error in the counts > sent by the Synapse layer. It counts more than what I > actually invoke from the client. > Could you please verify this. > > > My testing using BAM publisher confirms that there is an error > in the counts sent by Synapse. The clear logic does not seem > to work in a consistent manner. However, since I am testing > via BAM publisher, there is a chance that the actual bug is in > my code. Can you please test this with other means and confirm > that the counts are correct? > > Thanks, > Samisa... > > > > Samisa... > > On Wed, Oct 21, 2009 at 10:12 AM, Evanthika Amarasiri > mailto:evanth...@wso2.com>> wrote: > > We have tested this Ruwan, > > For me, for sequences, endpoints and Proxy services, > the Fault count is getting increased. In this scenario > the fault it occurring since the service is down. > > Thanks, > Evanthika > > > On Wed, Oct 21, 2009 at 8:40 AM, Samisa Abeysinghe > mailto:sam...@wso2.com>> wrote: > > > > On Wed, Oct 21, 2009 at 12:29 AM, Ruwan Linton > mailto:ru...@wso2.com>> wrote: > > Samisa Abeysinghe wrote: > > It looks to me that faults counts from ESB > stas are always zero. Even > > through an endpoint or a proxy sends me a > SOAP fault, it does not seem > > that the fault stat gets updated properly. > Have we tested this > > scenario??? I just want to make sure that I > am not mistaken here. > I guess we have tested this, Evanthika?? Is > this fault coming from the > actual service, or generated by the ESB?? > > > Actual service hosted with WSAS. Is that not a > fault with respect to ESB? > > Samisa... > > > > Thanks, > Ruwan > > > > Thanks, > > Samisa... > > > > -- > > Samisa Abeysinghe > > Director, Engineering - WSO2 Inc. > > > > http://www.wso2.com/ - "The Open Source SOA > Company" > > > > ---- > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > > > > https://mail.ws
Re: [Carbon-dev] Mediation stats - counting backend faults
Hiranya Jayathilaka wrote: > Hi Samisa, > > On Wed, Oct 21, 2009 at 10:49 AM, Samisa Abeysinghe <mailto:sam...@wso2.com>> wrote: > > It looks to me, that when you talk about fault count for a proxy, > that counts faults within the ESB and not the faults sent by back > end. > I agree that this is correct. > > However, at the same time, at the ESB level, there needs to be > some mechanism to track, using stats, if the back end sent a > fault. In other words, we need to be able to track both internal > faults, as well as external faults from the ESB mediation stats. > What is the technical feasibility of this? I need this for BAM > to portray the business meaning of the invocations. > > > This can be done but IMO implementing this feature means the ESB will > have to build and analyze each and every response message to see > whether it is a SOAP fault or not. So ideally we should implement this > in a configurable manner so users can enable it only when they want > to. This functionality can be implemented as a part of the proxy > service message dispatching or may be even as a mediator (I'm not sure > about this option - Need to dig deeper on this). We can simply add the > backend faults to the ESB fault count. No... Hiranaya we need to separate these tow out. Faults w.r.t. ESB are mediation faults, doesn't mean that is a SOAPFault, I agree it is better to count SOAPFaults going through the ESB as well separately. I think we already check whether a particular response is a fault or not, do not a big deal when it comes to performance, I guess Axis2 does that before Synapse :-) and sets a flag on the message context :-) > > If we can access the stats at the mediator level we can use the filter > mediator in the out-sequence to separate out SOAP faults and write a > custom mediator which will go and increment the Synapse fault count. Nope, stats are not something that should require a configuration to enable (it is bad to have a mediator to do that). How urgent is this? Can this wait one more week?? Thanks, Ruwan > > Thanks, > Hiranya > > > Thanks, > Samisa... > > On Wed, Oct 21, 2009 at 10:45 AM, Samisa Abeysinghe > mailto:sam...@wso2.com>> wrote: > > Evanthika, > I notice that there seem to be an error in the counts sent > by the Synapse layer. It counts more than what I actually > invoke from the client. > Could you please verify this. > > Samisa... > > On Wed, Oct 21, 2009 at 10:12 AM, Evanthika Amarasiri > mailto:evanth...@wso2.com>> wrote: > > We have tested this Ruwan, > > For me, for sequences, endpoints and Proxy services, the > Fault count is getting increased. In this scenario the > fault it occurring since the service is down. > > Thanks, > Evanthika > > > On Wed, Oct 21, 2009 at 8:40 AM, Samisa Abeysinghe > mailto:sam...@wso2.com>> wrote: > > > > On Wed, Oct 21, 2009 at 12:29 AM, Ruwan Linton > mailto:ru...@wso2.com>> wrote: > > Samisa Abeysinghe wrote: > > It looks to me that faults counts from ESB stas > are always zero. Even > > through an endpoint or a proxy sends me a SOAP > fault, it does not seem > > that the fault stat gets updated properly. Have > we tested this > > scenario??? I just want to make sure that I am > not mistaken here. > I guess we have tested this, Evanthika?? Is this > fault coming from the > actual service, or generated by the ESB?? > > > Actual service hosted with WSAS. Is that not a fault > with respect to ESB? > > Samisa... > > > > Thanks, > Ruwan > > > > Thanks, > > Samisa... > > > > -- > > Samisa Abeysinghe > > Director, Engineering - WSO2 Inc. > > > > http://www.wso2.com/ - "The Open Source SOA Company" > > > > ---- > > > > __
Re: [Carbon-dev] Changing the Carbon Startup Scripts
+1 Ruwan Paul Fremantle wrote: > +1 > > Paul > > 2009/10/21 Hiranya Jayathilaka : > >> Hi Devs, >> >> In our existing launcher scripts for Carbon (wso2server.sh) the path to >> log4j.properties file is stated as follows. >> >>-Djava.util.logging.config.file=log4j.properties >> >> It seems this causes some issues on certain JVMs. For instance on IBM JVM we >> get this error at startup. >> >> java.io.FileNotFoundException: log4j.properties (No such file or >> directory) >>at java.io.FileInputStream.(FileInputStream.java:112) >>at java.io.FileInputStream.(FileInputStream.java:72) >>at >> >> Changing the above property to >> -Djava.util.logging.config.file=$CARBON_HOME/lib/log4j.properties fixes the >> issue. Shall we permanently change out shell scripts with this modification? >> >> -- >> Hiranya Jayathilaka >> 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 >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> > > > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] axis2_1.5.0.wso2v2 bundle exports org.apache.axis2.transport.* packages
;mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com <mailto:hira...@wso2.com>; Mobile: +94 > 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Is carbon trunk compiles and runs?
Samisa Abeysinghe wrote: > Chamara, any updates on the repos?? I think the snapshot repo is ready but we need to be able to build the whole thing at least once and upload the artifacts, and we need to integrate that with the nightly build. Thanks, Ruwan > > Samisa... > > On Thu, Nov 12, 2009 at 4:32 AM, Afkham Azeez <mailto:az...@wso2.com>> wrote: > > I was not able to build. Some missing dependencies and so on. I > thought we agreed to update the snapshot repo & WSO2 Maven repo > regularly. > > Azeez > > On Wed, Nov 11, 2009 at 10:20 PM, Supun Kamburugamuwa > mailto:su...@wso2.com>> wrote: > > Has anyone done the $subject recently? > > > > Thanks, > > Supun.. > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" > -------- > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Is carbon trunk compiles and runs?
Chamara Silva wrote: > Snapshot repo updated upto carbon orbit.carbon component and carbon > core repo update plans currently disable now. because some components > produce release artifacts and it upload to http://dist.wso2.com/maven2 > repo.since 9th of November nightly build fails and repo didn't update. > If it is a release artifact it will be and it has to be uploaded to the dist.wso2.com/maven2 but running nightly builds and uploading release artifacts daily is deadly wrong. Please do not include released artifact builds in the nightly build. If we are to use the artifact uploading we need to follow the maven model correctly, any project which is under development cannot have a fixed version it has to be suffixed with SNAPSHOT. Thanks, Ruwan > http://builder.wso2.org/browse/CBNNIGHTLY-TRNSP-31 > > Thank you, > Regards, > Chamara > > On Thu, Nov 12, 2009 at 6:42 AM, Samisa Abeysinghe wrote: > >> Chamara, any updates on the repos?? >> Samisa... >> >> On Thu, Nov 12, 2009 at 4:32 AM, Afkham Azeez wrote: >> >>> I was not able to build. Some missing dependencies and so on. I >>> thought we agreed to update the snapshot repo & WSO2 Maven repo >>> regularly. >>> >>> Azeez >>> >>> On Wed, Nov 11, 2009 at 10:20 PM, Supun Kamburugamuwa >>> wrote: >>> >>>> Has anyone done the $subject recently? >>>> >>>> Thanks, >>>> Supun.. >>>> >>>> ___ >>>> Carbon-dev mailing list >>>> Carbon-dev@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>>> >>> >>> -- >>> -- >>> Afkham Azeez >>> az...@wso2.com >>> WSO2 Inc. http://wso2.com >>> Blog: http://afkham.org >>> >>> ___ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >> >> -- >> Samisa Abeysinghe >> Director, Engineering - WSO2 Inc. >> >> http://www.wso2.com/ - "The Open Source SOA Company" >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> > > > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Is carbon trunk compiles and runs?
Isuru Suriarachchi wrote: > Yes, if those artifacts went into dist.wso2, there should be a fixed > version somewhere. Chamra, can you list the artifacts which went into > dist? We have to fix the versions of those components. And also, what > happend to those artifacts which went into dist? Are they removed now? > If not, we have to remove all of those. Isuru, we cannot remove them we need to find that specific release artifact and replace them. Otherwise our builds will fail, this is because if there is a released version in the jar then it is most probably a version which we have already released. Thanks, Ruwan > > Thanks, > ~Isuru > > On Thu, Nov 12, 2009 at 8:47 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Chamara Silva wrote: > > Snapshot repo updated upto carbon orbit.carbon component and carbon > > core repo update plans currently disable now. because some > components > > produce release artifacts and it upload to > http://dist.wso2.com/maven2 > > repo.since 9th of November nightly build fails and repo didn't > update. > > > If it is a release artifact it will be and it has to be uploaded > to the > dist.wso2.com/maven2 <http://dist.wso2.com/maven2> but running > nightly builds and uploading release > artifacts daily is deadly wrong. Please do not include released > artifact > builds in the nightly build. > > If we are to use the artifact uploading we need to follow the maven > model correctly, any project which is under development cannot have a > fixed version it has to be suffixed with SNAPSHOT. > > Thanks, > Ruwan > > http://builder.wso2.org/browse/CBNNIGHTLY-TRNSP-31 > > > > Thank you, > > Regards, > > Chamara > > > > On Thu, Nov 12, 2009 at 6:42 AM, Samisa Abeysinghe > mailto:sam...@wso2.com>> wrote: > > > >> Chamara, any updates on the repos?? > >> Samisa... > >> > >> On Thu, Nov 12, 2009 at 4:32 AM, Afkham Azeez <mailto:az...@wso2.com>> wrote: > >> > >>> I was not able to build. Some missing dependencies and so on. I > >>> thought we agreed to update the snapshot repo & WSO2 Maven repo > >>> regularly. > >>> > >>> Azeez > >>> > >>> On Wed, Nov 11, 2009 at 10:20 PM, Supun Kamburugamuwa > mailto:su...@wso2.com>> > >>> wrote: > >>> > >>>> Has anyone done the $subject recently? > >>>> > >>>> Thanks, > >>>> Supun.. > >>>> > >>>> ___ > >>>> Carbon-dev mailing list > >>>> Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >>>> > >>>> > >>>> > >>> > >>> -- > >>> -- > >>> Afkham Azeez > >>> az...@wso2.com <mailto:az...@wso2.com> > >>> WSO2 Inc. http://wso2.com > >>> Blog: http://afkham.org > >>> > >>> _______ > >>> Carbon-dev mailing list > >>> Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >>> > >> > >> -- > >> Samisa Abeysinghe > >> Director, Engineering - WSO2 Inc. > >> > >> http://www.wso2.com/ - "The Open Source SOA Company" > >> > >> ___ > >> Carbon-dev mailing list > >> Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >> > >> > >> > > > > > > > > > > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 341 3097 > blog: http://blog.ruwan.org > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Some of the svn:externals are wrong in the cabon-platform trunk
This is wrong, Ideally we should try to move to a released version or to the particular trunk. If we are to depend on a internal branch in WSO2 that has to be branched out separately as you did in the ODE case. Please note that if we are depending on a previously released WSO2 branch, for example like wso2v1 version of wss4j there is no need to keep that on the carbon platform, because it is an already released version. Thanks, Ruwan Milinda Pathirage wrote: > Hi devs, > > Here are the set of svn:externals in carbon-platform trunk. > > carbonhttps://svn.wso2.org/repos/wso2/trunk/carbon > carbon-orbithttps://svn.wso2.org/repos/wso2/trunk/carbon-orbit > carbon-components > https://svn.wso2.org/repos/wso2/trunk/carbon-components > axis2 > https://svn.apache.org/repos/asf/webservices/axis2/trunk/java > synapsehttps://svn.apache.org/repos/asf/synapse/trunk/java > ode > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/ode > rampart > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/rampart > wss4j > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/wss4j > transports > https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/transport > commons/caching > https://svn.wso2.org/repos/wso2/trunk/commons/caching > commons/eventinghttps://svn.wso2.org/repos/wso2/trunk/commons/eventing > commons/throttlehttps://svn.wso2.org/repos/wso2/trunk/commons/throttle > commons/xkmshttps://svn.wso2.org/repos/wso2/trunk/commons/xkms > xmlsec > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/xmlsec > sandesha > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/sandesha > savan > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/savan > p2 > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/p2 > rhino > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/rhino > abdera > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.1.0/abdera > axiom > https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom > > According to this list we are getting ode, rampart, wss4j, xmlsec, > sandesha, savan, p2, rhino, abdera from 2.0.1 carbon platform branch. > Is that the correct place to get those. I know for ODE we must get it > from https://svn.wso2.org/repos/wso2/branches/ode/v2.1/. This is the > custom ODE branch we used. What we have followed until now is merge > the changes we did in release branch to this svn location. This branch > is like trunk for Apache ODE. > > Can some with experience about trunk's carbon-platform shed some light > on this. > > Thanks > Milinda > > -- > Milinda Pathirage > Product Manager, Business Process Server - WSO2 Inc > Blog: http://blog.mpathirage.com > ---- > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Some of the svn:externals are wrong in the cabon-platform trunk
Milinda Pathirage wrote: > Also there is a carbon-platform branch called 2.1.0[1] from where > Abdera was taken. It has only synapse, abdera and transports in it. > Who created this for what purpose? This has been created before the idea of a carbon-platform *trunk* representing the trunk versions of the branched projects. This is a stale branch with the introduction of the carbon-platform trunk, and we should remove it. Thanks, Ruwan > > Thanks > Milinda > > [1] https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.1.0/ > > On Tue, Nov 17, 2009 at 8:23 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > This is wrong, Ideally we should try to move to a released version > or to > the particular trunk. If we are to depend on a internal branch in WSO2 > that has to be branched out separately as you did in the ODE case. > > Please note that if we are depending on a previously released WSO2 > branch, for example like wso2v1 version of wss4j there is no need to > keep that on the carbon platform, because it is an already > released version. > > Thanks, > Ruwan > > Milinda Pathirage wrote: > > Hi devs, > > > > Here are the set of svn:externals in carbon-platform trunk. > > > > carbonhttps://svn.wso2.org/repos/wso2/trunk/carbon > > carbon-orbit > https://svn.wso2.org/repos/wso2/trunk/carbon-orbit > > carbon-components > > https://svn.wso2.org/repos/wso2/trunk/carbon-components > > axis2 > > https://svn.apache.org/repos/asf/webservices/axis2/trunk/java > > synapse > https://svn.apache.org/repos/asf/synapse/trunk/java > > ode > > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/ode > > rampart > > > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/rampart > > wss4j > > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/wss4j > > transports > > > > https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/transport > > commons/caching > > https://svn.wso2.org/repos/wso2/trunk/commons/caching > > commons/eventing > https://svn.wso2.org/repos/wso2/trunk/commons/eventing > > commons/throttle > https://svn.wso2.org/repos/wso2/trunk/commons/throttle > > commons/xkms > https://svn.wso2.org/repos/wso2/trunk/commons/xkms > > xmlsec > > > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/xmlsec > > sandesha > > > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/sandesha > > savan > > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/savan > > p2 > > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/p2 > > rhino > > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.0.1/rhino > > abdera > > > https://svn.wso2.org/repos/wso2/branches/carbon-platform/2.1.0/abdera > > axiom > > > https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom > > > > According to this list we are getting ode, rampart, wss4j, xmlsec, > > sandesha, savan, p2, rhino, abdera from 2.0.1 carbon platform > branch. > > Is that the correct place to get those. I know for ODE we must > get it > > from https://svn.wso2.org/repos/wso2/branches/ode/v2.1/. This is the > > custom ODE branch we used. What we have followed until now is merge > > the changes we did in release branch to this svn location. This > branch > > is like trunk for Apache ODE. > > > > Can some with experience about trunk's carbon-platform shed some > light > > on this. > > > > Thanks > > Milinda > > > > -- > > Milinda Pathirage > > Product Manager, Business Process Server - WSO2 Inc > > Blog: http://blog.mpathirage.com > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com&
Re: [Carbon-dev] Using local transport instead of call to OSGi Web service impl object
+1, lets get the local transport polished up and use it for all in-vm calls. Thanks, Ruwan Afkham Azeez wrote: > Hi Folks, > IMO, when the FE & BE reside on the same JVM, it is better yo use the > local transport instead of the OSGi Web service impl object. This way, > we do not have to make major code changes. Also, the security > mechanisms built in for securing the BE services will also work. > > I have been working with the local transport a bit, and there seem to > be no major issues with it. > > Thoughts welcome. > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ESB Url re-write and url parameter extraction
Supun, is this a HTTP GET request?? Thanks, Ruwan Supun Kamburugamuwa wrote: > Hi, > > I'll first explain the requirements. > > Lets say ESB get a URL like this. > > http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2 > <http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2> > > You can see above request is coming in to the proxy named Myproxy. > There are two requirements. > > First requirement is URL re-writing and second one is to extract > parameters from the URL. > > *URL-rewriting*: > > For example the second URL will be something like > > http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2 > <http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2>. > You can see that this is URL rewriting. We are getting a URL to one of > resources inside ESB and ESB send it to another service. The second > URL is constructed by appending the things that doesn't belong to the > Myproxy resource URL to the second resource. Ideal user expectation > is, there is a configuration in the Endpoint saying something like > url-rewrite=true. Then this will automatically happen or there is a > property. > > Do you think this is a genuine requirement in case of ESB? Note this > is specific to HTTP transport. > > *Parameter extraction:* > > The next requirement is to extract the parameters from the URL. I have > started to do this by introducing a new XPath variable context. For > example you can get the parameter named test1 by a XPath expression > like $url:test1. But it seems there is no way to get the parameters > directly from Axis2. Instead we only have access to the full URL. In > that case we need to break it down manually. Do you think this is the > correct approach or is there a way to get the parameters directly from > a hash map? > > Thanks, > Supun.. > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ESB Url re-write and url parameter extraction
Supun Kamburugamuwa wrote: > Sorry they can be GET or POST In that case it is a valid scenario, for GET requests all your requirements can be achieved even now. For POST requests with URL parameters in the request URL, URL re-write will be important. Thanks, Ruwan > > Thanks, > Supun.. > > On Wed, Nov 18, 2009 at 7:46 PM, Supun Kamburugamuwa <mailto:su...@wso2.com>> wrote: > > Yes, they are GET requests. > > Thanks, > Supun.. > > > On Wed, Nov 18, 2009 at 5:46 PM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Supun, is this a HTTP GET request?? > > Thanks, > Ruwan > > Supun Kamburugamuwa wrote: > > Hi, > > > > I'll first explain the requirements. > > > > Lets say ESB get a URL like this. > > > > > http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2 > <http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2> > > > <http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2 > <http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2>> > > > > You can see above request is coming in to the proxy named > Myproxy. > > There are two requirements. > > > > First requirement is URL re-writing and second one is to extract > > parameters from the URL. > > > > *URL-rewriting*: > > > > For example the second URL will be something like > > > > > http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2 > > <http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2> > > > <http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2 > > <http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2>>. > > You can see that this is URL rewriting. We are getting a URL > to one of > > resources inside ESB and ESB send it to another service. The > second > > URL is constructed by appending the things that doesn't > belong to the > > Myproxy resource URL to the second resource. Ideal user > expectation > > is, there is a configuration in the Endpoint saying > something like > > url-rewrite=true. Then this will automatically happen or > there is a > > property. > > > > Do you think this is a genuine requirement in case of ESB? > Note this > > is specific to HTTP transport. > > > > *Parameter extraction:* > > > > The next requirement is to extract the parameters from the > URL. I have > > started to do this by introducing a new XPath variable > context. For > > example you can get the parameter named test1 by a XPath > expression > > like $url:test1. But it seems there is no way to get the > parameters > > directly from Axis2. Instead we only have access to the full > URL. In > > that case we need to break it down manually. Do you think > this is the > > correct approach or is there a way to get the parameters > directly from > > a hash map? > > > > Thanks, > > Supun.. > > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esbWSO2> Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 > 341 3097 > blog: http://blog.ruwan.org > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ESB Url re-write and url parameter extraction
Supun Kamburugamuwa wrote: > > > On Fri, Nov 20, 2009 at 3:36 AM, Supun Kamburugamuwa <mailto:su...@wso2.com>> wrote: > > At the moment there is no way of getting the request parameters as > message context properties. So do you think introducing a XPath > variable context is the right solution? > > > I've done this and it works. But want to get your ideas weather this > is the correct solution. +1, there is a variable context introduced already for the synapse XPath, what you need to do is to register a variable with that context. I guess that is what you have done! So +1 for the approach. Thanks, Ruwan > > Supun.. > > > > This brings me to another question. How about improving the XPath > support of Synapse to be an extension point of Synapse? > > Thanks, > Supun.. > > > On Thu, Nov 19, 2009 at 9:21 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Supun Kamburugamuwa wrote: > > Sorry they can be GET or POST > In that case it is a valid scenario, for GET requests all your > requirements can be achieved even now. For POST requests with URL > parameters in the request URL, URL re-write will be important. > > Thanks, > Ruwan > > > > Thanks, > > Supun.. > > > > On Wed, Nov 18, 2009 at 7:46 PM, Supun Kamburugamuwa > mailto:su...@wso2.com> > > <mailto:su...@wso2.com <mailto:su...@wso2.com>>> wrote: > > > > Yes, they are GET requests. > > > > Thanks, > > Supun.. > > > > > > On Wed, Nov 18, 2009 at 5:46 PM, Ruwan Linton > mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>> wrote: > > > > Supun, is this a HTTP GET request?? > > > > Thanks, > > Ruwan > > > > Supun Kamburugamuwa wrote: > > > Hi, > > > > > > I'll first explain the requirements. > > > > > > Lets say ESB get a URL like this. > > > > > > > > > http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2 > <http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2> > > > <http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2 > <http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2>> > > > > > > <http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2 > <http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2> > > > <http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2 > <http://localhost:8280/services/Myproxy/mytest?test1=1&test2=2>>> > > > > > > You can see above request is coming in to the > proxy named > > Myproxy. > > > There are two requirements. > > > > > > First requirement is URL re-writing and second one > is to extract > > > parameters from the URL. > > > > > > *URL-rewriting*: > > > > > > For example the second URL will be something like > > > > > > > > > http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2 > > <http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2> > > > <http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2 > > <http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2>> > > > > > > <http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2 > > <http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2> > > > <http://myservice:9000/services/mySecondService/mytest?test1=1&test2=2 > > <http://myservice:9000/services/mySecondService/mytest?test1=1&test
Re: [Carbon-dev] carbon-core parent pom change request - 2.0.2 branch
HHhhmm, I am not so clear about the problem that you are trying to solve, but to me this seems like a workaround for the known issue that we are using the carbon parent pom as the parent pom for all the components, which is wrong. Does having a different pom as the parent pom fixes the issue that you are trying to resolve?? If so I would say "lets do it right" Thanks, Ruwan Lahiru Gunathilake wrote: > Anjana, > > On Fri, Nov 20, 2009 at 8:44 AM, Anjana Fernando <mailto:anj...@wso2.com>> wrote: > > Hi, > > Well, after this, the carbon version and the data services component > wont be in sync. It wont be the same version. So if we are releasing > the data services component as 2.0.3 now, maybe in the carbon 2.0.3 > release it would be something like 2.0.4. > > Ok, even thought it's inconsistent .. no idea about some other > solution. Good to wait for some feed back. > > Lahiru > > > Cheers, > Anjana. > > On Fri, Nov 20, 2009 at 8:36 AM, Lahiru Gunathilake > mailto:lah...@wso2.com>> wrote: > > Anjana, > > Are you going to do the release using this approach... ? If yes > I think that > > is wrong because when we do the actual release after you do the > ds release, > > dataservices 2.0.3 components will be replaced in the repository and > > something wrong can happen when someone build > dataservices(2.0.2) after the > > carbon 2.0.3 release. > > > > > > > > Lahiru > > > > On Thu, Nov 19, 2009 at 5:51 PM, Anjana Fernando > mailto:anj...@wso2.com>> wrote: > >> > >> Hello, > >> > >> We are creating a new directory in the data-services carbon > component, > >> which represents a new version as described by the new branching > >> strategy. The new component's version is selected as "2.0.3", > and it's > >> parents pom has a reference to the carbon-core parents pom with the > >> given version "2.0.2". > >> > >> So by this we are expecting the carbon 2.0.2 libraries to be > used by > >> the new component. But in carbon-core, the versions are stated > there > >> as "pom.version", which is expected to pick the version of its pom > >> (which is 2.0.2). But when we reference it from our component - > which > >> has the version 2.0.3 - carbon-core parent treats its > "pom.version" as > >> "2.0.3". So I'm suggesting to change the carbon-core parent pom > to not > >> to use the property "pom.version", but to keep a single property > >> "wso2carbon.version" with the value "2.0.2" and use it in all the > >> places where the version is needed. Here I've attached a diff > with the > >> changes I suggested. Hope for some feedback. > >> > >> Thanks, > >> Anjana. > >> > >> ___ > >> Carbon-dev mailing list > >> Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >> > > > > > > > > -- > > Lahiru Gunathilake > > Software Engineer - WSO2 Inc. > > > > > > > -- > Lahiru Gunathilake > Software Engineer - WSO2 Inc. > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] carbon-core parent pom change request - 2.0.2 branch
Anjana Fernando wrote: > Hello, > > Yeah, actually removing the carbon-core parent pom as our > data-services' parent works. Then I just had to add our own dependency > management section in our own parent pom to get some of the > carbon-core bundles (org.wso2.carbon.core, org.wso2.carbon.user.mgt.ui > etc ..) we need and also some orbit-bundles (poi, gdata .. ) . I > guess, that was the main reason for me to have the carbon-parent pom, > because of the dependency-management. But if we are explicitly stating > that info in our own component, then no problem. > +1, that is the correct approach, I saw this issue earlier and was telling this from a long time (no one care it on those days :-)) and now we can see the difficulties that we have to face with the current approach. I suggest changing all the component poms. I would like to engage in providing the help required for getting this right, lets discuss on next week, (Hopefully - If can make it to office next week) Thanks, Ruwan > Thanks and Regards, > Anjana. > > On Fri, Nov 20, 2009 at 7:42 PM, Ruwan Linton wrote: > >> HHhhmm, I am not so clear about the problem that you are trying to >> solve, but to me this seems like a workaround for the known issue that >> we are using the carbon parent pom as the parent pom for all the >> components, which is wrong. >> >> Does having a different pom as the parent pom fixes the issue that you >> are trying to resolve?? If so I would say "lets do it right" >> >> Thanks, >> Ruwan >> >> Lahiru Gunathilake wrote: >> >>> Anjana, >>> >>> On Fri, Nov 20, 2009 at 8:44 AM, Anjana Fernando >> <mailto:anj...@wso2.com>> wrote: >>> >>> Hi, >>> >>> Well, after this, the carbon version and the data services component >>> wont be in sync. It wont be the same version. So if we are releasing >>> the data services component as 2.0.3 now, maybe in the carbon 2.0.3 >>> release it would be something like 2.0.4. >>> >>> Ok, even thought it's inconsistent .. no idea about some other >>> solution. Good to wait for some feed back. >>> >>> Lahiru >>> >>> >>> Cheers, >>> Anjana. >>> >>> On Fri, Nov 20, 2009 at 8:36 AM, Lahiru Gunathilake >>> mailto:lah...@wso2.com>> wrote: >>> > Anjana, >>> > Are you going to do the release using this approach... ? If yes >>> I think that >>> > is wrong because when we do the actual release after you do the >>> ds release, >>> > dataservices 2.0.3 components will be replaced in the repository and >>> > something wrong can happen when someone build >>> dataservices(2.0.2) after the >>> > carbon 2.0.3 release. >>> > >>> > >>> > >>> > Lahiru >>> > >>> > On Thu, Nov 19, 2009 at 5:51 PM, Anjana Fernando >>> mailto:anj...@wso2.com>> wrote: >>> >> >>> >> Hello, >>> >> >>> >> We are creating a new directory in the data-services carbon >>> component, >>> >> which represents a new version as described by the new branching >>> >> strategy. The new component's version is selected as "2.0.3", >>> and it's >>> >> parents pom has a reference to the carbon-core parents pom with the >>> >> given version "2.0.2". >>> >> >>> >> So by this we are expecting the carbon 2.0.2 libraries to be >>> used by >>> >> the new component. But in carbon-core, the versions are stated >>> there >>> >> as "pom.version", which is expected to pick the version of its pom >>> >> (which is 2.0.2). But when we reference it from our component - >>> which >>> >> has the version 2.0.3 - carbon-core parent treats its >>> "pom.version" as >>> >> "2.0.3". So I'm suggesting to change the carbon-core parent pom >>> to not >>> >> to use the property "pom.version", but to keep a single property >>> >> "wso2carbon.version" with the value "2.0.2" and use it in all the >>> >> places where the version is needed. Here I've attached a diff >>> with the >>> &
[Carbon-dev] Test failure in EC2Client??
There seems to be a test failure in ec2client module of the carbon
components, surefire report attached. Is this local to me??
Thanks,
Ruwan
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
---
Test set: org.wso2.carbon.ec2client.EC2ClientTest
---
Tests run: 11, Failures: 0, Errors: 11, Skipped: 0, Time elapsed: 1.421 sec <<<
FAILURE!
testDescribeImages(org.wso2.carbon.ec2client.EC2ClientTest) Time elapsed:
1.074 sec <<< ERROR!
org.wso2.carbon.ec2client.EC2Exception: Cannot read decoded bytes
at org.wso2.carbon.ec2client.EC2Client.pem2der(EC2Client.java:228)
at org.wso2.carbon.ec2client.EC2Client.init(EC2Client.java:209)
at org.wso2.carbon.ec2client.EC2Client.(EC2Client.java:157)
at org.wso2.carbon.ec2client.EC2ClientTest.setUp(EC2ClientTest.java:71)
at junit.framework.TestCase.runBare(TestCase.java:128)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
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.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:122)
at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
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.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)
Caused by: java.io.FileNotFoundException: ${pk_file} (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:106)
at java.io.FileInputStream.(FileInputStream.java:66)
at java.io.FileReader.(FileReader.java:41)
at org.wso2.carbon.ec2client.utils.PKCS1.readWrappedBody(PKCS1.java:107)
at
org.wso2.carbon.ec2client.utils.PKCS1.readDecodedBytes(PKCS1.java:137)
at org.wso2.carbon.ec2client.EC2Client.pem2der(EC2Client.java:224)
... 24 more
testRunAndTerminateInstances(org.wso2.carbon.ec2client.EC2ClientTest) Time
elapsed: 0.049 sec <<< ERROR!
org.wso2.carbon.ec2client.EC2Exception: Cannot read decoded bytes
at org.wso2.carbon.ec2client.EC2Client.pem2der(EC2Client.java:228)
at org.wso2.carbon.ec2client.EC2Client.init(EC2Client.java:209)
at org.wso2.carbon.ec2client.EC2Client.(EC2Client.java:157)
at org.wso2.carbon.ec2client.EC2ClientTest.setUp(EC2ClientTest.java:71)
at junit.framework.TestCase.runBare(TestCase.java:128)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
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.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:122)
at org.apache.maven.surefire.Surefire.ru
Re: [Carbon-dev] Potential Memory Leak in MultiThreadedHttpConnectionManager may affect Carbon based products
http://www.codepoet.org/~markw/weber/java/ch6/notes.html > <http://www.codepoet.org/%7Emarkw/weber/java/ch6/notes.html> > [5] > > http://www.coderfriendly.com/2009/06/27/inner-classes-static-and-non-static/ > [6] > > https://svn.wso2.org/repos/wso2/trunk/carbon/org.wso2.carbon.registry.core/src/main/java/org/wso2/carbon/registry/app/RemoteRegistry.java > [7] > > http://svn.apache.org/repos/asf/abdera/java/trunk/client/src/main/java/org/apache/abdera/protocol/client/AbderaClient.java > > Thanks, > Senaka. > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com <mailto:sanj...@wso2.com>; phone: +1 408 > 754 7388 x51726; cell: +94 77 787 6880 > blog: http://sanjiva.weerawarana.org/ > > The Open Source SOA Company > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] How to create a new P2 feature & optionally add it to a product build?
Saminda Wijeratne wrote: > the script is used to create the maven project for a p2 feature. a > windows user can always create the maven project manually ;). Sameera > and I sometime back talked abt creating something like maven archtype > to create this maven2 project but I never got around to creating it > yet. for now I'll create the document for both linux (using the > script) and windows (manually create the m2 project). > +1 This is not a user thing mostly it is a developer thing and the developer should be smart enough to do it manually. Or the windows developers may use some third party bridge to run the linux script ;-) Thanks, Ruwan > Saminda > > On Wed, Dec 2, 2009 at 9:41 AM, Samisa Abeysinghe <mailto:sam...@wso2.com>> wrote: > > > > On Wed, Dec 2, 2009 at 9:33 AM, Afkham Azeez <mailto:az...@wso2.com>> wrote: > > Yeah, that will be fine. > > > Nop that is not fine! We have windows users!! > > Samisa... > > > > Azeez > > On Wed, Dec 2, 2009 at 9:28 AM, Saminda Wijeratne > mailto:samin...@wso2.com>> wrote: > > +1 > will do this today. Is it ok if it is linux specific? bcos > we use a linux script to save time on creating p2 features. > > Saminda > > > On Wed, Dec 2, 2009 at 1:20 AM, Supun Kamburugamuwa > mailto:su...@wso2.com>> wrote: > > On Wed, Dec 2, 2009 at 1:15 AM, Afkham Azeez > mailto:az...@wso2.com>> wrote: > > Hi Sameera & Saminda, > > Can you guys please draft a document which briefly > describes how to do > > $subject? I think most people in the team are not > aware on how this is being > > done. It will save a lot of your time as well since > you could point them to > > this doc when people ask about creating P2 features. > Can we get this done > > ASAP? > > > > +1. This will be really useful. > > Thanks, > Supun. > > > Thanks > > -- > > Afkham Azeez > > az...@wso2.com <mailto:az...@wso2.com> > > WSO2 Inc. http://wso2.com > > Blog: http://afkham.org > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Time for 2.0.3
> -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source > SOA Company" > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > <mailto:Carbon-dev@wso2.org> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Milinda Pathirage > Product Manager, Business Process Server - > WSO2 Inc > Blog: http://blog.mpathirage.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Tyrell Perera > > WSO2, Inc.; http://www.wso2.com/ > "The Open Source SOA Company" > > http://www.linkedin.com/in/tyrell > http://tyrellperera.blogspot.com > http://twitter.com/tyrellperera > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Milinda Pathirage > Product Manager, Business Process Server - WSO2 Inc > Blog: http://blog.mpathirage.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Senaka Fernando > Software Engineer > WSO2 Inc. > E-mail: sen...@wso2.com <mailto:sen...@wso2.com>; Mobile: > +94 77 322 1818 > > > http://www.wso2.com/ - "The Open Source SOA Company" > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Milinda Pathirage > Product Manager, Business Process Server - WSO2 Inc > Blog: http://blog.mpathirage.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Senaka Fernando > Software Engineer > WSO2 Inc. > E-mail: sen...@wso2.com <mailto:sen...@wso2.com>; Mobile: +94 77 > 322 1818 > > http://www.wso2.com/ - "The Open Source SOA Company" > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Milinda Pathirage > Product Manager, Business Process Server - WSO2 Inc > Blog: http://blog.mpathirage.com > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Can we disable mediaation stats with P2?
Samisa Abeysinghe wrote: > For BAM mediation publisher to correctly work, we need to be able to > remove mediation stat component. > > Can we do that with P2? Yes, we should be able to. > > Samisa... > > P.S. Hiranya is working on a new model for mediation stats to deal > with this problem in future releases! AFAIK, it is done. Thanks, Ruwan > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Multiple orbit bundles for different versions of same jar
Milinda Pathirage wrote: > Hi devs, > > We have multiple orbit bundles for different version of same third > party library. For example we have saxon 9.x version for bps and 8.9 > for ESB. Also we have two bundles for rhino and another two for axiom. > I think we can remove those older versions from orbit because we > published old versions in to maven repo and no need to keep two > versions in orbit. Is it ok to remove old versions and keep newest > version only? We need to test the ESB with the new version of the saxon before removing it. Thanks, Ruwan > > thanks > Milinda > > -- > Milinda Pathirage > Product Manager, Business Process Server - WSO2 Inc > Blog: http://blog.mpathirage.com > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Multiple orbit bundles for different versions of same jar
Milinda Pathirage wrote: > We don't need to keep old version. Because its already already in the > maven repo. Good point, then why do we need saxon 9.x it is also there on the repo unless we introduce a new version of saxon we do not need that as well. Milinda, we might need to fix issue (like imports and exports) and do a wso2v2 version of the orbit saxon-8.9 please do not remove that till we test the ESB with the 9.x verison. BTW: what exactly is the version of Saxon that you are using in BPS? Thanks, Ruwan > > Thanks, > Milinda > > On Sat, Dec 5, 2009 at 12:06 PM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Milinda Pathirage wrote: > > Hi devs, > > > > We have multiple orbit bundles for different version of same third > > party library. For example we have saxon 9.x version for bps and 8.9 > > for ESB. Also we have two bundles for rhino and another two for > axiom. > > I think we can remove those older versions from orbit because we > > published old versions in to maven repo and no need to keep two > > versions in orbit. Is it ok to remove old versions and keep newest > > version only? > We need to test the ESB with the new version of the saxon before > removing it. > > Thanks, > Ruwan > > > > thanks > > Milinda > > > > -- > > Milinda Pathirage > > Product Manager, Business Process Server - WSO2 Inc > > Blog: http://blog.mpathirage.com > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 341 3097 > blog: http://blog.ruwan.org > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Milinda Pathirage > Product Manager, Business Process Server - WSO2 Inc > Blog: http://blog.mpathirage.com > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Multiple orbit bundles for different versions of same jar
+1 At the mean time I will try to move the ESB saxon version to 9.x. BTW: With this structure you have to name the branch with the exact version, 9.1 or 9.0 or so. Thanks, Ruwan Milinda Pathirage wrote: > We can solve this issue with new svn structure. We can have multiple > versions of same orbit bundle in the svn. The only thing we need to do > is remove different orbit bundles for different versions and move them > to once parent. For example: > > saxon/ >8.9/ >9.x/ > > Thanks, > Milinda > > On Sat, Dec 5, 2009 at 6:41 PM, Lahiru Gunathilake <mailto:lah...@wso2.com>> wrote: > > > > On Sat, Dec 5, 2009 at 6:35 PM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Milinda Pathirage wrote: > > We don't need to keep old version. Because its already > already in the > > maven repo. > Good point, then why do we need saxon 9.x it is also there on > the repo > unless we introduce a new version of saxon we do not need that > as well. > > Milinda, we might need to fix issue (like imports and exports) > and do a > wso2v2 version of the orbit saxon-8.9 please do not remove > that till we > test the ESB with the 9.x verison. > > If doing a change I think we have to do it in the latest version > and if we are working on trunk we should change the places where > we use that particular orbit bundle and update them to new > version. Otherwise things might go wrong. > > > Regards > Lahiru > > > BTW: what exactly is the version of Saxon that you are using > in BPS? > > Thanks, > Ruwan > > > > Thanks, > > Milinda > > > > On Sat, Dec 5, 2009 at 12:06 PM, Ruwan Linton > mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>> wrote: > > > > Milinda Pathirage wrote: > > > Hi devs, > > > > > > We have multiple orbit bundles for different version > of same third > > > party library. For example we have saxon 9.x version > for bps and 8.9 > > > for ESB. Also we have two bundles for rhino and > another two for > > axiom. > > > I think we can remove those older versions from orbit > because we > > > published old versions in to maven repo and no need to > keep two > > > versions in orbit. Is it ok to remove old versions and > keep newest > > > version only? > > We need to test the ESB with the new version of the > saxon before > > removing it. > > > > Thanks, > > Ruwan > > > > > > thanks > > > Milinda > > > > > > -- > > > Milinda Pathirage > > > Product Manager, Business Process Server - WSO2 Inc > > > Blog: http://blog.mpathirage.com > > > > > > > -------- > > > > > > ___ > > > Carbon-dev mailing list > > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> > > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > -- > > Ruwan Linton > > Technical Lead & Product Manager; WSO2 ESB; > http://wso2.org/esb > > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > > email: ru...@wso2.com <mailto:ru...@wso2.com> > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>; cell: +94 77 > 341 3097 > > blog: http://blog.ruwan.org > > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/
Re: [Carbon-dev] Time for 2.0.3
lto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Milinda Pathirage > Product Manager, Business Process Server - WSO2 Inc > Blog: http://blog.mpathirage.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Multiple orbit bundles for different versions of same jar
Milinda Pathirage wrote: > This saxon is patched version by Intalio for ODE. That's why version > is 9.x. ODE guys are in the process of migrating saxon 9.1.0.8. We'll > migrate to that version once they are done with it. Milinda, what is the diff?? why do they have to patch saxon?? will the patch be an issue for the ESB?? Thanks, Ruwan > > Thanks > Milinda > > On Sun, Dec 6, 2009 at 5:35 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > +1 > > At the mean time I will try to move the ESB saxon version to 9.x. > > BTW: With this structure you have to name the branch with the exact > version, 9.1 or 9.0 or so. > > Thanks, > Ruwan > > Milinda Pathirage wrote: > > We can solve this issue with new svn structure. We can have multiple > > versions of same orbit bundle in the svn. The only thing we need > to do > > is remove different orbit bundles for different versions and > move them > > to once parent. For example: > > > > saxon/ > >8.9/ > >9.x/ > > > > Thanks, > > Milinda > > > > On Sat, Dec 5, 2009 at 6:41 PM, Lahiru Gunathilake > mailto:lah...@wso2.com> > > <mailto:lah...@wso2.com <mailto:lah...@wso2.com>>> wrote: > > > > > > > > On Sat, Dec 5, 2009 at 6:35 PM, Ruwan Linton <mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>> wrote: > > > > Milinda Pathirage wrote: > > > We don't need to keep old version. Because its already > > already in the > > > maven repo. > > Good point, then why do we need saxon 9.x it is also > there on > > the repo > > unless we introduce a new version of saxon we do not > need that > > as well. > > > > Milinda, we might need to fix issue (like imports and > exports) > > and do a > > wso2v2 version of the orbit saxon-8.9 please do not remove > > that till we > > test the ESB with the 9.x verison. > > > > If doing a change I think we have to do it in the latest version > > and if we are working on trunk we should change the places where > > we use that particular orbit bundle and update them to new > > version. Otherwise things might go wrong. > > > > > > Regards > > Lahiru > > > > > > BTW: what exactly is the version of Saxon that you are using > > in BPS? > > > > Thanks, > > Ruwan > > > > > > Thanks, > > > Milinda > > > > > > On Sat, Dec 5, 2009 at 12:06 PM, Ruwan Linton > > mailto:ru...@wso2.com> > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>> > > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com> > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>>> wrote: > > > > > > Milinda Pathirage wrote: > > > > Hi devs, > > > > > > > > We have multiple orbit bundles for different version > > of same third > > > > party library. For example we have saxon 9.x version > > for bps and 8.9 > > > > for ESB. Also we have two bundles for rhino and > > another two for > > > axiom. > > > > I think we can remove those older versions from > orbit > > because we > > > > published old versions in to maven repo and no > need to > > keep two > > > > versions in orbit. Is it ok to remove old > versions and > > keep newest > > > > version only? > > > We need to test the ESB with the new version of the > > saxon before > > > removing it. > > > > > > Thanks, > > > Ruwan > > > > > > > > thanks > > > > Milinda > > > > > &g
Re: [Carbon-dev] Multiple orbit bundles for different versions of same jar
Milinda Pathirage wrote: > the patch is for 9.1.0.2 version of Saxon. According to the > JIRAS[1][2] patch is there in the newest versions of Saxon. I'll test > it and migrate to newest version. +1 Ruwan > > Thanks > Milinda > > [1] https://issues.apache.org/jira/browse/ODE-369 > [2] https://issues.apache.org/jira/browse/ODE-728 > > On Sun, Dec 6, 2009 at 8:22 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Milinda Pathirage wrote: > > This saxon is patched version by Intalio for ODE. That's why version > > is 9.x. ODE guys are in the process of migrating saxon 9.1.0.8. > We'll > > migrate to that version once they are done with it. > Milinda, > > what is the diff?? > why do they have to patch saxon?? > will the patch be an issue for the ESB?? > > Thanks, > Ruwan > > > > Thanks > > Milinda > > > > On Sun, Dec 6, 2009 at 5:35 AM, Ruwan Linton <mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>> wrote: > > > > +1 > > > > At the mean time I will try to move the ESB saxon version to > 9.x. > > > > BTW: With this structure you have to name the branch with > the exact > > version, 9.1 or 9.0 or so. > > > > Thanks, > > Ruwan > > > > Milinda Pathirage wrote: > > > We can solve this issue with new svn structure. We can > have multiple > > > versions of same orbit bundle in the svn. The only thing > we need > > to do > > > is remove different orbit bundles for different versions and > > move them > > > to once parent. For example: > > > > > > saxon/ > > >8.9/ > > >9.x/ > > > > > > Thanks, > > > Milinda > > > > > > On Sat, Dec 5, 2009 at 6:41 PM, Lahiru Gunathilake > > mailto:lah...@wso2.com> > <mailto:lah...@wso2.com <mailto:lah...@wso2.com>> > > > <mailto:lah...@wso2.com <mailto:lah...@wso2.com> > <mailto:lah...@wso2.com <mailto:lah...@wso2.com>>>> wrote: > > > > > > > > > > > > On Sat, Dec 5, 2009 at 6:35 PM, Ruwan Linton > mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>> > > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com> > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>>> wrote: > > > > > > Milinda Pathirage wrote: > > > > We don't need to keep old version. Because its > already > > > already in the > > > > maven repo. > > > Good point, then why do we need saxon 9.x it is also > > there on > > > the repo > > > unless we introduce a new version of saxon we do not > > need that > > > as well. > > > > > > Milinda, we might need to fix issue (like imports and > > exports) > > > and do a > > > wso2v2 version of the orbit saxon-8.9 please do > not remove > > > that till we > > > test the ESB with the 9.x verison. > > > > > > If doing a change I think we have to do it in the > latest version > > > and if we are working on trunk we should change the > places where > > > we use that particular orbit bundle and update them to new > > > version. Otherwise things might go wrong. > > > > > > > > > Regards > > > Lahiru > > > > > > > > > BTW: what exactly is the version of Saxon that you > are using > > > in BPS? > > > > > > Thanks, > > > Ruwan > > > > > > > > Thanks, > > > > Milinda > > > > > > > > On Sat, Dec 5, 2009 at 12:06 PM, Ruwan Linton > > &
Re: [Carbon-dev] Error building BAM : Missing: au.com.bytecode.opencsv:opencsv:jar:${opencsv.version}
Seems like the ${opencsv.version} property has not been resolved to the
respective value. Do you have the property opencsv.version set at the
scope of the referred dependency.
Thanks,
Ruwan
Samisa Abeysinghe wrote:
> Comes from a DS dependency. Building online does not work. Looks like
> 1.8 of opencsv:opencsv:jar is in my repo.
>
> Thoughts please...
>
> Downloading:
> http://dist.wso2.org/maven2/au/com/bytecode/opencsv/opencsv/${opencsv.version}/opencsv-${opencsv.version}.jar
> <http://dist.wso2.org/maven2/au/com/bytecode/opencsv/opencsv/$%7Bopencsv.version%7D/opencsv-$%7Bopencsv.version%7D.jar>
> Downloading:
> http://tomcat.apache.org/dev/dist/m2-repository/au/com/bytecode/opencsv/opencsv/${opencsv.version}/opencsv-${opencsv.version}.jar
> <http://tomcat.apache.org/dev/dist/m2-repository/au/com/bytecode/opencsv/opencsv/$%7Bopencsv.version%7D/opencsv-$%7Bopencsv.version%7D.jar>
> Downloading:
> http://ws.zones.apache.org/repository2/au/com/bytecode/opencsv/opencsv/${opencsv.version}/opencsv-${opencsv.version}.jar
> <http://ws.zones.apache.org/repository2/au/com/bytecode/opencsv/opencsv/$%7Bopencsv.version%7D/opencsv-$%7Bopencsv.version%7D.jar>
> Downloading:
> http://repo1.maven.org/maven2/au/com/bytecode/opencsv/opencsv/${opencsv.version}/opencsv-${opencsv.version}.jar
> <http://repo1.maven.org/maven2/au/com/bytecode/opencsv/opencsv/$%7Bopencsv.version%7D/opencsv-$%7Bopencsv.version%7D.jar>
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
>
> Missing:
> --
> 1) au.com.bytecode.opencsv:opencsv:jar:${opencsv.version}
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=au.com.bytecode.opencsv
> -DartifactId=opencsv -Dversion=${opencsv.version} -Dpackaging=jar
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the
> file there:
> mvn deploy:deploy-file -DgroupId=au.com.bytecode.opencsv
> -DartifactId=opencsv -Dversion=${opencsv.version} -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -
> DrepositoryId=[id]
>
> Path to dependency:
> 1) org.wso2.bam:wso2bam:jar:1.0.0-beta001
> 2)
> org.wso2.carbon.dataservices:org.wso2.carbon.dataservices.core:jar:2.0.2.1
> 3) au.com.bytecode.opencsv:opencsv:jar:${opencsv.version}
>
> --
> 1 required artifact is missing.
>
> for artifact:
> org.wso2.bam:wso2bam:jar:1.0.0-beta001
>
> from the specified remote repositories:
> m2-snapshot-repository
> (http://people.apache.org/repo/m2-snapshot-repository),
> wso2-maven2-repository (http://dist.wso2.org/maven2),
> ws-zones-repository (http://ws.zones.apache.org/repository2),
> tomcat-repository (http://tomcat.apache.org/dev/dist/m2-repository),
> central (http://repo1.maven.org/maven2)
>
>
>
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 8 minutes 30 seconds
> [INFO] Finished at: Sun Dec 06 18:35:45 IST 2009
> [INFO] Final Memory: 49M/121M
> [INFO]
>
>
> --
> Samisa Abeysinghe
> Director, Engineering - WSO2 Inc.
>
> http://www.wso2.com/ - "The Open Source SOA Company"
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Error building BAM : Missing: au.com.bytecode.opencsv:opencsv:jar:${opencsv.version}
Samisa Abeysinghe wrote:
>
>
> On Sun, Dec 6, 2009 at 6:45 PM, Ruwan Linton <mailto:ru...@wso2.com>> wrote:
>
> Seems like the ${opencsv.version} property has not been resolved
> to the
> respective value. Do you have the property opencsv.version set at the
> scope of the referred dependency.
>
>
> Where? in BAM pom? I do not see such a property in BAM pom. I thought
> DS should set that.
Need to have a look at the source, can you point me to the source?
Thanks,
Ruwan
>
> Samisa...
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] BAM rlease - can we code freeze today?
.RuntimeException: Error obtaining parser from
> data source:DS Fault Message: Error in 'CallQuery.extractParams',
> cannot find Param with type:co
> lumn name:monthno
> Source Data Service:-
> Name: BAMSummaryGenerationDS
> Location:
> E:\testing\WSO2BA~1.0-B\bin\..\repository\dataservices\BAMSummaryGenerationDS.dbs
> Description: N/A
> Default Namespace: http://ws.wso2.org/dataservice
> Current Request Name: getMonthDim
> Current Params: {monthId=2}
>
> at
> org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getDirectReader(OMSourcedElementImpl.java:231)
> at
> org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getXMLStreamReaderWithoutCaching(OMSourcedElementImpl.java:517)
> at
> org.wso2.carbon.bam.core.client.BAMSummaryGenerationDSClient.fromOM(BAMSummaryGenerationDSClient.java:4476)
> ... 10 more
> [2009-12-07 04:49:16,140] ERROR - Failed retrieving endpoint list.
>
> Samisa...
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Usage of geronimo-jta in WSO2 ESB.
I remember some reason to have these in-place, Indika do you remember why?? Thanks, Ruwan Sameera Jayasoma wrote: > Hi devs, > > In the ESB distribution, geronimo-jta jar file is available as an OSGi > bundle and as an Extension bundle. Is there any specific reason for > this? Following is the output of the "p javax.transaction" command > executed in the OSGi console. This command is used to display > imported/exported package details > > osgi> p javax.transaction > *javax.transaction; version="0.0.0" [0]>* (System bundle extension) > axis2-transport-jms_1.0.0.wso2v1 [57] imports > axis2_1.5.0.wso2v2 [82] imports > synapse-core_1.3.0.wso2v2 [87] imports > quartz_1.6.0.wso2v1 [104] imports > compass_2.0.1.wso2v1 [112] imports > org.eclipse.core.expressions_3.4.100.v20090429-1800 [304] imports > org.eclipse.core.net_1.2.0.I20090522-1010 [306] imports > org.eclipse.core.runtime_3.5.0.v20090429-1800 [307] imports > org.eclipse.equinox.p2.director.app_1.0.100.v20090521-1912 [322] imports > org.eclipse.equinox.p2.engine_1.0.100.v20090520-1905 [324] imports > org.eclipse.equinox.p2.garbagecollector_1.0.100.v20090520-1905 [327] > imports > org.eclipse.equinox.p2.metadata.generator_1.0.100.v20090520-1905 > [330] imports > org.eclipse.equinox.p2.metadata.repository_1.0.100.v20090520-1905 > [331] imports > *javax.transaction; version="0.0.0" [83]>* (Bundle) > > Shall we remove one of them? It seems that no other bundle is > importing javax.transaction.* packages exported by the geranimo-jta > bundle. Safer option is to delete the geranimo-jta bundle. > > Thanks > Sameera > > > > > _______ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Removing 'solutions' parent directory from governance svn branch location
+1 Ruwan Samisa Abeysinghe wrote: > +1. > > Samisa... > > > On Tue, Dec 8, 2009 at 8:25 AM, Sanjiva Weerawarana <mailto:sanj...@wso2.com>> wrote: > > +1. > > On Tue, Dec 8, 2009 at 7:40 AM, Milinda Pathirage > mailto:mili...@wso2.com>> wrote: > > Hi Devs, > > SVN branch for latest Governance release contains 'solutions' > directory as its parent like following. > > https://svn.wso2.org/repos/wso2/branches/solutions/governance/3.0.2/ > > With the new SVN structure changes all the products are go in > to '../branches/carbon/2.0.3/products/' directory and we don't > need solutions parent directory from this point onward. So in > Governance case branch will look like following: > > .../branches/carbon/2.0.3/products/governance/3.0.3/... > > Is it ok to do this change? WDYT about this change? > > Thanks > Milinda > > -- > Milinda Pathirage > Product Manager, Business Process Server - WSO2 Inc > Blog: http://blog.mpathirage.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com <mailto:sanj...@wso2.com>; phone: +1 408 > 754 7388 x51726; cell: +94 77 787 6880 > blog: http://sanjiva.weerawarana.org/ > > > The Open Source SOA Company > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ESB trunk freezing during shutdown
Seems like a deadlock in the shutdown path, need to fix this ASAP, issue seems to be at the following logic; org.wso2.carbon.dnsserverregistration.ServerRegistration.unregisterServer(ServerRegistration.java:109) at org.wso2.carbon.dnsserverregistration.internal.ServerRegistrationComponent.deactivate(ServerRegistrationComponent.java:81) Thanks, Ruwan Lahiru Gunathilake wrote: > This is not coming always i guess. I sometimes get this in gaas but > not always. We have the gaas branch created more than 1.5 months back. > > Lahiru > > On Wed, Dec 9, 2009 at 10:24 AM, Waruna Ranasinghe <mailto:war...@wso2.com>> wrote: > > Hi, > We also see this issue in BPS too.. > > > Thanks, > Waruna > > > On Wed, Dec 9, 2009 at 10:18 AM, Thilina Mahesh Buddhika > mailto:thili...@wso2.com>> wrote: > > Hi, > > I also have experienced it when shutting down IS. So it seems > like this is applicable to all Carbon based products. > > thanks. > /thilina > > On Wed, Dec 9, 2009 at 10:01 AM, Miyuru Wanninayaka > mailto:miy...@wso2.com>> wrote: > > Hi all, > > ESB *trunk* is freezing sometimes during shutting down and > the only solution to stop after this is killing jvm. Looks > like a dead lock. I have attached the thread dump. > > Thanks, > Miyuru > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Thilina Mahesh Buddhika > > WSO2 Inc. ; http://wso2.com > http://blog.thilinamb.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Lahiru Gunathilake > Software Engineer - WSO2 Inc. > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon startup time drastically increased!
Azeez,
This is because of the JmDNS thing, basically server registration which
is causing the shutdown dead-lock as well.
Thanks,
Ruwan
Afkham Azeez wrote:
> Why is this?
>
> After the HTTP & HTTPS ports are printed out, it takes a long time to
> print the next line:
>
> Registered Server as: ${product.name
> <http://product.name>}._wso2server._tcp.local
>
> --
> --
> Afkham Azeez
> az...@wso2.com <mailto:az...@wso2.com>
> WSO2 Inc. http://wso2.com
> Blog: http://afkham.org
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon startup time drastically increased!
Afkham Azeez wrote:
> Ratha,
> You have written the ServerRegistration class. There is no class level
> comment which gives an indication what that class does. Also, if the
> registration fails, you are simply doing an e.printstacktrace().
>
> During every code review session, we keep repeating that these simple
> things have to be adhered to. Yet, it keeps falling on deaf ears!
>
> I'm wondering whether it is acceptable to do the server registration
> in a separate thread.
Yes I was having a discussion with Senaka in the evening and was having
the same thought. BTW: all these has to be optional isn't it, we
shouldn't make the simple case complex.
I had a separate chat with Hiranya on adding the ability specify
parameters in the carbon.xml like in axis2 so that we can let those
parameters configure these sorts of stuff.
Thanks,
Ruwan
>
> Azeez
>
> On Wed, Dec 9, 2009 at 7:36 PM, Afkham Azeez <mailto:az...@w2.com>> wrote:
>
> Why is this?
>
> After the HTTP & HTTPS ports are printed out, it takes a long time
> to print the next line:
>
> Registered Server as: ${product.name
> <http://product.name>}._wso2server._tcp.local
>
> --
> --
> Afkham Azeez
> az...@wso2.com <mailto:az...@wso2.com>
> WSO2 Inc. http://wso2.com
> Blog: http://afkham.org
>
>
>
>
> --
> --
> Afkham Azeez
> az...@wso2.com <mailto:az...@wso2.com>
> WSO2 Inc. http://wso2.com
> Blog: http://afkham.org
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Server shutdown & restart handlers
___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Lahiru Gunathilake > Software Engineer - WSO2 Inc. > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon startup time drastically increased!
+1 Ruwan Afkham Azeez wrote: > Please remove this from Carbon core ASAP & move it into a separate > component. There is an extensible feature and there is no need for it > to be in the core. > > Azeez > > On Wed, Dec 9, 2009 at 11:22 PM, Hiranya Jayathilaka <mailto:hira...@wso2.com>> wrote: > > > > On Wed, Dec 9, 2009 at 11:00 PM, ratha <mailto:rat...@wso2.com>> wrote: > > Hiranya Jayathilaka wrote: > > What does this server registration component actually do? Is > it same > > as what WS-D does (ie publishing service endpoints to a > discovery > > proxy and searching for service endpoints published by > peers)? In that > > case +1 for removing it. Now that we have solved this > problem the > > standard way, no need to have another custom solution. > > > > But my gut feeling is this is something different from WS-D. Can > > somebody please confirm? > > > > > Here server registration happens using zeroconf protocol. Zeroconf > enables the automatic configuration of network services, > through the use > of multicast on local networks. > So when we register a carbon server with JmDNS( dns server , > zeroconf > java implementation) , the services which are deployed in that > particular server can be accessible via the network. > > > Thanks for the clarification. I agree that having Carbon support > the Zeroconf protocol is totally cool. However we need to make > this functionality optional/configurable. IMO we should keep this > feature turned off by default and allow the user to turn it on if > required. Most users will not be interested in features > sophisticated as this one. > > What would be even better is to separate out this functionality > from the Carbon core and put it into its own Carbon component. > That's the approach we have taken for the WS-D support. Then we > can easily create P2 features out of such components and enable > interested parties to get them installed. WDYT? Is it feasible to > do that? > > Thanks, > Hiranya > > > /Zero configuration networking is good for environments where > administration is impractical or impossible.It is intended for > small > networks, ad-hoc networks or situations where devices need to > communicate > with each other over a direct connection.There is no provision > forrouting traffic in and out of the Zeroconf network.The > beauty of > Zeroconf Networking is that the protocols it defines are small > extensions of existing network protocols, and they coexist > peacefully > with their > centrally configured brethren. Also, the Zeroconf protocols do not > depend on each other: one can function in the absence of others./ > > > Thanks. > -Ratha. > > Thanks, > > Hiranya > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com <mailto:hira...@wso2.com>; Mobile: +94 > 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Server URL on ESB home page
We have once discussed to hide this and have a expand icon to show this text box if someone needs to change it, as in try-it. Well, that will not solve the problem in hand, but we will have enough space to describe the BE server URL in that case since it is hidden for normal logins. Thanks, Ruwan Samisa Abeysinghe wrote: > > > On Wed, Dec 9, 2009 at 11:32 AM, Afkham Azeez <mailto:az...@wso2.com>> wrote: > > This is the BE server to which you are pointing to. The FE server > has to provide this field in order to administer a different BE > server. > > This has nothing to do with the actual endpoints. > > > So there is a real usability problem here. I look at it and think that > to be the service endpoint. There is no mention on the BE here in this > page. > > Samisa.. > . > > > Azeez > > On Wed, Dec 9, 2009 at 9:03 AM, Samisa Abeysinghe <mailto:sam...@wso2.com>> wrote: > > $subject is shown to be https://10.100.1.103:9445/esb/services/ > > Note that, this is really the WSAS server URL. Not the > location where the ESB services are available. Minor issue but > need to fix. > > Samisa... > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > > http://www.wso2.com/ - "The Open Source SOA Company" > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] When happens to ESB when a back end service IP change at run time
Supun, What is the issue that we are trying to solve here? I am sorry I am confused :-( . ESB (to be more specific the nhttp transport) uses a connection pool to support keep-alive, if you want each and every request going out from ESB lookup the DNS and create a new connection, you may disable keep-alive by putting a property named http.connection.disable.keepalive into the nhttp.properties file. Yet again if a DNS change has been occurred while trying to reuse an existing connection, it will fail and the connection will be reset and there is a retry on the endpoint which is configurable and will connect to the correct endpoint. I am sorry, I don't see any issue here :-( Thanks, Ruwan Supun Kamburugamuwa wrote: > Actually this is not the server side of ESB that I'm talking about. It > is the client side of the ESB. > > Anyway if we can test a scenario like this it will be great. > > >From code here is what should happen. > > We have a connection pool with host name and ip address. So even > though the DNS server is configured to point to a new IP address for a > host name, the connection pool doesn't change. For these connections > to become un-usable the back end server which hosted the services > should be shut down. Until that ESB can still send messages to the old > server because it is taking connections from a connection pool. > > When ESB creates new connections after the DNS change, it will do it > correctly. > > Thanks, > Supun.. > > On Sat, Dec 12, 2009 at 12:15 PM, Senaka Fernando wrote: > >> Hi Supun, >> >> If you have configured the server to use the host name instead of the ip >> address, it should work without any issues. If you did use the ip address as >> the host name or didn't specify it, the change in ip address could cause >> some aspects not to work, such as calculated EPRs in EventBrokers. >> >> Thanks, >> Senaka. >> >> On Sat, Dec 12, 2009 at 9:35 AM, Afkham Azeez wrote: >> >>> Yeah, not only for ESB, but for any generic client-server system this >>> should not cause any problems as long as the first machine is kept online >>> until all requests it received have been served. If that machine is taken >>> offline immediately, the request which were in flight and which were being >>> processed will fail. So there should be a graceful mechanism to do this, >>> like our graceful shutdown procedure. Subsequent requests should be >>> successfully forwarded to the new machine though. >>> Azeez >>> >>> On Sat, Dec 12, 2009 at 5:23 AM, Supun Kamburugamuwa >>> wrote: >>> >>>> Hi, >>>> >>>> Suppose we have several back end services and ESB refer to them using >>>> a URL. These URLs are DNS resolvable URLs not IP address. Suppose we >>>> substitute a new physical machine with a different IP and configure >>>> the DNS server to point to the new IP for the same old URL. The >>>> question is what will happen? >>>> >>>> From the code it seems ESB will work correctly. I thought of bringing >>>> this question up to make sure that it will work. >>>> >>>> Thanks, >>>> Supun.. >>>> >>>> ___ >>>> Carbon-dev mailing list >>>> Carbon-dev@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>> >>> -- >>> -- >>> Afkham Azeez >>> az...@wso2.com >>> WSO2 Inc. http://wso2.com >>> Blog: http://afkham.org >>> >>> ___ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> -- >> Senaka Fernando >> Software Engineer >> WSO2 Inc. >> E-mail: sen...@wso2.com; Mobile: +94 77 322 1818 >> >> http://www.wso2.com/ - "The Open Source SOA Company" >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Killing the Endpoint Publisher Component
Hiranya Jayathilaka wrote: > Hi Folks, > > Now that the WS-D effort is in good shape, the endpoint-publisher > component is not necessary any more. This component is not complete > and was never used anyway. So shall we remove it from the trunk? +1 Thanks, Ruwan > > Thanks, > Hiranya > > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com <mailto:hira...@wso2.com>; Mobile: +94 77 > 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] In-VM service calls to the BE via OSGi services???
Folks, Are we going to continue using $subject?? I had an off-line chat with Azeez and we believe that we better get rid of due to security concerns specially with the introduction of the multi-tenancy. In that case we better get rid of the common bundles that we have introduced to get the OSGi service BE model working (Since that will increase the number of bundles by nearly 30%). So the option that is available for the in-vm calls is to use the local transport. WDYT? Thanks, Ruwan -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Repositories listed on the carbon-orbit pom
Folks, Why do we have repositories like people.apache.org and javanet, I guess we do have all the artifacts on the dist.wso2.org repository now. So we need to get rid of the other repositories. Specially it is not recommended to use the people.apache.org repo, it is just for the apache artifact synchronization with the main maven repositories. Shall we get rid of the other repositories?? That will increase the on-line build time drastically, since it reduces unwanted artifact lookups in these repositories. Also this will make sure that we put all the newly added artifacts into the dist.wso2.org repository since the build will fail otherwise. Thanks, Ruwan -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Repositories listed on the carbon-orbit pom
Senaka Fernando wrote: > > > On Sat, Dec 19, 2009 at 9:35 PM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Folks, > > Why do we have repositories like people.apache.org > <http://people.apache.org> and javanet, I guess > we do have all the artifacts on the dist.wso2.org > <http://dist.wso2.org> repository now. So we > need to get rid of the other repositories. > > Specially it is not recommended to use the people.apache.org > <http://people.apache.org> repo, it is > just for the apache artifact synchronization with the main maven > repositories. > > Shall we get rid of the other repositories?? That will increase the > on-line build time drastically, since it reduces unwanted artifact > lookups in these repositories. Also this will make sure that we > put all > the newly added artifacts into the dist.wso2.org > <http://dist.wso2.org> repository since the > build will fail otherwise. > > > +1. That should also solve the recent issues we had with regard to > repositories becoming unavailable all of a sudden. Yeah. That is why we wanted all the artifacts to be on the dist.wso2.org and we are not using that properly, if we still have the other repositories on the poms. Thanks, Ruwan > > Thanks, > Senaka. > > > Thanks, > Ruwan > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 341 3097 > blog: http://blog.ruwan.org > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Senaka Fernando > Software Engineer > WSO2 Inc. > E-mail: sen...@wso2.com <mailto:sen...@wso2.com>; Mobile: +94 77 322 1818 > > http://www.wso2.com/ - "The Open Source SOA Company" > ---- > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Repositories listed on the carbon-orbit pom
Same with carbon pom, I will commit the fixes after testing on a fresh repo. Thanks, Ruwan Ruwan Linton wrote: > Senaka Fernando wrote: > >> On Sat, Dec 19, 2009 at 9:35 PM, Ruwan Linton > <mailto:ru...@wso2.com>> wrote: >> >> Folks, >> >> Why do we have repositories like people.apache.org >> <http://people.apache.org> and javanet, I guess >> we do have all the artifacts on the dist.wso2.org >> <http://dist.wso2.org> repository now. So we >> need to get rid of the other repositories. >> >> Specially it is not recommended to use the people.apache.org >> <http://people.apache.org> repo, it is >> just for the apache artifact synchronization with the main maven >> repositories. >> >> Shall we get rid of the other repositories?? That will increase the >> on-line build time drastically, since it reduces unwanted artifact >> lookups in these repositories. Also this will make sure that we >> put all >> the newly added artifacts into the dist.wso2.org >> <http://dist.wso2.org> repository since the >> build will fail otherwise. >> >> >> +1. That should also solve the recent issues we had with regard to >> repositories becoming unavailable all of a sudden. >> > Yeah. That is why we wanted all the artifacts to be on the dist.wso2.org > and we are not using that properly, if we still have the other > repositories on the poms. > > Thanks, > Ruwan > >> Thanks, >> Senaka. >> >> >> Thanks, >> Ruwan >> >> -- >> Ruwan Linton >> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb >> WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org >> email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 341 3097 >> blog: http://blog.ruwan.org >> >> >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> >> >> -- >> Senaka Fernando >> Software Engineer >> WSO2 Inc. >> E-mail: sen...@wso2.com <mailto:sen...@wso2.com>; Mobile: +94 77 322 1818 >> >> http://www.wso2.com/ - "The Open Source SOA Company" >> >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Re-Organize the carbon-component pom files
Folks, We have been having number of issues because of the fact that we refer to the carbon parent pom from all the components, but from mavens point of view components are separate projects since we need to be able to do releases of each and every component separately. I propose we clean this out now otherwise we will be facing many issue when we are going to do individual product releases. WDYT? Thanks, Ruwan -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Next carbon version from Trunk?
Folks, What is the next Carbon version that we are planning to release from the trunk? I guess it is 3.0.0 right?, in which case we need to change the current trunk versions from 2.1.0-SNAPSHOT to 3.0.0-SNAPSHOT. Thanks, Ruwan -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Next carbon version from Trunk?
Lahiru, We need to fix P2 such that it wont require the physical artifact name to be the same as the bundle symbolic name. Otherwise we will not be able to use third party OSGi bundle as it is without wrapping any time. Also maven messes out the artifact order when we use '.' instead of '-' I am going to change the orbit versions. Thanks, Ruwan Hiranya Jayathilaka wrote: > > > On Sun, Dec 20, 2009 at 9:29 AM, Lahiru Gunathilake <mailto:lah...@wso2.com>> wrote: > > > > On Sun, Dec 20, 2009 at 8:03 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Folks, > > What is the next Carbon version that we are planning to > release from the > trunk? I guess it is 3.0.0 right?, in which case we need to > change the > current trunk versions from 2.1.0-SNAPSHOT to 3.0.0-SNAPSHOT. > > It should be 3.0.0.SNAPSHOT to work with P2 and I'm in the process > of changing it, now changing carbon-components versions. > > > +1 > > BTW does this change has any implications on the P2 features that > Saminda did for the trunk recently. Do we have to change them also? > > Thanks, > Hiranya > > > > > Lahiru > > > Thanks, > Ruwan > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esbWSO2> Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 > 341 3097 > blog: http://blog.ruwan.org > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Lahiru Gunathilake > Software Engineer - WSO2 Inc. > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com <mailto:hira...@wso2.com>; Mobile: +94 77 > 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Next carbon version from Trunk?
Afkham Azeez wrote: > AFAIK, there is no hard and fast rule in P2 like that, only a convention. Then why do we always say that for P2 to work it has to be the same, hasn't any one tried this? If so lets try that now :-) Thanks, Ruwan > > Azeez > > On Sun, Dec 20, 2009 at 1:42 PM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Lahiru, > > We need to fix P2 such that it wont require the physical artifact name > to be the same as the bundle symbolic name. Otherwise we will not be > able to use third party OSGi bundle as it is without wrapping any > time. > > Also maven messes out the artifact order when we use '.' instead > of '-' > > I am going to change the orbit versions. > > Thanks, > Ruwan > > Hiranya Jayathilaka wrote: > > > > > > On Sun, Dec 20, 2009 at 9:29 AM, Lahiru Gunathilake > mailto:lah...@wso2.com> > > <mailto:lah...@wso2.com <mailto:lah...@wso2.com>>> wrote: > > > > > > > > On Sun, Dec 20, 2009 at 8:03 AM, Ruwan Linton > mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>> wrote: > > > > Folks, > > > > What is the next Carbon version that we are planning to > > release from the > > trunk? I guess it is 3.0.0 right?, in which case we need to > > change the > > current trunk versions from 2.1.0-SNAPSHOT to > 3.0.0-SNAPSHOT. > > > > It should be 3.0.0.SNAPSHOT to work with P2 and I'm in the > process > > of changing it, now changing carbon-components versions. > > > > > > +1 > > > > BTW does this change has any implications on the P2 features that > > Saminda did for the trunk recently. Do we have to change them also? > > > > Thanks, > > Hiranya > > > > > > > > > > Lahiru > > > > > > Thanks, > > Ruwan > > > > -- > > Ruwan Linton > > Technical Lead & Product Manager; WSO2 ESB; > http://wso2.org/esb > > WSO2 <http://wso2.org/esbWSO2> Inc.; http://wso2.org > > email: ru...@wso2.com <mailto:ru...@wso2.com> > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>; cell: +94 77 > > 341 3097 > > blog: http://blog.ruwan.org > > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > > -- > > Lahiru Gunathilake > > Software Engineer - WSO2 Inc. > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > > -- > > Hiranya Jayathilaka > > Software Engineer; > > WSO2 Inc.; http://wso2.org > > E-mail: hira...@wso2.com <mailto:hira...@wso2.com> > <mailto:hira...@wso2.com <mailto:hira...@wso2.com>>; Mobile: +94 77 > > 633 3491 > > Blog: http://techfeast-hiranya.blogspot.com > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 341 3097 > blog: http://blog.ruwan.org > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Re-Organize the carbon-component pom files
Senaka Fernando wrote: > > > On Sun, Dec 20, 2009 at 1:12 PM, Afkham Azeez <mailto:az...@wso2.com>> wrote: > > +1. Please go ahead with this. > > > Ok, I will make the switch back to what it was (for the reg > component). But, to make things simple, let's make it a point to > define all the dependency versions in the root pom of each component. +1, that is how they should be. Individual components should be releasable at any time with a fe changes to the component root pom to change the artifact versions. Thanks, Ruwan > > Thanks, > Senaka. > > > Azeez > > > On Sun, Dec 20, 2009 at 7:15 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Folks, > > We have been having number of issues because of the fact that > we refer > to the carbon parent pom from all the components, but from > mavens point > of view components are separate projects since we need to be > able to do > releases of each and every component separately. > > I propose we clean this out now otherwise we will be facing > many issue > when we are going to do individual product releases. > > WDYT? > > Thanks, > Ruwan > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esbWSO2> Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 > 341 3097 > blog: http://blog.ruwan.org > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Senaka Fernando > Software Engineer > WSO2 Inc. > E-mail: sen...@wso2.com <mailto:sen...@wso2.com>; Mobile: +94 77 322 1818 > > http://www.wso2.com/ - "The Open Source SOA Company" > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Cloning an Axis2 module?
I don't think we can clone axis2 modules that easily, if we are to do so we need to write the logic in cloning a module and we might not be able to do cloning unless the modules has been written in a clonable manner. :-( Thanks, Ruwan Afkham Azeez wrote: > That is possible, but inefficient. If there a x number of modules, and > there are n number of tenants, (n+1)*x number of times the module.xml > file will have to be parsed and the AxisModule needs to be built. If > we can clone it, once we have crated an AxisModule instance, it will > be much more efficient. > > Azeez > > On Sun, Dec 20, 2009 at 3:14 PM, Senaka Fernando <mailto:sen...@wso2.com>> wrote: > > Azeez, > > Can't we initialize multiple instances of the same module? I > believe that this is possible. > > Thanks, > Senaka. > > On Sun, Dec 20, 2009 at 2:56 PM, Afkham Azeez <mailto:az...@wso2.com>> wrote: > > Hi folks, > Has anybody done $subject? For the multitenant admin console > funtionality, I need to clone some of the modules (cahing, > throttling, tracer etc) and add them to the tenant > AxisConfigurations. > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Senaka Fernando > Software Engineer > WSO2 Inc. > E-mail: sen...@wso2.com <mailto:sen...@wso2.com>; Mobile: +94 77 > 322 1818 > > > http://www.wso2.com/ - "The Open Source SOA Company" > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Cloning an Axis2 module?
Afkham Azeez wrote: > We do not require cloning of the org.apache.axis2.modules.Module > implementation. Only need to > clone, org.apache.axis2.description.AxisModule I see, so you do not need to clone the handlers associated with that module and so forth?? In that case I think you can write a fairly simple logic to clone the description. Thanks, Ruwan > > Azeez > > On Sun, Dec 20, 2009 at 4:24 PM, Afkham Azeez <mailto:az...@wso2.com>> wrote: > > Should the cloning logic be module specific? Won't it suffice if > we implement cloning in the AxisModule class alone? > > Azeez > > > On Sun, Dec 20, 2009 at 4:20 PM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > I don't think we can clone axis2 modules that easily, if we > are to do so > we need to write the logic in cloning a module and we might > not be able > to do cloning unless the modules has been written in a > clonable manner. :-( > > Thanks, > Ruwan > > Afkham Azeez wrote: > > That is possible, but inefficient. If there a x number of > modules, and > > there are n number of tenants, (n+1)*x number of times the > module.xml > > file will have to be parsed and the AxisModule needs to be > built. If > > we can clone it, once we have crated an AxisModule instance, > it will > > be much more efficient. > > > > Azeez > > > > On Sun, Dec 20, 2009 at 3:14 PM, Senaka Fernando > mailto:sen...@wso2.com> > > <mailto:sen...@wso2.com <mailto:sen...@wso2.com>>> wrote: > > > > Azeez, > > > > Can't we initialize multiple instances of the same module? I > > believe that this is possible. > > > > Thanks, > > Senaka. > > > > On Sun, Dec 20, 2009 at 2:56 PM, Afkham Azeez > mailto:az...@wso2.com> > > <mailto:az...@wso2.com <mailto:az...@wso2.com>>> wrote: > > > > Hi folks, > > Has anybody done $subject? For the multitenant admin > console > > funtionality, I need to clone some of the modules > (cahing, > > throttling, tracer etc) and add them to the tenant > > AxisConfigurations. > > > > -- > > -- > > Afkham Azeez > > az...@wso2.com <mailto:az...@wso2.com> > <mailto:az...@wso2.com <mailto:az...@wso2.com>> > > WSO2 Inc. http://wso2.com > > Blog: http://afkham.org > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> > > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > > -- > > Senaka Fernando > > Software Engineer > > WSO2 Inc. > > E-mail: sen...@wso2.com <mailto:sen...@wso2.com> > <mailto:sen...@wso2.com <mailto:sen...@wso2.com>>; Mobile: +94 77 > > 322 1818 > > > > > > http://www.wso2.com/ - "The Open Source SOA Company" > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > > -- > > -- > > Afkham Azeez > > az...@wso2.com <mailto:az...@wso2.com> > <mailto:az...@wso2.com <mailto:az...@wso2.com>> > > WSO2 Inc. http://wso2.com > > Blog: http://afkham.org > > > > > > > > ___ > > Carbon-dev mailing l
Re: [Carbon-dev] In-VM service calls to the BE via OSGi services???
+1, yeah we need to address that but we are better off from using OSGi services as admin services since we have the local transport serving the same purpose. If we use the OSGi service model we will be increasing the number of bundles by nearly 30% and we need to change each and every component to introduce a common bundle which is a huge change considering the number of components that we have. With the local transport model, it is just a matter of obtaining the correct EPR to be invoked by the client, from a small piece of utility code. Thanks, Ruwan Afkham Azeez wrote: > Yes. That is in my TODO list. There is a lot more work to be done to > be able to securely host logic on multitenant Carbon. > > Azeez > > On Sun, Dec 20, 2009 at 4:29 PM, Sanjiva Weerawarana <mailto:sanj...@wso2.com>> wrote: > > +1, but don't we still need to address OSGi security to prevent > random Java code from invoking any of our OSGi services? > > Sanjiva. > > 2009/12/19 Afkham Azeez mailto:az...@wso2.com>> > > First we need to get the SessionContext properly working in > Axis2 and then improve the local transport to be able to > handle transport session deployment. +1 for going with local > transport. > > Azeez > > > On Sat, Dec 19, 2009 at 7:14 PM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Folks, > > Are we going to continue using $subject?? I had an > off-line chat with > Azeez and we believe that we better get rid of due to > security concerns > specially with the introduction of the multi-tenancy. > > In that case we better get rid of the common bundles that > we have > introduced to get the OSGi service BE model working (Since > that will > increase the number of bundles by nearly 30%). > > So the option that is available for the in-vm calls is to > use the local > transport. > > WDYT? > > Thanks, > Ruwan > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; > http://wso2.org/esb > WSO2 <http://wso2.org/esbWSO2> Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 > 77 341 3097 > blog: http://blog.ruwan.org > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com <mailto:sanj...@wso2.com>; phone: +1 408 > 754 7388 x51726; cell: +94 77 787 6880 > blog: http://sanjiva.weerawarana.org/ > > The Open Source SOA Company > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Re-Organize the carbon-component pom files
Hiranya Jayathilaka wrote: > Hi Ruwan, > > On Sun, Dec 20, 2009 at 7:15 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Folks, > > We have been having number of issues because of the fact that we refer > to the carbon parent pom from all the components, but from mavens > point > of view components are separate projects since we need to be able > to do > releases of each and every component separately. > > I propose we clean this out now otherwise we will be facing many issue > when we are going to do individual product releases. > > > So are we going to make each and every component a separate Maven > project? In that case can we still use Maven to build all the > components or a subset of components at once? Yes, it is just a matter of putting the parent reference. We shouldn't put *carbon-parent* as the components parent, we need to point to the carbon-components parent as the components parent pom and declare all the dependencies at each and every component root pom (for example sequence-editor-root). Yes changing the full carbon version will require changing each and every component root pom, but if you look at the current way of doing that, still you need to change all the component root poms since the parent declaration has the carbon version declared to refer to the parent. :-) This is much cleaner because each and every component should be self contained and should be releasable separately. Thanks, Ruwan > > Thanks, > Hiranya > > > WDYT? > > Thanks, > Ruwan > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 341 3097 > blog: http://blog.ruwan.org > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com <mailto:hira...@wso2.com>; Mobile: +94 77 > 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > -------- > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Please increase Synapse version in Carbon 2.0.3 branch
Isuru Suriarachchi wrote: > Hi all, > > I can see code level commits into Synapse branch in Carbon 2.0.3. Could you please point me the commit message?? Thanks, Ruwan > But the Synapse version is still 1.3.0.wso2v3, which is the version of > the last release. So please increase it to 1.3.0.wso2v4 and do the > necessary changes in Carbon level. > > Thanks, > ~Isuru > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Please increase Synapse version in Carbon 2.0.3 branch
Senaka Fernando wrote: > > > On Sun, Dec 20, 2009 at 8:46 PM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Isuru Suriarachchi wrote: > > Hi all, > > > > I can see code level commits into Synapse branch in Carbon 2.0.3. > Could you please point me the commit message?? > > > http://wso2.org/svn/browse/wso2?view=rev&revision=52087 > <http://wso2.org/svn/browse/wso2?view=rev&revision=52087> Thanks Senaka. Yeah we need this change for the 2.0.3, lets increase the synapse version as Isuru mentioned. Thanks, Ruwan > > Thanks, > Senaka. > > > Thanks, > Ruwan > > But the Synapse version is still 1.3.0.wso2v3, which is the > version of > > the last release. So please increase it to 1.3.0.wso2v4 and do the > > necessary changes in Carbon level. > > > > Thanks, > > ~Isuru > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 341 3097 > blog: http://blog.ruwan.org > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Senaka Fernando > Software Engineer > WSO2 Inc. > E-mail: sen...@wso2.com <mailto:sen...@wso2.com>; Mobile: +94 77 322 1818 > > http://www.wso2.com/ - "The Open Source SOA Company" > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Next carbon version from Trunk?
Excellent! Thanks Saminda. Ruwan Saminda Wijeratne wrote: > guys I managed to create the feature generating mojo to determine the > correct osgi version from a maven artifact. Therefore we no longer > need to change versions of our maven artifacts to suit p2. We can > carry on as we were. Sorry for the late notice. I only just saw this > mail thread. > > Saminda > > > On Sun, Dec 20, 2009 at 7:58 PM, Lahiru Gunathilake <mailto:lah...@wso2.com>> wrote: > > > > On Sun, Dec 20, 2009 at 1:54 PM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Afkham Azeez wrote: > > AFAIK, there is no hard and fast rule in P2 like that, only > a convention. > Then why do we always say that for P2 to work it has to be the > same, > hasn't any one tried this? If so lets try that now :-) > > I have noticed that during the build process things get fails if > we don't have that convention. I'm almost done with the changes > but I will hold it without committing, if maven mess things > without "-", we have to fix it in P2 side. > > Lahiru > > > Regards > Lahiru > > > Thanks, > Ruwan > > > > Azeez > > > > On Sun, Dec 20, 2009 at 1:42 PM, Ruwan Linton > mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>> wrote: > > > > Lahiru, > > > > We need to fix P2 such that it wont require the physical > artifact name > > to be the same as the bundle symbolic name. Otherwise we > will not be > > able to use third party OSGi bundle as it is without > wrapping any > > time. > > > > Also maven messes out the artifact order when we use '.' > instead > > of '-' > > > > I am going to change the orbit versions. > > > > > > > Thanks, > > Ruwan > > > > Hiranya Jayathilaka wrote: > > > > > > > > > On Sun, Dec 20, 2009 at 9:29 AM, Lahiru Gunathilake > > mailto:lah...@wso2.com> > <mailto:lah...@wso2.com <mailto:lah...@wso2.com>> > > > <mailto:lah...@wso2.com <mailto:lah...@wso2.com> > <mailto:lah...@wso2.com <mailto:lah...@wso2.com>>>> wrote: > > > > > > > > > > > > On Sun, Dec 20, 2009 at 8:03 AM, Ruwan Linton > > mailto:ru...@wso2.com> > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>> > > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com> > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>>> wrote: > > > > > > Folks, > > > > > > What is the next Carbon version that we are > planning to > > > release from the > > > trunk? I guess it is 3.0.0 right?, in which > case we need to > > > change the > > > current trunk versions from 2.1.0-SNAPSHOT to > > 3.0.0-SNAPSHOT. > > > > > > It should be 3.0.0.SNAPSHOT to work with P2 and > I'm in the > > process > > > of changing it, now changing carbon-components > versions. > > > > > > > > > +1 > > > > > > BTW does this change has any implications on the P2 > features that > > > Saminda did for the trunk recently. Do we have to > change them also? > > > > > > Thanks, > > > Hiranya > > > > > > > > > > > > > > > Lahiru > > > > > > > > > Thanks, > > > Ruwan > > > > > > -- > > > Ruwan Linton > > > Technical Lead & Product Manager; WSO2 ESB; >
Re: [Carbon-dev] Cloning an Axis2 module?
Sanjiva Weerawarana wrote: > Right, so only the config needs to be cloned .. which should be easy (?). Hhhmm, I guess there is more to that Well, the answer is Yes, if we modify the state full modules like caching and throttling to be aware of the tenant. We use the ConfigurationContext to keep the state and assuming that the tenant is not getting its own ConfigurationContext we need to make the modules aware of the tenants. BTW: for a given message dispatched into the tenant is there anyway of getting the tenant id or something unique for the tenant to which this message is dispatched to?? Thanks, Ruwan > > Sanjiva. > > On Sun, Dec 20, 2009 at 11:50 PM, Afkham Azeez <mailto:az...@wso2.com>> wrote: > > In other words, yes, handlers and modules are stateless, but their > configurations can differ from tenant to tenant. > > Azeez > > > On Sun, Dec 20, 2009 at 11:45 PM, Afkham Azeez <mailto:az...@wso2.com>> wrote: > > The tenants can mess with things such as module parameters and > policies in a way that it affects everybody. > > Azeez > > > On Sun, Dec 20, 2009 at 10:20 PM, Sanjiva Weerawarana > mailto:sanj...@wso2.com>> wrote: > > Why? Handlers and modules are all stateless. Every tenant > can use the same object with no problem right?? > > Sanjiva. > > > On Sun, Dec 20, 2009 at 5:01 PM, Afkham Azeez > mailto:az...@wso2.com>> wrote: > > Ruwan, > You are right. Handlers also need to be cloned. > Otherwise, the tenants can mess with the handlers > which can affect the main AxisConfiguration as well. > So the easiest way is to programatically deploy these > modules within each of the tenant AxisConfigurations. > > Azeez > > > On Sun, Dec 20, 2009 at 4:38 PM, Ruwan Linton > mailto:ru...@wso2.com>> wrote: > > Afkham Azeez wrote: > > We do not require cloning of the > org.apache.axis2.modules.Module > > implementation. Only need to > > clone, org.apache.axis2.description.AxisModule > I see, so you do not need to clone the handlers > associated with that > module and so forth?? In that case I think you can > write a fairly simple > logic to clone the description. > > Thanks, > Ruwan > > > > Azeez > > > > On Sun, Dec 20, 2009 at 4:24 PM, Afkham Azeez > mailto:az...@wso2.com> > > <mailto:az...@wso2.com <mailto:az...@wso2.com>>> > wrote: > > > > Should the cloning logic be module specific? > Won't it suffice if > > we implement cloning in the AxisModule class > alone? > > > > Azeez > > > > > > On Sun, Dec 20, 2009 at 4:20 PM, Ruwan > Linton mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com > <mailto:ru...@wso2.com>>> wrote: > > > > I don't think we can clone axis2 modules > that easily, if we > > are to do so > > we need to write the logic in cloning a > module and we might > > not be able > > to do cloning unless the modules has > been written in a > > clonable manner. :-( > > > > Thanks, > > Ruwan > > > > Afkham Azeez wrote: > > > That is possible, but inefficient. If > there a x number of > > modules, and > > > there are n number of tenants, (n+1)*x > number of times the >
Re: [Carbon-dev] Repositories listed on the carbon-orbit pom
Lahiru Gunathilake wrote: > Hi Ruwan, > > On Sat, Dec 19, 2009 at 9:35 PM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Folks, > > Why do we have repositories like people.apache.org > <http://people.apache.org> and javanet, I guess > we do have all the artifacts on the dist.wso2.org > <http://dist.wso2.org> repository now. So we > need to get rid of the other repositories. > > If it's 2.0.3 branch all the artifacts are there in the dist.wso2.org > <http://dist.wso2.org>. > But we didn't host artifacts in to the dist.wso2.org > <http://dist.wso2.org> from the trunk build, since most of them are > snapshots and changing time to time. Right!, we shouldn't put SNAPSHOT dependencies to the dist.wso2.org/maven2 rather they should go into the dist.wso2.org/snapshots/maven2. We should use the proper repositories declaration at any WSO2 Java product pom which declares the repositories to pick SNAPSHOTs from the snapshot repo and releases from the main repo; The proper repositories declaration has to be as follows; wso2-maven2-snapshot-repository WSO2 Maven2 SNAPSHOTS http://dist.wso2.org/snapshots/maven2 true always ignore false wso2-maven2-repository WSO2 Maven2 Repository http://dist.wso2.org/maven2 false true never fail This will reduce the online build time a lot. Please note that release artifacts doesn't need to be re-fetched and that has been disabled and SNAPSHOT artifacts will be downloaded if the corresponding artifact on the snapshot repo has an updated version, this check will be done for every build. Thanks, Ruwan > +1 for removing other repositories from our pom files, and we can also > remove repositories from other third party projects we use like > axis2/synapse etc(We have all the artifacts in dist now, but only in > branch). > > Regards > Lhairu > > > Specially it is not recommended to use the people.apache.org > <http://people.apache.org> repo, it is > just for the apache artifact synchronization with the main maven > repositories. > > Shall we get rid of the other repositories?? That will increase the > on-line build time drastically, since it reduces unwanted artifact > lookups in these repositories. Also this will make sure that we > put all > the newly added artifacts into the dist.wso2.org > <http://dist.wso2.org> repository since the > build will fail otherwise. > > Thanks, > Ruwan > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 Inc.; http://wso2.org > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 341 3097 > blog: http://blog.ruwan.org > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Lahiru Gunathilake > Software Engineer - WSO2 Inc. > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Cloning an Axis2 module?
Sanjiva Weerawarana wrote: > Ruwan, every tenant gets its own CC .. and in fact its own AxisConfig > right Azeez? I don't know the implementation details, but I remember we talking about having multiple AxisConfigurations associated with a single ConfigurationContext... I agree that the tenant should get its own CC, in which case the answer to your first query is "YES" :-) BTW: I am a bit confused, if each and every tenant is getting its own AC and CC why do we need to clone modules?? Thanks, Ruwan > > Sanjiva. > > On Mon, Dec 21, 2009 at 7:31 AM, Ruwan Linton <mailto:ru...@wso2.com>> wrote: > > Sanjiva Weerawarana wrote: > > Right, so only the config needs to be cloned .. which should be > easy (?). > Hhhmm, I guess there is more to that Well, the answer is Yes, > if we > modify the state full modules like caching and throttling to be > aware of > the tenant. We use the ConfigurationContext to keep the state and > assuming that the tenant is not getting its own > ConfigurationContext we > need to make the modules aware of the tenants. > > BTW: for a given message dispatched into the tenant is there anyway of > getting the tenant id or something unique for the tenant to which this > message is dispatched to?? > > Thanks, > Ruwan > > > > Sanjiva. > > > > On Sun, Dec 20, 2009 at 11:50 PM, Afkham Azeez <mailto:az...@wso2.com> > > <mailto:az...@wso2.com <mailto:az...@wso2.com>>> wrote: > > > > In other words, yes, handlers and modules are stateless, but > their > > configurations can differ from tenant to tenant. > > > > Azeez > > > > > > On Sun, Dec 20, 2009 at 11:45 PM, Afkham Azeez > mailto:az...@wso2.com> > > <mailto:az...@wso2.com <mailto:az...@wso2.com>>> wrote: > > > > The tenants can mess with things such as module > parameters and > > policies in a way that it affects everybody. > > > > Azeez > > > > > > On Sun, Dec 20, 2009 at 10:20 PM, Sanjiva Weerawarana > > mailto:sanj...@wso2.com> > <mailto:sanj...@wso2.com <mailto:sanj...@wso2.com>>> wrote: > > > > Why? Handlers and modules are all stateless. Every > tenant > > can use the same object with no problem right?? > > > > Sanjiva. > > > > > > On Sun, Dec 20, 2009 at 5:01 PM, Afkham Azeez > > mailto:az...@wso2.com> > <mailto:az...@wso2.com <mailto:az...@wso2.com>>> wrote: > > > > Ruwan, > > You are right. Handlers also need to be cloned. > > Otherwise, the tenants can mess with the handlers > > which can affect the main AxisConfiguration as well. > > So the easiest way is to programatically deploy > these > > modules within each of the tenant > AxisConfigurations. > > > > Azeez > > > > > > On Sun, Dec 20, 2009 at 4:38 PM, Ruwan Linton > > mailto:ru...@wso2.com> > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>> wrote: > > > > Afkham Azeez wrote: > > > We do not require cloning of the > > org.apache.axis2.modules.Module > > > implementation. Only need to > > > clone, org.apache.axis2.description.AxisModule > > I see, so you do not need to clone the handlers > > associated with that > > module and so forth?? In that case I think > you can > > write a fairly simple > > logic to clone the description. > > > > Thanks, > > Ruwan > > > > > > Azeez > > > > > > On Sun, Dec 20, 2009 at 4:24 PM, Afkham Azeez > > mailto:az...@wso2.com> > <mailto:az...@wso2.com <mailto:az...@wso2.com>> > > > <mailto:az...@wso2.com >
Re: [Carbon-dev] Is there any reason why we haven't mentioned about carbon.home system property in README.txt of carbon distribution
We need to minimize the set of system properties that we are using, since it is not a good practice when it comes to webapp deployment model. Thanks, Ruwan Lahiru Gunathilake wrote: > Hi all, > > $subject ? > > If not I can add it to set of system properties we take. > > Lahiru > > -- > Lahiru Gunathilake > Software Engineer - WSO2 Inc. > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Accessing the registry within a component Admin service
Afkham Azeez wrote: > Better yet, I'll create another method in AbstractAdmin called > getRegistry() ++1 Thanks, Ruwan > > Azeez > > On Mon, Dec 21, 2009 at 4:44 PM, Afkham Azeez <mailto:az...@wso2.com>> wrote: > > Please do this if you want to access the registry in a proper > manner, within an Admin service in a component, in a multitenant > deployment; > > this.axisConfig = getAxisConfig(); > this.registry = (UserRegistry) > axisConfig.getParameterValue(WSO2Constants.REGISTRY_INSTANCE); > > The getAxisConfig() method is inherited from AbstractAdmin > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > > > > -- > -- > Afkham Azeez > az...@wso2.com <mailto:az...@wso2.com> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > > _______ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Carbon version has change
Folks, I am planning to change the carbon version (from 2.1.0-SNAPSHOT to 3.0.0-SNAPSHOT), so please do not execute full builds. It is hard to commit all the changes at once and hence you might experience some build failures if you do an update and do a full build. Will let you know once I am done! Thanks, Ruwan -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] DataService component groupid
$ subject is org.wso2.carbon.dataservices, where as all the other components have org.wso2.carbon? Any reason for this group id, if not shall we rename it to org.wso2.carbon?? Thanks, Ruwan -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] DataService component groupid
Same with Rule component, shall I unify those to have the org.wso2.carbon group id?? Thanks, Ruwan Ruwan Linton wrote: > $ subject is org.wso2.carbon.dataservices, where as all the other > components have org.wso2.carbon? Any reason for this group id, if not > shall we rename it to org.wso2.carbon?? > > Thanks, > Ruwan > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Please do not commit project files
Folks, Please do not commit project files like .classpath or .settings files, I see a few locations in the carbon-components trunk where we have committed the .classpath files. As a practice please do a svn stat and a svn diff before committing any change. I am in the process of adding svn:ignores as well. Thanks, Ruwan -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] DataService component groupid
+= mashup component; Thanks, Ruwan Ruwan Linton wrote: > Same with Rule component, shall I unify those to have the > org.wso2.carbon group id?? > > Thanks, > Ruwan > > Ruwan Linton wrote: > >> $ subject is org.wso2.carbon.dataservices, where as all the other >> components have org.wso2.carbon? Any reason for this group id, if not >> shall we rename it to org.wso2.carbon?? >> >> Thanks, >> Ruwan >> >> >> > > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon version has change
Version change has been done! New trunk version is 3.0.0-SNAPSHOT. Chamara please do a build and deploy the new SNAPSHOTs. Thanks, Ruwan Ruwan Linton wrote: > Folks, > > I am planning to change the carbon version (from 2.1.0-SNAPSHOT to > 3.0.0-SNAPSHOT), so please do not execute full builds. It is hard to > commit all the changes at once and hence you might experience some build > failures if you do an update and do a full build. > > Will let you know once I am done! > > Thanks, > Ruwan > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Re-formatting the carbon components maven structure
Folks, I am planning to re-format the maven structure of the carbon-components trunk and add svn:ignores as appropriate. You better not take svn update till I finish this off. I will let you know once I am done!, doing it atomically is extremely difficult and that is why I had to send this mail. Thanks, Ruwan -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Use proper svn:ignore symantics to improve the quality of the components
Folks, I have added svn:ignore directives to all the existing components under the carbon-components project and please note that, if you are adding a new component you should add svn:ignore properties to the component directories as well. You could first add the component and then on the component root directories [1] add the svn:ignore as described in [2]; [1] _Component root directories_ If the component that you are adding is called 'foo' probably you will add a top level component called 'foo' and inside that you will add 'org.wso2.carbon.foo' and 'org.wso2.carbon.foo.ui' and so forth, all the above three directories are considered as component root directories in this particular case. [2] _Adding svn:ignore properties_ Go to the directory that you want to add svn:ignore (please note that the directory has to be already under svn), and type the command; svn propedit svn:ignore . and then you will be prompted with the system text editor (for example vi or nano), then paste the following list of items in the editor. target *.ipr *.iml *.iws .classpath .project .settings after that save and close the editor (in the case of vi, CTRL+c followed by ':wq' and ENTER, while in nano just CTRL+x followed by 'y' and ENTER). commit the properties using svn commit; svn ci Now when you do a 'svn stat' you should be able to see a clean view of the changed file, while all the unwanted (ignored) files are filtered out of the changed files list. Please treat this as a best practice. Thanks, Ruwan -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Pay attention to the maven build time WARNINGs
Folks, I see a lot of maven WARNINGs specially from bundle plugin due to wrong bundle configurations. Please pay attention to them and try to get rid of all that. It will help you a lot in the long run, even though it doesn't seem to do any fix at the moment you see the warning. :-) Thanks, Ruwan -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Re-formatting the carbon components maven structure
An update: I am planning to comment out the modules in the carbon component parent default profile and enable them as and when I complete the migration of the components. Please note that you could work on your own component without trying to build all components. I will try to minimize the maven warnings while in the process of migration. Thanks, Ruwan Ruwan Linton wrote: > Folks, > > I am planning to re-format the maven structure of the carbon-components > trunk and add svn:ignores as appropriate. You better not take svn update > till I finish this off. > > I will let you know once I am done!, doing it atomically is extremely > difficult and that is why I had to send this mail. > > Thanks, > Ruwan > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] What is apacheds-server component?
Can someone please explain me $subject? What it is for? It seems it is not on the main components build as well. Thanks, Ruwan -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] What is apacheds-server component?
Paul Fremantle wrote: > I'm guessing Apache Directory Server (directory.apache.org). Its an LDAP > server. > I think you are correct, Paul. I had a look at the code and seems like it is an experimental code, are we planning to continue to use this component in any case? if so we need to improve this a lot. Thanks, Ruwan > Paul > > 2009/12/26 Ruwan Linton : > >> Can someone please explain me $subject? >> >> What it is for? It seems it is not on the main components build as well. >> >> Thanks, >> Ruwan >> >> -- >> Ruwan Linton >> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb >> WSO2 Inc.; http://wso2.org >> email: ru...@wso2.com; cell: +94 77 341 3097 >> blog: http://blog.ruwan.org >> >> >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
