@jon - yeah, I know how frustrating it can be when it's just not working for whatever reason. Tapestry have a great community though - so I'm sure you would have gotten some intelligent replies and help to solve the issues you were facing. Especially from Geoff.
Now back on topic. I would really like to see tapestry just work out of the box on all major deployment environments. I would expect nothing less. Actually Thiago made a post earlier about tapestry not working on openshift which also runs jboss as7.1 http://tapestry.1045711.n5.nabble.com/Tapestry-on-OpenShift-did-someone-already-tried-it-td5713476.html Should I create a jira issue/feature request for ClasspathURLConverter[1] and possibly cdi support as well [2] ? [1]ClasspathURLConverter - It's needed on jboss as it's having an internal vfs and can't find pages and components on it's own. I think http://wiki.apache.org/tapestry/HowToRunTapestry5OnJBoss6Dot1 could serve as initial codebase [2]CDI support With Jee6 it's highly desirable to use cdi(jsr 299) for managing beans. I dare to say in most cases spring can be avoided completely and what you get is a app(s) with far less dependencies and configuration. To top it off you even get conversational scope for free! The module - https://github.com/magnuskvalheim/tapestry-cdi - could be used as initial codebase for tapestry cdi. Let me know what you think cheers magnus On Tue, May 29, 2012 at 2:19 AM, Geoff Callender < geoff.callender.jumpst...@gmail.com> wrote: > Wow, you wasted a week with it and this is the first I've heard about it? > Why? > > As far as I know the instructions work fine - I can't know differently if > you don't tell me. So Jon, for the benefit of all of us, please post > specifics that can be acted on and I will see what I can do. Much more > useful than a rant. > > Geoff > > On Tuesday, 29 May 2012, Jon Williams wrote: > > > Well, the last version of the Jumpstart supposedly worked on JBoss also. > > Press 1 button, CPU cycles spin for 5 minutes, then your app is pooped > out > > into the appropriate JBoss directory. At this point you are told by the > > directions that's all there is to do, proceed with the next stage of your > > project. > > > > But, try to follow these instructions, by the letter, you'll find holy > > jesus Jboss is incapable of managing your database connections. It works, > > next time, doesn't work, refresh, works, refresh. nope totally not > working. > > Puzzle over this for a couple of days, reach the conclusion, OMG Jboss is > > total crap I can't use it. Then if you have a brain you go get Jetty, > build > > the f'r yourself. Mess around with ant scripts for the Jumpstart (why the > > fuck they are ant scripts I can not answer), god damn 4 days later the > > stupid thing actually works. > > > > Summary: Don't fucking release your shit without proper docs or you are > > kicked out of the club forever. > > > > I know you are trying to be helpful, but we are noobs. If you do not > > accurately detail specifics in your docs, most particularly the basic 123 > > get running doc. All your effort and good intention is regarded by people > > who really want to see your code working will end up 1)being too stupid > to > > untangle the puzzle and abandon all efforts 2)smart enough to realize > > something is fundamentally screwy, then roll up sleeves and repair the > > rubbish that could not ever have worked properly ever. > > 3)Get really really 1mm from total anyurism and god damn rant at the > > retards who wasted your week. > > > > On Mon, May 28, 2012 at 11:37 AM, Gmail <daniel.ho...@gmail.com > <javascript:;>> > > wrote: > > > > > Be advised that as7 is very different from previous versions so proceed > > > with that in mind. > > > > > > Sent from my iPhone > > > > > > On May 28, 2012, at 7:58 AM, Geoff Callender < > > > geoff.callender.jumpst...@gmail.com <javascript:;>> wrote: > > > > > > > It's not what you'd call a mission critical app, but the JumpStart > demo > > > runs on JBoss AS 7.1.1. > > > > > > > > On 28/05/2012, at 7:49 PM, Magnus Kvalheim wrote: > > > > > > > >> Hi tapestry friends. > > > >> > > > >> We are in process of converting a project to deploy on JBoss AS7 in > > > >> production. > > > >> I've used > > http://wiki.apache.org/tapestry/HowToRunTapestry5OnJBoss6Dot1and > > > >> seems to work fine. > > > >> > > > >> I'm wondering though if anyone else have/are using this in > production. > > > Is > > > >> it stable and efficient enough for production use? > > > >> > > > >> The best would be if T5 would work in JBoss 'out of the box'. > > > >> An official Tapestry module would be fine as well. > > > >> > > > >> Any thoughts or experiences on this? > > > >> > > > >> > > > >> ----------------- > > > >> Background: > > > >> We have spring jpa based apps that runs on jetty/tomcat for > > > dev/production. > > > >> One of these apps is using tapestry > > > >> Spring is mainly used for transaction management and dependency > > > injection. > > > >> > > > >> > > > >> The converted apps uses ejb's(tx management) and cdi. No spring > > > >> dependencies anymore. > > > >> Tapestry cdi support comes from my own module ( > > > >> https://github.com/magnuskvalheim/tapestry-cdi). So far it's > working > > > fine > > > >> and have no issues, but need more testing before it's ready for > > > production > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > <javascript:;> > > > > For additional commands, e-mail: users-h...@tapestry.apache.org > <javascript:;> > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > <javascript:;> > > > For additional commands, e-mail: users-h...@tapestry.apache.org > <javascript:;> > > > > > > > > >
