Re: [Resin-interest] 4.0.2 schedule

2009-11-30 Thread Scott Ferguson
Jan Kriesten wrote:
 Hi Georg,

   
 i can't reproduce this behaviour,
 * Resin-4.0.2 (Apache2 (2.2.9), mod_ssl, mod_caucho)
 

 I'm using Resin-4.0.2 with Apache/2.2.14 and mod_caucho

 The problem is a bit difficult to reproduce. Out of 5 times posting form data
 only once the content reaches Wicket. Else the posted data is null! It seems 
 to
 be a general problem and not just for the 'login-form'.
   

If you get a chance, can you check the snapshot? The issue fixed in the 
snapshot is related, but I'm not sure if it's the same problem as you're 
seeing.

-- Scott
 It looks like there might be a timing problem. I.e. when Wicket processes the
 form data, these seems not to be available in the request object yet!

 This doesn't happen with resin-4.0.1 at all.

 Best regards, --- Jan.



 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest

   




___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] 4.0.2 schedule

2009-11-30 Thread Jan Kriesten

Hi Scott,

 If you get a chance, can you check the snapshot? The issue fixed in the 
 snapshot is related, but I'm not sure if it's the same problem as you're 
 seeing.

I just checked with

Resin-4.0.s091130 (built Mon, 30 Nov 2009 11:11:59 PST)

and a quick first check didn't have any problems any more. So you may consider
the problem solved - thanks for the quick effort! :)

Best regards, --- Jan.



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] 4.0.2 schedule

2009-11-27 Thread Jan Kriesten

Hi Georg,

 i can't reproduce this behaviour,
 * Resin-4.0.2 (Apache2 (2.2.9), mod_ssl, mod_caucho)

I'm using Resin-4.0.2 with Apache/2.2.14 and mod_caucho

The problem is a bit difficult to reproduce. Out of 5 times posting form data
only once the content reaches Wicket. Else the posted data is null! It seems to
be a general problem and not just for the 'login-form'.

It looks like there might be a timing problem. I.e. when Wicket processes the
form data, these seems not to be available in the request object yet!

This doesn't happen with resin-4.0.1 at all.

Best regards, --- Jan.



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] 4.0.2 schedule

2009-11-25 Thread Mattias Jiderhamn
Resin 4.0.2 can now be found on the download page, and for anyone else 
wondering, the syntax to use Java session serialization seems to be like 
this:


 session-config
  ...
   serialization-typejava/serialization-type
 /session-config   


 Mattias

Mattias Jiderhamn wrote (2009-10-14 08:55):
This reminds me; what is the syntax for enabling Java serialization 
for persistent store (as of http://bugs.caucho.com/view.php?id=3648)?


 /Mattias

Wesley Wu wrote (2009-10-13 23:07):
Yes, I turned on use-persistent-store/ (simply copied from my 
previous 4.0.0 conf file).


When I turned it off (commented them out)
  !-- enable persistent sessions 
  session-config

use-persistent-store/
  /session-config
  --
@SessionScope worked fine.

Thanks.

-Wesley

2009/10/14 Scott Ferguson f...@caucho.com mailto:f...@caucho.com


On Oct 13, 2009, at 1:49 PM, Wesley Wu wrote:


I found two issues so far:

1. I have to use
@PersistenceUnit(name = myPU)

when I use
@PersistenceUnit(unitName = myPU)

resin reports 
com.caucho.server.webapp.WebApp setConfigException

... @PersistenceUnit(unitName='myPU') is an unknown persistence
unit.  No matching JPA persistence-units have been deployed


Thanks.  I've added that as http://bugs.caucho.com/view.php?id=3708.



2. @SessionScoped is not going to work well in my code.

I noticed that resin use Hessian to serialize all session scoped
beans (good approach).
But this result in I have to implement Serializable interface in
my session scoped beans and beans need to be injected in them.

Unfortunately that could not be done because sometimes I need to
inject third party beans and initiate third party objects in
my session scoped beans.

I think I could only use @SessionScoped annotation on SINGLE
beans, though not tested yet.


Do you have use-persistent-store/ enabled?  The sample
resin.xml does enable it, but you might want to change that if
you don't want persistent store.





Thanks Scott. Magnificent work!


thanks!

-- Scott


-Wesley






___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
  



--

 /Mattias

___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] 4.0.2 schedule

2009-10-13 Thread Wesley Wu
Thanks Scott.
I'll test the JPA  JSR299/330 stuff.

2009/10/14 Scott Ferguson f...@caucho.com

 The 4.0.2 snapshot is now available.  Bugs can be reported at
 bugs.caucho.com. The snapshot isn't clean yet, so a bug report might
 duplicate one of our failing regression tests, but it's better to have
 two reports for a bug than zero.

 -- Scott

 On Oct 12, 2009, at 2:38 PM, Scott Ferguson wrote:

 
  On Oct 12, 2009, at 1:06 PM, Jeff Schnitzer wrote:
 
  Thanks for the update.
 
  Would it be helpful if we filed bugs against trunk? I tried it out a
  week ago but pretty quickly ran into a problem (@Named @RequestScoped
  didn't show up in the request attrs). I figured you guys were still
  working on it and probably didn't need the distraction, but if it
  would be useful, we can start reporting issues.
 
  For JSR-299/330, you can now report against the trunk, since it's been
  cleaned up.
 
  Other stuff might want to hold up, because we're still working through
  important include/forward and i18n issues.
 
  -- Scott
 
 
  Thanks,
  Jeff
 
  On Monday, October 12, 2009, Scott Ferguson f...@caucho.com wrote:
  FYI, we're taking extra time on 4.0.2 to bring it up from a
  development release to a stable release.  That process is taking
  several weeks of extra work. Our current target is the end of
  October,
  but that may slip if 4.0.2 is not ready by then.
 
  -- Scott
 
 
 
  ___
  resin-interest mailing list
  resin-interest@caucho.com
  http://maillist.caucho.com/mailman/listinfo/resin-interest
 
 
 
  ___
  resin-interest mailing list
  resin-interest@caucho.com
  http://maillist.caucho.com/mailman/listinfo/resin-interest
 
 
 
  ___
  resin-interest mailing list
  resin-interest@caucho.com
  http://maillist.caucho.com/mailman/listinfo/resin-interest



 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest

___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] 4.0.2 schedule

2009-10-13 Thread Wesley Wu
Seems 4.0.2 snapshot passed most of my web test.
Passed:
Thirdparty Hibernate JPA integration (* see issues below)
@Inject
@Qualifier
@Observes (with @Qualifier bindings)
@ApplicationScoped
@RequestScoped

Failed:
@SessionScoped

not tested:
@InterceptorBinding

I found two issues so far:

1. I have to use
@PersistenceUnit(name = myPU)

when I use
@PersistenceUnit(unitName = myPU)

resin reports
com.caucho.server.webapp.WebApp setConfigException
... @PersistenceUnit(unitName='myPU') is an unknown persistence unit.  No
matching JPA persistence-units have been deployed

2. @SessionScoped is not going to work well in my code.

I noticed that resin use Hessian to serialize all session scoped beans (good
approach).
But this result in I have to implement Serializable interface in my session
scoped beans and beans need to be injected in them.

Unfortunately that could not be done because sometimes I need to inject
third party beans and initiate third party objects in my session scoped
beans.

I think I could only use @SessionScoped annotation on SINGLE beans, though
not tested yet.



Thanks Scott. Magnificent work!

-Wesley
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] 4.0.2 schedule

2009-10-13 Thread Wesley Wu
I think I could only use @SessionScoped annotation on SINGLE beans,
though not tested yet.

sorry, I mean SIMPLE beans not SINGLE.
-Wesley

2009/10/14 Wesley Wu wumen...@gmail.com

 Seems 4.0.2 snapshot passed most of my web test.
 Passed:
 Thirdparty Hibernate JPA integration (* see issues below)
 @Inject
 @Qualifier
 @Observes (with @Qualifier bindings)
 @ApplicationScoped
 @RequestScoped

 Failed:
 @SessionScoped

 not tested:
 @InterceptorBinding

 I found two issues so far:

 1. I have to use
 @PersistenceUnit(name = myPU)

 when I use
 @PersistenceUnit(unitName = myPU)

 resin reports
 com.caucho.server.webapp.WebApp setConfigException
 ... @PersistenceUnit(unitName='myPU') is an unknown persistence unit.  No
 matching JPA persistence-units have been deployed

 2. @SessionScoped is not going to work well in my code.

 I noticed that resin use Hessian to serialize all session scoped beans
 (good approach).
 But this result in I have to implement Serializable interface in my session
 scoped beans and beans need to be injected in them.

 Unfortunately that could not be done because sometimes I need to inject
 third party beans and initiate third party objects in my session scoped
 beans.

 I think I could only use @SessionScoped annotation on SINGLE beans,
 though not tested yet.



 Thanks Scott. Magnificent work!

 -Wesley


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] 4.0.2 schedule

2009-10-12 Thread Scott Ferguson
FYI, we're taking extra time on 4.0.2 to bring it up from a  
development release to a stable release.  That process is taking  
several weeks of extra work. Our current target is the end of October,  
but that may slip if 4.0.2 is not ready by then.

-- Scott



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] 4.0.2 schedule

2009-10-12 Thread Jamison Novak
Scott,

Any possibility of getting a snapshot ahead of the end of October, or is that 
an impossibility due to regressions, etc?

The main reason I ask is because we'd love to do further testing of the 4.0 
line in our QA environment, but the previously-resolved bug (3673) causes one 
of our sites to break and prevents us from moving to that version for testing. 
That, to my knowledge, is the only thing preventing us from upgrading.

Just thought I'd ask.

-Jamie


-Original Message-
From: resin-interest-boun...@caucho.com 
[mailto:resin-interest-boun...@caucho.com] On Behalf Of Scott Ferguson
Sent: Monday, October 12, 2009 11:06 AM
To: General Discussion for the Resin application server
Subject: [Resin-interest] 4.0.2 schedule

FYI, we're taking extra time on 4.0.2 to bring it up from a development release 
to a stable release.  That process is taking several weeks of extra work. Our 
current target is the end of October, but that may slip if 4.0.2 is not ready 
by then.

-- Scott



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] 4.0.2 schedule

2009-10-12 Thread Jeff Schnitzer
Thanks for the update.

Would it be helpful if we filed bugs against trunk? I tried it out a
week ago but pretty quickly ran into a problem (@Named @RequestScoped
didn't show up in the request attrs). I figured you guys were still
working on it and probably didn't need the distraction, but if it
would be useful, we can start reporting issues.

Thanks,
Jeff

On Monday, October 12, 2009, Scott Ferguson f...@caucho.com wrote:
 FYI, we're taking extra time on 4.0.2 to bring it up from a
 development release to a stable release.  That process is taking
 several weeks of extra work. Our current target is the end of October,
 but that may slip if 4.0.2 is not ready by then.

 -- Scott



 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] 4.0.2 schedule

2009-10-12 Thread Scott Ferguson

On Oct 12, 2009, at 1:06 PM, Jeff Schnitzer wrote:

 Thanks for the update.

 Would it be helpful if we filed bugs against trunk? I tried it out a
 week ago but pretty quickly ran into a problem (@Named @RequestScoped
 didn't show up in the request attrs). I figured you guys were still
 working on it and probably didn't need the distraction, but if it
 would be useful, we can start reporting issues.

For JSR-299/330, you can now report against the trunk, since it's been  
cleaned up.

Other stuff might want to hold up, because we're still working through  
important include/forward and i18n issues.

-- Scott


 Thanks,
 Jeff

 On Monday, October 12, 2009, Scott Ferguson f...@caucho.com wrote:
 FYI, we're taking extra time on 4.0.2 to bring it up from a
 development release to a stable release.  That process is taking
 several weeks of extra work. Our current target is the end of  
 October,
 but that may slip if 4.0.2 is not ready by then.

 -- Scott



 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest



 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] 4.0.2 schedule

2009-10-12 Thread Scott Ferguson

On Oct 12, 2009, at 9:49 AM, Jamison Novak wrote:

 Scott,

 Any possibility of getting a snapshot ahead of the end of October,  
 or is that an impossibility due to regressions, etc?

 The main reason I ask is because we'd love to do further testing of  
 the 4.0 line in our QA environment, but the previously-resolved bug  
 (3673) causes one of our sites to break and prevents us from moving  
 to that version for testing. That, to my knowledge, is the only  
 thing preventing us from upgrading.

Yes, I'll put one out tonight.  It might not be very stable, though,  
especially related to include/forward and i18n.

-- Scott


 Just thought I'd ask.

 -Jamie


 -Original Message-
 From: resin-interest-boun...@caucho.com 
 [mailto:resin-interest-boun...@caucho.com 
 ] On Behalf Of Scott Ferguson
 Sent: Monday, October 12, 2009 11:06 AM
 To: General Discussion for the Resin application server
 Subject: [Resin-interest] 4.0.2 schedule

 FYI, we're taking extra time on 4.0.2 to bring it up from a  
 development release to a stable release.  That process is taking  
 several weeks of extra work. Our current target is the end of  
 October, but that may slip if 4.0.2 is not ready by then.

 -- Scott



 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest


 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest