[jboss-as7-dev] Changes to .jsp in an exploded deployment no longer picked up?
Joel Tosi
jtosi at redhat.com
Tue Apr 26 11:03:02 EDT 2011
The eyes that we are getting on the betas - are they purely random
developers or do we have any customers with their developers looking at
it and how it affects their enterprise?
I know <#-- name was commented out --> has been looking at AS7 from a deployment perspective
and they really dig that, but I haven't heard much from their developers
regarding AS7. Do we have any customers helping drive AS7 and what are
they saying? If that is out in the community forums, my apologies for
not seeing it.
On 04/26/2011 09:56 AM, Andrig Miller wrote:
>
>
> ------------------------------------------------------------------------
>
> *From: *"Jim Tyrrell" <jtyrrell at redhat.com>
> *To: *"Andrig Miller" <anmiller at redhat.com>
> *Cc: *"jboss-as7-dev at lists.jboss.org Development"
> <jboss-as7-dev at lists.jboss.org>
> *Sent: *Tuesday, April 26, 2011 8:53:33 AM
> *Subject: *Re: [jboss-as7-dev] Changes to .jsp in an exploded
> deployment no longer picked up?
>
> Andy,
>
> So if AS 7 is more development focused, I agree it can/should be,
> can any and all decisions made/discussed/etc on this list, make
> that experience the best it can be.
>
> Yes, I would say so.
>
>
> Worrisome threads in the last week:
> Should a welcome page exist
>
> Being taken care of though, right.
>
> Should it be enabled to have a .jsp to be hot deployed
>
> Looks like David Lloyd has this in the right track.
>
> How should lifecyles of datasource deployments be
> "configured/monitored/changed"
>
> That discussion looks like it is also headed in the right direction.
>
>
> On a side vein I still worry about adoption and the learning curve
> of all of this new amazing stuff.
>
> I think we all do, and I think one of the things that we need to do is
> all of us get the message out there for people to download, and test
> out Beta 3 and 4, and see how many eyes we can get on it.
>
>
> Probably a few others, but those have been on my mind this week.
>
> Jim Tyrrell
> Senior JBoss Solutions Architect
>
> Did you see RHT on CNBC's Mad Money?
> http://www.cnbc.com/id/39401056
>
>
>
> On Apr 26, 2011, at 8:46 AM, Andrig Miller wrote:
>
>
>
> ------------------------------------------------------------------------
>
> *From:*"Jim Tyrrell" <jtyrrell at redhat.com
> <mailto:jtyrrell at redhat.com>>
> *To:*"jboss-as7-dev at lists.jboss.org
> <mailto:jboss-as7-dev at lists.jboss.org>Development"
> <jboss-as7-dev at lists.jboss.org
> <mailto:jboss-as7-dev at lists.jboss.org>>
> *Sent:*Tuesday, April 26, 2011 7:56:11 AM
> *Subject:*Re: [jboss-as7-dev] Changes to .jsp in an
> exploded deployment no longer picked up?
>
> My two cents,
>
> As we do today, I am thinking you need to have configs out
> of the box that can be started.
>
> Production
> Development
>
> Maybe even JMS
> or WS
> or....
>
> I think prepackaged tested configs are a good idea as one
> size will not fit all. We have done this for a long time
> and am wondering out loud why that notion would be removed?
>
> There is a requirement in the PRD to have a development
> configuration and a production configuration, but that is
> specific to EAP. Traditionally, we have made the AS
> distribution more "development" focused out-of-the-box.
>
> I'm not sure, in this specific case what is the best option,
> but EAP will have a production and development configuration
> (perhaps a script that sets things up for either using the
> management API).
>
> Andy
>
>
> Jim Tyrrell
> Senior JBoss Solutions Architect
>
> Did you see RHT on CNBC's Mad Money?
> http://www.cnbc.com/id/39401056
>
>
>
> On Apr 26, 2011, at 7:39 AM,ssilvert at redhat.com
> <mailto:ssilvert at redhat.com>wrote:
>
> Quoting Jaikiran Pai <jpai at redhat.com
> <mailto:jpai at redhat.com>>:
>
> Thinking a bit more about this, I don't see any
> use of supporting
>
> exploded deployments (out of the box) if we don't
> support dynamic
>
> changes to .jsps (out of the box). What else can
> be changed dynamically
>
> in an exploded deployment?
>
>
> xhtml (Facelets) pages can behave the same as JSP's as
> long as you are
> in development mode.
>
>
> -Jaikiran
>
> On Tuesday 26 April 2011 04:52 PM, Remy Maucherat
> wrote:
>
> On Tue, 2011-04-26 at 16:40 +0530, Jaikiran
> Pai wrote:
>
> The better default will now be used:
> development will remain as "false".
>
> IMO, before going to production with the
> server, any developer/team
>
> would go through a development phase in
> which he would definitely like
>
> this feature. So having this turned on by
> default (atleast in standalone
>
> mode), IMO, makes sense.
>
>
> P.S: I
> createdhttps://issues.jboss.org/browse/AS7-659and
> was about to
>
> send out a pull request with a patch,
> before I saw this reply. If
>
> there's any objection to this change, then
> I'll wait for a resolution on
>
> this discussion.
>
>
> I have rejected the jira.
>
>
>
> _______________________________________________
>
> jboss-as7-dev mailing list
>
> jboss-as7-dev at lists.jboss.org
> <mailto:jboss-as7-dev at lists.jboss.org>
>
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
>
>
>
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> <mailto:jboss-as7-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> <mailto:jboss-as7-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
>
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20110426/8385c9bd/attachment.html
More information about the jboss-as7-dev
mailing list