Hi,
Am Mittwoch, den 13.04.2011, 13:08 -0400 schrieb Rich M:
> ProxyPass /myApp http://localhost:8080/myApp
> ProxyPassReverse /myApp http://localhost:8080/myApp
Something like that works for our company too. The ProxyPassReverse
directive seems to be what's missing in your configuration.
Jochen
Hi,
I am new to tapestry and have a requirement to implement AJAX
Functionality in Tapestry 4.0. I am writing a simple program wherein i
enter a value in a textfield and click on the submit button and that value
has to be displayed in the same page without the page being
refreshed.Currently
> I don't think this is correct with regard to services that don't use
> HttpServletRequest or HttpServletResponse directly or indirectly. If I'm
> right, you can use most of your Tapestry services on them, speciallyl the
> singleton ones.
Ah yes, of course you are right. The proxy will get/create
On Wed, 13 Apr 2011 19:27:06 -0300, Josh Canfield
wrote:
When you receive a broadcast you are not in the Tapestry stack. You
might think it would be cool to use your @Inject'd services when you
get a broadcast, but you'll get an NPE because the thread that
executes the broadcast is not a thre
That is exactly what i had concluded except for the injection part of it.
Thanks for your insight
regards
Taha
On Thu, Apr 14, 2011 at 3:57 AM, Josh Canfield wrote:
> > Did you check the meteor module. In that case the Tapestry Filter will
> run
> > inside the Atmosphere Servlet.
>
> I've spent
Are you deploying multiple apps to glassfish? If not have you
considered deploying your app to the root context?
On Wed, Apr 13, 2011 at 8:04 AM, Jochen Heintz
wrote:
> Hi !
>
> I'm using Tapestry 5.2.5 and i use Glassfish behind a apache httpd as a
> proxy.
>
> The httpd is doing a ProxyPass / h
> Did you check the meteor module. In that case the Tapestry Filter will run
> inside the Atmosphere Servlet.
I've spent too much of today reading the white paper and experimenting
because I'm intrigued by anything async these days.
Atmosphere can work with Tapestry, as long as you don't want to
Hi Josh
Did you check the meteor module. In that case the Tapestry Filter will run
inside the Atmosphere Servlet.
regards
Taha
On Wed, Apr 13, 2011 at 10:38 PM, Josh Canfield wrote:
> I haven't played with Atmosphere specifically, but I've played a bit
> Jetty continuations, or Servlet 3's st
We faced problems with the root and app contexts using HTTPD/Apache in
front of a Servlet Container as well at my company. Our solution was as
follows, all in HTTPD. I thought I'd post this in case you find it
useful. You will probably be interested in the lines from ssl.conf (if
you don't use
I haven't played with Atmosphere specifically, but I've played a bit
Jetty continuations, or Servlet 3's startAsync in Tapestry.
It's not a trivial integration, but I've gotten something barely
working using Jetty's Continuations. For my solution I created an
@AsyncEvent which essentially hijacks
Hi,
i am tried this in AppModule :
public static void contributeAlias(Configuration configuration)
{
BaseURLSource source = new BaseURLSource()
{
public String getBaseURL(boolean secure)
{
return "http://";;
}
};
On Wed, 13 Apr 2011 12:04:38 -0300, Jochen Heintz
wrote:
Hi !
Hi!
Is it possible to change those relative uris to absolute uris ?
Take a look at BaseURLSource.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Ow
Hi !
I'm using Tapestry 5.2.5 and i use Glassfish behind a apache httpd as a
proxy.
The httpd is doing a ProxyPass / http://localhost:8080/myApp so that i am
able to call my site
from the root.
I'm able to see my site at http://test.local/ instead of
http://test.local/myApp.
That works fine exc
Taha -
You are correct, I was wrong. I patched up RadioGroup by adding:
Binding defaultValidate()
{
return defaultProvider.defaultValidatorBinding("value", resources);
}
and now the @Validate annotation on my bean enum property is read in
correctly. So this is the bug in Radi
On Wed, 13 Apr 2011 09:44:43 -0300, robnangle wrote:
Ok and this method should be in the getKeepers()?
It should be in the class of the objects used as options.
What do i check if its equal to?
It varies depending on the class itself, what it means and how object
identity is defined for
Thiago H. de Paula Figueiredo wrote:
>
> On Wed, 13 Apr 2011 09:33:04 -0300, robnangle
> wrote:
>
>> There is no goalkeepers class, goalkeepers is just a list of players
>> taken from the database:
>> public List getGoalkeepers() {
>> gsp = new GenerateSelect
On Wed, 13 Apr 2011 09:33:04 -0300, robnangle wrote:
There is no goalkeepers class, goalkeepers is just a list of players
taken from the database:
public List getGoalkeepers() {
gsp = new GenerateSelectPlayers(); // class that generates the
players
from the db
Thiago H. de Paula Figueiredo wrote:
>
> On Wed, 13 Apr 2011 08:30:42 -0300, robnangle
> wrote:
>
>> t:select t:id="goalkeeper" model="goalkeepers" value="team.keeper"
>> blankOption="never"/
>
> Make sure you overrode the equals() and hashCode() methods in the
> Goalkee
On Wed, 13 Apr 2011 08:30:42 -0300, robnangle wrote:
t:select t:id="goalkeeper" model="goalkeepers" value="team.keeper"
blankOption="never"/
Make sure you overrode the equals() and hashCode() methods in the
Goalkeeper class with a correct implementation.
--
Thiago H. de Paula Figueiredo
I
Hi Adam
Hi Adam
On Wed, Apr 13, 2011 at 5:19 PM, Adam Zimowski wrote:
> Hi Taha,
>
> > You are still not getting the point...
>
> Why so direct, having a bad day? Please tell me how am I not getting
> the point when I clearly wrote that:
>
>
Sorry if it appeared rude, that was certainly not my
Richard Hill-7 wrote:
>
> It depends. If you have a static list of players then you can store your
> select model in the session. If it's dynamic, you prob want to reload
> from the db each time.
>
> To be honest I'm not sure that storing stuff like this as an SSO is
> best-practice - it's more
It depends. If you have a static list of players then you can store your
select model in the session. If it's dynamic, you prob want to reload
from the db each time.
To be honest I'm not sure that storing stuff like this as an SSO is
best-practice - it's more for user session state. And you want
Richard Hill-7 wrote:
>
> are "add" and "edit" page classes?
>
>
They are yes.. All values are @Persist, @Property
So is the only way to get the default value up by setting all players as
sso's?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-Select-wont-find-sele
And what if we allowed to create defaultXxx method for persistent fields as
we do for component parameters, does it make sense ?
2011/4/12 Howard Lewis Ship
> This wouldn't have to be an extension to the @Property annotation, it
> could be a new annotation, (say) @AutoCreate, perhaps with a valu
Hi Taha,
> You are still not getting the point...
Why so direct, having a bad day? Please tell me how am I not getting
the point when I clearly wrote that:
Works. The validate parameter is not null with the above, and the
Radio group works as expected, as shown in RadioGroup
processSubmission(
are "add" and "edit" page classes?
If you instantiate an object in one page it won't be set in another,
unless you persist as an SSO
@Persist is only scoped to a particular page, i.e saves values between
requests. An @Persist'd object is not visible to other pages.
On Wed, 2011-04-13 at 04:4
Richard Hill-7 wrote:
>
> the value attribute will set (choose) the drop down value from the
> options defined in goalkeepers. Does this option/value exist in your
> model?
>
>
>
>
> On Wed, 2011-04-13 at 04:30 -0700, robnangle wrote:
>> t:select t:id="goalkeeper" model="goalkeepers" value="t
the value attribute will set (choose) the drop down value from the
options defined in goalkeepers. Does this option/value exist in your
model?
On Wed, 2011-04-13 at 04:30 -0700, robnangle wrote:
> t:select t:id="goalkeeper" model="goalkeepers" value="team.keeper"
> blankOption="never"/
>
> --
t:select t:id="goalkeeper" model="goalkeepers" value="team.keeper"
blankOption="never"/
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-Select-wont-find-selected-value-in-edit-tp4300292p4300356.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
You are still not getting the point...
1. fieldValidationSupport,validate is the service responsible for validating
a field. It requries a FieldValidator which is passed as a parameter to it.
If this @Parameter validate is null, as is the case with RadioGroup,
fieldValidationSupport is never call
no .tml here
On Wed, 2011-04-13 at 03:41 -0700, robnangle wrote:
> Hi I have a problem when I am trying to edit values that the selected value
> does not appear? My code is below and I thought you just put into
> value="team.keeper" which would return the keeper. The two classes both have
>
Hi Taha -
I agree with you it seems to be a bug, and I (think) I get what you are saying.
However, I am having a hard time seeing why the bug would be in
RadioGroup processSubmission() or anywhere in the RadioGroup class for
that matter.
Rather, it seems the bug (if exists) is deeper in the chai
Hi I have a problem when I am trying to edit values that the selected value
does not appear? My code is below and I thought you just put into
value="team.keeper" which would return the keeper. The two classes both have
@Property+@Persist annotations.
tml for edit class:
insert for creating the
it is the @Parameter validate in RadioGroup that is required not @Validate
as that is never checked in case @Parameter validate is not given in a
RadioGroup ... Please read my answer again :)
It seems to be bug!!
regards
Taha
On Wed, Apr 13, 2011 at 3:40 PM, Adam Zimowski wrote:
> Thanks Taha,
Thanks Taha, but I did supply @Validate("required") annotation and
validation did not happen.
Adam
On Tue, Apr 12, 2011 at 8:15 PM, Taha Hafeez wrote:
> Hi
>
> I compared the code from RadioGroup with that of Select and found the
> following difference
>
> In Select if parameter 'validate' is no
35 matches
Mail list logo