You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Magnus Kvalheim <ma...@kvalheim.dk> on 2012/05/28 11:49:27 UTC
Official jboss support
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/HowToRunTapestry5OnJBoss6Dot1 and
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
Re: Official jboss support
Posted by Chris Mylonas <ch...@opencsta.org>.
Hey mate,
Did you try JBoss community forums for your DB woes. Good on you for venting...
Release 7.1.1 has two bugs I have been waiting for a fix since Feburary, but they only got fixed in 7.1.2 which is an EAP release.
I'll have to wait it out til 7.1.3 is released to the community for the fixes: 1) hibernate settings related; and, 2) Timing service related (EJB on start up)
I'm still a tapestry n00b relatively.
Ant scripts are great for controlling what versions of libraries to use rather than using maven for building whatever transient dependencies are updated - sometimes it's great, sometimes it's a world of pain. Like anything we do...
Respect,
Chris
On 29/05/2012, at 5:38 AM, 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
Re: Official jboss support
Posted by 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
Re: Official jboss support
Posted by 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
Posted by Magnus Kvalheim <ma...@kvalheim.dk>.
On Tue, May 29, 2012 at 2:06 PM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Tue, 29 May 2012 07:47:12 -0300, Magnus Kvalheim <ma...@kvalheim.dk>
> wrote:
>
> [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<https://github.com/magnuskvalheim/tapestry-cdi>- could be used as initial codebase for tapestry cdi.
>>
>
> Something I was thinking about Tapestry-IoC with CDI was the possibility
> of configuring all services in Tapestry-IoC and then somehow pass them to
> CDI, so CDI could handle transactions and stuff like that. We could also
> provide injections from T-IoC to CDI. In this scenario, I was thinking of
> having a different TapestryFilter implementation that sets a Registry
> instance in the ServletContext that pulls services from CDI (T-IoC
> indirectly) and not directly from T-IoC. This way, we can have the best of
> both worlds (transactions and other stuff from CDI and the nice features of
> T-IoC like distributed configuration, easy decoration of services, etc). We
> probably would need
>
*Bootstrap*
cdi (weld) is normally triggered on the existence of beans.xml in
web/meta-inf. Once started a beanmanager will be registered in jndi and
available through context.
In the current implementation of tapestry-cdi (among other things) a custom
injectionprovider is registered. It looks up and injects cdi beans on
@Inject.
*T-IoC to CDI*
It is quite possible to wrap and feed tapestry services to CDI. This is
done by making a portable extension.
http://docs.jboss.org/weld/reference/1.1.0.Final/en-US/html_single/#extend
*Transactions*
CDI don't offer transactions yet. Although I think it's on the roadmap I
believe it's recommended to use ejb's.
(Maybe a little too much detail, but guess it's possible to use
interceptors which work much the same way as a
tapestry ComponentClassTransformWorker,
http://docs.jboss.org/weld/reference/1.1.0.Final/en-US/html_single/#interceptors
)
>
> What do you think? I have no CDI experience, so I'm not sure what I'm
> describing above is feasible. And this idea would be an option to what
> you've done in tapestry-cdi, so people can choose what CDI integration they
> want.
I'm still learning cdi as well, but from what I know I think it's best to
let cdi bootstap normally and then inject in tapestry through
injectionprovider - and contribute t-services to cdi through a portable
extension.
Perhaps others have some more input though...
>
>
> --
> Thiago
>
Re: Official jboss support
Posted by lprimak <lp...@hope.nyc.ny.us>.
Transactions are part of JEE (EJB3.1, not CDI)
but its just a matter of a @Stateless declaration, so don't get scared :)
I've been using the JEE stack for a while now with Tapestry with the
flowlogix integration module.
( http://code.google.com/p/flowlogix/wiki/TapestryLibrary )
and it works great with no configuration. I also use Jelastic
(http://jelastic.com/) and it work great with both
Tapestry add JEE integration. It is Glassfish based.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/Official-jboss-support-tp5713435p5713513.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
Re: Official jboss support
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Tue, 29 May 2012 07:47:12 -0300, Magnus Kvalheim <ma...@kvalheim.dk>
wrote:
> [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.
Something I was thinking about Tapestry-IoC with CDI was the possibility
of configuring all services in Tapestry-IoC and then somehow pass them to
CDI, so CDI could handle transactions and stuff like that. We could also
provide injections from T-IoC to CDI. In this scenario, I was thinking of
having a different TapestryFilter implementation that sets a Registry
instance in the ServletContext that pulls services from CDI (T-IoC
indirectly) and not directly from T-IoC. This way, we can have the best of
both worlds (transactions and other stuff from CDI and the nice features
of T-IoC like distributed configuration, easy decoration of services,
etc). We probably would need
What do you think? I have no CDI experience, so I'm not sure what I'm
describing above is feasible. And this idea would be an option to what
you've done in tapestry-cdi, so people can choose what CDI integration
they want.
--
Thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Official jboss support
Posted by Magnus Kvalheim <ma...@kvalheim.dk>.
@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.jumpstart@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.honig@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.jumpstart@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-unsubscribe@tapestry.apache.org
> <javascript:;>
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> <javascript:;>
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> <javascript:;>
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> <javascript:;>
> > >
> > >
> >
>
Re: Official jboss support
Posted by Geoff Callender <ge...@gmail.com>.
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.honig@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.jumpstart@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-unsubscribe@tapestry.apache.org<javascript:;>
> > > For additional commands, e-mail: users-help@tapestry.apache.org<javascript:;>
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org<javascript:;>
> > For additional commands, e-mail: users-help@tapestry.apache.org<javascript:;>
> >
> >
>
Re: Official jboss support
Posted by Jon Williams <wi...@gmail.com>.
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
Posted by Gmail <da...@gmail.com>.
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 <ge...@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/HowToRunTapestry5OnJBoss6Dot1 and
>> 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
Posted by Geoff Callender <ge...@gmail.com>.
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/HowToRunTapestry5OnJBoss6Dot1 and
> 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