Re: Request data

2010-01-14 Thread DaveS
Oli

It's easy to get back both lists in a single RPC call, by defining a
ResultType class such as:-

class MyResult implements Serializable {
  public ListItem items;
  public ListFilter filters;
}

where both classes Item and Filter are also serializable. Then
have a method like

public MyResult sendRequest(args...);

defined in the RPC interface.

I hope this makes sense

  Dave.

On Jan 14, 10:39 am, Olivier oliv...@digiworks.es wrote:
 Hi everyone,

 I have a form that is send to request some data on the server. The result I 
 need is a list of items and a list of filters.
 What would better, sending one request that will get me both list or sending 
 2 different requests, one for each list ?

 Thanks
 Oli

 ---
 Olivier
 Digiworks

 Política de Protección de Datos de Carácter Personal
 En cumplimiento de la Ley Orgánica 15/1999, de 13 de diciembre,  sobre 
 protección de Datos de Carácter Personal (LOPD) DIGIWORKS SPAIN, S.L. informa 
 a los usuarios de que:

 Los Datos de Carácter Personal que recoge son objeto de tratamiento 
 automatizado y se incorporan en los ficheros correspondientes,  debidamente 
 registrados en la Agencia Española de Protección de Datos. El usuario podrá,  
 en todo momento, ejercitar los derechos reconocidos en la LOPD, de acceso, 
 rectificación, cancelación y oposición. El ejercicio de estos derechos puede 
 realizarlo el propio usuario mediante comunicación escrita en la siguiente 
 dirección postal:

 DIGIWORKS SPAIN, S.L.
 AVDA SAN RAFAEL, 11, LOCAL 2
 03580 ALFAZ DEL PI
 ALICANTE

 También pueden ejercitar estos derechos en los términos que la normativa 
 aplicable establece y que puede consultar enwww.agpd.es.
-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.




Re: Any thing in GWT for Gridlayout???

2010-01-08 Thread DaveS
Seconded -- FlexTable is your friend here, and can cope with odd
widgets or labels that are too long by using
FlexTable.getFlexCellFormatter() to get the cell formatter, and then
set 'colspan' (or rowspan) for some cells if necessary.

It can produce great results, and basically maps to an HTML table I
believe.

 HTH

   Dave.

On Jan 8, 6:09 am, Abdullah Shaikh abdullah.shaik...@gmail.com
wrote:
 In my case I have used FlexTable, I guess GridTable will also do.

 You can set the controls using setWidget(row, column, widget)

 - Abdullah

 On Fri, Jan 8, 2010 at 11:09 AM, Abhay Singh abhay.asi...@gmail.com wrote:
  Hi

  Do we have any thing in GWT to implement GridLayout 
  I need to designs a form having lots of text/check boxes in it, but
  facing problem in placing them
  properly and well aligned.

  I tried with combination of HorizontalPanel and VeticalPanel but this
  is too tidious and not getting proper aignment...
  what should i do...

  Thanks...

  --
  You received this message because you are subscribed to the Google Groups
  Google Web Toolkit group.
  To post to this group, send email to google-web-tool...@googlegroups.com.
  To unsubscribe from this group, send email to
  google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com
  .
  For more options, visit this group at
 http://groups.google.com/group/google-web-toolkit?hl=en.
-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.




Re: How to minimize browser using GWT ?

2009-10-28 Thread DaveS

Why not just use the browser's own minimise button?

I'm sure you won't be able to minimise the browser from inside
JavaScript code.

  Dave.

On Oct 28, 1:24 pm, Rinku ashishkushwaha1...@gmail.com wrote:
 Please help me.
 It is very urgent.

 Thanks in advance.

 On Oct 28, 9:42 am, Rinku ashishkushwaha1...@gmail.com wrote:

  Thanks for your replies.
  First I am explaining my requirement :-

  I created my own minimize and maximize button in my Application.
  When I click on minimize button, my application should minimize like
  our application
   (If we minimize any application in our PC, that application is
  displaying in our taskbar)
  I want my application should display in taskbar after minimize.

  I know how to resize the application to its minimum size.
  But resize is not ful filling  my requirement.

  Please help me.

  On Oct 27, 7:07 pm, ganesh.shirsat ganesh.shir...@gmail.com wrote:

   i tried this but javascript not provide any solution for minimize the
   window.

   On Oct 27, 7:00 pm, Lothar Kimmeringer j...@kimmeringer.de wrote:

Rinku schrieb:

 How to minimize browser using GWT ?

If you replace GWT with HTML/Javascript and know the answer,
you can answer that for yourself. I don't know the answer, but
doubt that this is possible.

Regards, Lothar

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---



Re: When run jsp in GWT 1.7, error occurred Syntax error, parameterized types are only available if source level is 1.5

2009-08-23 Thread DaveS

Are you using maven? If so check your POM for the compiler settings
for the maven-compiler-plugin to make sure the java version  is set to
1.5 or above.

If not then there must be some equivalent setting that governs the
java-version compatibility of the GWT java-to-js compiler

On Aug 23, 10:45 am, betterdanielding betterdanield...@gmail.com
wrote:
 When I'am running jsp in GWT 1.7, the error occurred:

 Syntax error, parameterized types are only available if source level
 is 1.5

 I have set the servlet parameters in web.xml and set the Eclipse
 project JRE level, but it doesn't work.

 Can any one help?

 Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---



Re: Problem with GWT RPC when parameter contains collection.

2009-08-22 Thread DaveS

Have you tried enabling debugging in the browser, to see if any JS
exceptions are being thrown?

On Aug 21, 7:01 pm, Arkady arka...@gmail.com wrote:
 Actually the request is never posted and therefore never arrives to
 the impl class. I suspect that the problem is with the serialization
 of the MyItem class.

 On Aug 20, 5:42 pm, tolga ozdemir tka...@gmail.com wrote:

  Can you post the method of your impl class here to investigate the
  problem? I do not know yet but maybe my sample helps you to compare
  your code as well..

 http://www.tolgaozdemir.net/2009/08/19/gwt-101-lessons-2-gwt-17-with-...

  On Aug 20, 11:37 pm, Arkady arka...@gmail.com wrote:

   I am having problem with GWT RPC in the following scenario.

   I have a service:

   public interface MyService extends RemoteService {

         public MyResult getMyResult(MyParam param);

   }

   with corresponding Async version and Impl version. MyParam class
   contains ArrayListMyItem:

   public class MyParam implements Serializable {
      private ArrayListMyItem items;

      public MyParam() {

      }

      public MyParam(ArrayListMyItem items) {
            this.items = items;
      }

      public ArrayListMyItem getItems() {
            return items;
      }

      public void setItems(ArrayListMyItem items) {
            this.items = items;
      }

   }

   public class MyItem implements Serializable {

   }

   When I invoke getMyResult(new MyParam(new ArrayListMyItem()))
   everything works fine and the execution reaches the Impl class on the
   server. But if I invoke getMyResult() with non-empty list of items the
   request is never posted to the server and there is no exception in the
   log.

   Any help will be greatly appreciated.

   Thanks.- Hide quoted text -

  - Show quoted text -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---



Re: when should we use GWT RPC and HTTP mechanism to communicate to server

2009-08-20 Thread DaveS

I don't think you're ever *forced* to use RPC, it simply requires
writing a lot less code than writing a servlet, parsing XML, returning
XML and parsing that result in the client. GWT makes it very easy to
use RPC, but doesn't force you to do so.

In our app we do both, but by far the majority of client/server comms
is GWT RPC.

  DaveS.

On Aug 19, 1:43 pm, venki pola.ve...@gmail.com wrote:
 Thank you DaveS

 Ok cool instance... One more doubt Dave. I understand your example.
 Let us suppose my service is going to use by GWT client only. So in
 this case i can use either GWT RPC or HTTP. So i can do my application
 with out using RPC  also rather i can use HTTP.Can you please tell me
 an instances why should i opt for GWT RPC mechanism only. I mean i am
 expecting the answers that in what cases we are forced to use RPC
 rather than HTTP. If possible can you please tell me the advantages
 RPC over HTTP.

 Once again thank you very much for your reply..

 Have a good day Dave

 On Aug 19, 1:34 pm, DaveS dave.sell...@gmail.com wrote:

  Our application uses both, depending on quite a few factors. In some
  cases we are putting data into Flash (.swf) components, and need it in
  XML, so we use a 'raw' HTTP request to get the data. In most other
  cases we use GWT RPC to retreive data from the server, or to initiate
  actions in the server. There really is no single answer, it just
  depends on your application.

  We have considered moving away from GWT RPC more than once, thinking
  we might provide an 'open interface' or web-service interface, but so
  far the convenience of RPC has been the overwhelming reason we are
  continuing to use it.

  I guess you could say, if there is no need to make the service
  available to anything other than your GWT client, then use RPC, but if
  you want to open the interface to 3rd parties, other apps or anything
  like that, consider using HTTP.

    Dave.

  On Aug 18, 5:56 pm, venki pola.ve...@gmail.com wrote:

   Hi to all,

   I am new to GWT. I read GWT communication with server tutorial. It
   provides various mechanisms to communicate with the server. Any way i
   know how to use GWT RPC and HTTP mechanism to communicate with
   server.

   I request all of you can you give perfect explanation towhenshould
   we use RPC mechanism andwhenshould we use HTTP mechanism. I mean at
   what type instances we are forced to use particular mechanism.

   Great thanks in advance..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---



Re: when should we use GWT RPC and HTTP mechanism to communicate to server

2009-08-19 Thread DaveS

Our application uses both, depending on quite a few factors. In some
cases we are putting data into Flash (.swf) components, and need it in
XML, so we use a 'raw' HTTP request to get the data. In most other
cases we use GWT RPC to retreive data from the server, or to initiate
actions in the server. There really is no single answer, it just
depends on your application.

We have considered moving away from GWT RPC more than once, thinking
we might provide an 'open interface' or web-service interface, but so
far the convenience of RPC has been the overwhelming reason we are
continuing to use it.

I guess you could say, if there is no need to make the service
available to anything other than your GWT client, then use RPC, but if
you want to open the interface to 3rd parties, other apps or anything
like that, consider using HTTP.

  Dave.

On Aug 18, 5:56 pm, venki pola.ve...@gmail.com wrote:
 Hi to all,

 I am new to GWT. I read GWT communication with server tutorial. It
 provides various mechanisms to communicate with the server. Any way i
 know how to use GWT RPC and HTTP mechanism to communicate with
 server.

 I request all of you can you give perfect explanation to when should
 we use RPC mechanism and when should we use HTTP mechanism. I mean at
 what type instances we are forced to use particular mechanism.

 Great thanks in advance..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---



Re: JDBC Example using GWT

2009-08-13 Thread DaveS

Not really clear what you mean here... JDBC is a back-end (server
side) technology, compared to GWT which is for generating your client
side GUI. Even though you are apparently writing Java code for GWT,
remember that it gets compiled to JavaScript and executed in the
browser. You could just write a conventional Java server component
(J2EE / servlet / etc) and connect to JDBC with that, and have it talk
to your GWT-based GUI, but your GWT code will not be talking to JDBC
directly as far as I know.

  Dave.

On Aug 13, 5:27 am, Ravindra ravindrareddy...@gmail.com wrote:
 Hi,

 I am new to GWT. i am unable to connect to JDBC applications using
 GWT. Is it possible ??

 If anybody used it pls give a sample example...

 Please help in this..

 Thanks,
 Reddy
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---



large GWT app fails to load in IE - anyone else seeing this?

2009-06-05 Thread DaveS

[re-post with better title - sorry for the dup but this is killing
me!]

If anyone from the GWT dev team is reading, please get in touch, we
are struggling badly with this issue and would *really* appreciate any
help.

We have a fairly big GWT app, and we are experiencing some issues when
running it in IE.

Sometimes (and there's no rhyme or reason to it) the app simply fails
to start up. The HTML file is loaded by the browser, and the
my.app.nocache.js file is loaded, but it then gets stuck. After a
*lot* of debugging and cursing IE, we found out that it is stuck in
the .nocache.js file waiting for the document readyState to become
ready.

There is a timer-function in this file, that goes off every 50ms, and
checks to see if the $doc.readyState is loaded or complete and for
some reason, when our app fails to load, the $doc.readyState never has
either of those values (it seems to be stuck in interactive). When
the app loads and runs correctly, this timer finds the readyState the
first time it goes off, and it then triggers the app to be loaded. I
see there is also an event-listener on the DOMContentLoaded event
that effectively does the same thing, so it looks like the designers
tried to work around this in more ways than one already. Obviously, in
the cases where our app fails to start, this event is not firing
either.

Has anyone else ever seen this, or have any ideas about why IE is not
setting the document readyState. I can see it might be because the
document really isn't ready, but is there any way we can tell what
it's waiting for?

Any suggestions gratefully received

  Dave.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---



Problems with $doc.readyState and app sometimes failing to load/run in IE

2009-05-29 Thread DaveS

We have a fairly big GWT app, and we are experiencing some issues when
running it in IE.

Sometimes (and there's no rhyme or reason to it) the app simply fails
to start up. The HTML file is loaded by the browser, and the
my.app.nocache.js file is loaded, but it then gets stuck. After a
*lot* of debugging and cursing IE, we found out that it is stuck in
the .nocache.js file waiting for the document readyState to become
ready.

There is a timer-function in this file, that goes off every 50ms, and
checks to see if the $doc.readyState is loaded or complete and for
some reason, when our app fails to load, the $doc.readyState never has
either of those values (it seems to be stuck in interactive).

When the app loads and runs correctly, this timer finds the readyState
the first time it goes off, and it then triggers the app to be loaded.

I see there is also an event-listener on the DOMContentLoaded event
that effectively does the same thing, so it looks like the designers
tried to work around this in more ways than one already. Obviously, in
the cases where our app fails to start, this event is not firing
either.

Has anyone else ever seen this, or have any ideas about why IE is not
setting the document readyState. I can see it might be because the
document really isn't ready, but is there any way we can tell what
it's waiting for?

Any suggestions gratefully received

  Dave.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---