<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user">
    <title>gmane.comp.java.tapestry.user</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98360"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98359"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98358"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98357"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98356"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98355"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98354"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98353"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98352"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98351"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98350"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98349"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98348"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98347"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98346"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98345"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98344"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98343"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98342"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98341"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98360">
    <title>Re: How to get a service whithout using &lt; at &gt;Inject</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98360</link>
    <description>&lt;pre&gt;Whilst tapestry will happily work side-by-side with other servlets, you can
get tapestry to instantiate a servlet and delegate to it. Here is my recent
attempt at integrating DWR with tapestry before I abandoned the idea.

https://github.com/uklance/tapestry-push/blob/master/src/main/java/com/lazan/push/dwr/DwrHttpServletRequestFilter.java
https://github.com/uklance/tapestry-push/blob/master/src/main/java/com/lazan/services/AppModule.java

One of the benefits of this approach is that you can provide the
functionality in a separate jar without needing to add to web.xml and you
can configure the servlet init-params as tapestry symbols.

--
View this message in context: http://tapestry.1045711.n5.nabble.com/How-to-get-a-service-whithout-using-Inject-tp5713412p5713424.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe&amp;lt; at &amp;gt;tapestry.apache.org
For additional commands, e-mail: users-help&amp;lt; at &amp;gt;&lt;/pre&gt;</description>
    <dc:creator>Lance Java</dc:creator>
    <dc:date>2012-05-25T18:10:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98359">
    <title>Re: [OT] J2EE write to filesystem &amp; JEE6</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98359</link>
    <description>&lt;pre&gt;Very cool - thanks for giving me the reason when it's okay to bend these rules re: Assets not needing transactional business stuff


On 25/05/2012, at 9:43 PM, Geoff Callender wrote:



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe&amp;lt; at &amp;gt;tapestry.apache.org
For additional commands, e-mail: users-help&amp;lt; at &amp;gt;tapestry.apache.org


&lt;/pre&gt;</description>
    <dc:creator>Chris Mylonas</dc:creator>
    <dc:date>2012-05-25T15:33:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98358">
    <title>Re: Building object through wizard.</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98358</link>
    <description>&lt;pre&gt;Hi Thiago, when making updates to an existing object, at the start of the
wizard I'm initially populating it with a criteria query, then on submit to
page2 from page1, I populate the SessionState and rebuild my object in page
2 with the SessionState rather than the criteria query. I'm assuming that
this is the correct way to do it. However I've ran into issues where
hibernates lazing loading feature doesn't eagerly grab empty collections
which causes an exception when page 2's object has been populated from the
session object and try's to load a collection. I was able to fix this by
getting the collection size prior to persisting the object in page 1 to the
session state. Seems like a bit of a hack to me. Thanks Guys. 


--
View this message in context: http://tapestry.1045711.n5.nabble.com/Building-object-through-wizard-tp5713417p5713422.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-&lt;/pre&gt;</description>
    <dc:creator>George Christman</dc:creator>
    <dc:date>2012-05-25T15:29:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98357">
    <title>Re: Building object through wizard.</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98357</link>
    <description>&lt;pre&gt;Thanks Guys, for your input. All very helpful. 

--
View this message in context: http://tapestry.1045711.n5.nabble.com/Building-object-through-wizard-tp5713417p5713420.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe&amp;lt; at &amp;gt;tapestry.apache.org
For additional commands, e-mail: users-help&amp;lt; at &amp;gt;tapestry.apache.org


&lt;/pre&gt;</description>
    <dc:creator>George Christman</dc:creator>
    <dc:date>2012-05-25T15:09:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98356">
    <title>Re: Building object through wizard.</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98356</link>
    <description>&lt;pre&gt;On Fri, 25 May 2012 11:02:42 -0300, George Christman  
&amp;lt;gchristman&amp;lt; at &amp;gt;cardaddy.com&amp;gt; wrote:


Why not SessionState? Unless you need the same user using the same wizard  
for editing two different objects in two different threads, there's no  
reason to avoid it. When the wizard is finished, send the object to the  
database and set the &amp;lt; at &amp;gt;SessionState field to null (so it isn't stored in  
the session anymore when it ceases to be used).

&lt;/pre&gt;</description>
    <dc:creator>Thiago H. de Paula Figueiredo</dc:creator>
    <dc:date>2012-05-25T15:09:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98355">
    <title>Re: Building object through wizard.</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98355</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi George,

using some sort of conversation (i.e. HTTP session) state is one way
to go - you would either detach the entities or use some sort of
specialized Transfer Objects.

Another way to go is to put the wizard into a single Tapestry page and
use Ajax to switch between the different 'pages' of the wizard. For
very complex pages, the effort may be prohibitive, but you can remain
free of session state this way. You can store state of 'previous'
steps of the wizard in hidden fields, or you can just 'hide' currently
unused steps using CSS. Validation (both client and server side) can
be tricky though because you do *not* want to validate data for steps
that have not even been reached yet.

Using &amp;lt; at &amp;gt;Persist, i.e. storing stuff in the HTTP session, gets your code
up and working pretty fast. If your users open the same page in two
browser tabs at the same time however you run into sticky issues.
Removing data from the session in all situations when the user
finishes&lt;/pre&gt;</description>
    <dc:creator>Arno Haase</dc:creator>
    <dc:date>2012-05-25T14:47:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98354">
    <title>Re: Building object through wizard.</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98354</link>
    <description>&lt;pre&gt;Hi George!

What I am doing for this is following the Jumpstart example...I store all
of my entities in the Conversation, and on the last page of the Wizard I
write them to the database.  It's worked out very well so far.  Check out
http://jumpstart.doublenegative.com.au/jumpstart/examples/wizard/usingpages1
for
the example I am using.

There's also a page there for different techniques for passing data between
pages...check
http://jumpstart.doublenegative.com.au/jumpstart/examples/state/passingdatabetweenpages


Another big thanks to Geoff for providing this valuable resource!

On Fri, May 25, 2012 at 9:02 AM, George Christman
&amp;lt;gchristman&amp;lt; at &amp;gt;cardaddy.com&amp;gt;wrote:

&lt;/pre&gt;</description>
    <dc:creator>Chris Cureau</dc:creator>
    <dc:date>2012-05-25T14:25:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98353">
    <title>Building object through wizard.</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98353</link>
    <description>&lt;pre&gt;Hello, I'm building a small little wizard that consist of a few pages. The
wizard allows for updates as well. I'm a hibernate user with a fairly
complex data structure consisting of many joined entities. I do not want to
save/update the data until the last page of the wizard which has caused me
to lose my data from one page to the next. I thought there was a way to
persist it with hibernate and retrieve it on the next page, but I've failed
miserably with that. "Maybe I'm missing something". So my question is there
a alternative solution such as SessionState or Persist where I could store
the object in memory and then later save?

--
View this message in context: http://tapestry.1045711.n5.nabble.com/Building-object-through-wizard-tp5713417.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe&amp;lt; at &amp;gt;tapestry.apache.org
For additional commands, e-mail: users-help&amp;lt; at &amp;gt;tapestry.apache.org


&lt;/pre&gt;</description>
    <dc:creator>George Christman</dc:creator>
    <dc:date>2012-05-25T14:02:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98352">
    <title>Re: Tapestry Transactions</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98352</link>
    <description>&lt;pre&gt;So you put your transactional annotation on the DAO, right? The CommitAfter
does that for me as well, what I need is to put it on some layer above that
has multiple contats to the couple of different DAOs. One that saves one
part of the transaction, other that saves another but the should fail or
success together, can I do this with you configuration? Can I put
Transactional annotation on something other then HibernateDAO. 


--
View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-Transactions-tp5713299p5713416.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe&amp;lt; at &amp;gt;tapestry.apache.org
For additional commands, e-mail: users-help&amp;lt; at &amp;gt;tapestry.apache.org


&lt;/pre&gt;</description>
    <dc:creator>bhorvat</dc:creator>
    <dc:date>2012-05-25T13:33:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98351">
    <title>Re: How to get a service whithout using &lt; at &gt;Inject</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98351</link>
    <description>&lt;pre&gt;On Fri, 25 May 2012 07:18:32 -0300, Thim Anneessens &amp;lt;thimwork&amp;lt; at &amp;gt;gmail.com&amp;gt;  
wrote:


Hi!


The Tapestry-created Registry instance is stored in the  
TapestryFilter.REGISTRY_CONTEXT_NAME  
(org.apache.tapestry5.application-registry) attribute of the  
ServletContext. From the Registry instance you can use its getService()  
methods (which are inherited from ObjectLocator) to get configured  
services. That's exactly the methods used by the code that handles  
&amp;lt; at &amp;gt;Inject. Registry has also the autobuild() method to create an instance of  
any class with dependencies injected.

&lt;/pre&gt;</description>
    <dc:creator>Thiago H. de Paula Figueiredo</dc:creator>
    <dc:date>2012-05-25T12:21:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98350">
    <title>Re: [OT] J2EE write to filesystem &amp; JEE6</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98350</link>
    <description>&lt;pre&gt;Arno is spot on. The spec is being motherly, but in practice if you're uploading assets, as opposed to saving something that must be considered part of a transaction, then there's no harm done in writing to the file system. Everybody does it! Here's an example:

http://jumpstart.doublenegative.com.au/jumpstart/examples/javascript/fileupload

If you're in a clustered environment then just make sure the file is written to a file location that is shared across the cluster.

If the saved files are then to be served up in high volume (eg. lots of images on a page to lots of users) then it may be preferable to return special URLs for them rather than have Tapestry's return them as asset addresses. The special URLs could be detected by Apache (in front of Tapestry) which can then serve them up directly from the file system (rather than have Tapestry stream them).

Of course if there are security requirements (ie. who is allowed to see what files) or the need for a CDN then more is required than I've suggested abov&lt;/pre&gt;</description>
    <dc:creator>Geoff Callender</dc:creator>
    <dc:date>2012-05-25T11:43:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98349">
    <title>T5.3 customizing BeanEditForm's cancel button label</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98349</link>
    <description>&lt;pre&gt;Guys, this might be a silly question but I'm trying to figure out how to
customize the text of the Cancel button within a BeanEditForm. I believe
the "cancel" boolean attribute was introduced in T5.2 but unlike
"submitLabel" there's no "cancelLabel" property to override the default
text.

This also leads me to another question. Is it possible to override the
submit and cancel labels implicitly by including a special-formatted string
in the application message catalog? Using "submit-label" or "cancel-label"
in app.properties seems to have no effect (unless you specify
submitLabel="message:submit-label" for the submit button of course, but I
don't see a way to do this for the cancel button).

I may be overlooking something obvious (I googled for quite a while...) so
sorry if my question is silly and thanks for guidance in advance!

Rado
&lt;/pre&gt;</description>
    <dc:creator>Immutability</dc:creator>
    <dc:date>2012-05-25T11:06:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98348">
    <title>How to get a service whithout using &lt; at &gt;Inject</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98348</link>
    <description>&lt;pre&gt;Hello,

I need to use a Tapestry service outside of the Tapestry scope (in 
another servlet of the same web app) and would like to know what is the 
cleanest way to achieve this.

Thanks,
Thim.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe&amp;lt; at &amp;gt;tapestry.apache.org
For additional commands, e-mail: users-help&amp;lt; at &amp;gt;tapestry.apache.org


&lt;/pre&gt;</description>
    <dc:creator>Thim Anneessens</dc:creator>
    <dc:date>2012-05-25T10:18:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98347">
    <title>&lt; at &gt;Inject vs &lt; at &gt;InjectResource in 5.3</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98347</link>
    <description>&lt;pre&gt;Hi

I tried to &amp;lt; at &amp;gt;Inject a Logger into a service (a tapestry-resteasy resource if that matters) and got an exception:
oejs.ServletHandler:/intern/
java.lang.RuntimeException: Exception constructing service 'ResteasyRequestFilter': Error building service proxy for service 'Application' (at org.tynamo.resteasy.Application(Collection) (at Application.java:14) via org.tynamo.resteasy.ResteasyModule.bind(ServiceBinder) (at ResteasyModule.java:31)): Error invoking service contribution method org.tynamo.resteasy.ResteasyModule.javaxWsRsCoreApplication(Configuration, ObjectLocator, ResteasyPackageManager, ClassNameLocator): No service implements the interface org.slf4j.Logger.
at org.apache.tapestry5.ioc.internal.services.JustInTimeObjectCreator.obtainObjectFromCreator(JustInTimeObjectCreator.java:75)
...

Google quickly brought up the solution to use &amp;lt; at &amp;gt;InjectResource instead, and that works perfectly fine.
But &amp;lt; at &amp;gt;InjectResource shows up as deprecated and the documentation states it should behave identical to &amp;lt; at &amp;gt;Inject.
It&lt;/pre&gt;</description>
    <dc:creator>Arming, Sebastian</dc:creator>
    <dc:date>2012-05-25T10:13:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98346">
    <title>Re: Tapestry Transactions</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98346</link>
    <description>&lt;pre&gt;Our dependencies are configured via Ivy:

&amp;lt;dependency org="org.hibernate" name="hibernate-core"
rev="3.6.1.Final" conf="compile"&amp;gt;
&amp;lt;artifact name="hibernate-core" ext="jar"/&amp;gt;
&amp;lt;/dependency&amp;gt;

&amp;lt;dependency org="org.springframework" name="spring-core"
rev="3.1.0.RELEASE" conf="compile"/&amp;gt;
&amp;lt;dependency org="org.springframework" name="spring-context"
rev="3.1.0.RELEASE" conf="compile"/&amp;gt;
&amp;lt;dependency org="org.springframework" name="spring-tx"
rev="3.1.0.RELEASE" conf="compile"/&amp;gt;
&amp;lt;dependency org="org.springframework" name="spring-jdbc"
rev="3.1.0.RELEASE" conf="compile"/&amp;gt;
&amp;lt;dependency org="org.springframework" name="spring-context-support"
rev="3.1.0.RELEASE" conf="compile"&amp;gt;
&amp;lt;artifact name="spring-context-support" ext="jar"/&amp;gt;
&amp;lt;/dependency&amp;gt;

And yes, you need to use the Spring filter in your web.xml because
your transactional services will be Spring services - configured in
the usual Spring way via the application-context.xml.

Example DAO:

import org.springframework.orm.hibernate3.support.HibernateDaoSupport;
import or&lt;/pre&gt;</description>
    <dc:creator>Steve Eynon</dc:creator>
    <dc:date>2012-05-25T10:06:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98345">
    <title>Re: Component cannot be cast to Page?</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98345</link>
    <description>&lt;pre&gt;Tapestry does some byte code manipulation on component classes. Net result is
that the Login page instance is loaded by a different classloader than the
Login class that is referenced by your AuthenticationFilter. This means that
the two classes are not equal which causes the ClassCastException.

One option is for your Login page to implement an interface (interface must
not be in the pages/components packages) and cast to the interface instead
of Login.

Another option is to use a different mechanism to store the lastPage.

--
View this message in context: http://tapestry.1045711.n5.nabble.com/Component-cannot-be-cast-to-Page-tp5713408p5713409.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe&amp;lt; at &amp;gt;tapestry.apache.org
For additional commands, e-mail: users-help&amp;lt; at &amp;gt;tapestry.apache.org


&lt;/pre&gt;</description>
    <dc:creator>Lance Java</dc:creator>
    <dc:date>2012-05-25T09:50:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98344">
    <title>Component cannot be cast to Page?</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98344</link>
    <description>&lt;pre&gt;Hi,

I have an AuthenticationFilter Class with the following code snippet:

    private boolean dispatchedToLoginPage(String pageName) throws
IOException {

        Component page = componentSource.getPage(pageName);
    
        if (loginPage.equalsIgnoreCase(pageName)) {
            
            URL lastPage = urlHelperService.getUrl(((Login)
page).getLastPage());

The page component is my Login page and I want to access the getLastPage
method of this class but I get the following exception:

25.05.2012 11:24:02 (DefaultRequestExceptionHandler.java          :  63) 
ERROR  - Processing of request failed with uncaught exception:
com.example.pages.Login cannot be cast to com.example.pages.Login
java.lang.ClassCastException: com.example.pages.Login cannot be cast to
com.example.pages.Login
at
com.example.security.AuthenticationFilter.dispatchedToLoginPage(AuthenticationFilter.java:87)
at
com.example.security.AuthenticationFilter.handleComponentEvent(AuthenticationFilter.java:55)
at $ComponentRequestFilte&lt;/pre&gt;</description>
    <dc:creator>sub</dc:creator>
    <dc:date>2012-05-25T09:39:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98343">
    <title>Re: Tapestry Transactions</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98343</link>
    <description>&lt;pre&gt;Hi Steve,

Thanks for posting. Can I ask you to help a bit more :)

I have tried adding to pom tapestry-spring but it didn't resolve everything.
I was under the impression that tapestry-spring includes everything spring
related that is needed. The missing dependencies are related to hibernate

import org.springframework.orm.hibernate3.SessionFactoryUtils;
import org.springframework.orm.hibernate3.SessionHolder;
import
org.springframework.transaction.support.TransactionSynchronizationManager;


Also will I need to do anything from this page 

http://tapestry.apache.org/integrating-with-spring-framework.html

Something like 


  &amp;lt;filter&amp;gt;
    &amp;lt;filter-name&amp;gt;app&amp;lt;/filter-name&amp;gt;
    
   
&amp;lt;filter-class&amp;gt;org.apache.tapestry5.spring.TapestrySpringFilter&amp;lt;/filter-class&amp;gt;
  &amp;lt;/filter&amp;gt;

So if you can share a bit more light on the configuration (how did you
define services, since mine are defined in the code as normal tapestry
service, as your custom OpenSessionInViewFilter), how do I plug in the
filter into the tapestry (do I &lt;/pre&gt;</description>
    <dc:creator>bhorvat</dc:creator>
    <dc:date>2012-05-25T09:26:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98342">
    <title>Re: [OT] J2EE write to filesystem &amp; JEE6</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98342</link>
    <description>&lt;pre&gt;626 pages of spec... and you reply with section number and some copy and paste.
I am grateful Arno, thank you!


On 25/05/2012, at 5:45 PM, Arno Haase wrote:



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe&amp;lt; at &amp;gt;tapestry.apache.org
For additional commands, e-mail: users-help&amp;lt; at &amp;gt;tapestry.apache.org


&lt;/pre&gt;</description>
    <dc:creator>Chris Mylonas</dc:creator>
    <dc:date>2012-05-25T08:59:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98341">
    <title>Re: [OT] J2EE write to filesystem &amp; JEE6</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98341</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

JEE application servers typically do not actually prevent you from
accessing the file system, and the spec does not require them to. So
if it works with your specific app server / jee stack, you are home free.

The spec prohibits accessing the file system sort of to protect you
from yourseslf - the file system is not transactional, needs attention
in a clustered environment etc.

That is specified in section 21.2.2 "Programming Restrictions" of the
EJB 3.1 specification (JSR 318,
http://www.oracle.com/technetwork/java/javaee/tech/index.html):


•An enterprise bean must not use the java.io package to attempt to
access files and directories in the file system.

The file system APIs are not well-suited for business components to
access data. Business components should use a resource manager API,
such as JDBC, to store data.


The bottom line is:
* the spec allows file system access from a servlet. The restriction
applies only to EJBs.
* Even from EJBs it works an&lt;/pre&gt;</description>
    <dc:creator>Arno Haase</dc:creator>
    <dc:date>2012-05-25T07:45:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.tapestry.user/98340">
    <title>Re: null value in Boolean</title>
    <link>http://permalink.gmane.org/gmane.comp.java.tapestry.user/98340</link>
    <description>&lt;pre&gt;Thanks for your answer,
i just found jira issue for that problem. 
https://issues.apache.org/jira/browse/TAPESTRY-1928
(and that you can't override the built-in coercion)

So i try it with enums...


--
View this message in context: http://tapestry.1045711.n5.nabble.com/null-value-in-Boolean-tp5713346p5713349.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe&amp;lt; at &amp;gt;tapestry.apache.org
For additional commands, e-mail: users-help&amp;lt; at &amp;gt;tapestry.apache.org


&lt;/pre&gt;</description>
    <dc:creator>Lodorvonhal</dc:creator>
    <dc:date>2012-05-23T13:43:17</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.java.tapestry.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.java.tapestry.user</link>
  </textinput>
</rdf:RDF>

