You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by David Roberts <dl...@ukonline.co.uk> on 2008/05/23 11:25:24 UTC
Tapestry Spring Documentation Incomplete
Hi,
Just to say that I think the documentation here:
http://tapestry.apache.org/tapestry5/tapestry-spring/
needs updating.
Nowhere does it state that a dependency on tapestry-spring is needed in
pom.xml as such:
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-spring</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
I know this might seem obvious, but I for one assumed that this would
come with the Tapestry-core dependency files.
This cost me 3 hours with Tomcat "startup failed due to previous errors"
errors whenever spring was added to web.xml until I remembered to look
in the full tomcat log to find out what the problem was.
Perhaps the same sort of update is also needed for the file upload page
on the Tapestry web site as well.
Its probably difficult to decided what to do when half of users are
still downloading the full gzip file and the other half are doing this
stuff using Maven but I think this is definitely something worth adding.
David.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry Spring Documentation Incomplete
Posted by David Roberts <dl...@ukonline.co.uk>.
Yes I can take your point. What caught me out was following the link
from the wiki HowTo - I didn't even realise I was in part of the
documentation for the spring module - anyway, its nice to see that the
mailing list is so active, I'm looking forward to upgrading to Tapestry5.
Howard Lewis Ship wrote:
> It's a question of what's is assumed vs. what is understood. We can't
> be in the business of recapitulating all the Maven theory every time
> we talk about a dependency. Anyone whose used Maven will understand
> that each module, and from the project layout tapestry-spring is
> clearly its own module, is an additional dependency.
>
> I'm not saying your wrong, I'm saying that if this is important to
> you, you need to add a JIRA issue so the work can be prioritized. And
> a patch would help!
>
> One of the nice things in 5.0.12-SNAPSHOT is that the exception report
> inlcudes all the JVM system properties, including the classpath, which
> makes it easier to understand what's going on with many conflicts or
> missing modules.
>
> On Fri, May 23, 2008 at 8:59 AM, David Roberts <dl...@ukonline.co.uk> wrote:
>
>> Hi,
>>
>> Unfortunately, the documentation doesn't state that it **is** a separate
>> module - which is precisely my point. Spring is so ubiquitous now that it
>> would not be a wild assumption that Tapestry would come with Spring support
>> out of the box. I think its reasonable enough to have Spring as a 'second'
>> option to Tapestry IOC, if that is Howard's preference, but my point is
>> the documentation (I followed the 'snippets' link on the HowTo on the wiki)
>> emphasises just how little effort it takes to incorporate Spring -
>> unfortunately it misses out some vital information i.e. "This bit of code
>> has dependencies" - it would not harm the document to put the dependency
>> markup right at the top.
>>
>> David.
>>
>>
>>
>> SergeEby wrote:
>>
>>> Hi,
>>>
>>> It seems obvious to me that you need to add any self-contained module such
>>> as tapestry-spring, tapestry-hibernate or tapestry-upload to your
>>> application only if you use it.
>>>
>>> /Serge
>>>
>>>
>>> TapestryBeast wrote:
>>>
>>>
>>>> Hi,
>>>>
>>>> Just to say that I think the documentation here:
>>>>
>>>> http://tapestry.apache.org/tapestry5/tapestry-spring/
>>>>
>>>> needs updating.
>>>>
>>>>
>>>> Nowhere does it state that a dependency on tapestry-spring is needed in
>>>> pom.xml as such:
>>>>
>>>> <dependency>
>>>> <groupId>org.apache.tapestry</groupId>
>>>> <artifactId>tapestry-spring</artifactId>
>>>> <version>${tapestry-release-version}</version>
>>>> </dependency>
>>>>
>>>> I know this might seem obvious, but I for one assumed that this would
>>>> come with the Tapestry-core dependency files.
>>>> This cost me 3 hours with Tomcat "startup failed due to previous errors"
>>>> errors whenever spring was added to web.xml until I remembered to look in
>>>> the full tomcat log to find out what the problem was.
>>>>
>>>> Perhaps the same sort of update is also needed for the file upload page
>>>> on the Tapestry web site as well.
>>>>
>>>> Its probably difficult to decided what to do when half of users are still
>>>> downloading the full gzip file and the other half are doing this stuff using
>>>> Maven but I think this is definitely something worth adding.
>>>>
>>>>
>>>> David.
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry Spring Documentation Incomplete
Posted by Howard Lewis Ship <hl...@gmail.com>.
It's a question of what's is assumed vs. what is understood. We can't
be in the business of recapitulating all the Maven theory every time
we talk about a dependency. Anyone whose used Maven will understand
that each module, and from the project layout tapestry-spring is
clearly its own module, is an additional dependency.
I'm not saying your wrong, I'm saying that if this is important to
you, you need to add a JIRA issue so the work can be prioritized. And
a patch would help!
One of the nice things in 5.0.12-SNAPSHOT is that the exception report
inlcudes all the JVM system properties, including the classpath, which
makes it easier to understand what's going on with many conflicts or
missing modules.
On Fri, May 23, 2008 at 8:59 AM, David Roberts <dl...@ukonline.co.uk> wrote:
> Hi,
>
> Unfortunately, the documentation doesn't state that it **is** a separate
> module - which is precisely my point. Spring is so ubiquitous now that it
> would not be a wild assumption that Tapestry would come with Spring support
> out of the box. I think its reasonable enough to have Spring as a 'second'
> option to Tapestry IOC, if that is Howard's preference, but my point is
> the documentation (I followed the 'snippets' link on the HowTo on the wiki)
> emphasises just how little effort it takes to incorporate Spring -
> unfortunately it misses out some vital information i.e. "This bit of code
> has dependencies" - it would not harm the document to put the dependency
> markup right at the top.
>
> David.
>
>
>
> SergeEby wrote:
>>
>> Hi,
>>
>> It seems obvious to me that you need to add any self-contained module such
>> as tapestry-spring, tapestry-hibernate or tapestry-upload to your
>> application only if you use it.
>>
>> /Serge
>>
>>
>> TapestryBeast wrote:
>>
>>>
>>> Hi,
>>>
>>> Just to say that I think the documentation here:
>>>
>>> http://tapestry.apache.org/tapestry5/tapestry-spring/
>>>
>>> needs updating.
>>>
>>>
>>> Nowhere does it state that a dependency on tapestry-spring is needed in
>>> pom.xml as such:
>>>
>>> <dependency>
>>> <groupId>org.apache.tapestry</groupId>
>>> <artifactId>tapestry-spring</artifactId>
>>> <version>${tapestry-release-version}</version>
>>> </dependency>
>>>
>>> I know this might seem obvious, but I for one assumed that this would
>>> come with the Tapestry-core dependency files.
>>> This cost me 3 hours with Tomcat "startup failed due to previous errors"
>>> errors whenever spring was added to web.xml until I remembered to look in
>>> the full tomcat log to find out what the problem was.
>>>
>>> Perhaps the same sort of update is also needed for the file upload page
>>> on the Tapestry web site as well.
>>>
>>> Its probably difficult to decided what to do when half of users are still
>>> downloading the full gzip file and the other half are doing this stuff using
>>> Maven but I think this is definitely something worth adding.
>>>
>>>
>>> David.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>>
>>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry Spring Documentation Incomplete
Posted by David Roberts <dl...@ukonline.co.uk>.
Hi,
Unfortunately, the documentation doesn't state that it **is** a separate
module - which is precisely my point. Spring is so ubiquitous now that
it would not be a wild assumption that Tapestry would come with Spring
support out of the box. I think its reasonable enough to have Spring as
a 'second' option to Tapestry IOC, if that is Howard's preference, but
my point is the documentation (I followed the 'snippets' link on the
HowTo on the wiki) emphasises just how little effort it takes to
incorporate Spring - unfortunately it misses out some vital information
i.e. "This bit of code has dependencies" - it would not harm the
document to put the dependency markup right at the top.
David.
SergeEby wrote:
> Hi,
>
> It seems obvious to me that you need to add any self-contained module such
> as tapestry-spring, tapestry-hibernate or tapestry-upload to your
> application only if you use it.
>
> /Serge
>
>
> TapestryBeast wrote:
>
>> Hi,
>>
>> Just to say that I think the documentation here:
>>
>> http://tapestry.apache.org/tapestry5/tapestry-spring/
>>
>> needs updating.
>>
>>
>> Nowhere does it state that a dependency on tapestry-spring is needed in
>> pom.xml as such:
>>
>> <dependency>
>> <groupId>org.apache.tapestry</groupId>
>> <artifactId>tapestry-spring</artifactId>
>> <version>${tapestry-release-version}</version>
>> </dependency>
>>
>> I know this might seem obvious, but I for one assumed that this would
>> come with the Tapestry-core dependency files.
>> This cost me 3 hours with Tomcat "startup failed due to previous errors"
>> errors whenever spring was added to web.xml until I remembered to look
>> in the full tomcat log to find out what the problem was.
>>
>> Perhaps the same sort of update is also needed for the file upload page
>> on the Tapestry web site as well.
>>
>> Its probably difficult to decided what to do when half of users are
>> still downloading the full gzip file and the other half are doing this
>> stuff using Maven but I think this is definitely something worth adding.
>>
>>
>> David.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry Spring Documentation Incomplete
Posted by SergeEby <sd...@hotmail.com>.
Hi,
It seems obvious to me that you need to add any self-contained module such
as tapestry-spring, tapestry-hibernate or tapestry-upload to your
application only if you use it.
/Serge
TapestryBeast wrote:
>
> Hi,
>
> Just to say that I think the documentation here:
>
> http://tapestry.apache.org/tapestry5/tapestry-spring/
>
> needs updating.
>
>
> Nowhere does it state that a dependency on tapestry-spring is needed in
> pom.xml as such:
>
> <dependency>
> <groupId>org.apache.tapestry</groupId>
> <artifactId>tapestry-spring</artifactId>
> <version>${tapestry-release-version}</version>
> </dependency>
>
> I know this might seem obvious, but I for one assumed that this would
> come with the Tapestry-core dependency files.
> This cost me 3 hours with Tomcat "startup failed due to previous errors"
> errors whenever spring was added to web.xml until I remembered to look
> in the full tomcat log to find out what the problem was.
>
> Perhaps the same sort of update is also needed for the file upload page
> on the Tapestry web site as well.
>
> Its probably difficult to decided what to do when half of users are
> still downloading the full gzip file and the other half are doing this
> stuff using Maven but I think this is definitely something worth adding.
>
>
> David.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Tapestry-Spring-Documentation-Incomplete-tp17422069p17424715.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org