Hi Sameera/kernel team, Can you please have a look. This is urgent for us.
On Wed, May 13, 2015 at 11:18 AM, Sandamal Weerasinghe <[email protected]> wrote: > Since CXF is already being used in WSO2 products there is no need for > approval [1]. And even if we are embedding this dependency or making the > entire CXF-RM inbound an installable feature, we will need this as an Orbit > bundle first. > > [1] [Thrid Party Library Approval] Apache CXF > > Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd > > Mobile - +94-77-144-9640 > > On Wed, May 13, 2015 at 11:15 AM, Kasun Indrasiri <[email protected]> wrote: > >> Hi KasunG, >> >> Can you please review and merge asap. ESB 4.9 alpha release is blocked >> due to this. >> >> On Fri, May 8, 2015 at 2:09 PM, Sandamal Weerasinghe <[email protected]> >> wrote: >> >>> Hi KasunG, >>> >>> Updated the pull request after doing a version upgrade. The following >>> dependencies had to be embedded; neethi, woodstox-core-asl and >>> xmlschema-core. >>> I have removed the wss4j and slf4j bundles as they are not essential to >>> the functionality of the cxf ws-rm inbound endpoint and connector. As for >>> the changes in the spring.schemas and spring.handlers, without those >>> changes the following error gets thrown at when starting an inbound >>> endpoint. >>> >>> org.springframework.beans.factory.parsing.BeanDefinitionParsingException: >>> Configuration problem: Unable to locate Spring NamespaceHandler for XML >>> schema namespace [http://cxf.apache.org/core] >>> >>> Please review and merge. >>> >>> [1] https://github.com/wso2/orbit/pull/71 >>> >>> Thanks. >>> >>> Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd >>> >>> Mobile - +94-77-144-9640 >>> >>> On Tue, May 5, 2015 at 10:57 AM, KasunG Gajasinghe <[email protected]> >>> wrote: >>> >>>> Hi Sandamal, >>>> >>>> We have forked some of the bundles you have mentioned above such as the >>>> wss4j bundle. Are you doing a version upgrade here? How is this going to >>>> affect the components that rely on wss4j 1.5.11? >>>> >>>> And, can you also verify whether all these libraries approved? >>>> >>>> Thanks. >>>> >>>> On Thu, Apr 30, 2015 at 7:12 PM, Sandamal Weerasinghe < >>>> [email protected]> wrote: >>>> >>>>> Hi Prabath, >>>>> >>>>> Please check if the RMConnector works with the following in place, >>>>> >>>>> cxf-bundle-3.0.2.wso2v1.jar >>>>> jetty-bundle-8.1.15.v20140411.wso2v1.jar >>>>> slf4j-bundle-1.7.7.wso2v1.jar >>>>> wss4j-bundle-2.0.2.wso2v1.jar >>>>> >>>>> org.apache.aries.blueprint-1.1.0.jar >>>>> org.apache.aries.proxy-1.0.1.jar >>>>> org.apache.aries.util-1.1.0.jar >>>>> stax2-api-3.1.4.jar >>>>> >>>>> https://github.com/wso2/orbit/pull/71 >>>>> >>>>> Thanks. >>>>> >>>>> Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd >>>>> >>>>> Mobile - +94-77-144-9640 >>>>> >>>>> On Thu, Apr 23, 2015 at 2:29 PM, Sandamal Weerasinghe < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi KasunG, >>>>>> >>>>>> Please review and merge. >>>>>> >>>>>> Thanks. >>>>>> >>>>>> Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd >>>>>> >>>>>> Mobile - +94-77-144-9640 >>>>>> >>>>>> On Mon, Apr 20, 2015 at 7:48 AM, Prabath Ariyarathna < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi Sandamal. >>>>>>> >>>>>>> It's working with the RM connector without any issue. >>>>>>> >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>>> On Sun, Apr 19, 2015 at 12:11 AM, Sandamal Weerasinghe < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi KasunG, >>>>>>>> >>>>>>>> I updated the pull requests according to your instructions, please >>>>>>>> have a look. >>>>>>>> >>>>>>>> PrabathA : Can you please check if the RM connector works with the >>>>>>>> new Bundles >>>>>>>> >>>>>>>> Thanks. >>>>>>>> >>>>>>>> Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd >>>>>>>> >>>>>>>> Mobile - +94-77-144-9640 >>>>>>>> >>>>>>>> On Thu, Apr 16, 2015 at 6:01 PM, Sandamal Weerasinghe < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi KasunG, >>>>>>>>> >>>>>>>>> I split the cxf bundle in to 2 bundles (cxf and jetty) and now I >>>>>>>>> get the following error when starting up the ESB >>>>>>>>> >>>>>>>>> [2015-04-16 17:55:18,448] INFO - ServerImpl Setting the server's >>>>>>>>> publish address to be http://localhost:8081 >>>>>>>>> [2015-04-16 17:55:18,454] FATAL - ServiceBusInitializer Failed to >>>>>>>>> initialize ESB due to a fatal error >>>>>>>>> java.lang.LinkageError: loader constraint violation: loader >>>>>>>>> (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) >>>>>>>>> previously initiated loading for a different type with name >>>>>>>>> "javax/servlet/http/HttpServletResponse" >>>>>>>>> at >>>>>>>>> org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine.addServant(JettyHTTPServerEngine.java:327) >>>>>>>>> at >>>>>>>>> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.activate(JettyHTTPDestination.java:179) >>>>>>>>> at >>>>>>>>> org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:49) >>>>>>>>> at >>>>>>>>> org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFactory.java:95) >>>>>>>>> at >>>>>>>>> org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:895) >>>>>>>>> at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:123) >>>>>>>>> at >>>>>>>>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:215) >>>>>>>>> at >>>>>>>>> org.wso2.carbon.inbound.endpoint.protocol.cxf.wsrm.InboundRMHttpListener.init(InboundRMHttpListener.java:106) >>>>>>>>> at >>>>>>>>> org.apache.synapse.inbound.InboundEndpoint.init(InboundEndpoint.java:58) >>>>>>>>> >>>>>>>>> The javax.servlet package is exported by Tomcat. Any ideas on how >>>>>>>>> to resolve this? >>>>>>>>> >>>>>>>>> osgi> b 530 >>>>>>>>> tomcat-servlet-api_7.0.52.wso2v1 [530] >>>>>>>>> Id=530, Status=ACTIVE Data >>>>>>>>> Root=/home/sandamal/Programs/RM/wso2esb-4.9.0-SNAPSHOT/repository/components/default/configuration/org.eclipse.osgi/bundles/530/data >>>>>>>>> "No registered services." >>>>>>>>> No services in use. >>>>>>>>> Exported packages >>>>>>>>> javax.servlet; version="2.6.0"[exported] >>>>>>>>> javax.servlet.annotation; version="2.6.0"[exported] >>>>>>>>> javax.servlet.descriptor; version="2.6.0"[exported] >>>>>>>>> javax.servlet.http; version="2.6.0"[exported] >>>>>>>>> javax.servlet.resources; version="2.6.0"[exported] >>>>>>>>> *; version="0.0.0"<unwired><dynamic> >>>>>>>>> No fragment bundles >>>>>>>>> Named class space >>>>>>>>> tomcat-servlet-api; bundle-version="7.0.52.wso2v1"[provided] >>>>>>>>> No required bundles >>>>>>>>> >>>>>>>>> Thanks. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd >>>>>>>>> >>>>>>>>> Mobile - +94-77-144-9640 >>>>>>>>> >>>>>>>>> On Thu, Apr 9, 2015 at 10:56 AM, Kasun Gajasinghe <[email protected] >>>>>>>>> > wrote: >>>>>>>>> >>>>>>>>>> Hi Kasun, >>>>>>>>>> >>>>>>>>>> We'll review this and apply. There are some changes required. >>>>>>>>>> >>>>>>>>>> On Apr 9, 2015, at 10:29 AM, Kasun Indrasiri <[email protected]> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> Can we please add this. We are blocked on this for adding >>>>>>>>>> RM-Inbound endpoint to ESB M8 release >>>>>>>>>> >>>>>>>>>> On Tue, Apr 7, 2015 at 11:21 AM, Sandamal Weerasinghe < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hi all, >>>>>>>>>>> >>>>>>>>>>> Please find the pull request for the orbit bundle required for >>>>>>>>>>> the above feature. In the orbit bundle I embedded the dependencies >>>>>>>>>>> because >>>>>>>>>>> many of them don't have osgi bundles and this would ensure that the >>>>>>>>>>> RM >>>>>>>>>>> Inboundfeature would have all the dependencies it would need. >>>>>>>>>>> >>>>>>>>>>> https://github.com/wso2/orbit/pull/71 >>>>>>>>>>> >>>>>>>>>>> Thanks. >>>>>>>>>>> >>>>>>>>>>> Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd >>>>>>>>>>> >>>>>>>>>>> Mobile - +94-77-144-9640 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Kasun Indrasiri >>>>>>>>>> Software Architect >>>>>>>>>> WSO2, Inc.; http://wso2.com >>>>>>>>>> lean.enterprise.middleware >>>>>>>>>> >>>>>>>>>> cell: +94 77 556 5206 >>>>>>>>>> Blog : http://kasunpanorama.blogspot.com/ >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *Prabath Ariyarathna* >>>>>>> >>>>>>> *Associate Technical Lead* >>>>>>> >>>>>>> *WSO2, Inc. * >>>>>>> >>>>>>> *lean . enterprise . middleware * >>>>>>> >>>>>>> >>>>>>> *Email: [email protected] <[email protected]>* >>>>>>> >>>>>>> *Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>* >>>>>>> >>>>>>> *Flicker : https://www.flickr.com/photos/47759189@N08 >>>>>>> <https://www.flickr.com/photos/47759189@N08>* >>>>>>> >>>>>>> *Mobile: +94 77 699 4730 * >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >>>> email: kasung AT spamfree wso2.com >>>> linked-in: http://lk.linkedin.com/in/gajasinghe >>>> blog: http://kasunbg.org >>>> >>>> >>>> >>> >>> >> >> >> -- >> Kasun Indrasiri >> Software Architect >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> cell: +94 77 556 5206 >> Blog : http://kasunpanorama.blogspot.com/ >> > > -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
