Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] GSoC PDE template
Hi,
I am working on this.


On Fri, Jul 19, 2013 at 12:57 AM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
On 7/18/2013 11:53 AM, Suneth Vijayindu wrote:
Hi Scott,
Can you please check that following modifications to GUI of the wizard page are okay?

I'm going to focus for the moment on your snapshots...rather than the error.txt, because that seems to be something else related to your environment.

Comments: 

1) It seems that you have a number of invalid entries in the list box for the 'service.imported.configs' item.   That is...only appropriate (implementers of IRemoteServiceContainerAdapter) should be in this list...e.g. nothing would work if ecf.base or ecf.discovery.jmdns were to be selected as the distribution provider (which is what service.exported.configs is for).

2) I believe that the different remote service providers (e.g. ecf.generic.server, ecf.r_osgi.peer, etc) will have different required fields...i.e. not all of the providers will require a 'host', 'port', and 'path' as the generic provider does.  So it might be much better to have the fields that appear below 'service.exported.config' change based upon which selection a user makes.   I know this makes the UI more complex...but it would be much more convenient.

If others have comments about the remote services wizard UI, please chime in.

Scott




When I ran any osgi template gave me a error that port was in use.fixed it with adding 
-Dch.ethz.iks.r_osgi.registerDefaultChannel=false  
to arguments of the run configuration but there is another error[error.txt].
 


On Thu, Jul 18, 2013 at 8:05 AM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
Hi,


On 7/17/2013 7:16 PM, Suneth Vijayindu wrote:
Hi Scott,

I impoterted  org.eclipse.ecf.remoteservices.tooling.pde, project errors were shown on the manifest file  removing the bundle version information from the file, fixed it. and ran the plug-in project as Eclipse Application.

This plugin...i.e. org.eclipse.ecf.remoteservices.tooling.pde is an Eclipse plugin rather than an Eclipse Application...as it has dependencies on PDE (the Eclipse Plugin Development Environment)
It runs with out any errors but in the new Eclipse when I create a new plug-in project OSGi Remote Service Host Example, it shows errors in the manifest.MF file

that these packages not available

 org.eclipse.ecf.examples.remoteservices.hello,
 org.eclipse.ecf.osgi.services.distribution,
 org.eclipse.ecf.remoteservice,

how can I fix this?

These are ECF packages...and .  The way to fix this is to have ECF in the target platform for the workspace.  This can be done in two ways:

1) Install the ECF SDK into Eclipse
2) Goto Window->Preferences->Plugin Development->Target Platform and Add.. ECF Remote Services to the active target platform.

Since the usual way of installing org.eclipse.ecf.remoteservices.tooling.pde is to install it as part of the SDK...that would be my suggestion...i.e. that you

A) Install the ECF SDK into Eclipse
B) Create a new project using the Hello Host template...which will now be available because o.e.e.remoteservices.tooling.pde was installed by step A...and now...because of A...these packages will be available for the newly created project.

Scott







On Wed, Jul 17, 2013 at 7:35 PM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
Hi Vijayindu,

Here are some highlight possibilities for improving the template (which is here [1] btw):

1) The current template has only two fields on the wizard page (for host)...i.e. 'service.exported.configs' and 'ECF Generic Server URL'.   It could have a listbox or a drop down list box for the service.exported.configs...so that all ECF provider alternatives were presented...and the user could select one.  The ECF Generic Server URL could be broken down into it's constituent parts...e.g. ${host}:${port}${/path} and presented as separate fields...so that the user wouldn't have to create the full URL

2) It would be nice if the template also included a product.configuration...and perhaps created a feature project...so that people could (using PDE build) easily create a standalone, runnable host/client application (instead of just the one bundle).

3) It would be nice if folks could optionally (e.g. via additional templates or more options on the existing templates) create a more sophisticated remote service...e.g. and create/define their down service interface...rather than use the 'IHello' service interface example.

As the template gets more sophisticated, at a certain point this gets closer to a 'new remote service wizard'.    Actually, this might be a good idea in general...i.e. a wizard that would go under File->New and allow people to have assistance creating a new remote service (host and/or consumer).   Actually, this could also perhaps be generalized to support the creation of new OSGi services in general (not just remote services).

If others have suggestions for what would be good to add to the template...or the notion of an 'new OSGi remote services wizard'...please chime in here.  It would be good to hear from others what they would like to see in terms of additional support for learning and using OSGi remote services.

Thanks,

Scott

BTW...the git repo location for the existing template plugin is here:

[1] http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/tree/tooling/plugins/org.eclipse.ecf.remoteservices.tooling.pde


On 7/16/2013 11:36 PM, Suneth Vijayindu wrote:
Hi Scott,
I tested the   OSGi Remote Service Host Example and OSGi Remote Service Consumer Example. earlyer this  month and wrote about it im my blog[1]
After some discussion with Harshana. he asked me to get more familires with OSGI and exting templates. I went through the following book OSGi In Practice(Attached) and the links[2][3][4].I think I have the enough knowledge about OSGi. I would like  to enhance exiting remote services template can you give me some clarification about what need to be exactly added to the exiting template.

--
Thank You
Vijayindu


_______________________________________________
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




--
Thank You
Vijayindu


_______________________________________________
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




--
Thank You
Vijayindu


_______________________________________________
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




--
Thank You
Vijayindu

Back to the top