[Resin-interest] Re sin restarts after jsp change

[peteru25]

I have 3.0.24 and whenever i change a jsp the server restarts. I found a
thread with something similar
like i have to change auto-compile to false, but in general im confused
about the config files.
I have resin.conf and also resin-3_1.conf. Which one is overriding the
other? Where do i find
a doc describing all the config files and their role?
Thanks a lot in advance
Peter
-- 
View this message in context: 
http://www.nabble.com/Resin-restarts-after-jsp-change-tp19288765p19288765.html
Sent from the Resin mailing list archive at Nabble.com.
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Re: [Resin-interest] 3.0.27 status?

[Scott Ferguson]

On Sep 2, 2008, at 9:49 PM, Matt Pangaro wrote:

> Guys,
> Now that 3.1.7 is in the can, any ETA on a snapshot and then a release
> for 3.0.27?

We can do a snapshot today.  3.0.27 will take longer because we  
haven't started the release QA process yet.

-- Scott

>
>
> Thanks
> Matt
>
>
> ___
> 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] 3.0.27 status?

[Matt Pangaro]

Cool, thanks. Snapshot would be great, so we can vet the fixes.


Scott Ferguson wrote:
> We can do a snapshot today.  3.0.27 will take longer because we  
> haven't started the release QA process yet.
> 
> -- Scott



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

Re: [Resin-interest] 3.0.27 status? Ok, how about 3.2.1?

[Rob Lockstone]

On Sep 3, 2008, at 09:46, Scott Ferguson wrote:

>
> On Sep 2, 2008, at 9:49 PM, Matt Pangaro wrote:
>
>> Guys,
>> Now that 3.1.7 is in the can, any ETA on a snapshot and then a  
>> release
>> for 3.0.27?
>
> We can do a snapshot today.  3.0.27 will take longer because we
> haven't started the release QA process yet.
>
> -- Scott

This page  has the 3.2 snapshot date one  
week before the official 3.2.0 date. Should the snapshot even be  
listed? Same for the 3.1 snapshot, except the snapshot is almost a  
month older than the 3.1.7 release. Well, I guess if someone wanted to  
diff the code to see what changed?

And, if you know it, what's the release schedule for 3.2.1 looking like?

I know, I know, we're never satisfied. But hey, you guys have the  
three active branches going. ;-)

Rob





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

[Resin-interest] One more 3.0.27 question

[Matt Pangaro]

Scott,
I was also wondering if you'll get a chance, as you head into QA for 
3.0.27, to take a look at http://bugs.caucho.com/view.php?id=2764, which 
you reopened when it became apparent 3.0.27 would be needed.

Thanks,
Matt


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

Re: [Resin-interest] 3.0.27 status? Ok, how about 3.2.1?

[Scott Ferguson]

On Sep 3, 2008, at 10:46 AM, Rob Lockstone wrote:

> This page  has the 3.2 snapshot date one
> week before the official 3.2.0 date. Should the snapshot even be
> listed? Same for the 3.1 snapshot, except the snapshot is almost a
> month older than the 3.1.7 release. Well, I guess if someone wanted to
> diff the code to see what changed?

It's just easier to manage that way, even though it's not ideal.  That  
happens after every release.

As it happens, there's a new 3.2.1 snapshot today.

> And, if you know it, what's the release schedule for 3.2.1 looking  
> like?

Quite a bit slower than we'd like.  Normally we like 8 week releases,  
but that will probably be extended by about 4 weeks.

The major things we're looking at for 3.2.1 are:

   OSGi/Ivy integration
   Hessian 2.0 finalized (or at least sending our final draft to IETF  
for comments)
   Lots more bug fixes for Quercus and Resin
   Servlet, JSTL, JSP, JSF spec compliance
   Servlet 3.0, particularly the comet-related aspects
   OpenID
   clustering/JMS integration for BAM (The most complicated question  
is dealing with a singleton service in a clustered environment and  
handling failover issues.)

I'm not sure everything will fit in that timeframe, though.

-- Scott

>
>
> I know, I know, we're never satisfied. But hey, you guys have the
> three active branches going. ;-)
>
> Rob
>
>
>
>
>
> ___
> 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] ivy/osgi in 3.2.1 snapshot

[Scott Ferguson]

This is a work-in-progress, but I thought you'd like to know our  
current direction on this.

We're viewing ivy/osgi as basically a smarter WEB-INF/lib.  With all  
the libraries people include in their projects, it's becoming  
difficult to keep versions straight and consistent.  And the extra  
libraries are puffing up the sizes of .war files to large and  
difficult-to-maintain and deploy sizes.  (Or if not necessarily  
difficult, at least inelegant.)

A) Ivy

Our model is for Resin to manage a repository of artifacts (basically  
jars) at the top-level (either  or ), and let  
applications pull in the jars as necessary for the application.   It's  
an ivy cache repository managed by Resin and integrated into Resin's  
classloader environments.  The repository can populate itself by  
loading jars from public repositories, the filesystem, or your own  
local repository distribution system.  So you might have something like:

http://caucho.com/ns/resin";>
   
 
   http://library.foo.com/ivy"/>
 
   

(Basically identical to the ivy model).

In your resin-web.xml (or resin.xml), you could use a module/jar by  
its symbolic name.  The following configuration would add the my- 
module jar to the web-app's classpath.  The physical location of the  
jar would be Resin's top-level repository, so multiple web-apps would  
share the same .jar file (which helps the JVM's virtual memory  
efficiency):

http://caucho.com/ns/resin";>
   
 
   

B) OSGi (bundle/classloader features)

An OSGi bundle is basically a .jar file with some extra ivy-like  
dependency metadata in the manifest to properly hook up the right  
versions of a jar's dependencies.  There are a few classloader tricks  
to encapsulate and hide private implementation classes which is also  
nice.  By integrating the OSGi versioning with the ivy versioning, we  
think we can combine the ivy/OSGi concepts into a single framework.

Currently, the configuration for an OSGi bundle looks like:

http://caucho.com/ns/resin";>

   



C) OSGi (service features)

Along with its bundling/versioning, OSGi also provides a service  
lifecycle and registration system.  A good example might be a single- 
signon authentication service that's available for all the webapps.   
There's a manifest entry and an Activation class which will tell OSGi  
to start the service when Resin starts up.

Future (3.2.1?): we're looking at publishing those services  
automatically with WebBeans.  Your application could use an OSGi  
service (like the authentication), by using "@In Authentication _auth;"

Future (3.2.1?): we're also looking at configuring and publishing the  
services with WebBeans and Resin's standard  syntax.  This is  
very similar to what Spring is doing with its OSGi platform.  We'll  
probably also provide a plugin to publish those services to Spring  
inside Resin.

Future (3.2.2 ?): interestingly, Spring has proposed an OSGi plugin  
for the above two capabilities, using Spring's configuration syntax.   
Since it's a proposed standard, and the underlying IoC capabilities  
are similar to Resin's, we may implement this as a way of better  
integrating Spring applications and OSGi modules with Resin.





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