springide-eclip-developer

Re: [Springide-eclip-developer] springide compile problem (last cvs)

[Torsten J. <tor...@on...>]

Haris,

the CVS head is still not compilable (I didn't finish refactoring yet).
The version labled "release-1-1-0" is valid but outdated.

After refactoring I will commit a compilable version of Spring IDE to  
CVS head.
This version will be used to fill the initial version of the new  
Subversion repository.

Hopefully this can be done next week.

Cheers,
Torsten


On 30.03.2005, at 11:16, snpe wrote:

> Torsten,
>   What about cvs on sourceforge - is it valid yet ?
> Thanks
> On Tuesday 29 March 2005 09:52 pm, Torsten Juergeleit wrote:
>> Haris,
>>
>> I'm in the process of refactoring the Spring IDE plugins right now. So
>> the CVS head isn't compilable yet.
>>
>> The plan / status is as follows:
>>
>> - Migration to Eclipse 3 (native code, no compatibility plugins
>> required), remove all deprecation warnings
>>    -> done
>>
>> - Refactoring the core Spring / Eclipse stuff (project nature, basic /
>> generic incremental builder, globally
>>    needed jars) into separate plugins
>> (org.springframework.ide.eclipse.core,
>> org.springframework.ide.eclipse.ui)
>>    -> done
>>
>> - Adding an Eclipse extension point to plug-in your own incremental
>> builder for Spring projects, e.g. for a
>>    Spring Webflow validator
>>    -> done
>>
>> - fixing Bean Core's config validator
>>    -> ongoing (this stuff is really complicated :-( )
>>
>> - Adding an Eclipse extension point to plug-in your own bean config
>> file validator to the Beans Core's
>>    config validator
>>    -> not started yet
>>
>> - Migration of the Spring IDE source code to a Subversion repository,
>> Christian Dupuis (a colleague of mine)
>>    already set up the corresponding site (SVN repository with Trac
>> frontend [Wiki, source browsing and
>>    issue tracking]) on his server
>> (https://svn.christiandupuis.de/spring-ide/ ,
>> http://trac.christiandupuis.de/spring-ide/ )
>>    -> ongoing
>>
>> - Support for Spring Web Flow -> Christian is volunteering to use his
>> GEF knowledge (he already implemented an
>>    Eclipse plugin with a nice graphical Eclipse editor for workflow
>> definition files of a B2B application's backend
>>    services) to create a graphical editor for the config files of  
>> Spring
>> Webflow (coming with the new Spring 1.2)
>>    -> ongoiing
>>
>> - Integration of Dave's search extension into Spring IDE
>>    -> Dave, are you interested? ;-)
>>
>> Cheers,
>> Torsten
>>
>> On 28.03.2005, at 22:04, snpe wrote:
>>
>>> Hello,
>>>   I try compile last cvs eclipseide and get next error (class not
>>> found) :
>>> import
>>> org.springframework.ide.eclipse.beans.core.internal.model.validator.B 
>>> ea
>>> nsConfigValidator;
>>> import
>>> org.springframework.ide.eclipse.beans.core.internal.model.validator.B 
>>> ea
>>> nsValidatorUtil;
>>> import
>>> org.springframework.ide.eclipse.beans.core.internal.model.validator.I 
>>> Be
>>> ansConfigValidator;
>>>
>>> There isn't complete package
>>> org.springframework.ide.eclipse.beans.core.internal.model.validator
>>>
>>> What is a problem ?
>>>
>>> Regards
>>> Haris Peco
>>>
>>>
>>> -------------------------------------------------------
>>> SF email is sponsored by - The IT Product Guide
>>> Read honest & candid reviews on hundreds of IT Products from real
>>> users.
>>> Discover which products truly live up to the hype. Start reading now.
>>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>> _______________________________________________
>>> Springide-eclip-developer mailing list
>>> Spr...@li...
>>> https://lists.sourceforge.net/lists/listinfo/springide-eclip- 
>>> developer
>>>
>>
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real  
>> users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> _______________________________________________
>> Springide-eclip-developer mailing list
>> Spr...@li...
>> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real  
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>

RE: [Springide-eclip-developer] springide compile problem (last cvs)

[Watkins, D. <dav...@fa...>]

Hi Torsten,
Yeah, I'm still keen to contribute to this project!  Haven't had much
time to work on things recently, things are very busy at work (new=20
release of our software is imminent).  However I have been working away=20
on some internal plugins for our development team which utilise the=20
spring plugin stuff and I've got a few things I'd like to see if I can
add=20
into the base project (#1 is seeing how to get the import tag
recognized) =20

I'll go and take a look at the subversion repository this evening.

Cheers,
dw




> -----Original Message-----
> From: spr...@li...=20
> [mailto:spr...@li...]
>  On Behalf Of Torsten Juergeleit
> Sent: 29 March 2005 22:53
> To: Spring IDE Developer List
> Subject: Re: [Springide-eclip-developer] springide compile=20
> problem (last cvs)
>=20
> Haris,
>=20
> I'm in the process of refactoring the Spring IDE plugins=20
> right now. So the CVS head isn't compilable yet.
>=20
> The plan / status is as follows:
>=20
> - Migration to Eclipse 3 (native code, no compatibility=20
> plugins required), remove all deprecation warnings
>    -> done
>=20
> - Refactoring the core Spring / Eclipse stuff (project=20
> nature, basic / generic incremental builder, globally
>    needed jars) into separate plugins
> (org.springframework.ide.eclipse.core,
> org.springframework.ide.eclipse.ui)
>    -> done
>=20
> - Adding an Eclipse extension point to plug-in your own=20
> incremental builder for Spring projects, e.g. for a
>    Spring Webflow validator
>    -> done
>=20
> - fixing Bean Core's config validator
>    -> ongoing (this stuff is really complicated :-( )
>=20
> - Adding an Eclipse extension point to plug-in your own bean=20
> config file validator to the Beans Core's
>    config validator
>    -> not started yet
>=20
> - Migration of the Spring IDE source code to a Subversion=20
> repository, Christian Dupuis (a colleague of mine)
>    already set up the corresponding site (SVN repository with=20
> Trac frontend [Wiki, source browsing and
>    issue tracking]) on his server
> (https://svn.christiandupuis.de/spring-ide/ ,=20
> http://trac.christiandupuis.de/spring-ide/ )
>    -> ongoing
>=20
> - Support for Spring Web Flow -> Christian is volunteering to=20
> use his GEF knowledge (he already implemented an
>    Eclipse plugin with a nice graphical Eclipse editor for=20
> workflow definition files of a B2B application's backend
>    services) to create a graphical editor for the config=20
> files of Spring Webflow (coming with the new Spring 1.2)
>    -> ongoiing
>=20
> - Integration of Dave's search extension into Spring IDE
>    -> Dave, are you interested? ;-)
>=20
> Cheers,
> Torsten
>=20
> On 28.03.2005, at 22:04, snpe wrote:
>=20
> > Hello,
> >   I try compile last cvs eclipseide and get next error (class not
> > found) :
> > import
> >=20
> org.springframework.ide.eclipse.beans.core.internal.model.validator.Be
> > a
> > nsConfigValidator;
> > import
> >=20
> org.springframework.ide.eclipse.beans.core.internal.model.validator.Be
> > a
> > nsValidatorUtil;
> > import
> >=20
> org.springframework.ide.eclipse.beans.core.internal.model.validator.IB
> > e
> > ansConfigValidator;
> >
> > There isn't complete package
> > org.springframework.ide.eclipse.beans.core.internal.model.validator
> >
> > What is a problem ?
> >
> > Regards
> > Haris Peco
> >
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide Read honest=20
> & candid=20
> > reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start=20
> reading now.
> > http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> > _______________________________________________
> > Springide-eclip-developer mailing list=20
> > Spr...@li...
> >=20
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
> >
>=20
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide Read honest &=20
> candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>=20

Re: [Springide-eclip-developer] springide compile problem (last cvs)

[snpe <sn...@sn...>]

Torsten,
  What about cvs on sourceforge - is it valid yet ?
Thanks
On Tuesday 29 March 2005 09:52 pm, Torsten Juergeleit wrote:
> Haris,
> 
> I'm in the process of refactoring the Spring IDE plugins right now. So  
> the CVS head isn't compilable yet.
> 
> The plan / status is as follows:
> 
> - Migration to Eclipse 3 (native code, no compatibility plugins  
> required), remove all deprecation warnings
>    -> done
> 
> - Refactoring the core Spring / Eclipse stuff (project nature, basic /  
> generic incremental builder, globally
>    needed jars) into separate plugins  
> (org.springframework.ide.eclipse.core,  
> org.springframework.ide.eclipse.ui)
>    -> done
> 
> - Adding an Eclipse extension point to plug-in your own incremental  
> builder for Spring projects, e.g. for a
>    Spring Webflow validator
>    -> done
> 
> - fixing Bean Core's config validator
>    -> ongoing (this stuff is really complicated :-( )
> 
> - Adding an Eclipse extension point to plug-in your own bean config  
> file validator to the Beans Core's
>    config validator
>    -> not started yet
> 
> - Migration of the Spring IDE source code to a Subversion repository,  
> Christian Dupuis (a colleague of mine)
>    already set up the corresponding site (SVN repository with Trac  
> frontend [Wiki, source browsing and
>    issue tracking]) on his server  
> (https://svn.christiandupuis.de/spring-ide/ ,  
> http://trac.christiandupuis.de/spring-ide/ )
>    -> ongoing
> 
> - Support for Spring Web Flow -> Christian is volunteering to use his  
> GEF knowledge (he already implemented an
>    Eclipse plugin with a nice graphical Eclipse editor for workflow  
> definition files of a B2B application's backend
>    services) to create a graphical editor for the config files of Spring  
> Webflow (coming with the new Spring 1.2)
>    -> ongoiing
> 
> - Integration of Dave's search extension into Spring IDE
>    -> Dave, are you interested? ;-)
> 
> Cheers,
> Torsten
> 
> On 28.03.2005, at 22:04, snpe wrote:
> 
> > Hello,
> >   I try compile last cvs eclipseide and get next error (class not  
> > found) :
> > import  
> > org.springframework.ide.eclipse.beans.core.internal.model.validator.Bea 
> > nsConfigValidator;
> > import  
> > org.springframework.ide.eclipse.beans.core.internal.model.validator.Bea 
> > nsValidatorUtil;
> > import  
> > org.springframework.ide.eclipse.beans.core.internal.model.validator.IBe 
> > ansConfigValidator;
> >
> > There isn't complete package  
> > org.springframework.ide.eclipse.beans.core.internal.model.validator
> >
> > What is a problem ?
> >
> > Regards
> > Haris Peco
> >
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real  
> > users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > Springide-eclip-developer mailing list
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
> >
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
> 

Re: [Springide-eclip-developer] springide compile problem (last cvs)

[Torsten J. <tor...@on...>]

Haris,

I'm in the process of refactoring the Spring IDE plugins right now. So  
the CVS head isn't compilable yet.

The plan / status is as follows:

- Migration to Eclipse 3 (native code, no compatibility plugins  
required), remove all deprecation warnings
   -> done

- Refactoring the core Spring / Eclipse stuff (project nature, basic /  
generic incremental builder, globally
   needed jars) into separate plugins  
(org.springframework.ide.eclipse.core,  
org.springframework.ide.eclipse.ui)
   -> done

- Adding an Eclipse extension point to plug-in your own incremental  
builder for Spring projects, e.g. for a
   Spring Webflow validator
   -> done

- fixing Bean Core's config validator
   -> ongoing (this stuff is really complicated :-( )

- Adding an Eclipse extension point to plug-in your own bean config  
file validator to the Beans Core's
   config validator
   -> not started yet

- Migration of the Spring IDE source code to a Subversion repository,  
Christian Dupuis (a colleague of mine)
   already set up the corresponding site (SVN repository with Trac  
frontend [Wiki, source browsing and
   issue tracking]) on his server  
(https://svn.christiandupuis.de/spring-ide/ ,  
http://trac.christiandupuis.de/spring-ide/ )
   -> ongoing

- Support for Spring Web Flow -> Christian is volunteering to use his  
GEF knowledge (he already implemented an
   Eclipse plugin with a nice graphical Eclipse editor for workflow  
definition files of a B2B application's backend
   services) to create a graphical editor for the config files of Spring  
Webflow (coming with the new Spring 1.2)
   -> ongoiing

- Integration of Dave's search extension into Spring IDE
   -> Dave, are you interested? ;-)

Cheers,
Torsten

On 28.03.2005, at 22:04, snpe wrote:

> Hello,
>   I try compile last cvs eclipseide and get next error (class not  
> found) :
> import  
> org.springframework.ide.eclipse.beans.core.internal.model.validator.Bea 
> nsConfigValidator;
> import  
> org.springframework.ide.eclipse.beans.core.internal.model.validator.Bea 
> nsValidatorUtil;
> import  
> org.springframework.ide.eclipse.beans.core.internal.model.validator.IBe 
> ansConfigValidator;
>
> There isn't complete package  
> org.springframework.ide.eclipse.beans.core.internal.model.validator
>
> What is a problem ?
>
> Regards
> Haris Peco
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real  
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>

[Springide-eclip-developer] springide compile problem (last cvs)

[snpe <sn...@sn...>]

Hello,
  I try compile last cvs eclipseide and get next error (class not found) :
import org.springframework.ide.eclipse.beans.core.internal.model.validator.BeansConfigValidator;
import org.springframework.ide.eclipse.beans.core.internal.model.validator.BeansValidatorUtil;
import org.springframework.ide.eclipse.beans.core.internal.model.validator.IBeansConfigValidator;

There isn't complete package org.springframework.ide.eclipse.beans.core.internal.model.validator

What is a problem ?

Regards
Haris Peco

[Springide-eclip-developer] springide and eclipse 3.1M4 ?

[snpe <sn...@sn...>]

Hello,
Is there plan for move springide to eclipse 3.1M4.I try it (last cvs)and get null pointer when open graph editor ?

It be greta that it work with 3.1m4 beacuse 3.1m4 include jdk 5.0 (99.xx%)

regards
Haris Peco

Re: [Springide-eclip-developer] Brainstorming about validator improvements

[Torsten J. <tor...@on...>]

> P.S.  Speaking of validation, the problem marker on 'anonymous'
> inner beans doesn't give enough information to pinpoint the bean
> without relying on line number hacks.  It would be nice to come
> up with a 'path' for beans i.e.
>
> outerBean/middleInnerBean/innerInnerBean
>
> Though, we'd have to be carefull on the seperator (/ is not a good
> one!)

A bean path is not needed anymore. Anonymous inner beans have a unique 
name (pattern  "<class name>[#<occurrence counter>]") now (for details 
refer to my previous mail).

Cheers,
Torsten


On 15.11.2004, at 20:14, Watkins, David wrote:

>  Hi,
> I've been having a (slow) think about this and haven't really
> come up with any good options :(
>
> My current thinking.....Problem markers should be split into
> two broad categories:
>
> 1) Definate problems/errors - property doesn't exist/class
> not found etc.
>
> 2) Context warnings/information - referenced/parent bean
> not found in 'this' config file.
>
> These are the only markers attached to the resource.
>
> A second level of problem 'markers' (though not really markers)
> would operate on the config sets (only visible in the bean view)
> which indicate that a config set is incomplete (i.e. a bean ref
> is unresolvable) - this works only if we assume that there are
> no 'partial' config sets - which implies that a config set
> is roughly equivalent to a standard Spring Context.
>
> If this isn't acceptable then a flag could be included in the
> config set definition which indicates "I should be complete"
> - this flag would basically be a manual way of saying this
> config set is equivalent to a context.  In this scenario the
> validation steps in the above paragraph would only be applied
> if the flag is set.
>
> If we adopt the config set =~ context approach it gets us
> someway towards the idea put forward by Andreas Oberhack
> (some weeks ago - 4 Oct) that we could add a 'launch context'
> extension.  Perhaps a simpler option would be to add a
> 'Generate Spring Boot Class' action by resolving the
> config set into an array of classpath resources and
> feeding them into a spring ClassPathXmlApplicationContext.
>
> Anyway, just thought I'd chip in now before the question gets
> forgotten about!
>
> Cheers,
>   dw
>
> P.S.  Speaking of validation, the problem marker on 'anonymous'
> inner beans doesn't give enough information to pinpoint the bean
> without relying on line number hacks.  It would be nice to come
> up with a 'path' for beans i.e.
>
> outerBean/middleInnerBean/innerInnerBean
>
> Though, we'd have to be carefull on the seperator (/ is not a good
> one!)
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>

Re: [Springide-eclip-developer] Do we really need support for separate lists for "normal" beans and inner beans in BeansConfig and BeansConfigSet?

[Torsten J. <tor...@on...>]

> In the case of inner beans the id is currently (?) the
> class of the surrounding 'outer' bean.  This makes implementing
> quick fix suggestions on inner beans v. tricky!

The code in CVS head handles inner beans differently now. Every inner 
bean get's a unique name. This name is created via 
EventBeanDefinitionReader's inner SimpleBeanDefinitionRegistry which 
mimics a Spring's DefaultListableBeanFactory.
EventBeanDefinitionParser stores inner beans in 
SimpleBeanDefinitionRegistry to get a unique bean name for anonymouse 
inner beans (name pattern:  "<class name>[#<occurrence counter>]").

This unique bean name is stored in the problem marker's attribute 
"beanID" (IBeansProjectMarker.BEAN_ID). So you can retrieve the related 
IBean instance via IBeansConfig.getBean(). To distinguish between a 
"real" bean and an inner bean use IBean.isInnerBean().


So I would like to remove all the obsolete inner-bean-related stuff  
(separate list of inner beans, getInnerBeans(), ..) from 
BeansConfigHandler and (I)BeansConfig. Any issues?

Cheers,
Torsten


On 02.12.2004, at 11:54, Watkins, David wrote:

> I'll take a look at the code but I think we need a 'universal
> id' for inner beans and the like.  The specific scenario I'm
> thinking about is the problem markers.  As you know they have
> a couple of attributes, including the bean id and the problem
> type.  In the case of inner beans the id is currently (?) the
> class of the surrounding 'outer' bean.  This makes implementing
> quick fix suggestions on inner beans v. tricky!
>
> Anyway, I'll take a look at the new stuff (the 'incomplete config
> set' stuff sounds good!).  I'm hoping it'll allow me to simplify
> some of the refactoring participant code as I shouldn't have to
> walk a tree anymore.  I'll let you know if I hit any problems.
>
> Cheers,
>   dw
>
>
>
>
>
>> -----Original Message-----
>> From: spr...@li...
>> [mailto:spr...@li...]
>>  On Behalf Of Torsten Juergeleit
>> Sent: 02 December 2004 01:31
>> To: Spring IDE Developer List
>> Subject: [Springide-eclip-developer] Do we really need
>> support for separate lists for "normal" beans and inner beans
>> in BeansConfig and BeansConfigSet?
>>
>> While implementing the validation of bean references I added
>> the ability to Bean to know it's outer bean if it's an inner bean.
>> Now I'm just wondering if we still need to maintain separate
>> lists for the normal beans and inner beans in BeansConfig and
>> BeansConfigSet.
>>
>> This means that BeansConfig.getBeans() and
>> BeansConfigSet.getBeans() return the aggregated list of
>> normal and inner beans. The separate
>> getInnerBeans() methods are obsolete and will be removed from
>> the interfaces. If anyone still needs separate lists then the
>> aggregated list can be filtered via IBean.isInnerBean().
>>
>> What do you think?
>>
>> Cheers,
>> Torsten
>>
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide Read honest &
>> candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://productguide.itmanagersjournal.com/
>> _______________________________________________
>> Springide-eclip-developer mailing list
>> Spr...@li...
>> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>

RE: [Springide-eclip-developer] Do we really need support for separate lists for "normal" beans and inner beans in BeansConfig and BeansConfigSet?

[Watkins, D. <dav...@fa...>]

I'll take a look at the code but I think we need a 'universal=20
id' for inner beans and the like.  The specific scenario I'm=20
thinking about is the problem markers.  As you know they have
a couple of attributes, including the bean id and the problem=20
type.  In the case of inner beans the id is currently (?) the
class of the surrounding 'outer' bean.  This makes implementing
quick fix suggestions on inner beans v. tricky! =20

Anyway, I'll take a look at the new stuff (the 'incomplete config
set' stuff sounds good!).  I'm hoping it'll allow me to simplify=20
some of the refactoring participant code as I shouldn't have to=20
walk a tree anymore.  I'll let you know if I hit any problems.

Cheers,
  dw





> -----Original Message-----
> From: spr...@li...=20
> [mailto:spr...@li...]
>  On Behalf Of Torsten Juergeleit
> Sent: 02 December 2004 01:31
> To: Spring IDE Developer List
> Subject: [Springide-eclip-developer] Do we really need=20
> support for separate lists for "normal" beans and inner beans=20
> in BeansConfig and BeansConfigSet?
>=20
> While implementing the validation of bean references I added=20
> the ability to Bean to know it's outer bean if it's an inner bean.
> Now I'm just wondering if we still need to maintain separate=20
> lists for the normal beans and inner beans in BeansConfig and=20
> BeansConfigSet.
>=20
> This means that BeansConfig.getBeans() and=20
> BeansConfigSet.getBeans() return the aggregated list of=20
> normal and inner beans. The separate
> getInnerBeans() methods are obsolete and will be removed from=20
> the interfaces. If anyone still needs separate lists then the=20
> aggregated list can be filtered via IBean.isInnerBean().
>=20
> What do you think?
>=20
> Cheers,
> Torsten
>=20
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide Read honest &=20
> candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.=20
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>=20

[Springide-eclip-developer] Spring IDE adopted by different products

[Torsten J. <tor...@on...>]

Derek's Gaijin Studio for Spring MVC is not the only product which  
ships with Spring IDE ;-)

There are also commercial offerings shiping with Spring IDE:

    Exadel's Eclipse4Web ->  
http://www.exadel.com/products_eclipse4web.html
                                                   
http://www.eclipse4web.com/springEditor.html
    Yoxos' Eclipse Distribution -> http://www.yoxos.com/
                                                          
http://www.yoxos.com/featuredb/3.1M2/ 
org.springframework.ide.eclipse.beans/

Cheers,
Torsten

Re: [Springide-eclip-developer] Brainstorming about validator improvements

[Torsten J. <tor...@on...>]

> If this isn't acceptable then a flag could be included in the
> config set definition which indicates "I should be complete"
> - this flag would basically be a manual way of saying this
> config set is equivalent to a context.  In this scenario the
> validation steps in the above paragraph would only be applied
> if the flag is set.

In CVS head you can find an implementation of the suggested "incomplete 
config set" feature (additional checkbox in config set properties 
dialog). Incomplete config sets are validated differently (undefined 
parent beans or bean references are ignored).

The head version also provides a few bugfixes and enhancements:
- Cyclic Dependencies not supported in BeansGraph -> 
http://opensource.atlassian.com/projects/spring/browse/IDE-26
- Inner public class not recoginized -> 
http://opensource.atlassian.com/projects/spring/browse/IDE-27
- for complete config sets the validator checks bean references 
(including parent beans) too

Cheers,
Torsten


On 15.11.2004, at 20:14, Watkins, David wrote:

>  Hi,
> I've been having a (slow) think about this and haven't really
> come up with any good options :(
>
> My current thinking.....Problem markers should be split into
> two broad categories:
>
> 1) Definate problems/errors - property doesn't exist/class
> not found etc.
>
> 2) Context warnings/information - referenced/parent bean
> not found in 'this' config file.
>
> These are the only markers attached to the resource.
>
> A second level of problem 'markers' (though not really markers)
> would operate on the config sets (only visible in the bean view)
> which indicate that a config set is incomplete (i.e. a bean ref
> is unresolvable) - this works only if we assume that there are
> no 'partial' config sets - which implies that a config set
> is roughly equivalent to a standard Spring Context.
>
> If this isn't acceptable then a flag could be included in the
> config set definition which indicates "I should be complete"
> - this flag would basically be a manual way of saying this
> config set is equivalent to a context.  In this scenario the
> validation steps in the above paragraph would only be applied
> if the flag is set.
>
> If we adopt the config set =~ context approach it gets us
> someway towards the idea put forward by Andreas Oberhack
> (some weeks ago - 4 Oct) that we could add a 'launch context'
> extension.  Perhaps a simpler option would be to add a
> 'Generate Spring Boot Class' action by resolving the
> config set into an array of classpath resources and
> feeding them into a spring ClassPathXmlApplicationContext.
>
> Anyway, just thought I'd chip in now before the question gets
> forgotten about!
>
> Cheers,
>   dw
>
> P.S.  Speaking of validation, the problem marker on 'anonymous'
> inner beans doesn't give enough information to pinpoint the bean
> without relying on line number hacks.  It would be nice to come
> up with a 'path' for beans i.e.
>
> outerBean/middleInnerBean/innerInnerBean
>
> Though, we'd have to be carefull on the seperator (/ is not a good
> one!)
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>

[Springide-eclip-developer] Do we really need support for separate lists for "normal" beans and inner beans in BeansConfig and BeansConfigSet?

[Torsten J. <tor...@on...>]

While implementing the validation of bean references I added the 
ability to Bean to know it's outer bean if it's an inner bean.
Now I'm just wondering if we still need to maintain separate lists for 
the normal beans and inner beans in BeansConfig and BeansConfigSet.

This means that BeansConfig.getBeans() and BeansConfigSet.getBeans() 
return the aggregated list of normal and inner beans. The separate 
getInnerBeans() methods are obsolete and will be removed from the 
interfaces. If anyone still needs separate lists then the aggregated 
list can be filtered via IBean.isInnerBean().

What do you think?

Cheers,
Torsten

[Springide-eclip-developer] Gaijin Studio for Spring MVC Eclipse plugin released

[Derek A. <der...@ya...>]

A preview of the 0.9.0 Gaijin Studio plugin for
Eclipse has been released. It can be used to create a
Spring project in Eclipse and graphically build
process flows which generate code that runs on Spring
MVC. Check out the docs at
http://docs.gaijin-studio.org (they are nowhere near
complete, but give a good overview). You can download
the plugin and get more info at
http://www.gaijin-studio.org. More docs will be added
over the next week.

Let me know what you think!
Derek Adams
da...@ga...

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

RE: [Springide-eclip-developer] Brainstorming about validator improvements

[Watkins, D. <dav...@fa...>]

 Hi,
I've been having a (slow) think about this and haven't really=20
come up with any good options :(

My current thinking.....Problem markers should be split into=20
two broad categories:

1) Definate problems/errors - property doesn't exist/class
not found etc.

2) Context warnings/information - referenced/parent bean
not found in 'this' config file. =20

These are the only markers attached to the resource. =20

A second level of problem 'markers' (though not really markers)
would operate on the config sets (only visible in the bean view)=20
which indicate that a config set is incomplete (i.e. a bean ref=20
is unresolvable) - this works only if we assume that there are=20
no 'partial' config sets - which implies that a config set=20
is roughly equivalent to a standard Spring Context. =20

If this isn't acceptable then a flag could be included in the
config set definition which indicates "I should be complete"
- this flag would basically be a manual way of saying this=20
config set is equivalent to a context.  In this scenario the=20
validation steps in the above paragraph would only be applied=20
if the flag is set.

If we adopt the config set =3D~ context approach it gets us=20
someway towards the idea put forward by Andreas Oberhack=20
(some weeks ago - 4 Oct) that we could add a 'launch context'=20
extension.  Perhaps a simpler option would be to add a=20
'Generate Spring Boot Class' action by resolving the=20
config set into an array of classpath resources and=20
feeding them into a spring ClassPathXmlApplicationContext.

Anyway, just thought I'd chip in now before the question gets
forgotten about!

Cheers,
  dw

P.S.  Speaking of validation, the problem marker on 'anonymous'=20
inner beans doesn't give enough information to pinpoint the bean=20
without relying on line number hacks.  It would be nice to come
up with a 'path' for beans i.e.=20

outerBean/middleInnerBean/innerInnerBean=20

Though, we'd have to be carefull on the seperator (/ is not a good=20
one!)

[Springide-eclip-developer] Re: Distribution of constructor arguments

[Andreas S. <tu...@ya...>]

> Currently I don"t see any other option than dropping
> validation of constructor arguments completely.
> Any thoughts?

Hi Torsten, 

maybe you could check if a bean has no further
children and validate only these beans. However, that
might be difficult considering the possible existence
of multiple context files.

In my opinion the best (and I think the easiest)
solution would be the general validation of all non
abstract-beans which have a class assigned (defined or
inherited).
In my case it would be no problem to tag the offending
parent bean abstract and I do not see that it would
pose a problem in general. Lacking the complete set of
constructor arguments, a bean would never be usable
from a bean factory. So the validation would force
users to correctly tag those beans as abstract and
improve the meaning of their configuration.

Regards,
Andreas


	

	
		
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

Re: [Springide-eclip-developer] Upload site and Spring IDE dependencies

[Torsten J. <tor...@on...>]

> I agree with not packaging GEF. This has been my
> biggest beef with MyEclipse.

The different versions of GEF are compiled / tested against a certain 
version of Eclipse, e.g. GEF 3.0.1 requires Eclipse 3.0.1.
So bundling a specific version of GEF forces the users to use the 
corresponding version of Eclipse too or a newer one.

> I am going to go with Torsten's second option and
> include the Spring IDE core plugin in my standard
> distribution.

To decouple from Spring IDE releases you could set the version number 
of the bundled Spring IDE's core plugin in your plugin's dependency 
configuration, e.g.
    <requires>
       <import plugin="org.springframework.ide.eclipse.beans.core" 
version="1.1.0" match="perfect"/>
    </requires>

This way the bundled version will always be referenced even though a 
newer version of Spring IDE maybe installed.

But you shouldn't use the version number "1.1.0" before the real 
version 1.1.0 of Spring IDE is released. Otherwise the update manger 
will not install Spring IDE's core plugin v1.1.0 when it's finally 
released. Maybe you can use "1.0.9" instead (you have to modify 
plugin.xml of the bundled Spring IDE core plugin too).

Cheers,
Torsten

On 11.11.2004, at 16:33, Derek Adams wrote:

> I agree with not packaging GEF. This has been my
> biggest beef with MyEclipse. The fact that they
> install customized versions of core Eclipse plugins
> under higher version numbers seems like a real hack. I
> am going to go with Torsten's second option and
> include the Spring IDE core plugin in my standard
> distribution.
>
> Thanks for your help!
> Derek Adams
> http://www.gaijin-studio.org
>
> --- snpe <sn...@sn...> wrote:
>
>> Torsten,
>>   Please exclude GEF - myeclipse wrong - I will
>> three GEF : myeclipse, spring ide and my one
>>
>> regards
>> On Wednesday 10 November 2004 10:45 pm, Torsten
>> Juergeleit wrote:
>>> Derek,
>>>
>>> this is the same issue as with Spring IDE and GEF.
>> You have the
>>> following options:
>>>
>>> 1. Bundle Spring IDE's core jar (with it's
>> dependent libraries -> XML
>>> parser, Spring, commons-logging) with one of your
>> plugins.
>>>
>>> 2. Bundle Spring IDE's core plugin with your
>> feature.
>>>
>>> 3. Require the user to install Spring IDE. But
>> this way you inherit
>>> Spring IDE's dependency on GEF too.
>>>
>>> I'm tending to option 2. This approach is used by
>> MyEclipse too. They
>>> ship with all their dependent plugins (including
>> GEF).
>>>
>>> Cheers,
>>> Torsten
>>>
>>>
>>> On 08.11.2004, at 19:23, Derek Adams wrote:
>>>
>>>> My Eclipse feature uses the Spring IDE beans
>> model and
>>>> imports the beans core plugin in its
>> dependencies. I
>>>> want to allow people to go to my update site and
>>>> download both my feature/plugins and the Spring
>> IDE
>>>> feature/plugins that it depends on. Do I need to
>>>> package the Spring IDE jars with my stuff, or is
>> there
>>>> a way to indicate to the update manager where to
>> find
>>>> the feature dependency?
>>>>
>>>> Thanks!
>>>> Derek Adams
>>>> http://www.gaijin-studio.org
>>>>
>>>>
>> __________________________________________________
>>>> Do You Yahoo!?
>>>> Tired of spam?  Yahoo! Mail has the best spam
>> protection around
>>>> http://mail.yahoo.com
>>>>
>>>>
>>>>
>>
> -------------------------------------------------------
>>>> This SF.Net email is sponsored by:
>>>> Sybase ASE Linux Express Edition - download now
>> for FREE
>>>> LinuxWorld Reader's Choice Award Winner for best
>> database on Linux.
>>>>
>>
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
>>>> _______________________________________________
>>>> Springide-eclip-developer mailing list
>>>> Spr...@li...
>>>>
>>
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>>>>
>>>
>>>
>>>
>>>
>>
> -------------------------------------------------------
>>> This SF.Net email is sponsored by:
>>> Sybase ASE Linux Express Edition - download now
>> for FREE
>>> LinuxWorld Reader's Choice Award Winner for best
>> database on Linux.
>>>
>>
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
>>> _______________________________________________
>>> Springide-eclip-developer mailing list
>>> Spr...@li...
>>>
>>
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>>>
>>
>>
>>
> -------------------------------------------------------
>> This SF.Net email is sponsored by:
>> Sybase ASE Linux Express Edition - download now for
>> FREE
>> LinuxWorld Reader's Choice Award Winner for best
>> database on Linux.
>>
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
>> _______________________________________________
>> Springide-eclip-developer mailing list
>> Spr...@li...
>>
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>>
>
>
>
> 		
> __________________________________
> Do you Yahoo!?
> Check out the new Yahoo! Front Page.
> www.yahoo.com
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>

Re: [Springide-eclip-developer] Upload site and Spring IDE dependencies

[Derek A. <der...@ya...>]

I agree with not packaging GEF. This has been my
biggest beef with MyEclipse. The fact that they
install customized versions of core Eclipse plugins
under higher version numbers seems like a real hack. I
am going to go with Torsten's second option and
include the Spring IDE core plugin in my standard
distribution.

Thanks for your help!
Derek Adams
http://www.gaijin-studio.org

--- snpe <sn...@sn...> wrote:

> Torsten,
>   Please exclude GEF - myeclipse wrong - I will
> three GEF : myeclipse, spring ide and my one
> 
> regards
> On Wednesday 10 November 2004 10:45 pm, Torsten
> Juergeleit wrote:
> > Derek,
> > 
> > this is the same issue as with Spring IDE and GEF.
> You have the 
> > following options:
> > 
> > 1. Bundle Spring IDE's core jar (with it's
> dependent libraries -> XML 
> > parser, Spring, commons-logging) with one of your
> plugins.
> > 
> > 2. Bundle Spring IDE's core plugin with your
> feature.
> > 
> > 3. Require the user to install Spring IDE. But
> this way you inherit 
> > Spring IDE's dependency on GEF too.
> > 
> > I'm tending to option 2. This approach is used by
> MyEclipse too. They 
> > ship with all their dependent plugins (including
> GEF).
> > 
> > Cheers,
> > Torsten
> > 
> > 
> > On 08.11.2004, at 19:23, Derek Adams wrote:
> > 
> > > My Eclipse feature uses the Spring IDE beans
> model and
> > > imports the beans core plugin in its
> dependencies. I
> > > want to allow people to go to my update site and
> > > download both my feature/plugins and the Spring
> IDE
> > > feature/plugins that it depends on. Do I need to
> > > package the Spring IDE jars with my stuff, or is
> there
> > > a way to indicate to the update manager where to
> find
> > > the feature dependency?
> > >
> > > Thanks!
> > > Derek Adams
> > > http://www.gaijin-studio.org
> > >
> > >
> __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam?  Yahoo! Mail has the best spam
> protection around
> > > http://mail.yahoo.com
> > >
> > >
> > >
>
-------------------------------------------------------
> > > This SF.Net email is sponsored by:
> > > Sybase ASE Linux Express Edition - download now
> for FREE
> > > LinuxWorld Reader's Choice Award Winner for best
> database on Linux.
> > >
>
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> > > _______________________________________________
> > > Springide-eclip-developer mailing list
> > > Spr...@li...
> > >
>
https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
> > >
> > 
> > 
> > 
> >
>
-------------------------------------------------------
> > This SF.Net email is sponsored by:
> > Sybase ASE Linux Express Edition - download now
> for FREE
> > LinuxWorld Reader's Choice Award Winner for best
> database on Linux.
> >
>
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> > _______________________________________________
> > Springide-eclip-developer mailing list
> > Spr...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
> > 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for
> FREE
> LinuxWorld Reader's Choice Award Winner for best
> database on Linux.
>
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
>
https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
> 



		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com 
 

Re: [Springide-eclip-developer] Upload site and Spring IDE dependencies

[snpe <sn...@sn...>]

Torsten,
  Please exclude GEF - myeclipse wrong - I will three GEF : myeclipse, spring ide and my one

regards
On Wednesday 10 November 2004 10:45 pm, Torsten Juergeleit wrote:
> Derek,
> 
> this is the same issue as with Spring IDE and GEF. You have the 
> following options:
> 
> 1. Bundle Spring IDE's core jar (with it's dependent libraries -> XML 
> parser, Spring, commons-logging) with one of your plugins.
> 
> 2. Bundle Spring IDE's core plugin with your feature.
> 
> 3. Require the user to install Spring IDE. But this way you inherit 
> Spring IDE's dependency on GEF too.
> 
> I'm tending to option 2. This approach is used by MyEclipse too. They 
> ship with all their dependent plugins (including GEF).
> 
> Cheers,
> Torsten
> 
> 
> On 08.11.2004, at 19:23, Derek Adams wrote:
> 
> > My Eclipse feature uses the Spring IDE beans model and
> > imports the beans core plugin in its dependencies. I
> > want to allow people to go to my update site and
> > download both my feature/plugins and the Spring IDE
> > feature/plugins that it depends on. Do I need to
> > package the Spring IDE jars with my stuff, or is there
> > a way to indicate to the update manager where to find
> > the feature dependency?
> >
> > Thanks!
> > Derek Adams
> > http://www.gaijin-studio.org
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by:
> > Sybase ASE Linux Express Edition - download now for FREE
> > LinuxWorld Reader's Choice Award Winner for best database on Linux.
> > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> > _______________________________________________
> > Springide-eclip-developer mailing list
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
> >
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
> 

Re: [Springide-eclip-developer] Distribution of constructor arguments

[Torsten J. <tor...@on...>]

Andreas,

this is another usecase of parent beans I wasn't aware of. With all the 
flexibility of Spring bean configuration it's very hard to develop a 
validator which supports all the allowed usecases without creating the 
entire bean factory :-(

I'm not sure how to handle constructor arguments in parent beans 
correctly. If no bean class was specified or the bean is abstract then 
checking the constructor arguments could be skipped. But what if a bean 
class was specified for a non-abstract parent bean and (like in your 
case) the number of constructor arguments doesn't fit because the child 
bean's constructor arguments have to be added?

Currently I don't see any other option than dropping validation of 
constructor arguments completely.
Any thoughts?

Cheers,
Torsten


On 08.11.2004, at 13:29, Andreas Senft wrote:

>
> Hi,
>
> I recently installed Spring-IDE 1.1.0 on eclipse 3.0.1
> and encountered a problem.
>
> Scenario:
>
> I have a class with a constructor which takes 3
> arguments. In my configuration I have a parent bean
> (as template) which defines only the first argument.
> The bean specifies the "class" attribute.
>
> Then I have a bean which refers the above bean as
> parent and declares the other two constructor
> arguments.
> Spring-IDE complains in both beans that the class has
> no constructor with 1 or 2 arguments, respectively.
>
> I would expect that the specifications for the "child"
> bean should be merged with the specifications of the
> parent bean. The parent bean should, however, not be
> validated in this case. Note that the error on the
> parent bean also occurs if the parent bean is
> specified as "abstract".
>
> Overall, Spring-IDE is really fun to work with!
>
> Regards,
> Andreas
>
>
> 	
>
> 	
> 		
> ___________________________________________________________
> Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier 
> anmelden: http://mail.yahoo.de
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>

Re: [Springide-eclip-developer] Upload site and Spring IDE dependencies

[Torsten J. <tor...@on...>]

Derek,

this is the same issue as with Spring IDE and GEF. You have the 
following options:

1. Bundle Spring IDE's core jar (with it's dependent libraries -> XML 
parser, Spring, commons-logging) with one of your plugins.

2. Bundle Spring IDE's core plugin with your feature.

3. Require the user to install Spring IDE. But this way you inherit 
Spring IDE's dependency on GEF too.

I'm tending to option 2. This approach is used by MyEclipse too. They 
ship with all their dependent plugins (including GEF).

Cheers,
Torsten


On 08.11.2004, at 19:23, Derek Adams wrote:

> My Eclipse feature uses the Spring IDE beans model and
> imports the beans core plugin in its dependencies. I
> want to allow people to go to my update site and
> download both my feature/plugins and the Spring IDE
> feature/plugins that it depends on. Do I need to
> package the Spring IDE jars with my stuff, or is there
> a way to indicate to the update manager where to find
> the feature dependency?
>
> Thanks!
> Derek Adams
> http://www.gaijin-studio.org
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>

[Springide-eclip-developer] Upload site and Spring IDE dependencies

[Derek A. <der...@ya...>]

My Eclipse feature uses the Spring IDE beans model and
imports the beans core plugin in its dependencies. I
want to allow people to go to my update site and
download both my feature/plugins and the Spring IDE
feature/plugins that it depends on. Do I need to
package the Spring IDE jars with my stuff, or is there
a way to indicate to the update manager where to find
the feature dependency?

Thanks!
Derek Adams
http://www.gaijin-studio.org

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Springide-eclip-developer] Distribution of constructor arguments

[Andreas S. <tu...@ya...>]

Hi,

I recently installed Spring-IDE 1.1.0 on eclipse 3.0.1
and encountered a problem.

Scenario:

I have a class with a constructor which takes 3
arguments. In my configuration I have a parent bean
(as template) which defines only the first argument.
The bean specifies the "class" attribute.

Then I have a bean which refers the above bean as
parent and declares the other two constructor
arguments.
Spring-IDE complains in both beans that the class has
no constructor with 1 or 2 arguments, respectively.

I would expect that the specifications for the "child"
bean should be merged with the specifications of the
parent bean. The parent bean should, however, not be
validated in this case. Note that the error on the
parent bean also occurs if the parent bean is
specified as "abstract".

Overall, Spring-IDE is really fun to work with!

Regards,
Andreas


	

	
		
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

[Springide-eclip-developer] Brainstorming about validator improvements

[Torsten J. <tor...@on...>]

I would like to start a discussion about the internals of the 
BeansConfigValidator and it's shortcomings. Maybe we can get some ideas 
for improvements.

Ok, here it goes with  the internals:

BeansConfigValidator is responsible for validating a single Spring bean 
config file only. It does not read the Spring bean config XML files 
itself. This is done in BeansModel's implementation of IBeanConfig.

BeansConfigValidator is called by the BeansModel's internal 
ResourceChangeListener for a modified bean class' config files or by 
the core's IncrementalProjectBuilder for every modfied Spring bean 
config file.

BeansConfigValidator performs the following actions during validation 
of a single config file:

1. Delete all BeansConfigValidator-related problem markers from the 
given config file.

2. Reset the corresponding BeanConfig in the BeanModel to force 
re-reading the config file and updating the model.
     If an exception occurs during reading the config file then a 
corresponding problem marker is created.

3. Validate all beans (inner beans too) of the config file:

  	a) If a bean class is specified then check if the corresponding Java 
type is available in the projects build path.
	     The project build of any referenced external project is searched 
too.
	     If no Java type is found then create a problem marker for the 
corresponding bean.

	b) If no bean class is specified for a child bean then look for a Java 
type in it's parent bean chain.

	c) If a Java type was found via a) or b) then validate the bean's 
constructor arguments
	    (check if the Java type has a constructor with the same number of 
arguments) and properties
	    (check if the Java type has a set method for the property)

4. Validate all config set the config file belongs to:
      For every bean defined in the validated config file check if a 
bean with the same bean name is defined in one
      of the other config files of the config set. If yes then create a 
problem marker for the corresponding bean.
      This check is applied only to config sets where the option "Enable 
bean overide" is diasbled.


Now for the shortcomings of the current implementation of 
BeansConfigValidator:

1. If no Java type for a child bean is found, e.g. the parent bean is 
defined ia a different config file,  then no validation of the bean is 
performed.

Config sets could be used to resolve this issue. But how to decide 
which config set is the correct one.
Maybe in one of the config sets a bean with the parent bean' name is 
defined but it's not the intended one (only a name clash). Or we have 
multiple config sets which have a bean with the parent's name. Which 
one should we use? If we would use all then we would create multipe 
problem marker's for the same bean.

We could use the import tags. But these are only recognized by the 
EventBeanDefinitionParser which is used by BeansConfig during reading a 
config file. And EventBeanDefinitionParser is (like 
BeansConfigValidator) responsible for a single config file. So it only 
checks the existance of the specified resource.

Hhm, perhaps we should extend BeansConfig to expose the imported 
BeansConfigs and use these for parent bean name resolution during 
validation.

2. Bean references are not validated at all. We could check if the 
referenced bean is defined but if it's defined outside of the current 
config file then we have the same issues as with a child bean's parent 
Java type (refer to 1.).

What do you think? Any suggestions?

Cheers,
Torsten

RE: [Springide-eclip-developer] "Open Java Type" destroys browse functionality!

[Watkins, D. <dav...@fa...>]

That button's got me a few times.  I think it's there because=20
in conjunction with the Java Browsing Perspective it makes
IBM VisualAge for Java users feel at home ;) =20

With regards to your RFE I'm not sure how practical it would be
to implement.  Perhaps a better alternative is to put the toggle
on the outliner (since that's about the only way to navigate
once you've turned it on!).

Cheers,
  dw

Re: [Springide-eclip-developer] "Open Java Type" destroys browse functionality!

[Antranig B. <ant...@ca...>]

Watkins, David wrote:
> 
> This sounds more like you've accidently pushed the
> 'Show source of seleced element only' toggle button.  On
> mine it's button the next to the instance highlighter and
> looks like a sheet of A4 with a rectangular index card
> overlaid and to the right.
> 
> Can you check that and let us know if that's it.  Thanks
> 
> Cheers,
>  dw

Thanks for this suggestion, it sounds highly plausible. I can't
reproduce this reliably, although it has happened to me three
or four times now. What I think is happening is this: what I
frequently do after browsing from either beans view to Java
is to quite often want to browse right back again with the
"back" button. Now you have pointed out the "show selected 
source only" toggle I see it appears on code views exactly
where the back button does on non-code views. It's quite likely
the button refresh is lagging the view change slightly, or
else there is some event delivery problem that sometimes
activates the old button.
Well, I feel slightly foolish at having had to destroy all my 
preferences just to alter the state of this button, but on the
other hand it isn't a very noticeable one! 
I might submit a RFE asking for buttons representing actions
common to two views not to move when switching between them... in 
the meantime I will delete this button.
Many thanks, David :)

Antranig.