This looks like unrelated to gwt-maven too. http://code.google.com/p/emite/ http://www.ejabberd.im/
Emite project uses gwt-maven plugin for building, but it looks like problem lies beside it. As you said your host app starts successfully and that's the end of gwt-maven plugin role in this case. I would ask on emite project group for solution for problems with their client to server connection. On Jan 5, 4:56 am, karl <[email protected]> wrote: > Thanks. > I have checkout emite r844 and repair the pom.xml as follow: > 1. repair line 237 to "2.0-beta26" > 2. add a line after line 254, <extraJvmArgs>-Xmx512m</extraJvmArgs> > > I run emiteui as follow: > mvn com.totsp.gwt:maven-googlewebtoolkit2-plugin:gwt -P emiteui - > Dgoogle.webtoolkit.home=/path/to/gwt-linux-1.5.3 > > It can run successfully. > and I run ejabberd in my host. > But now the emiteui can't login ejabberd. > the bugs are here: > [INFO] [DEBUG] Signal session:onStateChanged fired with event: > connecting > [INFO] [DEBUG] GWT CONNECTOR SEND: <body to="localhost" content="text/ > xml; charset=utf-8" rid="377117" xmlns:xmpp="urn:xmpp:xbosh" ack="1" > hold="1" secure="true" xml:lang="en" wait="60" xmpp:version="1.0" > ver="1.6" xmlns="http://jabber.org/protocol/httpbind"; /> > [INFO] [DEBUG] Sending auth transaction: Ticket: 2...@karl-pad/ > emiteui-1231127609982-release704-0, 1234, notStarted > [INFO] [DEBUG] GWT CONNECTOR RECEIVED: <body type='terminate' > xmlns='http://jabber.org/protocol/httpbind'/> > [INFO] [DEBUG] Signal bosh:onDisconnected fired with event: > disconnected by server --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
