| Re: [ecf-dev] exporting a service via DS with current hostname |
For our environment (one server, server is known, test and production setups) the other discovery methods are to implicit or too complicated to setup (DNS etc) ....
So in case of localhost my EDEF Bundle generator is now falling back to
InetAddress.getLocalHost().getCanonicalHostName()
just like the generic provider is doing it. Works for me...
Regards, Peter
Am 14.08.2014 um 19:06 schrieb Wim Jongman:
Yes, or use one of the other discovery mechanisms instead of that file based one.
On Thu, Aug 14, 2014 at 2:28 PM, Peter Hermsdorf <peter.hermsdorf@xxxxxxxxx> wrote:
Hi,
yes of cause, but indeed reading it again pointed me at my problem.
Not the absence of the line but the different port configuration didn't make it work. So Adding
<property name="ecf.generic.server.port" type="String" value="8889"/>
made it working.
But there is still one issue left: depending of configuration I'm generating an EDEF description to discover the server.
In my development environment client and server are running on the local machine. But with the above configuration the server will bind to the actual hostname and will not be discovered when the client tries to connect with localhost ...
Only workaround i can think of is to extend the EDEF generator to replace localhost with the current hostname in that case...
Thanks anyway
Regards,
Peter
Am 14.08.2014 um 12:56 schrieb Wim Jongman:
Hi Peter,
Did you take a look at this?
Cheers,
Wim
On Thu, Aug 14, 2014 at 10:38 AM, Peter Hermsdorf <peter.hermsdorf@xxxxxxxxx> wrote:
Hi,
currently I'm exporting a remote service with a DS configuration like this:
<property name="service.exported.interfaces" type="String" value="*"/>
<property name="service.exported.configs" type="String" value="ecf.generic.server"/>
<property name="ecf.generic.server.id" type="String" value="ecftcp://localhost:8889/server"/>
which works when the clients running on the same machine and also use localhost to connect to the service.
the obvious problem: clients connecting from different machines cannot connect to that service because they use the real hostname of the server to connect (eg. ecftcp://myhost.com:8889/server)
When removing the ecf.generic.server.id line from the xml, the service does not seems to get exported at all, probably because it's not defined how.
This problem probably is adressed by the property org.eclipse.ecf.provider.generic.host.useHostName which defaults to true, but does not seems to get used because i defined the ecf.generic.server.id including localhost as hostname.
So the question is: how to trigger the generic server export without hard coding the hostname?
Best Regards,
Peter
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________ ecf-dev mailing list ecf-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________ ecf-dev mailing list ecf-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev