Hi,
As a gwt-log user I'd like to use the logging API from gwt-contrib. I
notice this one has the same limitation I got with gwt-log : user
can't configure the server URL for RemoteLogger. As my application has
multiple GWT modules, each of them will result with a dedicated
logging URI :
I notice running the Hosted mode server with wrong parameters output a help
message with :
-serverPrevents the embedded Tomcat server from running, even if a
port is specified
But Tomcat is supposed to have been replaced by Jetty, isn't it :D
On Wed, Feb 25, 2009 at 5:27 AM, Robert
On 25 fév, 09:18, nicolas.deloof nicolas.del...@gmail.com wrote:
Hi,
As a gwt-log user I'd like to use the logging API from gwt-contrib. I
notice this one has the same limitation I got with gwt-log : user
can't configure the server URL for RemoteLogger. As my application has
multiple GWT
I may misunderstand your suggestion, but my issue is not about where to
define the url-pattern, but having to define as many url-pattern my
application has GWT modules (and it has many)
I plan to migrate to gwt 1.6, but what does this changes ? RemoteLogging
will still call module/logging URI and
On a side note, I found when I was writing this patch that HasValue
extends HasValueChangeHandlers in trunk. It occurs to me that this
relationship could possibly be backwards. I don't think that something
with a value necessarily should be required to broadcast changes. See
the
Hi tfreitas,
You got the wrong group. You should try the regular GWT Group:
http://groups.google.com/group/Google-Web-Toolkit
To answer your question though, you would do date ranges using two
date pickers. One to choose the lower range, another to choose the
higher range. AFAIK there is no way
Thank you very much, and sorry for the wrong group ;)
Tony
On Feb 25, 10:11 am, Emily Crutcher e...@google.com wrote:
The current date picker widget does not support multi-select, it would
probably be a good candidate for a community contributed widget though :-).
On Tue, Feb 24, 2009 at
Hi
I'm testing the Eclipse lauch configuration generated by the
gwt-maven-plugin for gwt 1.6.
My webapp project has many dependencies managed as an Eclipse
classpath-container (thanks to m2eclipse plugin).
Running the lauch file I get a classpath issue :
16:57:29,331 ERROR [log.invoke0](?) failed
That looks fine to me, although that -Dcatalina.base shouldn't matter
anymore. Can you send me a VM crash log?
On Tue, Feb 24, 2009 at 11:26 PM, Robert Cooper keber...@gmail.com wrote:
I ran M1 and didn't get it, but at the time, I was still running
GWTShell and dealing with the deprecated
Huh, that should have been fixed in M2. It should now say Specify the TCP
port for the embedded web server (defaults to ). Are you sure that's
still an issue in M2?
On Wed, Feb 25, 2009 at 4:57 AM, nicolas de loof
nicolas.del...@gmail.comwrote:
I notice running the Hosted mode server with
I'm using M2 !
Unknown argument: -foo
Google Web Toolkit 1.6.1
HostedMode [-noserver] [-port port-number | auto] [-whitelist
whitelist-string] [-blacklist blacklist-string] [-logLevel level] [-gen dir]
[-style style] [-ea] [-server servletContainerLauncher] [-startupUrl url]
[-war dir] [-extra
I'm not sure I understand the issue exactly. Are you saying that web.xml
does not support url patterns of the form */logging? Or are you saying
that somehow this breaks when using GWT?
Here's one idea: if you have a servlet that's shared between a bunch of
different GWT modules, couldn't you
I've seen this before. The workaround is to put a copy of Xerces into your
WEB-INF/lib.
What's weird is that on my system, the default SAX parser factory is in the
com.sun.* namespace, which lives in the bootstrap ClassLoader and works
fine. I wonder why your default SAX parser factory is
Yes, servlet-api defines url-pattern to be [ somepath/* | *.somextension ]
Using gwt logging in a web application with multiple modules require to
setup as many servlet mappings as modules, just because url-pattern
*/logging is invalid. If gwt-incubator uses an extension based pattern like
On Wed, Feb 25, 2009 at 11:41 AM, nicolas de loof
nicolas.del...@gmail.comwrote:
I'm using M2 !
where
-noserver Prevents the embedded web server from running
-port Specify the TCP port for the embedded web server (defaults
to )
-serverPrevents the embedded
As I said my application has many other libs, including xerces (and spring,
hibernate, aspectJ ...) so there is MANY reason for me to have another SAX
parser in my classpath.
The issue here is that in my case I can manually put the parser in
web-inf/lib, but the maven plugin is expected to
Ah, okay. So it's not really a GWT problem. CC'ing some of the incubator
folks so they know about this use case.
On Wed, Feb 25, 2009 at 11:47 AM, nicolas de loof
nicolas.del...@gmail.comwrote:
Yes, servlet-api defines url-pattern to be [ somepath/* | *.somextension
]
Using gwt logging in a
I take your point.
In the general case, server side dependencies need to be copied into
WEB-INF/lib. Otherwise, the server code won't be able to access it. I can
see how an XML parser might be a special case where the servlet container
could be reasonably expected to provide it.
Toby, do you
On 25 fév, 17:47, nicolas de loof nicolas.del...@gmail.com wrote:
Yes, servlet-api defines url-pattern to be [ somepath/* | *.somextension ]
Oops, sorry!
Using gwt logging in a web application with multiple modules require to
setup as many servlet mappings as modules, just because
Nicolas, would you mind adding an issue to the incubator issue tracker?
http://code.google.com/p/google-web-toolkit-incubator/issues/entry
On Wed, Feb 25, 2009 at 9:01 AM, Scott Blum sco...@google.com wrote:
Ah, okay. So it's not really a GWT problem. CC'ing some of the incubator
folks so
I'm not sure I have all the context here, but as a guiding principle, Jetty
should be able to parse the XML files of web applications (web.xml, tag
libraries, etc...) regardless of whatever XML libraries are or are not
bundled with the webapp. This means:
1) Jetty should never use XML libraries
This is a very important issue. To resolve it, we had to code a custom
servlet container launcher, this way :
***/**
* Ensures that only Jetty and other server classes can be loaded into
the
* {...@link WebAppClassLoader}. This forces the user to put any necessary
*
On Wed, Feb 25, 2009 at 12:45 AM, BobV b...@google.com wrote:
dev/core/src/com/google/gwt/dev/jdt/AbstractCompiler.java
LG, but now I get a bunch of warnings about unused parameters due to
removing the suppression. :)
dev/core/src/com/google/gwt/dev/jdt/WebModeCompilerFrontEnd.java
issue
http://code.google.com/p/google-web-toolkit-incubator/issues/detail?id=243start=100created
for this.
On Wed, Feb 25, 2009 at 6:18 PM, Ray Ryan rj...@google.com wrote:
Nicolas, would you mind adding an issue to the incubator issue tracker?
Reviewers: bruce,
Description:
GWT issue 434
Please review this at http://gwt-code-reviews.appspot.com/7803
Affected files:
user/src/com/google/gwt/user/client/ui/MenuItem.java
Index: user/src/com/google/gwt/user/client/ui/MenuItem.java
That was kind of terse, wasn't it?
This is a one line javadoc fix to eradicate a confusing lie in MenuItem.
http://gwt-code-reviews.appspot.com/7803
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
On Thu, Feb 26, 2009 at 4:25 AM, Scott Blum sco...@google.com wrote:
1) Shove every singleJsoImpl in up front. The easiest way to do this would
be to add additional seedTypeNames in getCompilationUnitDeclarations() and
make no changes to AbstractCompiler.
Done.
The name of this type seems
On Sat, Feb 21, 2009 at 2:47 AM, Scott Blum sco...@google.com wrote:
On Fri, Feb 20, 2009 at 3:09 AM, nicolas de loof nicolas.del...@gmail.com
wrote:
I may be wrong, but doesn't the ProcessBuilder use the OS interpreter to
parse the forked process command line arguments ? (This may be JRE
28 matches
Mail list logo
