On Fri, 23 Oct 2015 14:33:32 -0200, Casey Link
wrote:
Do you mean the "container" variable in the loop?
Yes!
That might explain it, as every iteration through the loop the value
changes. Is there a way to suspend the dual-binding nature, or pass a
copy of the value?
No. Don't reuse para
Do you mean the "container" variable in the loop?
That might explain it, as every iteration through the loop the value
changes. Is there a way to suspend the dual-binding nature, or pass a
copy of the value?
Casey
On 10/23/2015 03:25 PM, Thiago H de Paula Figueiredo wrote:
> On Fri, 23 Oct 2015
On Fri, 23 Oct 2015 07:01:51 -0200, Casey Link
wrote:
Ah yea, I screwed up the example in my email, but yes, it's declared
like so:
@Parameter(required = true)
List fooList;
Mind you it works for the "normal" static cases, and the case where it's
passed as a property (#1 and #2), but not in
Ah yea, I screwed up the example in my email, but yes, it's declared
like so:
@Parameter(required = true)
List fooList;
Mind you it works for the "normal" static cases, and the case where it's
passed as a property (#1 and #2), but not inside a .
Casey Link
Outskirts Labs { https://outskirtslabs
Just checking to be sure, but are you sure you didn't forget the
@Parameter on the fooList property in your component?
Nathan
On 23/10/15 10:14, Casey Link wrote:
This is a strange one.
I have a Foo component that wraps a progressive display (not sure if
that part is relevant). One of the par
This is a strange one.
I have a Foo component that wraps a progressive display (not sure if
that part is relevant). One of the parameters to this component is a
list of strings, "t:fooList":
@Property
List fooList;
In the page I'm trying to include it in, it works as expected if I set
fooList wi
I feel that it is not so good that select's parameter model not allow null.
because when render, i get the model from Database, when submit i have
already selected value, so why i have to get the model again. the
performance is a problem.
i just want the selected value to do some work.
I feel that it is not so good that select's parameter model not allow null.
t;
>
>hello
>
>
>
> Could not find a coercion from type java.lang.String to type
> org.sample.entities.Group.
>
> How to make this work? Thanks,
>
> Angelo
>
>
>
> --
> View this message in context:
> http://tape
On Thu, 02 Aug 2012 04:49:00 -0300, Angelo C.
wrote:
hi,
Hi!
this works as 'tesGroup' is a property in the page:
hello
but this one will not:
hello
I really have no idea what you're trying to do here. Your parameter is a
Group. You're trying to pass a String to it. Is thi
ello
but this one will not:
hello
Could not find a coercion from type java.lang.String to type
org.sample.entities.Group.
How to make this work? Thanks,
Angelo
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/component-parameter-coercion-tp5714988.html
Sen
Nevermind, Resolved this with field.getControlName rather than
field.getClientId.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Pass-component-parameter-back-to-method-Exception-tp5712975p5713007.html
Sent from the Tapestry - User mailing list archive at Nabble.com
I managed to get the page to render without issue. At render it calls my
FieldValidator method and I can see the field.clientId(). However onSubmit,
the field.getClientId() becomes null. Any ideas?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Pass-component-parameter
/Pass-component-parameter-back-to-method-Exception-tp5712975p5713000.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: us
/>
>
>
> public FieldValidator getFieldValidatorTest(Field field) {
> return null;
> }
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Pass-component-parameter-back-to-method-Exception-tp5712975.html
> Sent from the Tap
Sorry, my I posted the wrong backend method in my question.
public FieldValidator getFieldValidator(Field field) {
return null;
}
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Pass-component-parameter-back-to-method-Exception-tp5712975p5712977.html
Sent from the
java.lang.RuntimeException
line 1:21 no viable alternative at input '('
The code I'm using is as followed.
public FieldValidator getFieldValidatorTest(Field field) {
return null;
}
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Pass-component-paramete
Thanks I was able to fix the issue by rewriting the code and removing all the
static references. No easy way around :)
-
--
Don't Forget to Rate
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Issue-with-Component-Parameter-tp5612950p5616931.html
Sent from the Tap
gt; which won't be common across the session but if you could give me some idea
> on how something like that could be implemented it would really help me out.
>
> -
> --
> Don't Forget to Rate
> --
> View this message in context:
> http://tapestry.1045711.n
something like that could be implemented it would really help me out.
-
--
Don't Forget to Rate
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Issue-with-Component-Parameter-tp5612950p5613703.html
Sent from the Tapestry - User mailing list archiv
On Mon, 02 Apr 2012 15:31:30 -0300, derkoe
wrote:
Robert asked if you have a @Persist on your CollageModel in the parent
component or page. Parameters in Tapestry have a bi-directional binding.
So, if you have a @Persist on the model it is shared in the session. Two
browser tabs/windows a
s message in context:
http://tapestry.1045711.n5.nabble.com/Issue-with-Component-Parameter-tp5612950p5613282.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tap
nnotations.Parameter.
>
> where model is the parameter name.
>
>
>
> -
> --
> Don't Forget to Rate
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Issue-with-Component-Parameter-tp5612950p561
@org.apache.tapestry5.annotations.Parameter.
where model is the parameter name.
-
--
Don't Forget to Rate
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Issue-with-Component-Parameter-tp5612950p5613227.html
Sent from the Tapestry - User mailing list archive at Nabbl
s the model holding the list of images and some other
> properties.*
>
>
> Thanks and Regards,
> Srijith
>
> -
> --
> Don't Forget to Rate
> --
> View this message in context:
> http://tapestry.1045711.n5.nab
ould solve this issue,
if anyone has faced the same please do advice.
*Java: This is the model holding the list of images and some other
properties.*
Thanks and Regards,
Srijith
-
--
Don't Forget to Rate
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/
A good thing about following Howard is you getter better in both
tapestry and english :)
On Thu, Sep 29, 2011 at 9:04 AM, Steve Eynon
wrote:
> I had to look up the meaning of "Staw Man Proposal" (!) but it seems
> it's all good!
>
> JIRA raised:
>
> https://issues.apache.org/jira/browse/TAP5-1677
I had to look up the meaning of "Staw Man Proposal" (!) but it seems
it's all good!
JIRA raised:
https://issues.apache.org/jira/browse/TAP5-1677
Have fun!
Steve.
On 28 September 2011 21:57, Massimo Lusetti wrote:
> On Wed, Sep 28, 2011 at 12:15 AM, Igor Drobiazko
> wrote:
>
>> Actually this
On Wed, Sep 28, 2011 at 12:15 AM, Igor Drobiazko
wrote:
> Actually this is supported since 5.2:
> https://issues.apache.org/jira/browse/TAP5-1094
I think the proposal here is to have the default value for some
parameters (like the grid's rowsPerPage) to bind to a Symbol so the
default can be cha
I thought this was a bad idea
On 28/09/2011, at 12:49 AM, Steve Eynon wrote:
> To enhance Tapestry, what are people's thoughts about defining default
> component values for some components as Symbols?
>
> For example, the Grid component has the following:
>
> @Parameter("25")
> private int rows
Actually this is supported since 5.2:
https://issues.apache.org/jira/browse/TAP5-1094
On Tue, Sep 27, 2011 at 4:52 PM, Howard Lewis Ship wrote:
> Good idea; A "symbol" binding prefix could do this quite easily, which
> would make your straw man proposal accurate.
>
> On Tue, Sep 27, 2011 at 7:49
Hi,
I think you can use a message: prefix as well (defining it in the
app.properties) - tough a symbol (or similar) binding for properties will
probably be less confusing.
For date field format the message: binding is a perfect match as you get all
the ordinary resource bundle goodness for free ;
Good idea; A "symbol" binding prefix could do this quite easily, which
would make your straw man proposal accurate.
On Tue, Sep 27, 2011 at 7:49 AM, Steve Eynon
wrote:
> To enhance Tapestry, what are people's thoughts about defining default
> component values for some components as Symbols?
>
> F
To enhance Tapestry, what are people's thoughts about defining default
component values for some components as Symbols?
For example, the Grid component has the following:
@Parameter("25")
private int rowsPerPage;
meaning if I wish for a pagination of 50 rows, I have to find all
instances of the
Dear lord, of course it is not bound, the name of the parameter is
inccorect. It should be
@Parameter(name = "*image*", required = false)
private byte[] imageBytes;
And I was already debugging Tapestry sources...
2010/7/15 Christophe Cordenier
> Hi
>
> AFAIK Primitive arrays are coer
Hi
AFAIK Primitive arrays are coerced to List.
2010/7/14 Borut Bolčina
> Hi,
>
> I am having problem binding a parameter of type byte[]. It is not bound for
> some reason while imageTitle works as expected. The page template looks
> like:
>
>
>
> DynaImage is my custom component which displays
Hi,
I am having problem binding a parameter of type byte[]. It is not bound for
some reason while imageTitle works as expected. The page template looks
like:
DynaImage is my custom component which displays image from byte[], or so it
should :-)
In my page class:
@Property
private Stri
On Wed, Mar 4, 2009 at 5:15 AM, dhning wrote:
> 1. Do in java
> public Object [] getContextValue() {
> return new Object[2]{user.id, user.name};
> }
You can also return a List.
--
Thiago
-
To unsubscribe, e-mail: users-uns
Got it! thanks!
- Original Message -
From: "dhning"
To: "Tapestry users"
Sent: Wednesday, March 04, 2009 5:28 PM
Subject: Re: component parameter binding question
welcome:)
Like context="contextValue">Delete
Since context is prop binding, it wil
welcome:)
Like Delete
Since context is prop binding, it will map getContextValue() method in java.
Thanks,
DH
- Original Message -
From: "丁振波"
To: "Tapestry users"
Sent: Wednesday, March 04, 2009 5:23 PM
Subject: Re: component parameter binding question
>
Thanks for your reply :)
I used 5.0.18 release version. What param should set in tml's context field
when I use the way do in java?
Delete
- Original Message -
From: "dhning"
To: "Tapestry users"
Sent: Wednesday, March 04, 2009 4:15 PM
Subject
rary
http://code.google.com/p/tapestry5-components/
Thanks
DH
- Original Message -
From: "丁振波"
To: "Tapestry users"
Sent: Wednesday, March 04, 2009 3:34 PM
Subject: component parameter binding question
> Hello guys, below is my case code:
>
>
> ${user.na
Hello guys, below is my case code:
${user.name}
my question is, how can I pass mutil param value in context , is there any
format like "user.id; user.name"?
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.or
Have you had any luck with this?
I'm trying to figure out the same thing...
I have a complicated form that uses several nested components to
implement it. The structure of the form is straightforward, though.
Everything renders just fine, but when the form is being submitted and
the form
Hi All,
I have been struggling with the following problem for quite a while. I
have a custom component for which I have defined a parameter with a
binding type of property. I have the component within a form that is
within a loop on my page. The parameter of my component is bound to the
valu
I am passing in a Select component to a custom component as a parameter.
In the custom component, I would like to retrieve the model parameter from the
passed in Select.
In Tapestry 4,
I would do something like the following.
IBinding bind = PropertySelection.getBinding("model");
Yep, you're right!
Thanks for the example.
-J.
On Mon, 2008-04-14 at 16:09 +0200, Christian Koeberl wrote:
> > inherit: binding - however this doesn't work for me.
> That should work.
>
> With the inherit keyword you can forward parameters to sub-components,
> like this example of a zebra Grid
> inherit: binding - however this doesn't work for me.
That should work.
With the inherit keyword you can forward parameters to sub-components,
like this example of a zebra Grid component:
public class MyGrid
{
@Parameter(required = true)
private GridDataSource source;
@
> I have an embedded component which should render something different
> depending on a component parameter of the component containing the
> embedded component (wow - try to say that quickly ;-).
>
> How can I do that?
>
> -J.
>
>
> -
Hi,
I have an embedded component which should render something different
depending on a component parameter of the component containing the
embedded component (wow - try to say that quickly ;-).
How can I do that?
-J.
-
To
Thanks to Josh this problem has been solved. The culprit was how I
invoked the components. I was using
I should use
Thanks for all help! And a special thank to Josh!
--Alec
Davor Hrg wrote:
how is getRows declared in your page class ?
OK, thanks...
In my page, I have
The columns
I actually got the same idea, just after pushing the send button. It's
quite a task, though, to carve this out. But it's certainly my job.
I'll make a try.
In the meanwhile: an observation. Looking at the breakpoint in
BugPage.getListsource () I can see the call stack. At the top is
Layout.
Hey Alec,
I was hoping for something a little more minimal, but still
complete/compilable. :)
I still can't reproduce the problem, but maybe @Persist on your report
property is the culprit? Try it with out that. That's a shot in the
dark though, so if that doesn't help I think I'll need something
Hm... looking more on your example... Seems that yoyr example and my
ReportSize component are similar and both do indeed work. So it's
something with the Layout component...
--alec
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
Hm... looking more into your example As I understand it, your
example and my ReportSize component are really similar and both do
indeed work demonstrating that *is* possible to pass the arguments. So
it is something with the Layout component...
Feeling dumb, need a better brain.
--alec
Josh Canfield wrote:
Hey Alec,
Looking at small excerpts from a large file leaves too much to the
imagination. Can you create a minimal but complete page and component
that reproduces the problem?
Yes, I should have done it long time ago, I know. Below is the complete
example, removing all o
Hey Alec,
Looking at small excerpts from a large file leaves too much to the
imagination. Can you create a minimal but complete page and component
that reproduces the problem?
It feels like there is a bad return type or something on one of the
methods in the chain, so having a complete non-workin
Collections$SingletonList. (?!)
The value from Layout.getOrvar() (sorry for Swedish foobar name) is 1 i.
e., the size of the Singleton list.
So: somewhere on the way from the page getter getListource() to the
component parameter listSource the value is converted from a List
to a
the page class.
You've shared the component code. Can you share the relevant page code?
(Declaration, initialization, getters and setters...)
Jonathan
-Original Message-
From: Alec Leamas [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 01, 2008 5:27 PM
To: Tapestry users
Subjec
tters and setters...)
Jonathan
> -Original Message-
> From: Alec Leamas [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 01, 2008 5:27 PM
> To: Tapestry users
> Subject: Re: T5, newbie: Component parameter passing problems (#2)
>
> My problem is not just with lists:
hat your MyMap
> > works?
> >
> > If you can present a non-Tapestry test that works, and corresponding
> > Tapestry test that doesn't, then I think you'll find an answer quickly.
> >
> > Jonathan
> >
> >
> >
> >
> >>
e proof that your code works outside of Tapestry? Why, and how,
did you EXTEND TreeMap? Do you have a unit test to prove that your MyMap
works?
If you can present a non-Tapestry test that works, and corresponding
Tapestry test that doesn't, then I think you'll find an answer quickly.
t that works, and corresponding
Tapestry test that doesn't, then I think you'll find an answer quickly.
Jonathan
-Original Message-
From: Alec Leamas [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 01, 2008 8:37 AM
To: Tapestry users
Subject: Re: T5, newbie: Compone
a non-Tapestry test that works, and corresponding
Tapestry test that doesn't, then I think you'll find an answer quickly.
Jonathan
> -Original Message-
> From: Alec Leamas [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 01, 2008 8:37 AM
> To: Tapestry users
> Subj
public List getRows() {...}
Davor Hrg wrote:
how is getRows declared in your page class ?
On Tue, Apr 1, 2008 at 2:09 PM, Michael Kolmodin <[EMAIL PROTECTED]>
wrote:
OK, thanks...
In my page, I have
The columns argument, a List is just fine.
The rows argument, a List is the problem.
how is getRows declared in your page class ?
On Tue, Apr 1, 2008 at 2:09 PM, Michael Kolmodin <[EMAIL PROTECTED]>
wrote:
> OK, thanks...
>
> In my page, I have rows="prop:rows"/>
>
> The columns argument, a List is just fine.
> The rows argument, a List is the problem.
>
> The page has a List
OK, thanks...
In my page, I have
The columns argument, a List is just fine.
The rows argument, a List is the problem.
The page has a List getRows() which is verified.
Looking in MyComponent.java, I have
@Parameter
private List rows;
@Parameter
private List columns;
public S
Tapestry support for Java generics is very limited,
you need a value encoder to make this work,
also, add more details on who calls what... so more is known
of the problem you are trying to solve.
Davor Hrg
On Tue, Apr 1, 2008 at 1:43 PM, Alec Leamas <[EMAIL PROTECTED]> wrote:
> I have problem
I have problems passing my own datatype(s) to my own component. The
component takes two parameters, one List and one List.
MyMap is declared as MyMap extends TreeMap {...}.
The first parameter, a list of strings arrives safely to my component.
However, the other one, seems to be mixed up: whe
Hi,
Every One
I am facing a problem relted to component parameter values.
I have a page which will contain components , these compnents will be
desided by a List of String from the page: If i give a code it will be like
this
o read the value of a component parameter within a
mixin
I think at this time the only option is to hack around Tapestry.
Derive your own TextField in which you can access the value parameter.
The usual component resources don't reveal the full bindings API:
@Inject
ComponentResource
I think at this time the only option is to hack around Tapestry.
Derive your own TextField in which you can access the value parameter.
The usual component resources don't reveal the full bindings API:
@Inject
ComponentResources _resources;
Mixins have only been developed as far as Howar
hi nick, i know about RenderDisabled... it decorates the input tag with a disabled attribute. but i need to render only the values not the input tag and whatever else is rendered... :). do you know how to access the parameter values? The only other alternative i see is to use a if and a block compo
Use the source ... check out how RenderDisabled works:
http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry/corelib/mixins/RenderDisabled.java?view=markup
Cheers,
Nick.
Kristian Marinkovic wrote:
hi,
how can i access the value of a component
hi,
how can i access the value of a component parameter
within a mixin?
i wrote a Editable mixin that can be applied to a TextField
component. If my application state is not EDIT it should short
circuit the TextField rendering (setupRender if false) and instead
only output the value of the
Hi,
I don't understand why ParameterPropertyWorker makes parameter mutator
throw an exception if called over an unbounded parameter. I see this
behaviour as illogic: ParameterPropertyWorker do create a property
field so why not using this field to set the parameter if no binding
is available inste
> > > > Any help appreciated,
> > > > thx,
> > > > Martin
> > > >
> > > >
> > > > On Thu, 2007-07-12 at 09:43 +0200, Martin Grotzke wrote:
> > > > > On Thu, 2007-07-12 at 08:45 +0200, Kristian Marinkovic wrote:
>
gt; > > >
> > > > How is it intended to work, when is a cached parameter reset?
> > > >
> > > > Thanx && cheers,
> > > > Martin
> > > >
> > > >
> > > > >
> > > > >
> > > > > @Parame
, 2007-07-12 at 08:45 +0200, Kristian Marinkovic wrote:
> > > >
> > > > hi martin,
> > > >
> > > > try to set the "cache" attribute of your @Parameter
> > > > annotation of your "currentPage" component parameter
> >
at 08:45 +0200, Kristian Marinkovic wrote:
> > >
> > > hi martin,
> > >
> > > try to set the "cache" attribute of your @Parameter
> > > annotation of your "currentPage" component parameter
> > > to false
> > I tried that,
; cheers,
> > Martin
> >
> >
> > >
> > >
> > > @Parameter(cache=false,...)
> > >
> > > g,
> > > kris
> > >
> > >
> > >
> > > Martin Grotzke
> > > <[EMAIL PROTECTED]>
>
>
> > hi martin,
> >
> > try to set the "cache" attribute of your @Parameter
> > annotation of your "currentPage" component parameter
> > to false
> I tried that, but it didn't solve the issue - same behavior. Debugging
> showe
On Thu, 2007-07-12 at 08:45 +0200, Kristian Marinkovic wrote:
>
> hi martin,
>
> try to set the "cache" attribute of your @Parameter
> annotation of your "currentPage" component parameter
> to false
I tried that, but it didn't solve the i
hi martin,
try to set the "cache" attribute of your @Parameter
annotation of your "currentPage" component parameter
to false
@Parameter(cache=false,...)
g,
kris
Martin Grotzke <[EMAIL PROTECTED]>
11.07.2007 22:20
Bitte antworten an
"Tapestry users"
Hi,
I wrote a simple pager component but one parameter (currentPage)
is not updated in a second request.
In the template I have the following:
In the page class this currentPage accessor:
public int getCurrentPage() {
return _currentPage;
}
which is an int and has the cor
These are beaneditforms editing credit card info, etc. I'll change my
builder methods to re-insert the tap-hibernate form of the DAOs (yay,
tap-ioc!).
Bill
On 6/22/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Are you detaching objects between requests? My strategy would be to
store object
Are you detaching objects between requests? My strategy would be to
store object ids and re-acquire objects on each new request.
On 6/22/07, Bill Holloway <[EMAIL PROTECTED]> wrote:
That's what I'm thinking: The session opened for the action request
is still open when the render request comes
That's what I'm thinking: The session opened for the action request
is still open when the render request comes and opens its session.
Thus, my person object, which is one-to-many with subscription payment
methods, triggers the collection error. I haven't figured out how to
debug this one. My h
Could this be related to the split between the action request and the
render request?
On 6/22/07, Bill Holloway <[EMAIL PROTECTED]> wrote:
wait wait...this is a hibernate error. i wanna go back to
tapestry-hibernate, but then i get "Illegal attempt to assoc.
collection w/ 2 open sessions". Gr
wait wait...this is a hibernate error. i wanna go back to
tapestry-hibernate, but then i get "Illegal attempt to assoc.
collection w/ 2 open sessions". G.
On 6/22/07, Bill Holloway <[EMAIL PROTECTED]> wrote:
Hmmm. Well, now the error is different. Here's my page template:
http://tapest
Hmmm. Well, now the error is different. Here's my page template:
http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
In EditCreditCard.java, onActivate (calling a DAO) gets a good value
for _creditCardInfo. Know that by debugging. Here's some of the
error p
Thanks appreciated!
On 6/21/07, Daniel Jue <[EMAIL PROTECTED]> wrote:
Thanks for your hard work Howard!
On 6/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> ... and I'm uploading new snapshots right now.
>
> On 6/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> > Don't add another bu
Thanks for your hard work Howard!
On 6/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
... and I'm uploading new snapshots right now.
On 6/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> Don't add another bug; I've checked in a change under TAPESTRY-1423.
>
> On 6/21/07, Howard Lewis
... and I'm uploading new snapshots right now.
On 6/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Don't add another bug; I've checked in a change under TAPESTRY-1423.
On 6/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> Ooh. I think I see what's happening ... I may need to re-work
Don't add another bug; I've checked in a change under TAPESTRY-1423.
On 6/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Ooh. I think I see what's happening ... I may need to re-work the fix
a little. I fixed in in terms of the PropertyBindingFactory, but not
as used here, to order proper
Ooh. I think I see what's happening ... I may need to re-work the fix
a little. I fixed in in terms of the PropertyBindingFactory, but not
as used here, to order properties for the BeanModel. Please add a
bug!
On 6/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Interesting! I thought t
Interesting! I thought the bug was fixed. It's supposed to be
working its way up the class hierarchy until it gets to a class it
knows about. I wonder what's up?
On 6/21/07, Bill Holloway <[EMAIL PROTECTED]> wrote:
Should have included this. This is from my Eclipse console upon
closing/re-op
Should have included this. This is from my Eclipse console upon
closing/re-opening the project:
6/21/07 7:30:28 PM CDT: [DEBUG] tapestry-core: resolved to version
5.0.5-20070616.164652-6 from repository tapestry-snapshots
Bill
On 6/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
This is a
Eeek. I'm in 5.0.5-SNAPSHOT:
5.0.5-SNAPSHOT
On 6/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
This is a known bug in 5.0.4 that should be fixed in the
5.0.5-SNAPSHOT. It relates to some classloader issues caused by the
mix of Tapestry, Javassist, Hibernate, and CGLIB.
On 6/21/07,
This is a known bug in 5.0.4 that should be fixed in the
5.0.5-SNAPSHOT. It relates to some classloader issues caused by the
mix of Tapestry, Javassist, Hibernate, and CGLIB.
On 6/21/07, Bill Holloway <[EMAIL PROTECTED]> wrote:
I have a component that needs to edit an object passed in as a
para
1 - 100 of 113 matches
Mail list logo
