portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <david_jen...@yahoo.com>
Subject Re: xbean spring experiments
Date Wed, 24 Oct 2007 15:43:47 GMT

On Oct 24, 2007, at 8:38 AM, Ate Douma wrote:

> Weaver, Scott wrote:
>> I think the trunk has moved to 100% Maven 2.  That being said, I  
>> have no
>> clue how to build it.
> First time setup:
>   mvn -P init test (everytime when maven and/or portal-resources  
> sub projects are changed)
>   mvn -P init-db test (everytime when you need to (re)initialize  
> the test database)
>
> Subsequently, you can build and test all components using:
>
>   mvn -Dmaven.test.skip=false install
>
> For portal deployment and j2-admin build setup have not yet been done.
>
>
>> Since the trunk represents Jetspeed 2.2, which
>> will be java 5 compliant, can we dump the javadoc annotations in  
>> favor
>> of using true annotations instead?  Other than that, I am +1 on  
>> seeing
>> how the xbean stuff pans out.
>
> David,
>
> I've just tried it out, applying your patch to the current trunk.
> As our test cases, in particular those for jetspeed-security and  
> jetspeed-portal, make use of the spring assemblies, the xbean  
> spring changes should be able to be tested for those components,  
> e.g running mvn -Dmaven.test.skip=false from within those sub  
> project folders.
>
> It doesn't yet work though...
>
> For one, I'm puzzled by the purpose of the new jetspeed-xbean- 
> spring component (which fails to build).

It collects all the source jars together and generates the schema for  
the components so all the components are in the same namespace.

> Secondly, all the tests in the jetspeed-security component project  
> fail with the following (or similar) error:
>
> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: 
>  Line 19 in XML document from class path resource [security- 
> atn.xml] is invalid; nested exception is  
> org.xml.sax.SAXParseException: Attribute "xmlns" must be declared  
> for element type "beans".
> Caused by: org.xml.sax.SAXParseException: Attribute "xmlns" must be  
> declared for element type "beans".
> 	at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> 	at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
> 	at  
> org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocume 
> nt(DefaultDocumentLoader.java:76)
> 	at  
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBe 
> anDefinitions(XmlBeanDefinitionReader.java:351)
> 	at  
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBean 
> Definitions(XmlBeanDefinitionReader.java:303)
> 	at  
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBean 
> Definitions(XmlBeanDefinitionReader.java:280)

I think I missed how to run the tests :-)  With your instructions  
I'll try to fix this up soon.

thanks!
david jencks

>
> Regards,
>
> Ate
>
>> -scott
>>> -----Original Message-----
>>> From: David Jencks [mailto:david_jencks@yahoo.com]
>>> Sent: Wednesday, October 24, 2007 4:10 AM
>>> To: Jetspeed Developers List
>>> Subject: xbean spring experiments
>>>
>>> A while back I suggested that using xbean-spring to generate a  
>>> schema
>>> for the spring config files might make jetspeed configuration
>>> simpler, and IIRC I got some favorable feedback for this idea.  I  
>>> had
>>> a bit of spare time recently and set up a bit of build structure for
>>> this and added the javadoc "annotations" for a few components and
>>> converted the administation and security-* spring config files.
>>> However I don't know how to tell if this breaks anything since it
>>> doesn't seem that trunk produces a working portal at the moment.  I
>>> may not have time to work on this continually for a bit so I thought
>>> I'd show what I have so far, so I opened JS2-794.
>>>
>>> I haven't been active for quite a while so don't want to barge in  
>>> and
>>> commit this without discussion review and approval.  I think that
>>> committing everything except the modified spring config files should
>>> be very low risk since the xbean context falls back to the behavior
>>> of the spring context when presented with regular spring xml.  I'm
>>> nervous about  committing the config file changes until we can tell
>>> that they work, but with only these changes to apply maintaining a
>>> patch wouldn't be difficult.
>>>
>>> If anyone has time to take a look that would be great and if you are
>>> all too busy getting 2.1.3 out that is fine too, perhaps I will have
>>> time to get some more stuff converted soon.
>>>
>>> many thanks
>>> david jencks
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
>>> For additional commands, e-mail: jetspeed-dev- 
>>> help@portals.apache.org
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message