Re: GWT and SOAP - an easier way?
GWT is to generate client code. I'm not sure why you'd want to access SOAP services directly from a webpage. You can make simple calls from the client with GWT-rpc, or AJAX REST or even JSON-RPC. SOAP is really heavy for this, and isn't built to work cross-domain. If you just need server-server SOAP calls, then you can use anything you'd like. Luis On Wed, Nov 16, 2011 at 2:54 PM, David Vree david.h.v...@gmail.com wrote: The documentation on GWT wrt SOAP states that we should use RequestBuilder to make the call and process the XML that is returned. However, Apache CXF's SOAP framework (and others) will generate Java client proxies for us. Is there some way to use these within GWT? Has anyone done this so as to avoid writing a ton of XML processing code? I ask because my company is building a commercial enterprise webapp and we are considering GWT for the UI. However, we also need to provide a web services API to our backend. Because our application is mostly about running various operations on complex, cyclic object graphs, we are inclined to go with SOAP instead of REST. -- 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. -- 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.
Two GWT scripts in one page.
So I've gotten GWT to make a cross domain script with the xsiframe linker and it works ok. However one problem: In my local GWT app i'm developing, I'm doing something like this: script type=text/javascript language=javascript src= http://otherhost.com/xsapp/xsapp.nocache.js;/script script type=text/javascript language=javascript src=/myapp/myapp.nocache.js/script This works fine if I load up http://127.0.0.1:/index.jsp If I try and debug it with: http://127.0.0.1:/index.jsp?gwt.codesvr=127.0.0.1:9997 it breaks. It looks like in the debugger, it's trying to debug xsapp.nocache.js which it should not need to. Is there a workaround for this? Seems like we can't just use standalone (non-inherited) GWT libraries if this can't be done. Luis -- 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: Two GWT scripts in one page.
That's the problem. I still need to use dev mode. There really should be some configuration for this. On Thu, Oct 27, 2011 at 9:23 AM, Thomas Broyer t.bro...@gmail.com wrote: You can use several GWT modules in the same HTML page, but then the DevMode applies for all of them. (at least I'm not aware of a way to filter the modules it'd apply to) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Engf9SXOUGgJ. 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. -- 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: jquery?
Maintaining JS doesn't have to become a nightmare on large projects. Other toolkits besides jquery have taken things like modularity,dependency management, and modularity into account. Write in GWT if you want to write in Java. On Tue, Oct 25, 2011 at 11:33 AM, Tomasz Gawel tomaszga...@op.pl wrote: hi, main gwt strong point is maintainability, team work support, and refactoring support which comes from java and java tools (and are not specific to gwt) and are not available in javascript and not possible be available in javascript. javascript is extremely flexible and powerful scripting language - but it is scripting language and becomes a nightmare to maintain large scale application or written by team especially by team with big rotation. -- 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. -- 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.
Cross domain builds
I'm trying to get a cross domain build of my app, so I added: add-linker name=xs / to my module xml file I'm getting: [ERROR] Invalid linker name 'xs' I found an example where I could define the linker as: define-linker name=xs class=com.google.gwt.dev.linker.XSLinker / but that class doesn't seem to exist in GWT 2.3 Is there a different way to do a cross domain build now? Luis -- 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: Cross domain builds
I've added an xsiframe linker. Should I have gotten an additional -xs.js file? The standard looking js file it created doesn't work loaded from a different domain. Luis On Wed, Oct 19, 2011 at 12:00 PM, Thomas Broyer t.bro...@gmail.com wrote: I didn't remember the linker being removed, but it's been deprecated for some time now. It's been replaced by the xsiframe linker. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/GKer7N469GgJ. 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. -- 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: Cross domain builds
Ok, the build output just looks like the standard linker was used. Since its still the nocahe.js and html files The output error looked the same as before: Unsafe JavaScript attempt to access frame with URL http://localhost:8080/webclient/ from frame with URL http://cmdev:/pe/PE/DBFC82AC1D77661A91A0E32C1F2FA501.cache.html. Domains, protocols and ports must match. On Wed, Oct 19, 2011 at 5:17 PM, Thomas Broyer t.bro...@gmail.com wrote: No, all linkers will generate a *.nocache.js (so changing linker doesn't require changing the HTML host page) and all related files will be linker-specific; in particular, xsiframe generates *.cache.js, while the standard linker generates *.cache.html files. And about doesn't work loaded from a different domain, what's your browser saying? (in its error console) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Bqs5gUWWHRgJ. 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. -- 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: Global Event Bus ?
Thanks for the help guys. I got it working using a modified version Tomasz's implementation. I think the main difference with mine was that it's only taking JavascriptObject for an event object and that the bus itself is an javascript object. Luis On Fri, Oct 14, 2011 at 5:25 PM, Stefan Ollinger stefan.ollin...@gmx.dewrote: Oh, and if you want to do local communication between separate modules, i would use a JSNI approach and de-/serialize the common message classes. Using the AutoBean framework for example: http://code.google.com/p/google-web-toolkit/wiki/AutoBean Am 15.10.2011 02:22, schrieb Stefan Ollinger: Hello, you could use a common library to define your message classes and import that library in both gwt modules. Then use something like comet to push your messages to the clients: http://code.google.com/p/gwt-comet/ Regards, Stefan -- 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. -- 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. -- 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.
Global Event Bus ?
I have a use case where I need to compile separate entry points into
separate javascript files and one or multiple files arbitrarily on different
pages. This is common with JSR-168 portlets, but plenty of other types of
apps might need this.
The problem is that I can't find a mechanism outside of writing JSNI code to
a pub/sub system such as this:
https://github.com/phiggins42/bloody-jquery-plugins/blob/master/pubsub.js
I've wrapped that code into a PubSub.java class here:
http://azprogrammer.com/gwt/PubSub.java
That class contains all the JSNI I should need, so I figure if I want say:
application GwtA to communicate with application GwtB I'd have to write
JSNI code in those apps to use the Global bus crated by PubSub. And that
works, but I'd rather PubSub was just a utility and have GwtA and GwtB not
require subscribing with JSNI.
So I created a Subsciber interface:
public interface Subscriber {
public void handleEvent(String name, Object val);
}
The GwtA B apps could just:
PubSub m_pubSub = new PubSub();
//send with:
m_pubSub.publish(sendName, Value from gwtA);
//or subcribe with:
m_pubSub.subscribe(sendName, new Subscriber() {
public void handleEvent(String name, Object val) {
//do something
}
});
This works fine once the app is compiled. I can even pub and sub to the
event bus with external non-GWT code in the page.
However, it doesn't work in dev mode in eclipse.I'm sure stuff only
working once compiled is a bug, but I can't really wait for this to be
fixed.
Is there a better way to achieve Pub/Sub globally on separately compiled GWT
apps? Can whatever mechanism that is be exported to be used by non-GWT
code?
Thanks,
Luis Montes
--
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.
