springframework-developer — Spring Framework developers list

Re: [Springframework-developer] DispatcherServlet - no mapping found

[Rod J. <rod...@in...>]

Trevor,

Sounds reasonable. I'm happy for you to change it.

Regards,
Rod

----- Original Message ----- 
From: "Trevor Cook" <pr...@se...>
To: "Spring Developers" <spr...@li...>
Sent: Saturday, September 27, 2003 7:21 PM
Subject: [Springframework-developer] DispatcherServlet - no mapping found


> I have a bit of a problem with the DispatcherServlet's doService method,
> specifically:
>
> if (mappedHandler == null || mappedHandler.getHandler() == null) {
> // if we didn't find a handler
> logger.error("No mapping for [" + WebUtils.getRequestUri(request) + "] in
> DispatcherServlet with name '" + getServletName() + "'");
> response.sendError(HttpServletResponse.SC_NOT_FOUND);
> return;
> }
>
> I think the 404 is fine (I noticed the previous thread for multiaction on
> this - see
http://sourceforge.net/mailarchive/message.php?msg_id=5986871).
> My problem is "logger.error".  I have log4j send me anything above info
for
> my code, and anything error/fatal for Spring.  Because of this, I am
> currently getting dozens of emails a day from spiders, spelling errors,
and
> 1 site that refuses to change a bad link on their page.   I considered
just
> changing my logging to only report fatal errors from Spring, but Spring
> doesn't have any, and other errors it reports are important (like
> transaction and configuration problems).  I'd like to change this from
error
> to warn.  "warn" is defined as:
>
> <quote>other runtime situations that are undesirable or unexpected, but
not
> necessarily "wrong".</quote> see
> http://jakarta.apache.org/commons/logging/userguide.html
>
> I think that a 404 is not a desirable thing, but is fairly normal for a
> webapp, so falls under the "not wrong" category.
>
> Let me know if there is general support for lowering the logging level of
> this message, or if I'm totally out to lunch.
>
> Trevor D. Cook
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

[Springframework-developer] DispatcherServlet - no mapping found

[Trevor C. <pr...@se...>]

I have a bit of a problem with the DispatcherServlet's doService method,
specifically:

		if (mappedHandler == null || mappedHandler.getHandler() == null) {
			// if we didn't find a handler
			logger.error("No mapping for [" + WebUtils.getRequestUri(request) + "] in
DispatcherServlet with name '" + getServletName() + "'");
			response.sendError(HttpServletResponse.SC_NOT_FOUND);
			return;
		}

I think the 404 is fine (I noticed the previous thread for multiaction on
this - see  http://sourceforge.net/mailarchive/message.php?msg_id=5986871).
My problem is "logger.error".  I have log4j send me anything above info for
my code, and anything error/fatal for Spring.  Because of this, I am
currently getting dozens of emails a day from spiders, spelling errors, and
1 site that refuses to change a bad link on their page.   I considered just
changing my logging to only report fatal errors from Spring, but Spring
doesn't have any, and other errors it reports are important (like
transaction and configuration problems).  I'd like to change this from error
to warn.  "warn" is defined as:

<quote>other runtime situations that are undesirable or unexpected, but not
necessarily "wrong".</quote> see
http://jakarta.apache.org/commons/logging/userguide.html

I think that a 404 is not a desirable thing, but is fairly normal for a
webapp, so falls under the "not wrong" category.

Let me know if there is general support for lowering the logging level of
this message, or if I'm totally out to lunch.

Trevor D. Cook

[Springframework-developer] RequestContextAwareTag / RequestContext commited

[Trevor C. <pr...@se...>]

I have commited the previously mentioned changes.

RequestContextAwareTag.doStartTagInternal is no longer abstract, and returns
super.doStartTag() by default.

RequestContext now contains a convenience method for getMessage(String).

Finally, a little warning/gotcha I noticed.  When upgrading our tags from
extending com.interface21.web.tags.TagInWebApplicationContext to
org.springframework.web.servlet.tags.RequestContextAwareTag, I found a
problem.  Our tags returned super.doStartTag().  While this works normally
when extending TagSupport and used to work in Spring, the new method with
"doStartTagInternal" means that you end up with an infinite loop.  Just FYI.

Trevor D. Cook

[Springframework-developer] Multipart File Handling

[Trevor C. <pr...@se...>]

First some history:
http://sourceforge.net/mailarchive/message.php?msg_id=3891279
http://sourceforge.net/mailarchive/message.php?msg_id=5175276
http://sourceforge.net/mailarchive/forum.php?thread_id=3125561&forum_id=3028
7
http://sourceforge.net/mailarchive/message.php?msg_id=6062288

To address a few things Juergen mentioned previously.

>> a less intrusive way would be to wrap the HttpServletRequest via a filter
I personally don't like the filter approach, at least for the framework.  It
requires additional setup for the user (in the web.xml file) and might be
less understandable since our normal strategy so far has been with resolvers
inside the servlet.

>>we would need to find concrete requirements for this
We have numerous uses for file upload handling.  We have a public photo
contest where users can upload fotos.  We have special access for suppliers
to upload product files (csv) which we then add in to our ordering system.
Finally, we have a web administration interface which allows our client to
upload files to the website so they can be downloaded.  I think that
including this support (multipart handling) is a no-brainer.

Basically, I have used COS exclusively in our projects, but I don't think
that's easy for Spring to use (due to the licensing).  I would simply code
this according to Spring norms using an interface and a default version
using Commons FileUpload.  Later, if somebody wants to create a cos version
we can (but to be honest, if we have a working, integrated solution I'm not
sure that is necessary - at least not in the Spring framework).  Basically,
provide hooks and a default implementation, and allow users to adopt as
necessary.

In our project we had modified the AbstractController and put the code into
it to handle the multipart processing, returning a wrapped
HttpServletRequest through the handlers.  This is very similiar to Juergen's
outline (http://sourceforge.net/mailarchive/message.php?msg_id=3891279).

Since we are migrating to the current Spring codebase, I need to move our
multipart handling code.  The main question is whether we keep it
internally, or place it into Spring.  I propose modifying
org.springframework.web.servlet.DispatcherServlet to have a
"MultipartResolver".  In the DispatcherServlet, the resolver would be called
to wrap the request in doService immediately before getHandler(request) -
currently line 351, and then called to do any cleanup immediately before
exiting the doService method.

I have about 2/3 of the code already written, and I will be writing the rest
between now and Monday.  Does this strategy sound appropriate for Spring
(meaning should I commit it to the Spring codebase) when it's finished?

Trevor D. Cook
Interprise Software

[Springframework-developer] JDBC core tests

[Trevor C. <pr...@se...>]

Just an FYI that I will NOT be working on the JDBC core tests, at least for
a week or so.  We are currently porting our app to the new (cvs) version of
Spring, and there is a bunch of changes required.  This is mainly in case
anyone is waiting for me before touching the JDBC packages, feel free to do
it.

The good news is that there is some additional functionality we should be
able to add back into Spring (but I'll cover that in other threads).

Trevor D. Cook

[Springframework-developer] Sequence diagrams

[Kopylenko, D. <dko...@ac...>]

Hello everybody,

I'm thinking it would be useful to have UML sequence diagrams for different
parts of framework (processes) i.e "BeanFactory bootstrap process", "AOP
interception process", "MVC framework request/response round trip" etc. Can
anyone try to produce it?

Dmitriy. 

RE: [Springframework-developer] setApplicationContext() not called on Singletons???

[Alef A. \(JTeam\) <al...@jt...>]

Thanks!

There is something in the JavaDoc, but it doesn't explicitly state the
applicationcontext isn't set yet... Maybe we should have state-like
diagrams or a on page description of  the lifecycle of a bean bean in
the container when using the different callback interfaces available...

Alef


-----Oorspronkelijk bericht-----
Van: spr...@li...
[mailto:spr...@li...] Namens
Rod Johnson
Verzonden: Wednesday, September 24, 2003 9:22 PM
Aan: al...@jt...; spr...@li...
Onderwerp: Re: [Springframework-developer] setApplicationContext() not
called on Singletons???



> Ok, I admit, I didn't think hard enough ;-)
>
> afterPropertiesSet() is called after all properties are set.
> setApplicationContext() is called when getting a bean from the 
> Context.
>
> So I'm basically not allowed to do anything related to the 
> ApplicationContext in my afterPropertiesSet() method???

Yes. Sorry I didn't remember and point this out earlier. Configuring the
ApplicationContext layer is a later stage of configuration than
configuring the BeanFactory layer. We should document this more
prominently though. (I seem to remember putting something in Javadocs).
So if you do everything that depends on the AppContext is
setApplicationContext() you should be OK.




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] RequestContext.getMessage(String)

[Rod J. <rod...@in...>]

I think this is worth adding.

R
----- Original Message ----- 
From: "Alef Arendsen (JTeam)" <al...@jt...>
To: "'Trevor Cook'" <pr...@se...>; "'Spring Developers'"
<spr...@li...>
Sent: Wednesday, September 24, 2003 10:09 PM
Subject: RE: [Springframework-developer] RequestContext.getMessage(String)


> Although I'm not really a big fan of convenience methods, this sounds
> like a reasonable one...
>
> Alef
>
>
> -----Oorspronkelijk bericht-----
> Van: spr...@li...
> [mailto:spr...@li...] Namens
> Trevor Cook
> Verzonden: Wednesday, September 24, 2003 9:56 PM
> Aan: Spring Developers
> Onderwerp: [Springframework-developer] RequestContext.getMessage(String)
>
>
> I have finally received permission to migrate our major Spring project
> from our snapshot (modified 0.8 from March) and started the conversion
> this afternoon.  So far pretty smooth, and I'm really impressed with
> some of the design changes I'm seeing now that I haven't had a chance to
> before.  Good work guys!
>
> With that in mind, I am noticing a few minor items, and I'll post as I
> find any that I think are important enough to change.
>
> The first is adding a convenience method to
> org.springframework.web.servlet.support.RequestContext for
> "getMessage(String)".  The same effect can be achieved by calling the
> "getMessage(String, Object[])" method with null (it's documented :) ),
> however I think the cleaner code with a utility method is worth adding
> it. The convenience method implementation would be:
>
> return getMessage(code, null, this.defaultHtmlEscape);
>
> I can commit this unless there are any major objections.
>
> Trevor D. Cook
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

RE: [Springframework-developer] RequestContext.getMessage(String)

[Alef A. \(JTeam\) <al...@jt...>]

Although I'm not really a big fan of convenience methods, this sounds
like a reasonable one...

Alef


-----Oorspronkelijk bericht-----
Van: spr...@li...
[mailto:spr...@li...] Namens
Trevor Cook
Verzonden: Wednesday, September 24, 2003 9:56 PM
Aan: Spring Developers
Onderwerp: [Springframework-developer] RequestContext.getMessage(String)


I have finally received permission to migrate our major Spring project
from our snapshot (modified 0.8 from March) and started the conversion
this afternoon.  So far pretty smooth, and I'm really impressed with
some of the design changes I'm seeing now that I haven't had a chance to
before.  Good work guys!

With that in mind, I am noticing a few minor items, and I'll post as I
find any that I think are important enough to change.

The first is adding a convenience method to
org.springframework.web.servlet.support.RequestContext for
"getMessage(String)".  The same effect can be achieved by calling the
"getMessage(String, Object[])" method with null (it's documented :) ),
however I think the cleaner code with a utility method is worth adding
it. The convenience method implementation would be:

		return getMessage(code, null, this.defaultHtmlEscape);

I can commit this unless there are any major objections.

Trevor D. Cook



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

RE: [Springframework-developer] org.springframework.web.servlet.tags.RequestContextAwareTag

[Alef A. \(JTeam\) <al...@jt...>]

+1

Should not be abstract indeed!

-----Oorspronkelijk bericht-----
Van: spr...@li...
[mailto:spr...@li...] Namens
Trevor Cook
Verzonden: Wednesday, September 24, 2003 10:16 PM
Aan: Spring Developers
Onderwerp: [Springframework-developer]
org.springframework.web.servlet.tags.RequestContextAwareTag


Is there a specific reason that "doStartTagInternal" is abstract.  You
are not required to have a "doStart", so you can place your code in the
"doEnd" method (some of my tags do).  A more reusable solution would be
to have the
following:

	protected int doStartTagInternal() throws Exception {
		return super().doStartTag();
	}

which could still be overridden by subclasses but does not require an
implementation (and will function according to spec without one).

Again, I can commit this unless there are any major objections.

Trevor



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] org.springframework.web.servlet.tags.RequestContextAwareTag

[Trevor C. <pr...@se...>]

Is there a specific reason that "doStartTagInternal" is abstract.  You are
not required to have a "doStart", so you can place your code in the "doEnd"
method (some of my tags do).  A more reusable solution would be to have the
following:

	protected int doStartTagInternal() throws Exception {
		return super().doStartTag();
	}

which could still be overridden by subclasses but does not require an
implementation (and will function according to spec without one).

Again, I can commit this unless there are any major objections.

Trevor

[Springframework-developer] RequestContext.getMessage(String)

[Trevor C. <pr...@se...>]

I have finally received permission to migrate our major Spring project from
our snapshot (modified 0.8 from March) and started the conversion this
afternoon.  So far pretty smooth, and I'm really impressed with some of the
design changes I'm seeing now that I haven't had a chance to before.  Good
work guys!

With that in mind, I am noticing a few minor items, and I'll post as I find
any that I think are important enough to change.

The first is adding a convenience method to
org.springframework.web.servlet.support.RequestContext for
"getMessage(String)".  The same effect can be achieved by calling the
"getMessage(String, Object[])" method with null (it's documented :) ),
however I think the cleaner code with a utility method is worth adding it.
The convenience method implementation would be:

		return getMessage(code, null, this.defaultHtmlEscape);

I can commit this unless there are any major objections.

Trevor D. Cook

Re: [Springframework-developer] setApplicationContext() not called on Singletons???

[Rod J. <rod...@in...>]

> Ok, I admit, I didn't think hard enough ;-)
>
> afterPropertiesSet() is called after all properties are set.
> setApplicationContext() is called when getting a bean from the Context.
>
> So I'm basically not allowed to do anything related to the
> ApplicationContext in my afterPropertiesSet() method???

Yes. Sorry I didn't remember and point this out earlier. Configuring the
ApplicationContext layer is a later stage of configuration than configuring
the BeanFactory layer. We should document this more prominently though. (I
seem to remember putting something in Javadocs). So if you do everything
that depends on the AppContext is setApplicationContext() you should be OK.

RE: [Springframework-developer] setApplicationContext() not called on Singletons???

[Alef A. \(JTeam\) <al...@jt...>]

Ok, I admit, I didn't think hard enough ;-)

afterPropertiesSet() is called after all properties are set.
setApplicationContext() is called when getting a bean from the Context.

So I'm basically not allowed to do anything related to the
ApplicationContext in my afterPropertiesSet() method???

Thanks for any help!

Alef

RE: [Springframework-developer] TransactionInterceptor setup in t he webapp-aop skeleton file is bad

[Kopylenko, D. <dko...@ac...>]

Thanks Colin.

Dmitriy.

-----Original Message-----
From: Colin Sampaleanu [mailto:col...@ex...] 
Sent: Wednesday, September 24, 2003 12:04 PM
To: Kopylenko, Dmitry; spr...@li...
Subject: Re: [Springframework-developer] TransactionInterceptor setup in t
he webapp-aop skeleton file is bad


Dmitry,

I just noticed that your update is not correct. You changed the 
'proxyInterfaces' value in the ProxyFactoryBean use to be the name of 
the business impl class name.

What should in fact have been changed is in the TransactionInterceptor 
parameter 'transactionAttributeSource', the use of the business 
interface name instead of the business impl class name.

So I have changed bad the proxyInterfaces value to be the business 
interface name, and modified the transactionAttributeSource to use the 
interface as well.

I have not touched your other modification, to add an example of the use 
of TransactionProxyFactoryBean...

Regards,
Colin



Kopylenko, Dmitry wrote:

>Colin,
>
>I'll update it in the CVS.
>
>Regards,
>Dmitriy.
>
>-----Original Message-----
>From: Colin Sampaleanu [mailto:col...@ex...]
>Sent: Wednesday, September 03, 2003 6:35 PM
>To: 'springframework-developer '
>Cc: ben...@ac...
>Subject: [Springframework-developer] TransactionInterceptor setup in the
>webapp-aop skeleton file is bad
>
>
>In the file
>  samples/skeletons/webapp-aop/WEB-INF/applicationContext.xml
>there is an example of how to set up a transaction interceptor. It is
>using the old mechanism, which is not the problem, but is wrong, which 
>is the problem.
>
>The example uses
>    <bean id="exampleTransactionInterceptor"
>class="org.springframework.transaction.interceptor.TransactionInterceptor">
>        <property name="transactionManager"><ref 
>bean="myTransactionManager"/></property>
>        <property name="transactionAttributeSource">
>            <value>
>                
>example.ExampleBusinessObject.exampleMethod=PROPAGATION_REQUIRED
>                
>example.ExampleBusinessObject.anotherExampleMethod=PROPAGATION_REQUIRED
>            </value>
>        </property>
>    </bean>
>    <bean id="exampleBusinessObject"
>class="org.springframework.aop.framework.ProxyFactoryBean">
>        <property 
>name="proxyInterfaces"><value>example.ExampleBusinessInterface</value></pro
p
>erty>
>        <property
>name="interceptorNames"><value>exampleTransactionInterceptor,exampleBusines
s
>ObjectTarget</value></property>
>    </bean>
>
>Now this is specifyng that ExampleBusinessObject.exmpleMethod and
>ExampleBuisnessObject.anotherExampleMethod should be intercepted and 
>handled transactionally, but if the user comes in via the interface 
>ExampleBusinessInterface like he should be, then the interceptor will 
>not match up on the method names, since the class he is coming in as is 
>ExampleBusinessInterface not the ExampleBusinessObject the interceptor 
>is looking for.
>
>This is the exact problem that Ben Alex was having last week (but I
>didn't spot it at the time). Hopefully he didn't give up on spring yet :-)
>
>Can somebody fix this?  Also, fwiw this doesn't happen with the new,
>streamlined mechanism, TransactionProxyFactoryBean, since there you 
>directly point to the object you are proxying, and match the method 
>coming in regardless.
>
>Also, it's probably worth updating the example to show both the old
>mechanism and the new one.
>
>Regards,
>Colin
>  
>

Re: [Springframework-developer] TransactionInterceptor setup in t he webapp-aop skeleton file is bad

[Colin S. <col...@ex...>]

Dmitry,

I just noticed that your update is not correct. You changed the 
'proxyInterfaces' value in the ProxyFactoryBean use to be the name of 
the business impl class name.

What should in fact have been changed is in the TransactionInterceptor 
parameter 'transactionAttributeSource', the use of the business 
interface name instead of the business impl class name.

So I have changed bad the proxyInterfaces value to be the business 
interface name, and modified the transactionAttributeSource to use the 
interface as well.

I have not touched your other modification, to add an example of the use 
of TransactionProxyFactoryBean...

Regards,
Colin



Kopylenko, Dmitry wrote:

>Colin,
>
>I'll update it in the CVS.
>
>Regards,
>Dmitriy.
>
>-----Original Message-----
>From: Colin Sampaleanu [mailto:col...@ex...] 
>Sent: Wednesday, September 03, 2003 6:35 PM
>To: 'springframework-developer '
>Cc: ben...@ac...
>Subject: [Springframework-developer] TransactionInterceptor setup in the
>webapp-aop skeleton file is bad
>
>
>In the file
>  samples/skeletons/webapp-aop/WEB-INF/applicationContext.xml
>there is an example of how to set up a transaction interceptor. It is 
>using the old mechanism, which is not the problem, but is wrong, which 
>is the problem.
>
>The example uses
>    <bean id="exampleTransactionInterceptor" 
>class="org.springframework.transaction.interceptor.TransactionInterceptor">
>        <property name="transactionManager"><ref 
>bean="myTransactionManager"/></property>
>        <property name="transactionAttributeSource">
>            <value>
>                
>example.ExampleBusinessObject.exampleMethod=PROPAGATION_REQUIRED
>                
>example.ExampleBusinessObject.anotherExampleMethod=PROPAGATION_REQUIRED
>            </value>
>        </property>
>    </bean>
>    <bean id="exampleBusinessObject" 
>class="org.springframework.aop.framework.ProxyFactoryBean">
>        <property 
>name="proxyInterfaces"><value>example.ExampleBusinessInterface</value></prop
>erty>
>        <property 
>name="interceptorNames"><value>exampleTransactionInterceptor,exampleBusiness
>ObjectTarget</value></property>
>    </bean>
>
>Now this is specifyng that ExampleBusinessObject.exmpleMethod and 
>ExampleBuisnessObject.anotherExampleMethod should be intercepted and 
>handled transactionally, but if the user comes in via the interface 
>ExampleBusinessInterface like he should be, then the interceptor will 
>not match up on the method names, since the class he is coming in as is 
>ExampleBusinessInterface not the ExampleBusinessObject the interceptor 
>is looking for.
>
>This is the exact problem that Ben Alex was having last week (but I 
>didn't spot it at the time). Hopefully he didn't give up on spring yet :-)
>
>Can somebody fix this?  Also, fwiw this doesn't happen with the new, 
>streamlined mechanism, TransactionProxyFactoryBean, since there you 
>directly point to the object you are proxying, and match the method 
>coming in regardless.
>
>Also, it's probably worth updating the example to show both the old 
>mechanism and the new one.
>
>Regards,
>Colin
>  
>

Re: [Springframework-developer] Spring scheduler?

[Ivan R. <iv...@we...>]

Kopylenko, Dmitry wrote:
> Perhaps SpringSchedulerHelper should not implement Scheduler,
 > but use it as underlying strategy ?

   Implementation is only formal, calls to methods from
   the Scheduler interface would be forwarded to the underlying
   strategy object. The benefit of this is that you only
   need to concern yourself with one object reference (when
   you are using a scheduler).

-- 
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]

RE: [Springframework-developer] Spring scheduler?

[Kopylenko, D. <dko...@ac...>]

Perhaps SpringSchedulerHelper should not implement Scheduler, but use =
it as
underlying strategy ?

Regards,
Dmitriy.

-----Original Message-----
From: Ivan Ristic [mailto:iv...@we...]=20
Sent: Wednesday, September 24, 2003 10:28 AM
To: "j=FCrgen h=F6ller [werk3AT]"
Cc: Kopylenko, Dmitry; al...@jt...; Colin Sampaleanu;
spr...@li...
Subject: Re: [Springframework-developer] Spring scheduler?


j=FCrgen h=F6ller [werk3AT] wrote:
> On related terms, I'll work on J2EE integration for SBB's UC4
 > job scheduling system in October. There is definitely a lot of
> overlap here, and the big plus that SBB have agreed to define common=20
> parts and interfaces as open source project a la AOP Alliance. =
Generic=20
> interfaces and definitions for implementing jobs, and implementations =

> for UC4 via JCA/JMS and for Spring in a bean factory style... sounds=20
> interesting to me :-) Additionally, SBB have good relations with SAP=20
> and the makers of Flux, so there should be plenty of feedback and=20
> chances for future developments.

   That's very good news. As far as I am concerned we can wait for
   that, especially since I moved my scheduler-related project
   for early next year.

   However, I did put some work toward this since our last email
   exchange and would like to proceed (slowly, as you can see)
   with it:

   I have reviewed Quartz and, now that I've invested time to learn
   how it works, I have no real desire to create a new scheduling
   library. I still find it too complex, though, but nothing is
   perfect. Therefore I am proposing what someone else proposed
   before, to create a simple Quartz wrapper.

   I also looked at the J2EE timer service and found it too
   simplistic. There is an interesting article on the subject:

=20
http://www2.theserverside.com/resources/article.jsp?l=3DMonsonHaefel-Col=
umn4

   I've tried to create a very simple (as simple as it can be) =
scheduling
   wrapper and this is what I've come up with:

-------------------------

public interface Scheduler {
     // schedule is cron-like scheduling formula
     public int createTask(String schedule, Runnable runnable);
     public boolean removeTask(int taskid);
}

public class SpringSchedulerHelper implements Scheduler {
     public int createTask(String schedule, String bean);
     public int createTask(String schedule, String bean, String =
method);
     public int createTask(String schedule, String bean, String method, =

String[] args);

     // these two are not specific to Spring, actually=09
     public int createTask(String schedule, Object instance, Method m);
     public int createTask(String schedule, Object instance, Method m,=20
Object[] args);
=09
     public int createTask(String schedule, ApplicationEvent event);

     // perhaps more createTask methods here

     // scheduler implementation set at runtime
     public void setScheduler(Scheduler scheduler);
     public void getScheduler();
}

public class SpringTaskWrapper implements Runnable {
     // todo ...
}

--=20
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]

Re: [Springframework-developer] Spring scheduler?

[Ivan R. <iv...@we...>]

jürgen höller [werk3AT] wrote:
> On related terms, I'll work on J2EE integration for SBB's UC4
 > job scheduling system in October. There is definitely a lot of
> overlap here, and the big plus that SBB have agreed to define common
> parts and interfaces as open source project a la AOP Alliance. Generic
> interfaces and definitions for implementing jobs, and implementations
> for UC4 via JCA/JMS and for Spring in a bean factory style... sounds
> interesting to me :-) Additionally, SBB have good relations with SAP
> and the makers of Flux, so there should be plenty of feedback and
> chances for future developments.

   That's very good news. As far as I am concerned we can wait for
   that, especially since I moved my scheduler-related project
   for early next year.

   However, I did put some work toward this since our last email
   exchange and would like to proceed (slowly, as you can see)
   with it:

   I have reviewed Quartz and, now that I've invested time to learn
   how it works, I have no real desire to create a new scheduling
   library. I still find it too complex, though, but nothing is
   perfect. Therefore I am proposing what someone else proposed
   before, to create a simple Quartz wrapper.

   I also looked at the J2EE timer service and found it too
   simplistic. There is an interesting article on the subject:

   http://www2.theserverside.com/resources/article.jsp?l=MonsonHaefel-Column4

   I've tried to create a very simple (as simple as it can be) scheduling
   wrapper and this is what I've come up with:

-------------------------

public interface Scheduler {
     // schedule is cron-like scheduling formula
     public int createTask(String schedule, Runnable runnable);
     public boolean removeTask(int taskid);
}

public class SpringSchedulerHelper implements Scheduler {
     public int createTask(String schedule, String bean);
     public int createTask(String schedule, String bean, String method);
     public int createTask(String schedule, String bean, String method, 
String[] args);

     // these two are not specific to Spring, actually	
     public int createTask(String schedule, Object instance, Method m);
     public int createTask(String schedule, Object instance, Method m, 
Object[] args);
	
     public int createTask(String schedule, ApplicationEvent event);

     // perhaps more createTask methods here

     // scheduler implementation set at runtime
     public void setScheduler(Scheduler scheduler);
     public void getScheduler();
}

public class SpringTaskWrapper implements Runnable {
     // todo ...
}

-- 
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]

RE: [Springframework-developer] setApplicationContext() not called on Singletons???

[Alef A. \(JTeam\) <al...@jt...>]

I've had another look at it and __moved__ the dataControllerSupport bean
to the applicationContext, while the formContrller still resides in the
web-app-ctx. This fixes the problem, however, I still think,
resolveReferences, calling getBeanInternal, should also call
setApplicationContext() when creating a shared instance!

Alef


-----Oorspronkelijk bericht-----
Van: spr...@li...
[mailto:spr...@li...] Namens
Alef Arendsen (JTeam)
Verzonden: Wednesday, September 24, 2003 1:05 PM
Aan: spr...@li...
Onderwerp: [Springframework-developer] setApplicationContext() not
called on Singletons???


Hi all,

I've been spending like an hour on it, but can't find it:

I've got a bean (dataControllerSupport) defined which is referenced from
another bean (accountFormController), via <ref bean>. When the second
bean is loaded, it received the bean it's depending on. After that,
afterPropertiesSet() is called (on accountFormController), in which I'm
using the dataControllerSupport bean to resolve some things for me. The
dataControllerSupport bean needs the applicationcontext and therefore,
is ApplicationContext Aware. Hwoever, it does NOT have the application
context set!!! I've been investigating a while and really think
somewhere there's a flaw (using latest CVS code).

You can find the context (parts of it) below. Also, there some output...

The two beans...
	<bean id="dataControllerSupport"
class="jteam.web.controller.DataControllerSupport">
		<property name="addExtension">
			<value>add</value>
		</property>
		<property name="editExtension">
			<value>edit</value>
		</property>
		<property name="detailsViewPrefix">
			<value>details.</value>
		</property>
		<property name="listViewPrefix">
			<value>list.</value>
		</property>
		<property name="formViewPrefix">
			<value>form.</value>
		</property>
		<property name="recordHelperClass">
	
<value>jteam.jbosssupport.data.RecordHelper</value>
		</property>
		<property name="propertyEditorsFactory">
			<ref bean="propertyEditorsFactory"/>
		</property>
	</bean>
	<bean id="accountFormController"
class="jteam.web.controller.DataFormController">
    	<property name="dataControllerSupport">
    		<ref bean="dataControllerSupport"/>
    	</property>
        <property name="objectType">
            <value>Account</value>
        </property>
        <property name="sessionForm">
            <value>true</value>
        </property>
        <property name="bindOnNewForm">
            <value>true</value>
        </property>
        <property name="dataHelper">
            <ref external="accountHelper"/>
        </property>
        <property name="validator"><ref
bean="recordValidator"></ref></property>
        <property name="referenceData">
            <map>
                <entry key="billingAddress.country">
                    <ref external="countries"/>
                </entry>
                <entry key="companyAddress.country">
                    <ref external="countries"/>
                </entry>
            </map>
        </property>
    </bean>

The output I'm receiving when the dataControllerSupport is instantiated
(it's a Thread.dumpStack()). I've put some output at the places where
the applicationcontext is __supposed__ to be set, but it's not
outputting anything. Also, in the AbstractBeanFactory class, when
resolving references, I can't find any calls to setApplicationContext()
being done, however, afterPropertiesSet() on the depending bean _IS_
called, in which I'm relying on setApplicationContext() on the second
bean being called!!!

Anybody???

[XmlWebApplicationContext] 42 beans defined in ApplicationContext
[WebApplicationContext for namespace 'jbosssupport-servlet']
[XmlWebApplicationContext] ******* Retrieving bean contextOptions
[XmlWebApplicationContext] ******* Retrieving bean contextOptions
[XmlWebApplicationContext] No options bean ("contextOptions") found:
using default [XmlWebApplicationContext] ******* Retrieving bean
messageSource [XmlWebApplicationContext] ******* Retrieving bean
messageSource [XmlWebApplicationContext] ******* Going to see if I need
to set the context on messageSource [XmlWebApplicationContext] *******
No, NOT DOING IT! [XmlWebApplicationContext] ******* Going to see if I
need to set the context on messageSource [XmlWebApplicationContext]
******* No, NOT DOING IT! [XmlWebApplicationContext] ******* Retrieving
bean themeSource [XmlWebApplicationContext] ******* Retrieving bean
themeSource [UiApplicationContextUtils] No ThemeSource found for
[WebApplicationContext for namespace 'jbosssupport-servlet']: using
ResourceBundleThemeSour [XmlWebApplicationContext] Refreshing listeners
[XmlWebApplicationContext] Configuring singleton beans in context
[XmlWebApplicationContext] ******* Retrieving bean
contractViewController [XmlBeanFactory] Creating shared instance of
singleton bean 'contractViewController' [XmlBeanFactory] Creating shared
instance of singleton bean 'dataControllerSupport'
[DataControllerSupport] DataControllerSupport instantantiated [STDERR]
java.lang.Exception: Stack trace
[STDERR]     at java.lang.Thread.dumpStack(Thread.java:1071)
[STDERR]     at
jteam.web.controller.DataControllerSupport.<init>(DataControllerSupport.
java:83)
[STDERR]     at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[STDERR]     at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA
ccessorImpl.java:39)
[STDERR]     at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons
tructorAccessorImpl.java:27)
[STDERR]     at
java.lang.reflect.Constructor.newInstance(Constructor.java:274)
[STDERR]     at java.lang.Class.newInstance0(Class.java:306)
[STDERR]     at java.lang.Class.newInstance(Class.java:259)
[STDERR]     at
org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:26)
[STDERR]     at
org.springframework.beans.BeanWrapperImpl.<init>(BeanWrapperImpl.java:16
5)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.createBean
(AbstractBeanFactory.java:295)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.getSharedI
nstance(AbstractBeanFactory.java:233)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.getBeanInt
ernal(AbstractBeanFactory.java:162)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveRef
erence(AbstractBeanFactory.java:447)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveVal
ueIfNecessary(AbstractBeanFactory.java:403)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.applyPrope
rtyValues(AbstractBeanFactory.java:367)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.createBean
(AbstractBeanFactory.java:319)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.getSharedI
nstance(AbstractBeanFactory.java:233)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.getBeanInt
ernal(AbstractBeanFactory.java:162)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(Ab
stractBeanFactory.java:140)
[STDERR]     at
org.springframework.context.support.AbstractApplicationContext.getBean(A
bstractApplicationContext.java:453)
[STDERR]     at
org.springframework.context.support.AbstractApplicationContext.preInstan
tiateSingletons(AbstractApplicationContext.java:303)
[STDERR]     at
org.springframework.context.support.AbstractApplicationContext.refresh(A
bstractApplicationContext.java:229)
[STDERR]     at
org.springframework.web.context.support.XmlWebApplicationContext.setServ
letContext(XmlWebApplicationContext.java:121)
[STDERR]     at
org.springframework.web.servlet.FrameworkServlet.createWebApplicationCon
text(FrameworkServlet.java:167)
[STDERR]     at
org.springframework.web.servlet.FrameworkServlet.initServletBean(Framewo
rkServlet.java:146)
[STDERR]     at
org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.jav
a:82)
[STDERR]     at
javax.servlet.GenericServlet.init(GenericServlet.java:256)
[STDERR]     at
org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:219)
[STDERR]     at
org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandl
er.java:436)
[STDERR]     at
org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebAp
plicationHandler.java:150)
[STDERR]     at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationCont
ext.java:440)
[STDERR]     at
org.mortbay.j2ee.J2EEWebApplicationContext.start(J2EEWebApplicationConte
xt.java:85)
[STDERR]     at
org.jboss.jetty.JBossWebApplicationContext.start(JBossWebApplicationCont
ext.java:89)
[STDERR]     at org.jboss.jetty.Jetty.deploy(Jetty.java:331)
[STDERR]     at
org.jboss.jetty.JettyService.performDeploy(JettyService.java:242)
[STDERR]     at
org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:399)
[STDERR]     at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:822)
[STDERR]     at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
[STDERR]     at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:630)
[STDERR]     at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:603)
[STDERR]     at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown
Source)
[STDERR]     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
[STDERR]     at java.lang.reflect.Method.invoke(Method.java:324)
[STDERR]     at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
spatcher.java:284)
[STDERR]     at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
[STDERR]     at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
[STDERR]     at $Proxy7.deploy(Unknown Source)
[STDERR]     at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentSc
anner.java:302)
[STDERR]     at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScan
ner.java:476)
[STDERR]     at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doS
can(AbstractDeploymentScanner.java:200)
[STDERR]     at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abst
ractDeploymentScanner.java:273)
[STDERR]     at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
[STDERR]     at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown
Source)
[STDERR]     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
[STDERR]     at java.lang.reflect.Method.invoke(Method.java:324)
[STDERR]     at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
spatcher.java:284)
[STDERR]     at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
[STDERR]     at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController
.java:966)
[STDERR]     at $Proxy0.start(Unknown Source)
[STDERR]     at
org.jboss.system.ServiceController.start(ServiceController.java:392)
[STDERR]     at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown
Source)
[STDERR]     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
[STDERR]     at java.lang.reflect.Method.invoke(Method.java:324)
[STDERR]     at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
spatcher.java:284)
[STDERR]     at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
[STDERR]     at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
[STDERR]     at $Proxy5.start(Unknown Source)
[STDERR]     at
org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
[STDERR]     at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:822)
[STDERR]     at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:630)
[STDERR]     at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:603)
[STDERR]     at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:587)
[STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[STDERR]     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
[STDERR]     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
[STDERR]     at java.lang.reflect.Method.invoke(Method.java:324)
[STDERR]     at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
spatcher.java:284)
[STDERR]     at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
[STDERR]     at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
[STDERR]     at $Proxy6.deploy(Unknown Source)
[STDERR]     at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:365)
[STDERR]     at
org.jboss.system.server.ServerImpl.start(ServerImpl.java:272)
[STDERR]     at org.jboss.Main.boot(Main.java:150)
[STDERR]     at org.jboss.Main$1.run(Main.java:388)
[STDERR]     at java.lang.Thread.run(Thread.java:536)
[XmlBeanFactory] Creating shared instance of singleton bean
'propertyEditorsFactory' [XmlWebApplicationContext] ******* Going to see
if I need to set the context on contractViewController
[XmlWebApplicationContext] ******* Yes, doing it! [RecordController]
Setting application context ApplicationContext:
displayName=[WebApplicationContext for namespace
'jbosssupport-servlet']; cla

==
JTeam B.V.
Donker Curtiusstraat 7-412
1051 JL  Amsterdam
T: +31 20 486 20 36
M: +31 6 24 11 1996
F: +31 84 837 00 00
E: al...@jt...
W: www.jteam.nl




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] setApplicationContext() not called on Singletons???

[Alef A. \(JTeam\) <al...@jt...>]

Hi all,

I've been spending like an hour on it, but can't find it:

I've got a bean (dataControllerSupport) defined which is referenced from
another bean (accountFormController), via <ref bean>. When the second
bean is loaded, it received the bean it's depending on. After that,
afterPropertiesSet() is called (on accountFormController), in which I'm
using the dataControllerSupport bean to resolve some things for me. The
dataControllerSupport bean needs the applicationcontext and therefore,
is ApplicationContext Aware. Hwoever, it does NOT have the application
context set!!! I've been investigating a while and really think
somewhere there's a flaw (using latest CVS code).

You can find the context (parts of it) below. Also, there some output...

The two beans...
	<bean id="dataControllerSupport"
class="jteam.web.controller.DataControllerSupport">
		<property name="addExtension">
			<value>add</value>
		</property>
		<property name="editExtension">
			<value>edit</value>
		</property>
		<property name="detailsViewPrefix">
			<value>details.</value>
		</property>
		<property name="listViewPrefix">
			<value>list.</value>
		</property>
		<property name="formViewPrefix">
			<value>form.</value>
		</property>
		<property name="recordHelperClass">
	
<value>jteam.jbosssupport.data.RecordHelper</value>
		</property>
		<property name="propertyEditorsFactory">
			<ref bean="propertyEditorsFactory"/>
		</property>
	</bean>
	<bean id="accountFormController"
class="jteam.web.controller.DataFormController">
    	<property name="dataControllerSupport">
    		<ref bean="dataControllerSupport"/>
    	</property>
        <property name="objectType">
            <value>Account</value>
        </property>
        <property name="sessionForm">
            <value>true</value>
        </property>
        <property name="bindOnNewForm">
            <value>true</value>
        </property>
        <property name="dataHelper">
            <ref external="accountHelper"/>
        </property>
        <property name="validator"><ref
bean="recordValidator"></ref></property>
        <property name="referenceData">
            <map>
                <entry key="billingAddress.country">
                    <ref external="countries"/>
                </entry>
                <entry key="companyAddress.country">
                    <ref external="countries"/>
                </entry>
            </map>
        </property>
    </bean>

The output I'm receiving when the dataControllerSupport is instantiated
(it's a Thread.dumpStack()). I've put some output at the places where
the applicationcontext is __supposed__ to be set, but it's not
outputting anything. Also, in the AbstractBeanFactory class, when
resolving references, I can't find any calls to setApplicationContext()
being done, however, afterPropertiesSet() on the depending bean _IS_
called, in which I'm relying on setApplicationContext() on the second
bean being called!!!

Anybody???

[XmlWebApplicationContext] 42 beans defined in ApplicationContext
[WebApplicationContext for namespace 'jbosssupport-servlet']
[XmlWebApplicationContext] ******* Retrieving bean contextOptions
[XmlWebApplicationContext] ******* Retrieving bean contextOptions
[XmlWebApplicationContext] No options bean ("contextOptions") found:
using default
[XmlWebApplicationContext] ******* Retrieving bean messageSource
[XmlWebApplicationContext] ******* Retrieving bean messageSource
[XmlWebApplicationContext] ******* Going to see if I need to set the
context on messageSource
[XmlWebApplicationContext] ******* No, NOT DOING IT!
[XmlWebApplicationContext] ******* Going to see if I need to set the
context on messageSource
[XmlWebApplicationContext] ******* No, NOT DOING IT!
[XmlWebApplicationContext] ******* Retrieving bean themeSource
[XmlWebApplicationContext] ******* Retrieving bean themeSource
[UiApplicationContextUtils] No ThemeSource found for
[WebApplicationContext for namespace 'jbosssupport-servlet']: using
ResourceBundleThemeSour
[XmlWebApplicationContext] Refreshing listeners
[XmlWebApplicationContext] Configuring singleton beans in context
[XmlWebApplicationContext] ******* Retrieving bean
contractViewController
[XmlBeanFactory] Creating shared instance of singleton bean
'contractViewController'
[XmlBeanFactory] Creating shared instance of singleton bean
'dataControllerSupport'
[DataControllerSupport] DataControllerSupport instantantiated
[STDERR] java.lang.Exception: Stack trace
[STDERR]     at java.lang.Thread.dumpStack(Thread.java:1071)
[STDERR]     at
jteam.web.controller.DataControllerSupport.<init>(DataControllerSupport.
java:83)
[STDERR]     at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[STDERR]     at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA
ccessorImpl.java:39)
[STDERR]     at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons
tructorAccessorImpl.java:27)
[STDERR]     at
java.lang.reflect.Constructor.newInstance(Constructor.java:274)
[STDERR]     at java.lang.Class.newInstance0(Class.java:306)
[STDERR]     at java.lang.Class.newInstance(Class.java:259)
[STDERR]     at
org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:26)
[STDERR]     at
org.springframework.beans.BeanWrapperImpl.<init>(BeanWrapperImpl.java:16
5)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.createBean
(AbstractBeanFactory.java:295)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.getSharedI
nstance(AbstractBeanFactory.java:233)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.getBeanInt
ernal(AbstractBeanFactory.java:162)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveRef
erence(AbstractBeanFactory.java:447)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.resolveVal
ueIfNecessary(AbstractBeanFactory.java:403)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.applyPrope
rtyValues(AbstractBeanFactory.java:367)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.createBean
(AbstractBeanFactory.java:319)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.getSharedI
nstance(AbstractBeanFactory.java:233)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.getBeanInt
ernal(AbstractBeanFactory.java:162)
[STDERR]     at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(Ab
stractBeanFactory.java:140)
[STDERR]     at
org.springframework.context.support.AbstractApplicationContext.getBean(A
bstractApplicationContext.java:453)
[STDERR]     at
org.springframework.context.support.AbstractApplicationContext.preInstan
tiateSingletons(AbstractApplicationContext.java:303)
[STDERR]     at
org.springframework.context.support.AbstractApplicationContext.refresh(A
bstractApplicationContext.java:229)
[STDERR]     at
org.springframework.web.context.support.XmlWebApplicationContext.setServ
letContext(XmlWebApplicationContext.java:121)
[STDERR]     at
org.springframework.web.servlet.FrameworkServlet.createWebApplicationCon
text(FrameworkServlet.java:167)
[STDERR]     at
org.springframework.web.servlet.FrameworkServlet.initServletBean(Framewo
rkServlet.java:146)
[STDERR]     at
org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.jav
a:82)
[STDERR]     at
javax.servlet.GenericServlet.init(GenericServlet.java:256)
[STDERR]     at
org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:219)
[STDERR]     at
org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandl
er.java:436)
[STDERR]     at
org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebAp
plicationHandler.java:150)
[STDERR]     at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationCont
ext.java:440)
[STDERR]     at
org.mortbay.j2ee.J2EEWebApplicationContext.start(J2EEWebApplicationConte
xt.java:85)
[STDERR]     at
org.jboss.jetty.JBossWebApplicationContext.start(JBossWebApplicationCont
ext.java:89)
[STDERR]     at org.jboss.jetty.Jetty.deploy(Jetty.java:331)
[STDERR]     at
org.jboss.jetty.JettyService.performDeploy(JettyService.java:242)
[STDERR]     at
org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:399)
[STDERR]     at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:822)
[STDERR]     at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
[STDERR]     at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:630)
[STDERR]     at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:603)
[STDERR]     at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown
Source)
[STDERR]     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
[STDERR]     at java.lang.reflect.Method.invoke(Method.java:324)
[STDERR]     at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
spatcher.java:284)
[STDERR]     at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
[STDERR]     at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
[STDERR]     at $Proxy7.deploy(Unknown Source)
[STDERR]     at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentSc
anner.java:302)
[STDERR]     at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScan
ner.java:476)
[STDERR]     at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doS
can(AbstractDeploymentScanner.java:200)
[STDERR]     at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abst
ractDeploymentScanner.java:273)
[STDERR]     at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
[STDERR]     at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown
Source)
[STDERR]     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
[STDERR]     at java.lang.reflect.Method.invoke(Method.java:324)
[STDERR]     at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
spatcher.java:284)
[STDERR]     at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
[STDERR]     at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController
.java:966)
[STDERR]     at $Proxy0.start(Unknown Source)
[STDERR]     at
org.jboss.system.ServiceController.start(ServiceController.java:392)
[STDERR]     at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown
Source)
[STDERR]     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
[STDERR]     at java.lang.reflect.Method.invoke(Method.java:324)
[STDERR]     at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
spatcher.java:284)
[STDERR]     at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
[STDERR]     at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
[STDERR]     at $Proxy5.start(Unknown Source)
[STDERR]     at
org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
[STDERR]     at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:822)
[STDERR]     at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:630)
[STDERR]     at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:603)
[STDERR]     at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:587)
[STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[STDERR]     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
[STDERR]     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
[STDERR]     at java.lang.reflect.Method.invoke(Method.java:324)
[STDERR]     at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
spatcher.java:284)
[STDERR]     at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
[STDERR]     at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
[STDERR]     at $Proxy6.deploy(Unknown Source)
[STDERR]     at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:365)
[STDERR]     at
org.jboss.system.server.ServerImpl.start(ServerImpl.java:272)
[STDERR]     at org.jboss.Main.boot(Main.java:150)
[STDERR]     at org.jboss.Main$1.run(Main.java:388)
[STDERR]     at java.lang.Thread.run(Thread.java:536)
[XmlBeanFactory] Creating shared instance of singleton bean
'propertyEditorsFactory'
[XmlWebApplicationContext] ******* Going to see if I need to set the
context on contractViewController
[XmlWebApplicationContext] ******* Yes, doing it!
[RecordController] Setting application context ApplicationContext:
displayName=[WebApplicationContext for namespace
'jbosssupport-servlet']; cla

==
JTeam B.V.
Donker Curtiusstraat 7-412
1051 JL  Amsterdam
T: +31 20 486 20 36
M: +31 6 24 11 1996
F: +31 84 837 00 00
E: al...@jt...
W: www.jteam.nl

Re: [Springframework-developer] Test coverage

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

On Sunday 21 September 2003 01:54, Darren Davison wrote:
> On Saturday 20 September 2003 22:16, Rod Johnson wrote:
> > Current major gaps include:
> > - XSLT support. I wrote this code so I guess I really should do the tests
> > but I'm not sure I have time. (These days I work entirely test first, but
> > I wrote that last year.) If any of the dev team are using this, maybe
> > they could take a look? It might require some refactoring.
>
> I may be able to help out a little on this next week.  Although I've
> switched mostly to Velocity, I was using XSLT support a lot recently.

suggested patches for FormatHelper and corresponding FormatHelperTests 
attached.. still hoping to look at XSLT view this week.

hth,

-- 

Darren Davison
Public Key: http://www.davison.uk.net/key.jsp

RE: [Springframework-developer] Mail support

[<jue...@we...>]

SnVzdCB3b25kZXJpbmcgZnJvbSB5b3VyIGRlc2NyaXB0aW9uOiBXaHkgZG9lc24ndCB0aGUgc2Vu
ZE1haWwgbWV0aG9kIHNpbXBseSB0YWtlIGEgTWFpbFNldHRpbmdzIHBhcmFtZXRlcj8gVGhlIGNh
bGxiYWNrIGltcGxlbWVudGF0aW9uIGRvZXNuJ3QgdXNlIGFueSBwcmVwYXJlZCByZXNvdXJjZSBs
aWtlIGEgSkRCQyBDb25uZWN0aW9uIG9yIEhpYmVybmF0ZSBTZXNzaW9uLCBzbyB3aHkgdXNlIGEg
Y2FsbGJhY2sgYXQgYWxsPw0KIA0KQlRXLCB3ZSBzaG91bGQgZGVmaW5pdGVseSBhaW0gdG8gYWdy
ZWUgb24gc3VjaCBwdWJsaWMgQVBJIGJlZm9yZSByZWxlYXNpbmcgMS4wIE0yLiBSZWxlYXNlZCBB
UElzIHNob3VsZCBzdGF5IGFzIHN0YWJsZSBhcyBwb3NzaWJsZS4NCiANCkp1ZXJnZW4NCiANCg0K
CS0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tIA0KCUZyb206IEtvcHlsZW5rbywgRG1pdHJ5IFtt
YWlsdG86ZGtvcHlsZW5rb0BhY3MucnV0Z2Vycy5lZHVdIA0KCVNlbnQ6IFdlZCA5LzEwLzIwMDMg
OTo1MSBQTSANCglUbzogJ3NwcmluZ2ZyYW1ld29yay1kZXZlbG9wZXJAbGlzdHMuc291cmNlZm9y
Z2UubmV0JyANCglDYzogDQoJU3ViamVjdDogW1NwcmluZ2ZyYW1ld29yay1kZXZlbG9wZXJdIE1h
aWwgc3VwcG9ydA0KCQ0KCQ0KDQoJSGVsbG8gZXZlcnlib2R5LCANCg0KCU5vdyB0aGVyZSBpcyBh
IG5ldyBtYWlsIHN1cHBvcnQgaW4gdGhlIHBhY2thZ2Ugb3JnLnNwcmluZ2ZyYW1ld29yay5tYWls
IA0KDQoJSXQgZm9sbG93cyB0aGUgY29uc2lzdGVudCBTcHJpbmcncyB0ZW1wbGF0ZS9jYWxsYmFj
ayBwYXR0ZXJuLiBUaGUgY2VudHJhbCBjb21wb25lbnQgaXMgTWFpbFRlbXBsYXRlIHdoaWNoIHVz
ZXMgTWFpbFNlbmRlciBzdHJhdGVneSAod2hpY2ggY291bGQgYmUgaW1wbGVtZW50ZWQgd2l0aCBh
bnkgZW1haWwgcHJvdG9jb2wvQVBJKSBhbmQgTWFpbENhbGxiYWNrLiBUeXBpY2FsbHkgbWFpbFNl
bmRlciBwcm9wZXJ0eSBvbiB0aGUgTWFpbFRlbXBsYXRlIGlzIHNldCB0aHJvdWdoIGFuIEFwcGxp
Y2F0aW9uQ29udGV4dC4gTWFpbENhbGxiYWNrIGhhcyBvbmUgbWV0aG9kIGNvbmZpZ3VyZSgpIGlu
IHdoaWNoIHRoZSBjbGllbnQncyBpbXBsZW1lbnRhdGlvbiB3b3VsZCBjb25maWd1cmUgdGhlIE1h
aWxTZXR0aW5ncyB2YWx1ZSBvYmplY3Qgd2l0aCBwcm9wZXJ0aWVzIG5lZWRlZCB0byBzZW5kIG1h
aWwuIEFsc28gdGhlIEphdmFNYWlsU2VuZGVyIGltcGxlbWVudGF0aW9uIGlzIHByb3ZpZGVkLg0K
DQoJRXhhbXBsZSB1c2FnZTogDQoNCglNYWlsVGVtcGxhdGUgbXQgPSBuZXcgTWFpbFRlbXBsYXRl
KCk7IA0KCU1haWxTZW5kZXIgbXMgPSBuZXcgSmF2YU1haWxTZW5kZXIoKTsgDQoJbXQuc2V0TWFp
bFNlbmRlcihtcyk7IA0KDQoJbXQuc2VuZE1haWwobmV3IE1haWxDYWxsYmFjaygpIHsgDQoJICAg
ICAgICBwdWJsaWMgdm9pZCBjb25maWd1cmUoTWFpbFNldHRpbmdzIG1haWxTZXR0aW5ncykgeyAN
CgkgICAgICAgICAgICAgICAgICAgICAgICBtYWlsU2V0dGluZ3Muc2V0TWFpbFRvKCJ4eHhAeWFo
b28uY29tIik7IA0KCSAgICAgICAgICAgICAgICAgICAgICAgIG1haWxTZXR0aW5ncy5zZXRNYWls
RnJvbSgieHh4QG9yZy5zcHJpbmdmcmFtZXdvcmsuY29tIik7IA0KCSAgICAgICAgICAgICAgICAg
ICAgICAgIG1haWxTZXR0aW5ncy5zZXRNYWlsU3ViamVjdCgidGVzdCIpOyANCgkgICAgICAgICAg
ICAgICAgICAgICAgICBtYWlsU2V0dGluZ3Muc2V0TWFpbFRleHQoInRlc3QiKTsgDQoJICAgICAg
ICAgICAgICAgICAgICAgICAgbWFpbFNldHRpbmdzLnNldE1haWxIb3N0KCJsb2NhbGhvc3QiKTsg
DQoJICAgICAgICAgICAgICAgIH0gDQoJICAgICAgICB9KTsgDQoNCglSZWdhcmRzLCANCglEbWl0
cml5LiANCg0K

RE: [Springframework-developer] Spring scheduler?

[<jue...@we...>]

T24gcmVsYXRlZCB0ZXJtcywgSSdsbCB3b3JrIG9uIEoyRUUgaW50ZWdyYXRpb24gZm9yIFNCQidz
IFVDNCBqb2Igc2NoZWR1bGluZyBzeXN0ZW0gaW4gT2N0b2Jlci4gVGhlcmUgaXMgZGVmaW5pdGVs
eSBhIGxvdCBvZiBvdmVybGFwIGhlcmUsIGFuZCB0aGUgYmlnIHBsdXMgdGhhdCBTQkIgaGF2ZSBh
Z3JlZWQgdG8gZGVmaW5lIGNvbW1vbiBwYXJ0cyBhbmQgaW50ZXJmYWNlcyBhcyBvcGVuIHNvdXJj
ZSBwcm9qZWN0IGEgbGEgQU9QIEFsbGlhbmNlLiBHZW5lcmljIGludGVyZmFjZXMgYW5kIGRlZmlu
aXRpb25zIGZvciBpbXBsZW1lbnRpbmcgam9icywgYW5kIGltcGxlbWVudGF0aW9ucyBmb3IgVUM0
IHZpYSBKQ0EvSk1TIGFuZCBmb3IgU3ByaW5nIGluIGEgYmVhbiBmYWN0b3J5IHN0eWxlLi4uIHNv
dW5kcyBpbnRlcmVzdGluZyB0byBtZSA6LSkgQWRkaXRpb25hbGx5LCBTQkIgaGF2ZSBnb29kIHJl
bGF0aW9ucyB3aXRoIFNBUCBhbmQgdGhlIG1ha2VycyBvZiBGbHV4LCBzbyB0aGVyZSBzaG91bGQg
YmUgcGxlbnR5IG9mIGZlZWRiYWNrIGFuZCBjaGFuY2VzIGZvciBmdXR1cmUgZGV2ZWxvcG1lbnRz
Lg0KIA0KSSdsbCBwcm92aWRlIG1vcmUgZGV0YWlscyB3aGVuIEknbSBiYWNrIGF0IHdvcmsgLSBh
dCB0aGUgbW9tZW50LCBJJ20gc3RpbGwgaW4gQXVzdHJhbGlhLi4uDQogDQpKdWVyZ2VuDQogDQoN
CgktLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLSANCglGcm9tOiBLb3B5bGVua28sIERtaXRyeSBb
bWFpbHRvOmRrb3B5bGVua29AYWNzLnJ1dGdlcnMuZWR1XSANCglTZW50OiBGcmkgOS8xMi8yMDAz
IDY6MjMgUE0gDQoJVG86ICdhbGVmQGp0ZWFtLm5sJzsgJ0l2YW4gUmlzdGljJzsgJ0NvbGluIFNh
bXBhbGVhbnUnIA0KCUNjOiAnc3ByaW5nZnJhbWV3b3JrLWRldmVsb3BlckBsaXN0cy5zb3VyY2Vm
b3JnZS5uZXQnIA0KCVN1YmplY3Q6IFJFOiBbU3ByaW5nZnJhbWV3b3JrLWRldmVsb3Blcl0gU3By
aW5nIHNjaGVkdWxlcj8NCgkNCgkNCg0KCT4gSSB0aGluayB0aGF0IG1pZ2h0IGJlIHRoZSBiZXN0
IHdheSB0byBkbyB0aGluZ3MuIFdlJ3ZlIGRvbmUgaXQgd2l0aA0KCT4gdmlld3MgYW5kIGFyZSBk
b2luZyBpdCB3aXRoIHBlcnNpc3RlbmNlLCBzbyB3aHkgbm90IGRvIGl0IHdpdGggc2NoZWR1bGVy
cw0KCWFzIHdlbGwuLi4NCgkNCglTbywgaWYgd2UgdGFrZSB0aGF0IGFwcHJvYWNoLCB0aGUgZmly
c3QgdGhpbmcgd291bGQgYmUgdG8gZGVzaWduIGENCgkiU2NoZWR1bGVyIiBzdHJhdGVneSBpbnRl
cmZhY2Ugd2hpY2ggdGhlbiBjb3VsZCBiZSBpbXBsZW1lbnRlZCBieSBkaWZmZXJlbnQNCgkid3Jh
cHBlcnMiIGFyb3VuZCBleGlzdGluZyBpbXBsZW1lbnRhdGlvbnMuIFdoYXQgZXZlcnlib2R5IHRo
aW5rcz8NCgkNCglSZWdhcmRzLA0KCURtaXRyaXkuDQoJDQoJDQoJDQoJLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KCVRoaXMgc2YubmV0IGVt
YWlsIGlzIHNwb25zb3JlZCBieTpUaGlua0dlZWsNCglXZWxjb21lIHRvIGdlZWsgaGVhdmVuLg0K
CWh0dHA6Ly90aGlua2dlZWsuY29tL3NmDQoJX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCglTcHJpbmdmcmFtZXdvcmstZGV2ZWxvcGVyIG1haWxpbmcgbGlz
dA0KCVNwcmluZ2ZyYW1ld29yay1kZXZlbG9wZXJAbGlzdHMuc291cmNlZm9yZ2UubmV0DQoJaHR0
cHM6Ly9saXN0cy5zb3VyY2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vc3ByaW5nZnJhbWV3b3Jr
LWRldmVsb3Blcg0KCQ0KDQo=

Re: [Springframework-developer] Test coverage

[Rod J. <rod...@in...>]

I took a look and mocking JavaMail isn't really an option (superbly
untestable API, with static methods and final classes).

So this is probably the only way to go... Thanks.

Regards,
Rod

----- Original Message ----- 
From: "Alef Arendsen (JTeam)" <al...@jt...>
To: "'Rod Johnson'" <rod...@in...>;
<spr...@li...>
Sent: Monday, September 22, 2003 10:48 PM
Subject: RE: [Springframework-developer] Test coverage


> If nobody's busy doing it already, I'll see what I can do on the
> javamail package. I've got a devnull mailer lying around somewhere that
> we use for testing, maybe I can integrate it somehow...
>
> By the way, up to 76,7 now...
>
> Alef
>
> -----Oorspronkelijk bericht-----
> Van: spr...@li...
> [mailto:spr...@li...] Namens
> Rod Johnson
> Verzonden: Saturday, September 20, 2003 11:17 PM
> Aan: spr...@li...
> Onderwerp: [Springframework-developer] Test coverage
>
>
> I think one of the things that has contributed to the success and
> quality of Spring is our commitment to a good test suite. I've put a
> fair bit more work into the test suite over the weekend, with the
> upgrade to EasyMock 1.0 and new test suites for Velocity etc.
>
> I'm really pleased that everyone is emphasising tests in new coding, but
> there is a still a bit of catchup to do.
>
> With this and Alef's new tag tests, test coverage is now 75.8%. I'd like
> to see this go above 80% before 1.0RC1.
>
> So I think we should all kick in and add tests to our areas of interest.
> Please run the Clover analysis as a starting point.
>
> Current major gaps include:
> - XSLT support. I wrote this code so I guess I really should do the
> tests but I'm not sure I have time. (These days I work entirely test
> first, but I wrote that last year.) If any of the dev team are using
> this, maybe they could take a look? It might require some refactoring.
> - jdbc.core.support: No tests for incrementer support. Can the
> developers looking after this please try to add some tests?
>
> Any volunteers for these or other areas in which tests can be improved?
>
> Regards,
> Rod
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>