Confirming the export worked?

32 views
Skip to first unread message

Ken Brown

unread,
Sep 30, 2013, 6:39:26 PM9/30/13
to gwtex...@googlegroups.com
I'm wondering if there's any way to confirm that the export is actually working. I've added the JAR to my project, injected the proper tags into my gwt.xml, annotated my class and implemented Exportable. However, I don't see any errors (well...other than that Eclipse doesn't like the @Export tag...now I can't debug GWT any more). Is there any simple way to see if it failed or confirm the object references exist somewhere? Any extra files you create?

Ken Brown

unread,
Oct 17, 2013, 8:18:32 PM10/17/13
to gwtex...@googlegroups.com
Anybody? I know people here have actually successfully used this product. Is there anything I can refer to in order to determine that this tool has done anything at all? Does it create a file? Does it throw errors? If so, where?

田传武

unread,
Oct 17, 2013, 9:48:03 PM10/17/13
to gwtex...@googlegroups.com
Do you invoke ExporterUtil.exportAll() within onModuleLoad()? See an example at:

If so, after compilation, open chrome development tools, and select the console tab, type your exported variable or function name to verify if it exists.


--
Has recibido este mensaje porque estás suscrito al grupo "gwtexporter" de Grupos de Google.
Para anular la suscripción a este grupo y dejar de recibir sus correos electrónicos, envía un correo electrónico a gwtexporter...@googlegroups.com.
Para obtener más opciones, visita https://groups.google.com/groups/opt_out.

Ken Brown

unread,
Oct 18, 2013, 5:44:31 PM10/18/13
to gwtex...@googlegroups.com
Thank you very much for your reply.

I did have exportAll() in place. Thank you for the tip with the console. That does help quite a bit and I do have it working now.

My issue was that, while I am having my class implement Exportable, I was not using the @Export annotation because it was causing a compile error. I finally saw that Eclipse suggested I import org.timepedia.exporter.client.Export to fix that, and it did. But it wasn't clear at all because it wasn't really mentioned in the docs (I didn't even know you could add annotations to the compiler via classes like that).
Reply all
Reply to author
Forward
0 new messages