On 2014/06/04 (Jun), at 12:51 PM, Thiago H de Paula Figueiredo wrote:
> I like this suggestion. :) Could you file a JIRA please?
Filed:
https://issues.apache.org/jira/browse/TAP5-2347
--
Robert Hailey
-
To unsubscribe, e-mai
On 2014/05/20 (May), at 4:54 PM, Kalle Korhonen wrote:
> I don't know if there's an existing issue around this.
> Take a look and open a new one if no existing issues are found. Should be
> straightforward to get it fixed.
>
> Kalle
Filed:
https://issues.apache.org/jira/browse/TAP5-2346
--
Ro
I like this suggestion. :) Could you file a JIRA please?
On Wed, 04 Jun 2014 14:35:45 -0300, Robert Hailey
wrote:
After writing yet another Dispatcher, I've come to think that the
Dispatcher interface should have return values as public constants.
The trouble is one of readability, and
After writing yet another Dispatcher, I've come to think that the Dispatcher
interface should have return values as public constants.
The trouble is one of readability, and quite minor, but worse when there is a
bunch of return statements, or when reviewing a long dispatcher (when you come
to
Thanks Thiago, looks as if I had SessionState being used in the layout.
On Wed, Jun 4, 2014 at 11:46 AM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Wed, 04 Jun 2014 12:11:00 -0300, George Christman <
> gchrist...@cardaddy.com> wrote:
>
> Hi Thiago, I just disabled coolkies w
On Wed, 04 Jun 2014 12:11:00 -0300, George Christman
wrote:
Hi Thiago, I just disabled coolkies within my browser and I'm finding
every link is being generated with a session id despite not needing to
be logged in. What would cause this?
Any page with @Persist or @SessionState being visi
George,
you can try debugging this by implementing
http://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpSessionListener.html
Put a breakpoint in sessionCreated and inspect the stack trace.
Maybe this will help.
On Wed, Jun 4, 2014 at 7:11 PM, George Christman
wrote:
> Hi Thiago, I just
Hi Thiago, I just disabled coolkies within my browser and I'm finding every
link is being generated with a session id despite not needing to be logged
in. What would cause this? I'm not sure if this would effect things, but
I'm using remember me with tapestry-security, however I'm not logged in to
There's another interesting case (probably related to this problem). I'll
keep it very simple.
1) component1
...
...
2) component2
...
...
void onMyEventFromComponent3 () {
// do something
}
3) component3
...
...
void onSelectedFromSubmit () {
componentResources.triggerEvent ( "m
On Wed, 04 Jun 2014 10:16:24 -0300, Dmitry Gusev
wrote:
I don't think requiring cookies is a bad idea.
I think every normal user would have cookies enabled.
Some proxies mess up with cookies, causing them to not work. At my work
I've got lots of client complaints because of that.
I thin
Hi guys, I ended up using StreamResponse from the jumpstart example
http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/returntypes1
along with JAXB. This appears to be working perfectly.
On Tue, Jun 3, 2014 at 3:52 AM, Magnus Kvalheim wrote:
> Hi.
> Yes, you can generate the s
Thanks Dmitry. I'll move forward with that solution.
On Wed, Jun 4, 2014 at 9:16 AM, Dmitry Gusev wrote:
> I don't think requiring cookies is a bad idea.
> I think every normal user would have cookies enabled.
>
>
> On Wed, Jun 4, 2014 at 4:59 PM, George Christman
> wrote:
>
> > I'm already us
I don't think requiring cookies is a bad idea.
I think every normal user would have cookies enabled.
On Wed, Jun 4, 2014 at 4:59 PM, George Christman
wrote:
> I'm already using tomcat7. Do you think requiring all users to have cookies
> enabled is a bad idea?
>
>
> On Wed, Jun 4, 2014 at 8:32 A
I'm already using tomcat7. Do you think requiring all users to have cookies
enabled is a bad idea?
On Wed, Jun 4, 2014 at 8:32 AM, Dmitry Gusev wrote:
> I don't think you should migrate your app server to do this, your current
> server probably supports this feature too!
> What is it btw?
>
> T
I don't think you should migrate your app server to do this, your current
server probably supports this feature too!
What is it btw?
There will be side-effects: users without cookies won't be able to use
sessions in your app.
On Wed, Jun 4, 2014 at 4:28 PM, George Christman
wrote:
> Thanks Dmi
Thanks Dmitry, so if I understand this correctly, I should be able to just
do the following and it should address the issue without side effects?
3. Switch to Tomcat 7 !
The Servlet 3.0 standard gives you two ways to disable URL session
rewriting. This works in Tomcat 7, Glassfish v3, and any oth
Hi George,
The ID appears in URLs if your app creates session for current user & this
user has cookies disabled.
You can either not create a session for guests, or disable session ID in
URLs in servlet container level,
here's an example for tomcat:
https://fralef.me/tomcat-disable-jsessionid-in-u
17 matches
Mail list logo