Re: Official jboss support

[Geoff Callender <ge...@gmail.com>]

In response to Jon's rant I have re-tested every JumpStart version from 5.4 to 5.10, with OpenEJB, JBoss, Glassfish, and Tomcat, with HSQL, Derby, and MySQL. Yes, sorry, I found some flaws had crept in to some combinations, and I believe I have addressed them: I've updated all instructions on the site and, to fix the support of MySQL (its issues were a bit too tricky to handle with instructions alone) I've released a new version, 5.10.1.

Please, if anyone finds something doesn't work, or finds the instructions are confusing or lacking, just drop me an email or post on this mailing list so we can get it fixed, pronto, for everyone's benefit!

Cheers,

Geoff

On 29/05/2012, at 10:19 AM, Geoff Callender 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 <da...@gmail.com> 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.jumpstart@gmail.com> 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-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: Official jboss support

[Jon Williams <wi...@gmail.com>]

Sorry no offence anyone,
I should have asked for help 1st before flipping on the rant nuerons.
Been working on my own so long I must have temporarily forgotten the
rest of the world that exisits on the internet.

God knows I've created some infathomable devient/ingenius code in my
day that came sans documantation. LOL
I know this is innevitable when the push is on.

Anyhow, gave me a chance to build the version of Jetty that my hosting
service supports. Suprise, suprise, building Jetty is a far larger
pain than building the Jumpstart!

So really, it was 2 days of mucknig w/Jumpstart & 2 days w/Jetty

When they release my from the Psych ward I'll try again from scratch
with the latest Jumpstart, my hosting service I think is up to date
with JBoss.

Thanks All



On 6/12/12, Geoff Callender <ge...@gmail.com> wrote:
> In response to Jon's rant I have re-tested every JumpStart version from 5.4
> to 5.10, with OpenEJB, JBoss, Glassfish, and Tomcat, with HSQL, Derby, and
> MySQL. Yes, sorry, I found some flaws had crept in to some combinations, and
> I believe I have addressed them: I've updated all instructions on the site
> and, to fix the support of MySQL (its issues were a bit too tricky to handle
> with instructions alone) I've released a new version, 5.10.1.
>
> Please, if anyone finds something doesn't work, or finds the instructions
> are confusing or lacking, just drop me an email or post on this mailing list
> so we can get it fixed, pronto, for everyone's benefit!
>
> Cheers,
>
> Geoff
>
> On 29/05/2012, at 10:19 AM, Geoff Callender 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 <da...@gmail.com> 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.jumpstart@gmail.com> 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-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