springframework-developer — Spring Framework developers list

[Springframework-developer] Spring WebFlow build.12 FAILED

[<al...@in...>]

Errors and a list of modifications can be found in the build log (http://static.springframework.org/spring-webflow/build/index.html).

[Springframework-developer] Spring build.446 SUCCEEDED

[<ale...@in...>]

Snapshot has been uploaded to http://www.springframework.org/snaphots
    			
The list of modifications for this build can be found in the build log (http://static.springframework.org/spring/build/index.html).    			
			

[Springframework-developer] Spring build.445 SUCCEEDED

[<ale...@in...>]

Snapshot has been uploaded to http://www.springframework.org/snaphots
    			
The list of modifications for this build can be found in the build log (http://static.springframework.org/spring/build/index.html).    			
			

[Springframework-developer] Spring WebFlow build.12 FAILED

[<al...@in...>]

Errors and a list of modifications can be found in the build log (http://static.springframework.org/spring-webflow/build/index.html).

[Springframework-developer] Spring build.444 SUCCEEDED

[<ale...@in...>]

Snapshot has been uploaded to http://www.springframework.org/snaphots
    			
The list of modifications for this build can be found in the build log (http://static.springframework.org/spring/build/index.html).    			
			

[Springframework-developer] Spring build.443 SUCCEEDED

[<ale...@in...>]

Snapshot has been uploaded to http://www.springframework.org/snaphots
    			
The list of modifications for this build can be found in the build log (http://static.springframework.org/spring/build/index.html).    			
			

[Springframework-developer] Spring WebFlow build.12 FAILED

[<al...@in...>]

Errors and a list of modifications can be found in the build log (http://static.springframework.org/spring-webflow/build/index.html).

[Springframework-developer] Spring build.442 SUCCEEDED

[<ale...@in...>]

Snapshot has been uploaded to http://www.springframework.org/snaphots
    			
The list of modifications for this build can be found in the build log (http://static.springframework.org/spring/build/index.html).    			
			

[Springframework-developer] Spring WebFlow build.12 FAILED

[<al...@in...>]

Errors and a list of modifications can be found in the build log (http://static.springframework.org/spring-webflow/build/index.html).

[Springframework-developer] Spring WebFlow build.12 FAILED

[<al...@in...>]

Errors and a list of modifications can be found in the build log (http://static.springframework.org/spring-webflow/build/index.html).

[Springframework-developer] Spring build.441 SUCCEEDED

[<ale...@in...>]

Snapshot has been uploaded to http://www.springframework.org/snaphots
    			
The list of modifications for this build can be found in the build log (http://static.springframework.org/spring/build/index.html).    			
			

Re: [Springframework-developer] FrameworkServlet and Acegi Security's AccessDeniedException

[Ben A. <ben...@ac...>]

katentim wrote:
> Can org.springframework.web.servlet.FrameworkServlet.processRequest be 
> altered to not wrap runtime exceptions? It should be able to re-throw 
> them just like ServletException and IOException unless there are 
> backward compatability issues.
>
> http://opensource2.atlassian.com/projects/spring/browse/SEC-199
>
Hi Tim

I have commented on the JIRA issue, as this change to FrameworkServlet 
shouldn't be necessary.

Best regards
Ben

[Springframework-developer] Spring WebFlow build.12 FAILED

[<al...@in...>]

Errors and a list of modifications can be found in the build log (http://static.springframework.org/spring-webflow/build/index.html).

RE: [Springframework-developer] somewhat confusing behavior w/ LSFB create/update/dropSchema methods.

[Tim K. <tim...@gm...>]

Dmitriy,

Thanks for writing in with the suggestion.  I will certainly give this a
try.  

I still think, however, that it would be useful if the stock LSFB methods
would at least return some type of output regarding the operations that
occurred inside, or at least throw DAE.. since the javadocs are misleading
in that sense when they suggest that DAE will be thrown upon script
compilation errors.  That's my view, at least.

Thanks again,

-tim


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Dmitriy Kopylenko
Sent: Friday, March 17, 2006 1:52 PM
To: spr...@li...
Subject: Re: [Springframework-developer] somewhat confusing behavior w/ LSFB
create/update/dropSchema methods.

Dmitriy Kopylenko wrote:
>>
>> So it would seem that my only option is to subclass LSFB and modify
>> the behavior of those to collect the error messages and pass them on
>> up.  I would think, however that those methods could benefit from
>> clearer javadoc comments on what I've just covered, and it would be
>> nice to be able to obtain that output (or to at least know somehow) to
>> be able to determine if any errors were generated, and have some sort
>> of output on the reasons why, since there is no way to accomplish that
>> right now without subclassing the LSFB itself (as far as I can see) -
>> and I'm somewhat leery of having to maintain a subclass of LSFB for
>> the entire foreseeable future of the application since it is such a
>> critical part of the spring/hibernate functionality.  If I'm mistaken
>> on this, I'd greatly appreciate a point in the right direction.
>>
>
> If you call *DatabaseSchema() methods directly on LSFB instance, I 
> think there could be more modular, cleaner, etc. solution than 
> extending LSFB, by using AspectJ with Inter-Type declaration and 
> "handler" pointcut designator...
>
>
Here's how you could possibly do it:

public aspect DatabaseShemaOperationsErrorsCollector {
   
    private List<SQLException> LocalSessionFactoryBean.exceptions = new 
ArrayList<SQLException>();
   
    public List<SQLException> 
LocalSessionFactoryBean.getDatabaseShemaErrors() {
        return this.exceptions;
    }
   
    private void 
LocalSessionFactoryBean.recordDatabaseSchemaException(SQLException 
sqlException) {
        this.exceptions.add(sqlException);
    }
   
    public pointcut databaseSchemaOperationExceptionHandler(SQLException 
sqlException, LocalSessionFactoryBean localSessionFactoryBean):
        handler(SQLException) &&
            args(sqlException) &&
                this(localSessionFactoryBean);
   
   
    before(SQLException sqlException, LocalSessionFactoryBean 
localSessionFactoryBean) :
        databaseSchemaOperationExceptionHandler(sqlException, 
localSessionFactoryBean) {
            
localSessionFactoryBean.recordDatabaseSchemaException(sqlException);
    }

}


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] somewhat confusing behavior w/ LSFB create/update/dropSchema methods.

[Dmitriy K. <dko...@ru...>]

Dmitriy Kopylenko wrote:
>>
>> So it would seem that my only option is to subclass LSFB and modify
>> the behavior of those to collect the error messages and pass them on
>> up.  I would think, however that those methods could benefit from
>> clearer javadoc comments on what I've just covered, and it would be
>> nice to be able to obtain that output (or to at least know somehow) to
>> be able to determine if any errors were generated, and have some sort
>> of output on the reasons why, since there is no way to accomplish that
>> right now without subclassing the LSFB itself (as far as I can see) -
>> and I'm somewhat leery of having to maintain a subclass of LSFB for
>> the entire foreseeable future of the application since it is such a
>> critical part of the spring/hibernate functionality.  If I'm mistaken
>> on this, I'd greatly appreciate a point in the right direction.
>>
>
> If you call *DatabaseSchema() methods directly on LSFB instance, I 
> think there could be more modular, cleaner, etc. solution than 
> extending LSFB, by using AspectJ with Inter-Type declaration and 
> "handler" pointcut designator...
>
>
Here's how you could possibly do it:

public aspect DatabaseShemaOperationsErrorsCollector {
   
    private List<SQLException> LocalSessionFactoryBean.exceptions = new 
ArrayList<SQLException>();
   
    public List<SQLException> 
LocalSessionFactoryBean.getDatabaseShemaErrors() {
        return this.exceptions;
    }
   
    private void 
LocalSessionFactoryBean.recordDatabaseSchemaException(SQLException 
sqlException) {
        this.exceptions.add(sqlException);
    }
   
    public pointcut databaseSchemaOperationExceptionHandler(SQLException 
sqlException, LocalSessionFactoryBean localSessionFactoryBean):
        handler(SQLException) &&
            args(sqlException) &&
                this(localSessionFactoryBean);
   
   
    before(SQLException sqlException, LocalSessionFactoryBean 
localSessionFactoryBean) :
        databaseSchemaOperationExceptionHandler(sqlException, 
localSessionFactoryBean) {
            
localSessionFactoryBean.recordDatabaseSchemaException(sqlException);
    }

}

[Springframework-developer] Spring WebFlow build.12 FAILED

[<al...@in...>]

Errors and a list of modifications can be found in the build log (http://static.springframework.org/spring-webflow/build/index.html).

[Springframework-developer] Re: Phav8ramacy news

[Manoel Q. <qui...@wi...>]

=20
w C v i u a g I q i x s $ v 99 (10 qL   s p x i h l z l s s w )
q V e a i I n i v u x m $10 p 5 (3 VA 0  n p a i m l f l d s t )
l V l i r a w g k r i a $ x 69 (1 zE 0  z p o i r l c l y s v )
=20
Many oth Em er, Visi N9 t our si ih te <http://qyni2.fomspuepav.com>
and S 7Y ave ov 8E er 50 FC %

[Springframework-developer] Spring build.440 SUCCEEDED

[<ale...@in...>]

Snapshot has been uploaded to http://www.springframework.org/snaphots
    			
The list of modifications for this build can be found in the build log (http://static.springframework.org/spring/build/index.html).    			
			

[Springframework-developer] Spring WebFlow build.12 FAILED

[<al...@in...>]

Errors and a list of modifications can be found in the build log (http://static.springframework.org/spring-webflow/build/index.html).

Re: [Springframework-developer] C3P0NativeJdbcExtractor problem with Hibernate 3.1.2

[Juergen H. <ju...@in...>]

This is caused by Hibernate 3.1's introduction of its
"BorrowedConnectionProxy". Any Connection returned from a Hibernate =
Session
is now such a proxy instead of the target Connection. Of course our
NativeJdbcExtractor doesn't know how to deal with this, since it =
operates on
actual connection pool handles.

This is not a Spring issue in the first place, of course: It will affect =
any
code calling Session.connection() and expecting to cast it to a driver =
impl
class - or usually, first connection pool impl class, then driver impl
class.

I've just checked the Hibernate implementation of that
BorrowedConnectionProxy: There is no direct way of retrieving the =
underlying
target Connection; it's simply not been considered. This is a pain, of
course, but we can do something about it: apply the same =
DatabaseMetaData
trick that our SimpleNativeJdbcExtractor uses.

So what I've done is refined our NativeJdbcExtractorAdapter base class: =
It
first tries the subclass's extraction process. If that failed - that is,
returned the same Connection handle as passed in - we'll simply call
con.getMetaData().getConnection() and retry the subclass's extraction
process.

Since Hibernate doesn't wrap the Connection exposed by the =
DatabaseMetaData
object, we'll get access to the actual pool Connection and are able to =
apply
our C3P0 / Commons DBCP / etc extraction rules. This will also work for =
all
other sorts of simple proxying, for example by other persistence =
providers.

The NativeJdbcExtractorAdapter refinement will be released in Spring 2.0 =
M4
and also (a bit later) in Spring 1.2.8. For the time being, simply =
subclass
your extractor and call con.getMetaData().getConnection() before =
attempting
to cast for C3P0ProxyConnection (or the like).

Juergen
=20

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf =
Of
Magnus Heino
Sent: Monday, March 13, 2006 2:01 PM
To: spr...@li...
Subject: [Springframework-developer] C3P0NativeJdbcExtractor problem =
with
Hibernate 3.1.2

Hi.

I'm not sure if this is a bug, new feature, or if it's me just being =
dumb :)

I have a class that extends JdbcDAOSupport. I'm using
com.mchange.v2.c3p0.ComboPooledDataSource,
org.springframework.orm.hibernate3.LocalSessionFactoryBean and
org.springframework.jdbc.support.nativejdbc.C3P0NativeJdbcExtractor.

I do this:

conn =3D (OracleConnection) getJdbcTemplate()
=09
.getNativeJdbcExtractor().getNativeConnection(
=09
DataSourceUtils.getConnection(getDataSource()));

in the c3p0jdbcextractor, this instanceof

protected Connection doGetNativeConnection(Connection con) throws
SQLException {
		if (con instanceof C3P0ProxyConnection) {


returns true when using hibernate 3.0.5. When using 3.1.2 however, "con"
looks like this:

con=3D $Proxy19  (id=3D196)
	h=3D BorrowedConnectionProxy  (id=3D253)
		connectionManager=3D ConnectionManager  (id=3D256)
			batcher=3D BatchingBatcher  (id=3D261)
			borrowedConnection=3D $Proxy19  (id=3D196)
			callback=3D JDBCContext  (id=3D265)
			connection=3D NewProxyConnection  (id=3D268)
			factory=3D SessionFactoryImpl  (id=3D269)
			interceptor=3D EmptyInterceptor  (id=3D275)
			isClosed=3D false
			releaseMode=3D ConnectionReleaseMode  (id=3D278)
			wasConnectionSupplied=3D false
		useable=3D true

the "con" when used hibernate 3.0.5 is now in
con->h->connectionManager->connection

Is this a configuration error, hibernate bug, C3P0NativeJdbcExtractor =
bug,
or what?

--

  /Magnus Heino


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting =
language
that extends applications into web and mobile media. Attend the live =
webcast
and join the prime developer group breaking into this new coding =
territory!
http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=121642
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] Spring WebFlow build.12 FAILED

[<al...@in...>]

Errors and a list of modifications can be found in the build log (http://static.springframework.org/spring-webflow/build/index.html).

[Springframework-developer] Spring WebFlow build.12 FAILED

[<al...@in...>]

Errors and a list of modifications can be found in the build log (http://static.springframework.org/spring-webflow/build/index.html).

[Springframework-developer] Spring WebFlow build.12 FAILED

[<al...@in...>]

Errors and a list of modifications can be found in the build log (http://static.springframework.org/spring-webflow/build/index.html).

[Springframework-developer] Spring build.439 SUCCEEDED

[<ale...@in...>]

Snapshot has been uploaded to http://www.springframework.org/snaphots
    			
The list of modifications for this build can be found in the build log (http://static.springframework.org/spring/build/index.html).    			
			

[Springframework-developer] Spring WebFlow build.12 FAILED

[<al...@in...>]

Errors and a list of modifications can be found in the build log (http://static.springframework.org/spring-webflow/build/index.html).