RE: [ecf-dev] Tracing

["Konradi, Philipp" <philipp.konradi@xxxxxxxxxxx>]

Scott,

thank you, tracing worked perfectly with the newest daily build!

Philipp


> -----Original Message-----
> From: ecf-dev-bounces@xxxxxxxxxxx [mailto:ecf-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Scott Lewis
> Sent: Monday, September 14, 2009 6:56 PM
> To: Eclipse Communication Framework (ECF) developer mailing list.
> Subject: Re: [ecf-dev] Tracing
> 
> Hi Philipp,
> 
> Konradi, Philipp wrote:
> >> Also, there are trace options for the discovery and distribution
> >>
> > impls.
> >
> >> Unfortunately, we accidently left the .options files out of the
> >>
> > bundles
> >
> >> for the 3.0 build, but they are/will be in the target bundles for
> 3.1.
> >>
> > I've stumbled upon this right now :-)
> > Would be great if those could be added to the current daily builds.
I
> > could also fix it, just let me know which build files need to be
> > adjusted.
> >
> 
> I've updated the build.properties on these two projects to include the
> .options files for both the binary and source builds on the
Release_3_0
> branch (where the daily builds are currently coming from).  So they
> should be in today's daily build later today.
> 
> Scott
> 
> 
> 
> > Regards,
> > Philipp
> >
> >
> >> -----Original Message-----
> >> From: ecf-dev-bounces@xxxxxxxxxxx [mailto:ecf-dev-
> bounces@xxxxxxxxxxx]
> >> On Behalf Of Scott Lewis
> >> Sent: Monday, September 14, 2009 4:21 AM
> >> To: Eclipse Communication Framework (ECF) developer mailing list.
> >> Subject: Re: [ecf-dev] ECF 3.1 download?
> >>
> >> Hi Bryan,
> >>
> >> For debugging purposes, you may wish to register your own
> >> implementations of the following services:
> >>
> >> Discovery listeners
> >> org.eclipse.ecf.osgi.services.discovery.IHostDiscoveryListener
> >> org.eclipse.ecf.osgi.services.discovery.IProxyDiscoveryListener
> >>
> >> Distribution Listeners
> >>
org.eclipse.ecf.osgi.services.distribution.IHostDistributionListener
> >>
> org.eclipse.ecf.osgi.services.distribution.IProxyDistributionListener
> >>
> >> If you register an implementer of these listeners as a service,
then
> >>
> > at
> >
> >> runtime they will be notified (on the host and proxy processes,
> >> respectively), when the various steps in the discovery/distribution
> >> process occur.
> >>
> >> Also, there are trace options for the discovery and distribution
> >>
> > impls.
> >
> >> Unfortunately, we accidently left the .options files out of the
> >>
> > bundles
> >
> >> for the 3.0 build, but they are/will be in the target bundles for
> 3.1.
> >>
> >>
> >> Scott
> >>
> >>
> >> Bryan Hunt wrote:
> >>
> >>> HI Scott,
> >>>
> >>> I'm using r-OSGi with my own discovery provider as I'm deploying
> >>> services on a WAN.  What I know so far is that the server seems to
> >>> advertise the services I expect, the client connects to the
> >>>
> > discovery
> >
> >>> provider and gets the list of services from my provider,  and
after
> >>> that, things go badly.  I might be able to give you more info
later
> >>> tonight, and if not, hopefully tomorrow.
> >>>
> >>> Bryan
> >>>
> >>> On Sep 13, 2009, at 7:29 PM, Scott Lewis wrote:
> >>>
> >>>
> >>>> Hi Bryan,
> >>>>
> >>>> Bryan Hunt wrote:
> >>>>
> >>>>> Hi Scott,
> >>>>>
> >>>>> It turned out that one of the fixes I was looking for was
already
> >>>>>
> >> in
> >>
> >>>>> my target platform.
> >>>>>
> >>>>> I'm having a lot of problems with RFC119 - I'm getting errors
> when
> >>>>> the client discovers remote services.  I'll be diving into the
> >>>>> problems in the next day or two and opening bugs as I figure out
> >>>>> what is really going wrong.
> >>>>>
> >>>> Ok...I would expect the crucial info is likely to be
> >>>>
> >>>> a) what discovery provider you are using and what your network
> >>>> environment is for that discovery protocol;
> >>>> b) what remote services provider you are using (e.g. r-OSGi, ECF
> >>>> generic, JMS/ActiveMQ, etc).
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Scott
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> ecf-dev mailing list
> >>>> ecf-dev@xxxxxxxxxxx
> >>>> https://dev.eclipse.org/mailman/listinfo/ecf-dev
> >>>>
> >>> _______________________________________________
> >>> ecf-dev mailing list
> >>> ecf-dev@xxxxxxxxxxx
> >>> https://dev.eclipse.org/mailman/listinfo/ecf-dev
> >>>
> >> _______________________________________________
> >> ecf-dev mailing list
> >> ecf-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/ecf-dev
> >>
> > _______________________________________________
> > ecf-dev mailing list
> > ecf-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/ecf-dev
> >
> 
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev