search

jescapo / gwteventservice

Automatically exported from code.google.com/p/gwteventservice
Other
0 stars 0 forks source link

UnableToCompleteException as rusult of missed gwt.version in gwt-user dependency of demo modules #43

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
In 1.2.0 version used GWT 2.1.0, but as misseed gwt-user dependency for demo it 
was taken 2.3.0 and as result: UnableToCompleteException (gwt 2.3.0 was in my 
local maven repository).

Solution: set <version>${gwt.version}</version>

Some more comments:
Thank you for your considerable work on this framework. I find it very useful 
and going to integrate with it.

Let me give you some comments to make it even better:)

1. Why use own interface ServerLogger iso standard SLF4J. SLF4J has many 
implementation and to use it, it is enough add in classpath any of existing one.

2. It seems to me that GWT 2.3 and 2.4 work OK with gwteventservice, so maybu 
switch to the GWT version?

3. Missed developer section in de.novanic.gwteventservice parent.

4. Most impotent: server side realization is hold on thread and connection 
until event happens and couldn't be used in case of hi loading.
There are low-level comet implementation 
https://github.com/Atmosphere/atmosphere with gwt module gwt-demo. It coud be 
used different server strategy for many AS (continuation, Web-Socket API 
etc..). May be it worth to integrate with it or build server implementation on 
the top of there server side code.

Best regards,
Kislin Grigory.
http://gkislin.narod.ru

Original issue reported on code.google.com by gkislin13@gmail.com on 27 Feb 2012 at 7:21

GoogleCodeExporter commented 9 years ago 
Hi,

thank you for your constructive feedback.

I don't see the problem with the missing version-tag. The versions of the 
GWT-dependencies are resolved via the parent pom.xml, so the version-tag should 
be unnecessary. All the productive modules like "eventservice-rpc" doesn't 
declare it, too.

1.) I have created a feature task for SLF4J 
(https://code.google.com/p/gwteventservice/issues/detail?id=51) and plan it for 
1.3.

2.) GWTEventService 1.3 will be upgraded to GWT 2.4

3.) The developers section is already existing (line 248 within the parent 
pom.xml of  1.2 or trunk).

4.) That is planned for GWTEventService 2.0

Please let me know if there are still problems with the pom.xmls in your 
opinion and I will fix it directly.

Original comment by sven.strohschein@googlemail.com on 16 Jul 2012 at 6:37