springframework-developer — Spring Framework developers list

[Springframework-developer] AbstractModelAndViewTest

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

Rob and I were thinking about adding a convenient superclass for MVC 
testing after having seen Keith's demo where he used one of those for 
testing web flow stuff.

I've added the org.springframework.web.servlet.test package, with an 
AbstractModelAndViewTest class that has some convenience methods for 
testing the contents of a ModelAndView object (compare a list, compare 
the entire model, check the view name, check to see if a model entry 
exists, et cetera). I'm looking into adding one of those for the 
SimpleFormController as well (checking binding errors et cetera).

Juergen, could you check the package. It's currently in 
web.servlet.test, as we might also want one of these for the Portlet 
support.

cheers,
-a

[Springframework-developer] FAILED BUILD: x86-linux2 (last 30 lines included)

[Darren D. <da...@sh...>]

1134297509
FAILED
    [junit] Testcase: testNaming took 0,006 sec
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,015 sec
    [junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,015 sec

    [junit] Testcase: testNaming took 0,004 sec
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,016 sec
    [junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,016 sec

    [junit] Testcase: testNaming took 0,001 sec
    [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,121 sec
    [junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
    [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,121 sec

    [junit] Testcase: testStartupWithLocatedServer took 0,063 sec
    [junit] Testcase: testStartupWithSuppliedServer took 0,024 sec
    [junit] Testcase: testRegisterWithMBeanServer took 0,012 sec
    [junit] 	Caused an ERROR
    [junit] Address already in use
    [junit] java.net.BindException: Address already in use
    [junit] 	at java.net.PlainSocketImpl.socketBind(Native Method)
    [junit] 	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
    [junit] 	at java.net.ServerSocket.bind(ServerSocket.java:318)
    [junit] 	at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
    [junit] 	at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
    [junit] 	at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
    [junit] 	at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:183)
    [junit] 	at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testRegisterWithMBeanServer(ConnectorServerFactoryBeanTests.java:78)

Last CVS updates prior to this build were:
1134295981
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml

This is an automated mail from one of the SF Compile Farm machines.  
The machine name noted in the subject encountered a failure building
or running the Spring test suite.  The last few lines of the output
were included for info.

NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.

See http://springframework.sourceforge.net/test/ for further
information.

[Springframework-developer] FAILED BUILD: x86-linux2 (last 30 lines included)

[Darren D. <da...@sh...>]

1134153438
FAILED

    [junit] Testcase: testNaming took 0,012 sec
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,015 sec
    [junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,015 sec

    [junit] Testcase: testNaming took 0,004 sec
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,017 sec
    [junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,017 sec

    [junit] Testcase: testNaming took 0,001 sec
    [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,068 sec
    [junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
    [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,068 sec

    [junit] Testcase: testStartupWithLocatedServer took 0,024 sec
    [junit] Testcase: testStartupWithSuppliedServer took 0,024 sec
    [junit] 	Caused an ERROR
    [junit] Address already in use
    [junit] java.net.BindException: Address already in use
    [junit] 	at java.net.PlainSocketImpl.socketBind(Native Method)
    [junit] 	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
    [junit] 	at java.net.ServerSocket.bind(ServerSocket.java:318)
    [junit] 	at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
    [junit] 	at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
    [junit] 	at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
    [junit] 	at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:183)
    [junit] 	at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testStartupWithSuppliedServer(ConnectorServerFactoryBeanTests.java:65)

Last CVS updates prior to this build were:
1134151981
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml

This is an automated mail from one of the SF Compile Farm machines.  
The machine name noted in the subject encountered a failure building
or running the Spring test suite.  The last few lines of the output
were included for info.

NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.

See http://springframework.sourceforge.net/test/ for further
information.

[Springframework-developer] spring build.382 Build Fixed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051209001640Lbuild.382

[Springframework-developer] FAILED BUILD: x86-linux2 (last 30 lines included)

[Darren D. <da...@sh...>]

1134067106
FAILED

    [junit] Testcase: testNaming took 0,005 sec
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,02 sec
    [junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,02 sec

    [junit] Testcase: testNaming took 0,004 sec
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,012 sec
    [junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,012 sec

    [junit] Testcase: testNaming took 0,001 sec
    [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,104 sec
    [junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
    [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,104 sec

    [junit] Testcase: testStartupWithLocatedServer took 0,064 sec
    [junit] Testcase: testStartupWithSuppliedServer took 0,011 sec
    [junit] 	Caused an ERROR
    [junit] Address already in use
    [junit] java.net.BindException: Address already in use
    [junit] 	at java.net.PlainSocketImpl.socketBind(Native Method)
    [junit] 	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
    [junit] 	at java.net.ServerSocket.bind(ServerSocket.java:318)
    [junit] 	at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
    [junit] 	at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
    [junit] 	at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
    [junit] 	at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:183)
    [junit] 	at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testStartupWithSuppliedServer(ConnectorServerFactoryBeanTests.java:65)

Last CVS updates prior to this build were:
1134065582

This is an automated mail from one of the SF Compile Farm machines.  
The machine name noted in the subject encountered a failure building
or running the Spring test suite.  The last few lines of the output
were included for info.

NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.

See http://springframework.sourceforge.net/test/ for further
information.

[Springframework-developer] spring Build Failed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051208001642

[Springframework-developer] MAIL LIST

[Victor G. <vic...@gm...>]

[Springframework-developer] spring Build Failed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051207001659

[Springframework-developer] spring Build Failed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051206001702

[Springframework-developer] Acegi Security - new release 1.0.0 RC1

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

Dear Spring Community

I'm pleased to announce that Acegi Security release 1.0.0 Release 
Candidate 1 is now available. This release includes 28 improvements and 
fixes since 0.9.0. Please visit 
http://opensource2.atlassian.com/projects/spring/secure/ReleaseNote.jspa?projectId=10040&styleName=Html&version=10252 
for a detailed changelog. Upgrade instructions (from 0.9.0 to 1.0.0) are 
included in the release ZIP file.

We recommend that users upgrade to 1.0.0 RC 1 in order to take advantage 
of the bug fixes and improvements in this release. Upgrading to 1.0.0 
will also assist us in identifying any issues as we move towards our 
final 1.0.0 release.

For those of you attending The Spring Experience in Florida, I look 
forward to seeing you in a few days' time. I'll be presenting two 
practical sessions on Acegi Security, so please come along if you'd like 
to learn more about the project or ask questions.

Please visit http://acegisecurity.org to learn more about Acegi 
Security's features, browse online documentation, or download the latest 
release.

We hope you find this new release useful in your projects.

Cheers
Ben

[Springframework-developer] spring Build Failed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051205001652

[Springframework-developer] ClassPathResource and GenericApplicationContext.setClassLoader()

[Alex A. <aar...@pi...>]

Hello,

I am having an issue with spring when I use GenericApplicationContext.  =
Even though I have used setClassLoader() prior to loading my beans, it =
seems at some point that ClassPathResource loses focus of it.

After spending some time debugging, it seems that ClassPathResource has =
a private member "classLoader" that gets set to the ClassLoader of the =
thread context.  So, even though ClassPathResource was actually loaded =
with the ClassLoader I used to override, it uses the private member =
instead.

My current brutish fix resets ClassPathResource.classLoader to =
getClass().getClassLoader() if it was indeed loaded by my classloader.  =
I do this in the constructor.

Is ClassPathResource behaving as expected here?  That is, shouldn't it =
be loaded with the ClassLoader that I set using =
GenericApplicationContext?

Best regards,
--Alex

#######DON'T REPLY TO THIS EMAIL DIRECTLY#########
sorry but I'm on my web client where I can't set my reply-to.

[Springframework-developer] spring Build Failed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051204001653

[Springframework-developer] spring Build Failed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051203001615

Re: [Springframework-developer] auto-proxying with dynamic script factories

[Rob H. <rob...@in...>]

David,

The scripting functionality is currently in an inconsistent state. I 
have been working on some modifications and a fix which will be released 
as part of the 1.3 M2/RC2 release branch. Until that time I would not 
recommend that anyone tries to use the current scripting support.

Rob

David Bowers wrote:

> I was looking at the script support in the sandbox and trying to get 
> it to work.  It looks like the structure around AutoProxy-ing has 
> changed its structure quite a bit since this sandbox code was written.
>
> In particular, the following line of code is in 
> AbstractAutowireCapableBeanFactory.createBean.  Since the scripts are 
> created using factory methods, they don't have a class, and never run 
> through the BeanPostProcessor.
>
>         // Give BeanPostProcessors a chance to return a proxy instead 
> of the target bean instance.
>         if (mergedBeanDefinition.hasBeanClass()) {
>             bean = 
> applyBeanPostProcessorsBeforeInstantiation(mergedBeanDefinition.getBeanClass(), 
> beanName);
>             if (bean != null) {
>                 return bean;
>             }
>         }
>
> Later in the same method, after the bean is instantiated, I inserted 
> the following code:
>             bean = instanceWrapper.getWrappedInstance();
>             if (!mergedBeanDefinition.hasBeanClass()) {
>                 Object altBean = 
> applyBeanPostProcessorsBeforeInstantiation(bean.getClass(), beanName);
>                 if (altBean != null) {
>                     return altBean;
>                 }
>             }
> Yes, this is a big semantic violation to call a "beforeInstantiation" 
> method *after* instantiation.  However, this, plus a few changes in 
> the sandbox, gets the Groovy support code to pass most of its tests!  
> Any ideas?
>
> Related to all this, I'm a bit surprised that the dynamic script 
> functionality has been dormant in the sandbox for so long.  Am I the 
> only one who thinks this would be a powerful feature?  Especially for 
> creating test stubs.  Are other people using scripting support with 
> Spring in different ways?


-- 
Rob Harrop
Principal Consultant
Interface21 - Spring Services from the Source
http://www.springframework.com 

[Springframework-developer] spring Build Failed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051202001637

[Springframework-developer] auto-proxying with dynamic script factories

[David B. <viv...@gm...>]

I was looking at the script support in the sandbox and trying to get it to
work.  It looks like the structure around AutoProxy-ing has changed its
structure quite a bit since this sandbox code was written.

In particular, the following line of code is in
AbstractAutowireCapableBeanFactory.createBean.  Since the scripts are
created using factory methods, they don't have a class, and never run
through the BeanPostProcessor.

        // Give BeanPostProcessors a chance to return a proxy instead of th=
e
target bean instance.
        if (mergedBeanDefinition.hasBeanClass()) {
            bean =3D applyBeanPostProcessorsBeforeInstantiation(
mergedBeanDefinition.getBeanClass(), beanName);
            if (bean !=3D null) {
                return bean;
            }
        }

Later in the same method, after the bean is instantiated, I inserted the
following code:
            bean =3D instanceWrapper.getWrappedInstance();
            if (!mergedBeanDefinition.hasBeanClass()) {
                Object altBean =3D applyBeanPostProcessorsBeforeInstantiati=
on(
bean.getClass(), beanName);
                if (altBean !=3D null) {
                    return altBean;
                }
            }
Yes, this is a big semantic violation to call a "beforeInstantiation" metho=
d
*after* instantiation.  However, this, plus a few changes in the sandbox,
gets the Groovy support code to pass most of its tests!  Any ideas?

Related to all this, I'm a bit surprised that the dynamic script
functionality has been dormant in the sandbox for so long.  Am I the only
one who thinks this would be a powerful feature?  Especially for creating
test stubs.  Are other people using scripting support with Spring in
different ways?

[Springframework-developer] spring Build Failed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051201001536

[Springframework-developer] FAILED BUILD: x86-linux2 (last 30 lines included)

[Darren D. <da...@sh...>]

1133318001
FAILED
Buildfile: build.xml

clean:
   [delete] Deleting directory /var/local/home/users/d/da/davison/checkouts/spring/target/classes
   [delete] Deleting directory /var/local/home/users/d/da/davison/checkouts/spring/target

compileattr:
[attribute-compiler] Generated attribute information for 1 classes. Ignored 0 classes.

buildmain:
    [mkdir] Created dir: /var/local/home/users/d/da/davison/checkouts/spring/target/classes
    [mkdir] Created dir: /var/local/home/users/d/da/davison/checkouts/spring/target/classes/META-INF
    [javac] Compiling 1200 source files to /var/local/home/users/d/da/davison/checkouts/spring/target/classes
    [javac] /var/local/home/users/d/da/davison/checkouts/spring/src/org/springframework/aop/support/aspectj/AspectJExpressionPointcut.java:77: <identifier> expected
    [javac] 	public AspectJExpressionPointcut(Class scope, String[] paramNames, Class<?>[] paramTypes) {
    [javac]                                                                                 ^
    [javac] /var/local/home/users/d/da/davison/checkouts/spring/src/org/springframework/aop/support/aspectj/AspectJExpressionPointcut.java:180: ')' expected
    [javac] }
    [javac] ^
    [javac] 2 errors
Last CVS updates prior to this build were:
1133316781
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml

This is an automated mail from one of the SF Compile Farm machines.  
The machine name noted in the subject encountered a failure building
or running the Spring test suite.  The last few lines of the output
were included for info.

NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.

See http://springframework.sourceforge.net/test/ for further
information.

Re: [Springframework-developer] typo

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

Michael,

thanks for spotting this. Fixed in CVS.

Dmitriy.


On Nov 29, 2005, at 6:17 PM, Michael E. Moores wrote:

> small type in section 18.3.2, should be "Chapter 8", right?
>
>
>      18.3.2. Transaction Management
>
> Spring provides a JmsTransactionManager that manages transactions  
> for a single JMS ConnectionFactory. This allows JMS applications to  
> leverage the managed transaction features of Spring as described in  
> Chapter 7
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through  
> log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD  
> SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] spring Build Failed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051130001623

[Springframework-developer] typo

[Michael E. M. <mm...@re...>]

small type in section 18.3.2, should be "Chapter 8", right?


      18.3.2. Transaction Management

Spring provides a JmsTransactionManager that manages transactions for a 
single JMS ConnectionFactory. This allows JMS applications to leverage 
the managed transaction features of Spring as described in Chapter 7

[Springframework-developer] spring build.381 Build Fixed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051129001648Lbuild.381

[Springframework-developer] spring Build Failed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051128001704

[Springframework-developer] spring build.380 Build Fixed

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

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051127001702Lbuild.380