Re: Autocompleter probs
Ok Jesse,
I'll try to prepare a sample.tar.gz and attach to jira this evening when
I'll be back home ;-p
On 3/20/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
I can't follow any of this anymore . =p
If someone attaches a very simple example (knowing that referencing
any objects / other things means I'll have to try manually creating
what you probably were doing in anything I can't see) and attaches
it to jira I'll take a look at it.
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED] wrote:
No I did this without the autocompleter outside the @Else :)
-Original Message-
From: Andrea Chiumenti [mailto:[EMAIL PROTECTED]
Sent: 19 March 2007 17:39
To: Tapestry users
Subject: Re: Autocompleter probs
This should work because you have already added a static widget: the
autocompleter (outside the @Else, as you have already done)
kiuma
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED] wrote:
Sorry I was a little too brief in explaining what i did..Take the same
HTML template we have been discussing during the past few days but
instead of
span jwcid=@Else
span jwcid=clientAutoCompleter/
/span
i added the date picker in there, still in the conditional flow so now
it looks like this.
span jwcid=@Else
span jwcid=clientAutoCompleter/
span jwcid=testWidget/
/span
Y
On Mon, 2007-03-19 at 18:25 +0100, Andrea Chiumenti wrote:
No, I didn't mean this,
I wanted to say that if you have something like:
form
if (condition)
a widget component/
/if
/form
shouldn't work
if you don't write another widget (of your choice) that is needed
for
say
'initialization'.
so you should have this to make it work:
form
a widget component of your choice (display:hidden)/
if (condition)
a widget component/
/if
/form
kiuma
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED] wrote:
Something like this?
component id=testWidget type=DropdownDatePicker
binding name=value value=ognl:dateValue /
/component
and
span jwcid=@Else
span jwcid=clientAutoCompleter/
span jwcid=testWidget/
/span
I tested it and the datepicker works fine, as far as rendering and
choosing a date are concerned.
Y
On Mon, 2007-03-19 at 18:12 +0100, Andrea Chiumenti wrote:
This example shouldn't work too, except you ad a 'static' (not
conditional)
widget to the form I think.
html jwcid=@Shell ajaxEnabled=true browserLogLevel=DEBUG
title=Edit Shipment
body jwcid=@Body
span jwcid=pageCss/
span jwcid=tabsScript/
div id=shipmentTabContainer
div id=ccs
form jwcid=[EMAIL PROTECTED]
updateComponents=ognl:{'clientUpdate'}
div
jwcid=[EMAIL PROTECTED]
id
=clientUpdate
div
class=titleTextClient/div
span jwcid=@If
condition=ognl:shipment.client!=null
span
jwcid=@If
condition=ognl:!clientClicked
a
jwcid=
[EMAIL PROTECTED]
updateComponents=ognl:{'clientUpdate'}
listener=listener:clientClick
span
jwcid=clientClient/span
/a
/span
span
jwcid=@Else
span
class=auto_complete jwcid=clientDropdownDatePicker/
/span
/span
/div
input type=submit
jwcid=@Submit
action=listener:doEditClientShipperCons async=ognl:true
value=Save
Changes/
/form
/div
/div
/body
/html
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED]
wrote:
In what respect would the DropdownDatePicker not function ok??
On Mon, 2007-03-19 at 17:49 +0100, Andrea Chiumenti wrote:
Yiannis,
I think it's not an autocompleter problem, I think it's
someway
related
to
widgets in general, you should have the same problem also
with
other
widjets
when they are created with an ajax req., and the form
started
without
one
defined.
For example you should have the same problem if you'd use
the
datepicker.
kiuma
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED]
wrote:
Latest snapshot doesn't emit any errors but it also doesnt
return
any
data (according to firebug) unfortunately. The
autocompleter
outside
Re: Unable to parse OGNL expression
Filed under http://jira.opensymphony.com/browse/OGNL-16
On 20.3.2007 5:45, Jesse Kuhnert wrote:
If you file an issue in
http://jira.opensymphony.com/browse/OGNL I
should be able to fix it tomorrow.
On 3/19/07, Borut Bolčina [EMAIL PROTECTED] wrote:
I am trying to use Tacos 4.1 Tree component.
I generated a skeleton
project with Tapestry 4 Maven archetype and copied SimpleTree files
from
Tacos 4.0.1 sources. Any quick hints on the following error:
Unable to parse OGNL _expression_ 'offsetAttribute + ': ' +
(((contentProvider.hasChildren(value) ? 0 : 1) + treeIterator.depth) *
offset) + 'px;'': Error compiling _expression_ on object
[EMAIL PROTECTED]/tree] with _expression_ node offsetAttribute +
": " + (((contentProvider.hasChildren(value) ? 0 : 1) +
treeIterator.depth) * offset) + "px;" getter body: { return ($w)
((($Tree_8)$2).getOffsetAttribute() + ": " +
ognl.OgnlOps.booleanValue(((net.sf.tacos.model.ITreeContentProvider)(($Tree_8)$2).getContentProvider()).hasChildren((($Tree_8)$2).getValue()))
? 0 : 1 + .getTreeIterator().getDepth() * (($Tree_8)$2).getOffset() +
"px;");} setter body: null
syntax error near "0 : 1 + .getTreeIter"
Here are the dependencies
http://flickr.com/photo_zoom.gne?id=426708374size=o
And some code:
### SimpleTree.html ###
div jwcid="tree" id="tree" style="overflow: auto; width: auto;
height:
auto;"
span jwcid="@Insert" value="ognl:item.name"/
/div
### SimpleTree.page ###
property name="item" /
component id="tree" type="tacos:Tree"
binding name="contentProvider" value="new
com.acme.simpletree.SimpleTreeContentProvider()"/
binding name="value" value="item"/
binding name="nodeLinkAjax" value="ognl:false" /
/component
### SimpleTreeContentProvider.java ###
### Folder.java ###
### Item.java ###
All three copied from Tacos-demo 4.0.1 sources.
Thanks,
Borut
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Re: T5 - radio input
Oh, industrious man! Thank you Howard. ?? Tue, 20 Mar 2007 13:19:11 +0800??Howard Lewis Ship [EMAIL PROTECTED] ?? ??: Certainly for 5.0.4, but I'm back on a Tapestry project full time, so things are going to slow down on T5 for a little bit, as I only have nights and weekends for T5 currently. On 3/19/07, Bogdan Calmac [EMAIL PROTECTED] wrote: Hi all, As far as the features available in T5 I thought it was mentioned that all form elements are already implemented, but today I needed a radio input and I realized it's not available yet. Howard, any ideea when the radio input will be available? Thank you, Bogdan Calmac. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Autocompleter probs
Aye Captain ;-)
On Tue, 2007-03-20 at 00:37 -0400, Jesse Kuhnert wrote:
I can't follow any of this anymore . =p
If someone attaches a very simple example (knowing that referencing
any objects / other things means I'll have to try manually creating
what you probably were doing in anything I can't see) and attaches
it to jira I'll take a look at it.
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED] wrote:
No I did this without the autocompleter outside the @Else :)
-Original Message-
From: Andrea Chiumenti [mailto:[EMAIL PROTECTED]
Sent: 19 March 2007 17:39
To: Tapestry users
Subject: Re: Autocompleter probs
This should work because you have already added a static widget: the
autocompleter (outside the @Else, as you have already done)
kiuma
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED] wrote:
Sorry I was a little too brief in explaining what i did..Take the same
HTML template we have been discussing during the past few days but
instead of
span jwcid=@Else
span jwcid=clientAutoCompleter/
/span
i added the date picker in there, still in the conditional flow so now
it looks like this.
span jwcid=@Else
span jwcid=clientAutoCompleter/
span jwcid=testWidget/
/span
Y
On Mon, 2007-03-19 at 18:25 +0100, Andrea Chiumenti wrote:
No, I didn't mean this,
I wanted to say that if you have something like:
form
if (condition)
a widget component/
/if
/form
shouldn't work
if you don't write another widget (of your choice) that is needed
for
say
'initialization'.
so you should have this to make it work:
form
a widget component of your choice (display:hidden)/
if (condition)
a widget component/
/if
/form
kiuma
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED] wrote:
Something like this?
component id=testWidget type=DropdownDatePicker
binding name=value value=ognl:dateValue /
/component
and
span jwcid=@Else
span jwcid=clientAutoCompleter/
span jwcid=testWidget/
/span
I tested it and the datepicker works fine, as far as rendering and
choosing a date are concerned.
Y
On Mon, 2007-03-19 at 18:12 +0100, Andrea Chiumenti wrote:
This example shouldn't work too, except you ad a 'static' (not
conditional)
widget to the form I think.
html jwcid=@Shell ajaxEnabled=true browserLogLevel=DEBUG
title=Edit Shipment
body jwcid=@Body
span jwcid=pageCss/
span jwcid=tabsScript/
div id=shipmentTabContainer
div id=ccs
form jwcid=[EMAIL PROTECTED]
updateComponents=ognl:{'clientUpdate'}
div
jwcid=[EMAIL PROTECTED]
id
=clientUpdate
div
class=titleTextClient/div
span jwcid=@If
condition=ognl:shipment.client!=null
span
jwcid=@If
condition=ognl:!clientClicked
a
jwcid=
[EMAIL PROTECTED]
updateComponents=ognl:{'clientUpdate'}
listener=listener:clientClick
span
jwcid=clientClient/span
/a
/span
span
jwcid=@Else
span
class=auto_complete jwcid=clientDropdownDatePicker/
/span
/span
/div
input type=submit
jwcid=@Submit
action=listener:doEditClientShipperCons async=ognl:true
value=Save
Changes/
/form
/div
/div
/body
/html
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED]
wrote:
In what respect would the DropdownDatePicker not function ok??
On Mon, 2007-03-19 at 17:49 +0100, Andrea Chiumenti wrote:
Yiannis,
I think it's not an autocompleter problem, I think it's
someway
related
to
widgets in general, you should have the same problem also
with
other
widjets
when they are created with an ajax req., and the form
started
without
one
defined.
For example you should have the same problem if you'd use
the
datepicker.
kiuma
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED]
wrote:
Latest snapshot doesn't emit any errors but it also doesnt
Re: Autocompleter probs
Andrea, I'll be sending you something as well so that you can submit it
too.
Y.
On Tue, 2007-03-20 at 09:23 +0100, Andrea Chiumenti wrote:
Ok Jesse,
I'll try to prepare a sample.tar.gz and attach to jira this evening when
I'll be back home ;-p
On 3/20/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
I can't follow any of this anymore . =p
If someone attaches a very simple example (knowing that referencing
any objects / other things means I'll have to try manually creating
what you probably were doing in anything I can't see) and attaches
it to jira I'll take a look at it.
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED] wrote:
No I did this without the autocompleter outside the @Else :)
-Original Message-
From: Andrea Chiumenti [mailto:[EMAIL PROTECTED]
Sent: 19 March 2007 17:39
To: Tapestry users
Subject: Re: Autocompleter probs
This should work because you have already added a static widget: the
autocompleter (outside the @Else, as you have already done)
kiuma
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED] wrote:
Sorry I was a little too brief in explaining what i did..Take the same
HTML template we have been discussing during the past few days but
instead of
span jwcid=@Else
span jwcid=clientAutoCompleter/
/span
i added the date picker in there, still in the conditional flow so now
it looks like this.
span jwcid=@Else
span jwcid=clientAutoCompleter/
span jwcid=testWidget/
/span
Y
On Mon, 2007-03-19 at 18:25 +0100, Andrea Chiumenti wrote:
No, I didn't mean this,
I wanted to say that if you have something like:
form
if (condition)
a widget component/
/if
/form
shouldn't work
if you don't write another widget (of your choice) that is needed
for
say
'initialization'.
so you should have this to make it work:
form
a widget component of your choice (display:hidden)/
if (condition)
a widget component/
/if
/form
kiuma
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED] wrote:
Something like this?
component id=testWidget type=DropdownDatePicker
binding name=value value=ognl:dateValue /
/component
and
span jwcid=@Else
span jwcid=clientAutoCompleter/
span jwcid=testWidget/
/span
I tested it and the datepicker works fine, as far as rendering and
choosing a date are concerned.
Y
On Mon, 2007-03-19 at 18:12 +0100, Andrea Chiumenti wrote:
This example shouldn't work too, except you ad a 'static' (not
conditional)
widget to the form I think.
html jwcid=@Shell ajaxEnabled=true browserLogLevel=DEBUG
title=Edit Shipment
body jwcid=@Body
span jwcid=pageCss/
span jwcid=tabsScript/
div id=shipmentTabContainer
div id=ccs
form jwcid=[EMAIL PROTECTED]
updateComponents=ognl:{'clientUpdate'}
div
jwcid=[EMAIL PROTECTED]
id
=clientUpdate
div
class=titleTextClient/div
span jwcid=@If
condition=ognl:shipment.client!=null
span
jwcid=@If
condition=ognl:!clientClicked
a
jwcid=
[EMAIL PROTECTED]
updateComponents=ognl:{'clientUpdate'}
listener=listener:clientClick
span
jwcid=clientClient/span
/a
/span
span
jwcid=@Else
span
class=auto_complete jwcid=clientDropdownDatePicker/
/span
/span
/div
input type=submit
jwcid=@Submit
action=listener:doEditClientShipperCons async=ognl:true
value=Save
Changes/
/form
/div
/div
/body
/html
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED]
wrote:
In what respect would the DropdownDatePicker not function ok??
On Mon, 2007-03-19 at 17:49 +0100, Andrea Chiumenti wrote:
Yiannis,
I think it's not an autocompleter problem, I think it's
someway
related
to
widgets in general, you should have the same problem also
with
other
Re: Autocompleter probs
Yiannis,
thank you very much.
kiuma
On 3/20/07, Yiannis Mavroukakis [EMAIL PROTECTED] wrote:
Andrea, I'll be sending you something as well so that you can submit it
too.
Y.
On Tue, 2007-03-20 at 09:23 +0100, Andrea Chiumenti wrote:
Ok Jesse,
I'll try to prepare a sample.tar.gz and attach to jira this evening when
I'll be back home ;-p
On 3/20/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
I can't follow any of this anymore . =p
If someone attaches a very simple example (knowing that referencing
any objects / other things means I'll have to try manually creating
what you probably were doing in anything I can't see) and attaches
it to jira I'll take a look at it.
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED] wrote:
No I did this without the autocompleter outside the @Else :)
-Original Message-
From: Andrea Chiumenti [mailto:[EMAIL PROTECTED]
Sent: 19 March 2007 17:39
To: Tapestry users
Subject: Re: Autocompleter probs
This should work because you have already added a static widget: the
autocompleter (outside the @Else, as you have already done)
kiuma
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED] wrote:
Sorry I was a little too brief in explaining what i did..Take the
same
HTML template we have been discussing during the past few days but
instead of
span jwcid=@Else
span jwcid=clientAutoCompleter/
/span
i added the date picker in there, still in the conditional flow so
now
it looks like this.
span jwcid=@Else
span jwcid=clientAutoCompleter/
span jwcid=testWidget/
/span
Y
On Mon, 2007-03-19 at 18:25 +0100, Andrea Chiumenti wrote:
No, I didn't mean this,
I wanted to say that if you have something like:
form
if (condition)
a widget component/
/if
/form
shouldn't work
if you don't write another widget (of your choice) that is
needed
for
say
'initialization'.
so you should have this to make it work:
form
a widget component of your choice (display:hidden)/
if (condition)
a widget component/
/if
/form
kiuma
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED]
wrote:
Something like this?
component id=testWidget type=DropdownDatePicker
binding name=value value=ognl:dateValue /
/component
and
span jwcid=@Else
span jwcid=clientAutoCompleter/
span jwcid=testWidget/
/span
I tested it and the datepicker works fine, as far as rendering
and
choosing a date are concerned.
Y
On Mon, 2007-03-19 at 18:12 +0100, Andrea Chiumenti wrote:
This example shouldn't work too, except you ad a 'static'
(not
conditional)
widget to the form I think.
html jwcid=@Shell ajaxEnabled=true
browserLogLevel=DEBUG
title=Edit Shipment
body jwcid=@Body
span jwcid=pageCss/
span jwcid=tabsScript/
div id=shipmentTabContainer
div id=ccs
form jwcid=
[EMAIL PROTECTED]
updateComponents=ognl:{'clientUpdate'}
div
jwcid=[EMAIL PROTECTED]
id
=clientUpdate
div
class=titleTextClient/div
span
jwcid=@If
condition=ognl:shipment.client!=null
span
jwcid=@If
condition=ognl:!clientClicked
a
jwcid=
[EMAIL PROTECTED]
updateComponents=ognl:{'clientUpdate'}
listener=listener:clientClick
span
jwcid=clientClient/span
/a
/span
span
jwcid=@Else
span
class=auto_complete jwcid=clientDropdownDatePicker/
/span
/span
/div
input type=submit
jwcid=@Submit
action=listener:doEditClientShipperCons async=ognl:true
value=Save
Changes/
/form
/div
/div
/body
/html
On 3/19/07, Yiannis Mavroukakis [EMAIL PROTECTED]
wrote:
In what respect would the DropdownDatePicker not function
ok??
On Mon, 2007-03-19 at 17:49 +0100, Andrea Chiumenti wrote:
Yiannis,
I think it's not an autocompleter problem, I think it's
someway
Binding Loop parameters
Hi,
Excuse me if this is a silly question but I'm new to Tapestry.
In order to use Loop's value (or index) inside its body, one has to bind it
to some property. Usually this means creating a new property in the page
class.
Here is an example from T5 tutorial.
t:loop source=1..10 value=index
${index}
/t:loop
and in the Java code
private int _index;
public int getIndex()
{
return _index;
}
public void setIndex(int index)
{
_index = index;
}
It seems very clumsy for me to write all this Java code to support a simple
loop.
Can't the Loop component remember its value?
Isn't it possible to use loop's value/index direclty without binding?
Something like this.
t:loop source=1..10 t:id=aLoop
${aLoop.index}
/t:loop
Also, what is the business with those heartbeats in Loop component? I
couldn't understand it from the documentation.
Best regards,
Peter
--
View this message in context:
http://www.nabble.com/Binding-Loop-parameters-tf3433109.html#a9570601
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5 - Jetty - ISO-8859-1 instead of UTF-8; deploying
Hi Igor, On 20/03/07, Igor E. Poteryaev [EMAIL PROTECTED] wrote: PrintWriter pw = response.getPrintWriter(text/html; charset=UTF-8); instead of PrintWriter pw = response.getPrintWriter(text/html); thanks for the suggestion. I had the same thing in mind but have not had time to find the code. I'll use your patch for the time being. Kofa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5 - Context parameters and style sheets links
Hi all, this problem is very nice solved in c:url JSP tag. When the URL is absolute (starting with /) then the context is added before (request.getContextPath()) otherwise the URL is relative and leaved the same as it was. I think it shouldn't be problem to create component solving this problem. Jirka Howard Lewis Ship napsal(a): This is a conscious decision, that you will know early on what the context path will be. The effort to avoid this in T4, using a base tag, caused far more problems than it solved. A solution using query parameters is likewise: it makes your site off-limits to any kind of search engine, and it tends to create longer and less pretty URLs. On 3/12/07, DJ Gredler [EMAIL PROTECTED] wrote: I've never had to operate out of a context other than root, so I've just hardcoded it to /mystyle.css or whatever... On 3/12/07, Bogdan Calmac [EMAIL PROTECTED] wrote: Consider a UserDetail page that has an URL like http://server/context/UserDetail/jdoe;. Here I'm using the tapestry style of passing parameters, as part of the context. The problem here is that if you have a styleset link to mystyle.css, it will try to look for http://server/context/userdetail/mystyle.css which of course does not exit. The alternative to use the full path to the css, /context/mystyle.css is also bad because you don't want to hardcode the name of the context. There are 2 correct solutions to this problem which would be nice to be part of the framework: 1. Allow context information to (optionally) be passed to a page as query parameters, so the above URL would be http://server/context/UserDetail?userid=jdoe;. The relative link to the stylesheet would be fine now, but I don't know if this fits with the design of the framework. 2. Create something like an AssetLink component that takes care to prepend so context, so that: link t:type=AssetLink href=/mystyle.css rel=stylesheet type=text/css/ would generate; link href=/context/mystyle.css rel=stylesheet type=text/css/ I would expect there were others who encountered the same quirk. How did you address it? Thank you, Bogdan Calmac. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jiří Mareš (mailto:[EMAIL PROTECTED]) ČSAD SVT Praha, s.r.o. (http://www.svt.cz) Czech Republic - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tap4 Obtaining assets dynamically
Hi, Well I solved this problem: I just needed to Inject tapestry's ContextAssetFactory, into my component, like this: @InjectObject(service:tapestry.asset.ContextAssetFactory) public abstract AssetFactory getAssetFactory(); Then I invoked the createAbsoluteAsset method on the factory like this: getAssetFactory().createAbsolute(context-path-to-file, getPage().getLocale(),getLocation()); I got this hint by reading the HiveDoc for tapestry, which imho is a little hard to read... regards, miguel On 3/19/07, Miguel Angel Hernández [EMAIL PROTECTED] wrote: Hi all, Does anybody nows a way to obtain Assets dynamically? cheers, miguel
Session
Hello, We have an admin side with a user login etc. The problem is, the session times out after soo many minutes(we run under tomcat) of being idle and they user has to log back in. Is there any way to make this indefinate and if so, is there any impact on resources etc? Thanks, James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
compilation problem with Tapestry 5 tutorial files
Hi all, On attempting to build the hilo project in the Tapestry 5 tutorial, i got a compilation error from Maven with these lines: - D:\projects\hilo\src\main\java\org\example\hilo\services\AppModule.java:[8,43] cannot find symbol symbol : class Contribute location: package org.apache.tapestry.ioc.annotations - And indeed the class org.apache.tapestry.ioc.annotations.Contribute is not there in the local repository. i guess the files have just run out of synce. It's also true with another class in the same package: Id Any ideas? Thanks a lot! celia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why is IE6 freezing? [Solution!]
Hi Andreas,
we have almost the same problem (msie freezing, javascript errors) by using
tomcat + tapestry 4.1 + MSIE.
we hope maybe you could give us some hints how to solve this issue
especially because i see that your web page http://www.fsbutiken.se
doesn't work 100% well on msie, and i thought you are still working on the
fix? did you already realize that your page sometimes returns javascript
errors?
Unfortunatelly, the solution you mentioned earlier doesn't work for as - our
server had all the time the compression flag turned off. the question is
does it really work for you?
we've tested our application using at least three client computers with same
configured msie browsers. Sometimes (but not always) we got the javascript
errors such
tapestry.form object doesn't exist or the msie just start to freeze. These
errors always appear in
conjunction with use of tapestry SubmitLink component. we can not reproduce
that...
best regards,
aleks
Andreas Pardeike-2 wrote:
Thanks Martin,
Yes, I was using this for testing. I have now switched back to my
defaults and
the problem persists.
UPDATE: after E-N-D-L-E-S-S testing, I found the problem:
dojo + tomcat + compression + IE6 - BAD
I commented out
compression=on compressionMinSize=2048
noCompressionUserAgents=gozilla, traviata
compressableMimeType=text/html,text/xml,image/gif
and everything works again.
This took me 5 hours and I can honestly say that I really really
*hate* IE now
(I knew I hated it before, but I didn't realize how deeply).
Andreas Pardeike
On 9 mar 2007, at 18.52, Martin Strand wrote:
Looks like certain dojo files can't be found, you should see some
404s in your logs.
You seem to be using two different dojo urls (/assets/dojo/ and /js/
dojo/)
script type=text/javascriptdjConfig =
{isDebug:false,debugContainerId:debug,baseRelativePath:/
assets/static/
dojo/,preventBackButtonFix:false,parseWidgets:false,locale:en-
gb} /script
script type=text/javascript src=/js/dojo/dojo.js/script
script type=text/javascript
dojo.registerModulePath(tapestry, /assets/static/tapestry);
/script
script type=text/javascript src=/js/tapestry/core.js/script
Not sure exactly what the problem is but perhaps you just need to
change the dojoPath parameter on your Shell
http://tapestry.apache.org/tapestry4.1/components/general/shell.html
On Fri, 09 Mar 2007 18:33:20 +0100, Andreas Pardeike [EMAIL PROTECTED]
wrote:
Hi,
just released our site and now people call in angry telling me that
IE6 freezes on our site. I've tested the site on my local computer
using tomcat and the wonderful Web Project plugin and it works just
fine. When deployed, it does not.
I'm using 4.1.1 and I tried to use the latest dojo.js but it's the
same. Anyone who knows why it's freezing? Interestingly, all other
browsers work fine (although Safari sometimes keeps loading some
elements). The problem can be reproduced when the IE cache is
cleared.
The site: http://www.fsbutiken.se
Help!
Andreas Pardeike
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Why-is-IE6-freezing--tf3377078.html#a9577631
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: compilation problem with Tapestry 5 tutorial files
In the current snapshot of Tapestry 5, Contribute and Id annotations have been removed in favour of convention. You can read about the way things work now on the following sites: http://tapestry.apache.org/tapestry5/tapestry-ioc/module.html -- read up until Cacheing Services for what to do about Id http://tapestry.apache.org/tapestry5/tapestry-ioc/configuration.html Basically replace the @Contribute(serviceName) with a conventional method name: contributeServiceName( ...) Hope this helps On 3/20/07, Celia Mou [EMAIL PROTECTED] wrote: Hi all, On attempting to build the hilo project in the Tapestry 5 tutorial, i got a compilation error from Maven with these lines: - D:\projects\hilo\src\main\java\org\example\hilo\services\AppModule.java:[8,43] cannot find symbol symbol : class Contribute location: package org.apache.tapestry.ioc.annotations - And indeed the class org.apache.tapestry.ioc.annotations.Contribute is not there in the local repository. i guess the files have just run out of synce. It's also true with another class in the same package: Id Any ideas? Thanks a lot! celia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Peter Beshai Computer Science Student University of Waterloo
maven problem following Tapestry 5 Turorial
Hi everyone, i've encountered a problem trying to follow the Tapestry 5 Turorial. When executing mvn jetty:run there is a BUILD ERROR and it says: [INFO] The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid version could be found i wondered perhaps it's because the plugin is not there. i went to Maven's site and couldn't find a list of plugins from this link they provide: http://mirrors.ibiblio.org/pub/mirrors/maven2/plugins/ Does anyone have clues on how to solve this problem? Thanks a lot! celia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tapestry 5 tutorial: classes don't exist on package
Hello. On AppModule class of hilo application (Tapestry 5 tutorial) there are some imports: import org.apache.tapestry.ioc.annotations.Contribute; import org.apache.tapestry.ioc.annotations.Id; but these classes (Contribute and Id) aren't on the tapestry-ioc-5.0.3.jarpackage... Where are them? Thanks
Re: Tapestry 5 tutorial: classes don't exist on package
Because the tutorial is currently out of date with respect to the code-base. tapestry-ioc switched to flat namespacing which resulted in not needing Contribute or Id. Robert On Mar 20, 2007, at 3/202:54 PM , acarrara wrote: Hello. On AppModule class of hilo application (Tapestry 5 tutorial) there are some imports: import org.apache.tapestry.ioc.annotations.Contribute; import org.apache.tapestry.ioc.annotations.Id; but these classes (Contribute and Id) aren't on the tapestry-ioc-5.0.3.jarpackage... Where are them? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
T5 ASO
Hi I am trying to use few ASO's so share data across the pages. I have declared the following, but looks like if one gets a value, the second varaible also gets the same value. Is it not possible to define different ASO's of same type? @ApplicationState private String enterprisePrice; @ApplicationState private String clientPrice; i saw this in the T5 website Any other component or page that declares a field of the same type, regardless of name, and marks it with the ApplicationState annotation will share the same value. . So is it not possible to have two different ASO's os same type? Thanks! Anjana Gopinath [EMAIL PROTECTED]
downloading Tapestry 5
Hello. Is the package of Tapestry 5 consists only of the files: tapestry-core-5.0.3.jar tapestry-ioc-5.0.3.jar tapestry-test-5.0.3.jar ? If not, where can I download the rest of them? Despite the tutorial says ... Tapestry 5.0.2 You should not have to download this directly; as we'll see, Maven should take care of downloading Tapestry, and its dependencies, as needed. ... the command: mvn archetype:create ↵ -DarchetypeGroupId=org.apache.tapestry ↵ -DarchetypeArtifactId=quickstart ↵ -DarchetypeVersion=5.0.3 ↵ -DgroupId=org.example ↵ -DartifactId=hilo ↵ -DpackageName=org.example.hilo doesn't download any jar file, only the structure and other files (xml, java etc). Thanks a lot.
Re: T5 ASO
Correct. Why not create, say, a Pricing object with enterprisePrice and clientPrice properties? Then you could do: @ApplicationState private Pricing _pricing; Then you have one less injection to do/page that requires pricing information. :) Robert On Mar 20, 2007, at 3/203:26 PM , Anjana Gopinath wrote: Hi I am trying to use few ASO's so share data across the pages. I have declared the following, but looks like if one gets a value, the second varaible also gets the same value. Is it not possible to define different ASO's of same type? @ApplicationState private String enterprisePrice; @ApplicationState private String clientPrice; i saw this in the T5 website Any other component or page that declares a field of the same type, regardless of name, and marks it with the ApplicationState annotation will share the same value. . So is it not possible to have two different ASO's os same type? Thanks! Anjana Gopinath [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: downloading Tapestry 5
Minor typo there about the version number; it is a work in progress and it's very hard to keep everything coordinated. You'll see the Tapestry JARs downloaded when you try to compile and run the application. On 3/20/07, acarrara [EMAIL PROTECTED] wrote: Hello. Is the package of Tapestry 5 consists only of the files: tapestry-core-5.0.3.jar tapestry-ioc-5.0.3.jar tapestry-test-5.0.3.jar ? If not, where can I download the rest of them? Despite the tutorial says ... Tapestry 5.0.2 You should not have to download this directly; as we'll see, Maven should take care of downloading Tapestry, and its dependencies, as needed. ... the command: mvn archetype:create ↵ -DarchetypeGroupId=org.apache.tapestry ↵ -DarchetypeArtifactId=quickstart ↵ -DarchetypeVersion=5.0.3 ↵ -DgroupId=org.example ↵ -DartifactId=hilo ↵ -DpackageName=org.example.hilo doesn't download any jar file, only the structure and other files (xml, java etc). Thanks a lot. -- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
Re: T5 ASO
Thanks Robert for responding. I can do that, but was wondering why there is a restriction like this? Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 4:29 PM, Robert Zeigler wrote: Correct. Why not create, say, a Pricing object with enterprisePrice and clientPrice properties? Then you could do: @ApplicationState private Pricing _pricing; Then you have one less injection to do/page that requires pricing information. :) Robert On Mar 20, 2007, at 3/203:26 PM , Anjana Gopinath wrote: Hi I am trying to use few ASO's so share data across the pages. I have declared the following, but looks like if one gets a value, the second varaible also gets the same value. Is it not possible to define different ASO's of same type? @ApplicationState private String enterprisePrice; @ApplicationState private String clientPrice; i saw this in the T5 website Any other component or page that declares a field of the same type, regardless of name, and marks it with the ApplicationState annotation will share the same value. . So is it not possible to have two different ASO's os same type? Thanks! Anjana Gopinath [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5 ASO
I see it as simplification rather than a restriction. I guess I don't normally store application state in a bunch of separate strings; rather, I always store state in one or more POJO's, exactly analogous to the Pricing object. So, for me, less mess, because I don't have to have a bunch of extra string properties in my page, and less mess because I don't have to constantly refer to what I called some variable on some other page. Robert On Mar 20, 2007, at 3/203:35 PM , Anjana Gopinath wrote: Thanks Robert for responding. I can do that, but was wondering why there is a restriction like this? Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 4:29 PM, Robert Zeigler wrote: Correct. Why not create, say, a Pricing object with enterprisePrice and clientPrice properties? Then you could do: @ApplicationState private Pricing _pricing; Then you have one less injection to do/page that requires pricing information. :) Robert On Mar 20, 2007, at 3/203:26 PM , Anjana Gopinath wrote: Hi I am trying to use few ASO's so share data across the pages. I have declared the following, but looks like if one gets a value, the second varaible also gets the same value. Is it not possible to define different ASO's of same type? @ApplicationState private String enterprisePrice; @ApplicationState private String clientPrice; i saw this in the T5 website Any other component or page that declares a field of the same type, regardless of name, and marks it with the ApplicationState annotation will share the same value. . So is it not possible to have two different ASO's os same type? Thanks! Anjana Gopinath [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
T5 vs T4 vs Community
Hello, We are developing application based on T4.1. We have one T4 in production. And quite disappointed by the situation happening with Tapestry right now. Let me explain it from _my_ personal point of view. 1. Investments in T4 are lost. Application will not be portable to T5. 2. Project lead is only participating in the discussion of the T5 questions on the mail list. 3. T4.1 is in deep development and release plan is _very_ unclear. Development will the development of T4.1 ever come to some meaningful conclusion? Feature stability? Snapshot releases can be broken any time. I haven't seen any non-snapshot release of 4.1.X so far. Latest update of the new OGNL version? Was was the reason for that? Less stability? One snapshot depends on another snapshot? I have a serious fear that 4.1 will never see the release. In half a year (?) T5 is planned to be released? How important for project lead and project team stability of the framework? I can understand the pursuit of new fancy features and improvements, but never the less how do you see the project plan? How do you see migration path from 4 to 5, from 4.1 to 5? How do you see AJAX and JSON features to be implemented in 5.0? Wouldn't it be better to made some conclusion in 4.1 and put all efforts in 5.0? -- Best regards, Renat Zubairov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5 ASO
Robert Thanks for explaining and i perfectly understand your point. But i still feel this is a restriction as i cant have ASOs of same type. Anyway, right now i can continue with the way you suggested. Thanks! Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 4:55 PM, Robert Zeigler wrote: I see it as simplification rather than a restriction. I guess I don't normally store application state in a bunch of separate strings; rather, I always store state in one or more POJO's, exactly analogous to the Pricing object. So, for me, less mess, because I don't have to have a bunch of extra string properties in my page, and less mess because I don't have to constantly refer to what I called some variable on some other page. Robert On Mar 20, 2007, at 3/203:35 PM , Anjana Gopinath wrote: Thanks Robert for responding. I can do that, but was wondering why there is a restriction like this? Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 4:29 PM, Robert Zeigler wrote: Correct. Why not create, say, a Pricing object with enterprisePrice and clientPrice properties? Then you could do: @ApplicationState private Pricing _pricing; Then you have one less injection to do/page that requires pricing information. :) Robert On Mar 20, 2007, at 3/203:26 PM , Anjana Gopinath wrote: Hi I am trying to use few ASO's so share data across the pages. I have declared the following, but looks like if one gets a value, the second varaible also gets the same value. Is it not possible to define different ASO's of same type? @ApplicationState private String enterprisePrice; @ApplicationState private String clientPrice; i saw this in the T5 website Any other component or page that declares a field of the same type, regardless of name, and marks it with the ApplicationState annotation will share the same value. . So is it not possible to have two different ASO's os same type? Thanks! Anjana Gopinath [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5 ASO
T4 allowed multiple ASOs of the same type, however each and every ASO had to be defined with a unique name, plus an XML snippet to identify how to instantiate it. This violated the Dont Repeat Yourself principle, since you had to know and repeat the ASO name on every use throughout the application. T5 simplifies this; the ASO name is simply the fully qualified class name and, in lieu of a definition (which is optional), Tapestry will simply instantiate the class by its default constructor. This doesn't work if you are trying to store many simple values, such as a few Strings, but that's not how ASOs are designed to be used. They are expected to contain a collection of typed properties that will be used individually or in conjunction throughout the application. So this is a trade off ... a feature that was not used (multiple ASOs of the same type), or at least, not widely used (and easily worked around) vs. extra duplicated effort (knowing and using the name). On 3/20/07, Anjana Gopinath [EMAIL PROTECTED] wrote: Robert Thanks for explaining and i perfectly understand your point. But i still feel this is a restriction as i cant have ASOs of same type. Anyway, right now i can continue with the way you suggested. Thanks! Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 4:55 PM, Robert Zeigler wrote: I see it as simplification rather than a restriction. I guess I don't normally store application state in a bunch of separate strings; rather, I always store state in one or more POJO's, exactly analogous to the Pricing object. So, for me, less mess, because I don't have to have a bunch of extra string properties in my page, and less mess because I don't have to constantly refer to what I called some variable on some other page. Robert On Mar 20, 2007, at 3/203:35 PM , Anjana Gopinath wrote: Thanks Robert for responding. I can do that, but was wondering why there is a restriction like this? Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 4:29 PM, Robert Zeigler wrote: Correct. Why not create, say, a Pricing object with enterprisePrice and clientPrice properties? Then you could do: @ApplicationState private Pricing _pricing; Then you have one less injection to do/page that requires pricing information. :) Robert On Mar 20, 2007, at 3/203:26 PM , Anjana Gopinath wrote: Hi I am trying to use few ASO's so share data across the pages. I have declared the following, but looks like if one gets a value, the second varaible also gets the same value. Is it not possible to define different ASO's of same type? @ApplicationState private String enterprisePrice; @ApplicationState private String clientPrice; i saw this in the T5 website Any other component or page that declares a field of the same type, regardless of name, and marks it with the ApplicationState annotation will share the same value. . So is it not possible to have two different ASO's os same type? Thanks! Anjana Gopinath [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5,page template location ?
/WEB-INF/test/TestForm.html On 3/19/07, Jun Tsai [EMAIL PROTECTED] wrote: I had read http://tapestry.apache.org/tapestry5/tapestry-core/guide/templates.html,but my webapp structure is /images/xx.gif /test/TestForm.html /WEB-INF/web.xml How to do? ps:I think the structure is best for dreamweaver. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5 ASO
Thanks Howard for explaining. It makes sense. But what if i want to store a list of objects as a ASO? For example public ArrayListApplication appList; public ArrayListNetwork networkList; Both the above are of type List, but list of two objects. Will this be an issue? Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 5:38 PM, Howard Lewis Ship wrote: T4 allowed multiple ASOs of the same type, however each and every ASO had to be defined with a unique name, plus an XML snippet to identify how to instantiate it. This violated the Dont Repeat Yourself principle, since you had to know and repeat the ASO name on every use throughout the application. T5 simplifies this; the ASO name is simply the fully qualified class name and, in lieu of a definition (which is optional), Tapestry will simply instantiate the class by its default constructor. This doesn't work if you are trying to store many simple values, such as a few Strings, but that's not how ASOs are designed to be used. They are expected to contain a collection of typed properties that will be used individually or in conjunction throughout the application. So this is a trade off ... a feature that was not used (multiple ASOs of the same type), or at least, not widely used (and easily worked around) vs. extra duplicated effort (knowing and using the name). On 3/20/07, Anjana Gopinath [EMAIL PROTECTED] wrote: Robert Thanks for explaining and i perfectly understand your point. But i still feel this is a restriction as i cant have ASOs of same type. Anyway, right now i can continue with the way you suggested. Thanks! Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 4:55 PM, Robert Zeigler wrote: I see it as simplification rather than a restriction. I guess I don't normally store application state in a bunch of separate strings; rather, I always store state in one or more POJO's, exactly analogous to the Pricing object. So, for me, less mess, because I don't have to have a bunch of extra string properties in my page, and less mess because I don't have to constantly refer to what I called some variable on some other page. Robert On Mar 20, 2007, at 3/203:35 PM , Anjana Gopinath wrote: Thanks Robert for responding. I can do that, but was wondering why there is a restriction like this? Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 4:29 PM, Robert Zeigler wrote: Correct. Why not create, say, a Pricing object with enterprisePrice and clientPrice properties? Then you could do: @ApplicationState private Pricing _pricing; Then you have one less injection to do/page that requires pricing information. :) Robert On Mar 20, 2007, at 3/203:26 PM , Anjana Gopinath wrote: Hi I am trying to use few ASO's so share data across the pages. I have declared the following, but looks like if one gets a value, the second varaible also gets the same value. Is it not possible to define different ASO's of same type? @ApplicationState private String enterprisePrice; @ApplicationState private String clientPrice; i saw this in the T5 website Any other component or page that declares a field of the same type, regardless of name, and marks it with the ApplicationState annotation will share the same value. . So is it not possible to have two different ASO's os same type? Thanks! Anjana Gopinath [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5 ASO
Tapestry works its magic using runtime type information, and since generics in java were implemented using type erasure, the two types will be the same at runtime. So you'll need to wrap the two lists in some type of enclosure, just like with the pricing information. Robert On Mar 20, 2007, at 3/204:43 PM , Anjana Gopinath wrote: Thanks Howard for explaining. It makes sense. But what if i want to store a list of objects as a ASO? For example public ArrayListApplication appList; public ArrayListNetwork networkList; Both the above are of type List, but list of two objects. Will this be an issue? Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 5:38 PM, Howard Lewis Ship wrote: T4 allowed multiple ASOs of the same type, however each and every ASO had to be defined with a unique name, plus an XML snippet to identify how to instantiate it. This violated the Dont Repeat Yourself principle, since you had to know and repeat the ASO name on every use throughout the application. T5 simplifies this; the ASO name is simply the fully qualified class name and, in lieu of a definition (which is optional), Tapestry will simply instantiate the class by its default constructor. This doesn't work if you are trying to store many simple values, such as a few Strings, but that's not how ASOs are designed to be used. They are expected to contain a collection of typed properties that will be used individually or in conjunction throughout the application. So this is a trade off ... a feature that was not used (multiple ASOs of the same type), or at least, not widely used (and easily worked around) vs. extra duplicated effort (knowing and using the name). On 3/20/07, Anjana Gopinath [EMAIL PROTECTED] wrote: Robert Thanks for explaining and i perfectly understand your point. But i still feel this is a restriction as i cant have ASOs of same type. Anyway, right now i can continue with the way you suggested. Thanks! Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 4:55 PM, Robert Zeigler wrote: I see it as simplification rather than a restriction. I guess I don't normally store application state in a bunch of separate strings; rather, I always store state in one or more POJO's, exactly analogous to the Pricing object. So, for me, less mess, because I don't have to have a bunch of extra string properties in my page, and less mess because I don't have to constantly refer to what I called some variable on some other page. Robert On Mar 20, 2007, at 3/203:35 PM , Anjana Gopinath wrote: Thanks Robert for responding. I can do that, but was wondering why there is a restriction like this? Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 4:29 PM, Robert Zeigler wrote: Correct. Why not create, say, a Pricing object with enterprisePrice and clientPrice properties? Then you could do: @ApplicationState private Pricing _pricing; Then you have one less injection to do/page that requires pricing information. :) Robert On Mar 20, 2007, at 3/203:26 PM , Anjana Gopinath wrote: Hi I am trying to use few ASO's so share data across the pages. I have declared the following, but looks like if one gets a value, the second varaible also gets the same value. Is it not possible to define different ASO's of same type? @ApplicationState private String enterprisePrice; @ApplicationState private String clientPrice; i saw this in the T5 website Any other component or page that declares a field of the same type, regardless of name, and marks it with the ApplicationState annotation will share the same value. . So is it not possible to have two different ASO's os same type? Thanks! Anjana Gopinath [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5 ASO
Thanks Robert! Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 5:47 PM, Robert Zeigler wrote: Tapestry works its magic using runtime type information, and since generics in java were implemented using type erasure, the two types will be the same at runtime. So you'll need to wrap the two lists in some type of enclosure, just like with the pricing information. Robert On Mar 20, 2007, at 3/204:43 PM , Anjana Gopinath wrote: Thanks Howard for explaining. It makes sense. But what if i want to store a list of objects as a ASO? For example public ArrayListApplication appList; public ArrayListNetwork networkList; Both the above are of type List, but list of two objects. Will this be an issue? Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 5:38 PM, Howard Lewis Ship wrote: T4 allowed multiple ASOs of the same type, however each and every ASO had to be defined with a unique name, plus an XML snippet to identify how to instantiate it. This violated the Dont Repeat Yourself principle, since you had to know and repeat the ASO name on every use throughout the application. T5 simplifies this; the ASO name is simply the fully qualified class name and, in lieu of a definition (which is optional), Tapestry will simply instantiate the class by its default constructor. This doesn't work if you are trying to store many simple values, such as a few Strings, but that's not how ASOs are designed to be used. They are expected to contain a collection of typed properties that will be used individually or in conjunction throughout the application. So this is a trade off ... a feature that was not used (multiple ASOs of the same type), or at least, not widely used (and easily worked around) vs. extra duplicated effort (knowing and using the name). On 3/20/07, Anjana Gopinath [EMAIL PROTECTED] wrote: Robert Thanks for explaining and i perfectly understand your point. But i still feel this is a restriction as i cant have ASOs of same type. Anyway, right now i can continue with the way you suggested. Thanks! Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 4:55 PM, Robert Zeigler wrote: I see it as simplification rather than a restriction. I guess I don't normally store application state in a bunch of separate strings; rather, I always store state in one or more POJO's, exactly analogous to the Pricing object. So, for me, less mess, because I don't have to have a bunch of extra string properties in my page, and less mess because I don't have to constantly refer to what I called some variable on some other page. Robert On Mar 20, 2007, at 3/203:35 PM , Anjana Gopinath wrote: Thanks Robert for responding. I can do that, but was wondering why there is a restriction like this? Anjana Gopinath True North Technology 11465 John's Creek Parkway, Suite 300 Duluth, GA 30079 [EMAIL PROTECTED] On Mar 20, 2007, at 4:29 PM, Robert Zeigler wrote: Correct. Why not create, say, a Pricing object with enterprisePrice and clientPrice properties? Then you could do: @ApplicationState private Pricing _pricing; Then you have one less injection to do/page that requires pricing information. :) Robert On Mar 20, 2007, at 3/203:26 PM , Anjana Gopinath wrote: Hi I am trying to use few ASO's so share data across the pages. I have declared the following, but looks like if one gets a value, the second varaible also gets the same value. Is it not possible to define different ASO's of same type? @ApplicationState private String enterprisePrice; @ApplicationState private String clientPrice; i saw this in the T5 website Any other component or page that declares a field of the same type, regardless of name, and marks it with the ApplicationState annotation will share the same value. . So is it not possible to have two different ASO's os same type? Thanks! Anjana Gopinath [EMAIL PROTECTED] --- - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New OGNL version problem
Hi Jesse, Sorry, I can't do that. We've already spent about 13 hours analyzing this problem because it is quite critical for our project, however we can't create a component with artificial parameters (Tapestry testing package creating only those which abstract methods - which is quite ok for normal testing). Evaluation expression is quite simple valueOne || valueTwo where valueTwo is artificial one. Another possibility would be offcourse for you to checkout our project from the repository on http://code.google.com/p/bookie And launch bookie-jetty project (which will launch tweaked jetty 6.0). Renat On 20/03/07, Jesse Kuhnert [EMAIL PROTECTED] wrote: Hi Renat, Do you think you could provide me with a sample expression string and corresponding description of what objects are involved in the expression and file the issue here? : http://jira.opensymphony.com/browse/OGNL On 3/20/07, Renat Zubairov [EMAIL PROTECTED] wrote: Hello We have a problem with latest 2.7 OGNL snapshot. It seems that OGNL is not capable to read properties that are purely artificial - only declared in the *.page or *.jwc files and has no abstract accessors in the java classes. The exceptions are very wired, sometimes it's simply javassist.compiler.CompileError: ; is missing Sometimes different: Unable to parse OGNL expression 'menuItems': Error compiling expression on object [EMAIL PROTECTED]/border.menu] with expression node menuItems getter body: null setter body: null In all cases class HiveMindExpressionCompiler is participating in the stacktrace. -- Best regards, Renat Zubairov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Best regards, Renat Zubairov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New OGNL version problem
What does artificial mean in this instance? I'd love to help, but if you aren't willing to give me the information I need then I guess you're on your own...Sorry. On 3/20/07, Renat Zubairov [EMAIL PROTECTED] wrote: Hi Jesse, Sorry, I can't do that. We've already spent about 13 hours analyzing this problem because it is quite critical for our project, however we can't create a component with artificial parameters (Tapestry testing package creating only those which abstract methods - which is quite ok for normal testing). Evaluation expression is quite simple valueOne || valueTwo where valueTwo is artificial one. Another possibility would be offcourse for you to checkout our project from the repository on http://code.google.com/p/bookie And launch bookie-jetty project (which will launch tweaked jetty 6.0). Renat On 20/03/07, Jesse Kuhnert [EMAIL PROTECTED] wrote: Hi Renat, Do you think you could provide me with a sample expression string and corresponding description of what objects are involved in the expression and file the issue here? : http://jira.opensymphony.com/browse/OGNL On 3/20/07, Renat Zubairov [EMAIL PROTECTED] wrote: Hello We have a problem with latest 2.7 OGNL snapshot. It seems that OGNL is not capable to read properties that are purely artificial - only declared in the *.page or *.jwc files and has no abstract accessors in the java classes. The exceptions are very wired, sometimes it's simply javassist.compiler.CompileError: ; is missing Sometimes different: Unable to parse OGNL expression 'menuItems': Error compiling expression on object [EMAIL PROTECTED]/border.menu] with expression node menuItems getter body: null setter body: null In all cases class HiveMindExpressionCompiler is participating in the stacktrace. -- Best regards, Renat Zubairov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Best regards, Renat Zubairov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New OGNL version problem
Sorry for the wording,
Under artificial property I ment a property that is not appearing in
the component/page class as normal or abstract getter/setter.
Artificial property - property declared in the .jwc or .page files.
For example you might have a component called Basket
You will have a Basket.java -
public abstract class BasketComponent extends BaseComponent {
public abstract boolean isProperty();
}
Then you will have a component descriptor
Basket.jwc
component ... ... class=... ... BasketComponent
property name=property/
property name=artificialProperty initial-value=false/
/component
As you can see component has two properties property and
artificial. One of them appears in the java class as abstract
getter, another one do not appear anywhere except component
specification, however component specification may contain a OGNL
expression with all it's properties:
In this case property || artificialProperty which brings the error.
Links to the source code:
Java class:
http://bookie.googlecode.com/svn/trunk/bookie-web/src/main/java/org/bookie/web/components/TabPanel.java
JWC descriptor:
http://bookie.googlecode.com/svn/trunk/bookie-web/src/main/webapp/WEB-INF/TabPanel.jwc
Error appearing in:
component id=link type=DirectLink
binding name=listener value=listener:doClick/
binding name=parameters value=blockId/
binding name=disabled value=ognl: tabSelected || readonly/
binding name=async value=ognl: !(tabSelected || readonly)/
/component
When evaluating
ognl: tabSelected || readonly
Renat
On 20/03/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
What does artificial mean in this instance?
I'd love to help, but if you aren't willing to give me the information
I need then I guess you're on your own...Sorry.
On 3/20/07, Renat Zubairov [EMAIL PROTECTED] wrote:
Hi Jesse,
Sorry, I can't do that. We've already spent about 13 hours analyzing
this problem because it is quite critical for our project, however we
can't create a component with artificial parameters (Tapestry testing
package creating only those which abstract methods - which is quite ok
for normal testing).
Evaluation expression is quite simple valueOne || valueTwo where
valueTwo is artificial one.
Another possibility would be offcourse for you to checkout our project
from the repository on
http://code.google.com/p/bookie
And launch bookie-jetty project (which will launch tweaked jetty 6.0).
Renat
On 20/03/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
Hi Renat,
Do you think you could provide me with a sample expression string and
corresponding description of what objects are involved in the
expression and file the issue here? :
http://jira.opensymphony.com/browse/OGNL
On 3/20/07, Renat Zubairov [EMAIL PROTECTED] wrote:
Hello
We have a problem with latest 2.7 OGNL snapshot.
It seems that OGNL is not capable to read properties that are purely
artificial - only declared in the *.page or *.jwc files and has no
abstract accessors in the java classes.
The exceptions are very wired, sometimes it's simply
javassist.compiler.CompileError: ; is missing
Sometimes different:
Unable to parse OGNL expression 'menuItems': Error compiling
expression on object [EMAIL PROTECTED]/border.menu] with
expression node menuItems getter body: null setter body: null
In all cases class HiveMindExpressionCompiler is participating in the
stacktrace.
--
Best regards,
Renat Zubairov
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Best regards,
Renat Zubairov
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Best regards,
Renat Zubairov
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: New OGNL version problem
Ok it's been filed - you can monitor progress via
http://jira.opensymphony.com/browse/OGNL-17
On 3/20/07, Renat Zubairov [EMAIL PROTECTED] wrote:
Sorry for the wording,
Under artificial property I ment a property that is not appearing in
the component/page class as normal or abstract getter/setter.
Artificial property - property declared in the .jwc or .page files.
For example you might have a component called Basket
You will have a Basket.java -
public abstract class BasketComponent extends BaseComponent {
public abstract boolean isProperty();
}
Then you will have a component descriptor
Basket.jwc
component ... ... class=... ... BasketComponent
property name=property/
property name=artificialProperty initial-value=false/
/component
As you can see component has two properties property and
artificial. One of them appears in the java class as abstract
getter, another one do not appear anywhere except component
specification, however component specification may contain a OGNL
expression with all it's properties:
In this case property || artificialProperty which brings the error.
Links to the source code:
Java class:
http://bookie.googlecode.com/svn/trunk/bookie-web/src/main/java/org/bookie/web/components/TabPanel.java
JWC descriptor:
http://bookie.googlecode.com/svn/trunk/bookie-web/src/main/webapp/WEB-INF/TabPanel.jwc
Error appearing in:
component id=link type=DirectLink
binding name=listener value=listener:doClick/
binding name=parameters value=blockId/
binding name=disabled value=ognl: tabSelected || readonly/
binding name=async value=ognl: !(tabSelected || readonly)/
/component
When evaluating
ognl: tabSelected || readonly
Renat
On 20/03/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
What does artificial mean in this instance?
I'd love to help, but if you aren't willing to give me the information
I need then I guess you're on your own...Sorry.
On 3/20/07, Renat Zubairov [EMAIL PROTECTED] wrote:
Hi Jesse,
Sorry, I can't do that. We've already spent about 13 hours analyzing
this problem because it is quite critical for our project, however we
can't create a component with artificial parameters (Tapestry testing
package creating only those which abstract methods - which is quite ok
for normal testing).
Evaluation expression is quite simple valueOne || valueTwo where
valueTwo is artificial one.
Another possibility would be offcourse for you to checkout our project
from the repository on
http://code.google.com/p/bookie
And launch bookie-jetty project (which will launch tweaked jetty 6.0).
Renat
On 20/03/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
Hi Renat,
Do you think you could provide me with a sample expression string and
corresponding description of what objects are involved in the
expression and file the issue here? :
http://jira.opensymphony.com/browse/OGNL
On 3/20/07, Renat Zubairov [EMAIL PROTECTED] wrote:
Hello
We have a problem with latest 2.7 OGNL snapshot.
It seems that OGNL is not capable to read properties that are purely
artificial - only declared in the *.page or *.jwc files and has no
abstract accessors in the java classes.
The exceptions are very wired, sometimes it's simply
javassist.compiler.CompileError: ; is missing
Sometimes different:
Unable to parse OGNL expression 'menuItems': Error compiling
expression on object [EMAIL PROTECTED]/border.menu] with
expression node menuItems getter body: null setter body: null
In all cases class HiveMindExpressionCompiler is participating in the
stacktrace.
--
Best regards,
Renat Zubairov
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Best regards,
Renat Zubairov
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Best regards,
Renat Zubairov
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Re: New OGNL version problem
Thanks!
On 20/03/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
Ok it's been filed - you can monitor progress via
http://jira.opensymphony.com/browse/OGNL-17
On 3/20/07, Renat Zubairov [EMAIL PROTECTED] wrote:
Sorry for the wording,
Under artificial property I ment a property that is not appearing in
the component/page class as normal or abstract getter/setter.
Artificial property - property declared in the .jwc or .page files.
For example you might have a component called Basket
You will have a Basket.java -
public abstract class BasketComponent extends BaseComponent {
public abstract boolean isProperty();
}
Then you will have a component descriptor
Basket.jwc
component ... ... class=... ... BasketComponent
property name=property/
property name=artificialProperty initial-value=false/
/component
As you can see component has two properties property and
artificial. One of them appears in the java class as abstract
getter, another one do not appear anywhere except component
specification, however component specification may contain a OGNL
expression with all it's properties:
In this case property || artificialProperty which brings the error.
Links to the source code:
Java class:
http://bookie.googlecode.com/svn/trunk/bookie-web/src/main/java/org/bookie/web/components/TabPanel.java
JWC descriptor:
http://bookie.googlecode.com/svn/trunk/bookie-web/src/main/webapp/WEB-INF/TabPanel.jwc
Error appearing in:
component id=link type=DirectLink
binding name=listener value=listener:doClick/
binding name=parameters value=blockId/
binding name=disabled value=ognl: tabSelected || readonly/
binding name=async value=ognl: !(tabSelected || readonly)/
/component
When evaluating
ognl: tabSelected || readonly
Renat
On 20/03/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
What does artificial mean in this instance?
I'd love to help, but if you aren't willing to give me the information
I need then I guess you're on your own...Sorry.
On 3/20/07, Renat Zubairov [EMAIL PROTECTED] wrote:
Hi Jesse,
Sorry, I can't do that. We've already spent about 13 hours analyzing
this problem because it is quite critical for our project, however we
can't create a component with artificial parameters (Tapestry testing
package creating only those which abstract methods - which is quite ok
for normal testing).
Evaluation expression is quite simple valueOne || valueTwo where
valueTwo is artificial one.
Another possibility would be offcourse for you to checkout our project
from the repository on
http://code.google.com/p/bookie
And launch bookie-jetty project (which will launch tweaked jetty 6.0).
Renat
On 20/03/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
Hi Renat,
Do you think you could provide me with a sample expression string and
corresponding description of what objects are involved in the
expression and file the issue here? :
http://jira.opensymphony.com/browse/OGNL
On 3/20/07, Renat Zubairov [EMAIL PROTECTED] wrote:
Hello
We have a problem with latest 2.7 OGNL snapshot.
It seems that OGNL is not capable to read properties that are purely
artificial - only declared in the *.page or *.jwc files and has no
abstract accessors in the java classes.
The exceptions are very wired, sometimes it's simply
javassist.compiler.CompileError: ; is missing
Sometimes different:
Unable to parse OGNL expression 'menuItems': Error compiling
expression on object [EMAIL PROTECTED]/border.menu] with
expression node menuItems getter body: null setter body: null
In all cases class HiveMindExpressionCompiler is participating in the
stacktrace.
--
Best regards,
Renat Zubairov
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Best regards,
Renat Zubairov
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Re: T5 vs T4 vs Community
Hi Renat, Sorry to hear about your frustrations. I will try to address each point inline below. On 3/20/07, Renat Zubairov [EMAIL PROTECTED] wrote: Hello, We are developing application based on T4.1. We have one T4 in production. And quite disappointed by the situation happening with Tapestry right now. Let me explain it from _my_ personal point of view. 1. Investments in T4 are lost. Application will not be portable to T5. I don't think anyone has said T4 investments will be lost. I've stated many times already that I'll be writing some sort of upgrade kit for one version of tapestry to T5. I think I've already sort of made up my mind that this will be T4 - T5. (of course anyone can change that with $$ ) On this very list I've seen people talking about running some form of hivemind services with the new T5 IoC...So I suspect that this will eventually not be as hard as people may think. The only reason we've not said an upgrade path won't be provided is because that would limit the future of tapestry - T5 - designsNo one said that they might not end up being something that will actually be easy to upgrade It's just a playing it safe kind of thing. Nothing is worse than making promises and not coming through - esp. on projects like this where the community is the only thing that keeps something alive. 2. Project lead is only participating in the discussion of the T5 questions on the mail list. I've seen him answering T4 questions as well. We all do have to manage our time very carefully - and right now Howard has a lot of people playing with the very bleeding edge versions of T5...So he really has to give them highest priority as that is the right thing to do . Andreas / myself / everyone else are all still here to help with T4 whenever Howard is busy though. I've been trying hard to make sure I stay on top of list questions. Do people think there questions are going un-answered or is it that you just really would prefer to hear them from Howard? 3. T4.1 is in deep development and release plan is _very_ unclear. Development will the development of T4.1 ever come to some meaningful conclusion? Feature stability? Snapshot releases can be broken any time. I haven't seen any non-snapshot release of 4.1.X so far. Latest update of the new OGNL version? Was was the reason for that? Less stability? One snapshot depends on another snapshot? Deep development isn't exactly true. At least not from my perspective. Feature stability / bug fixing / old issue fixing is the main thing I'm concentrating on now. Not to say that I'm not going to do anything new wrt Ajax / etc , just that it seems like the right time to fix up some of what are roughly 130 outstanding jira issues for T4 . The OGNL upgrade was a performance boost. I may have mis-read what people wanted, but over time I've seen lots of complaints about OGNL performance and since I didn't see anyone else doing anything about it (other than Howard creating tapestry-prop for everyone) I decided to go ahead and fix it myself. I'm now also the lead OGNL developer. I do also try to give special priority to OGNL issues once they are properly reported. I can understand this being a little frustrating for those of you still running into these last few little compilation issues I have to fix - but I hope the end result in vastly improved runtime performance of your production applications will make up for the temporary setbacks now. Bugs reported for ognl usually get fixed within a day or two of reporting. For example, I'm sure no ExpressionCompiler related bugs will exist tomorrow. They aren't that hard to fix but there are still conditions that pop up that the current test cases haven't handled yet. I get them when they come up or I spot a pattern of problems. Also, T 4.1.1 was released a while back...And it ~is~ SNAPSHOT sort of alpha software... I have a serious fear that 4.1 will never see the release. In half a year (?) T5 is planned to be released? How important for project lead and project team stability of the framework? I can understand the pursuit of new fancy features and improvements, but never the less how do you see the project plan? How do you see migration path from 4 to 5, from 4.1 to 5? How do you see AJAX and JSON features to be implemented in 5.0? Wouldn't it be better to made some conclusion in 4.1 and put all efforts in 5.0? I can't really answer to T5 questions right now. I may help a little here and there if it's really needed but I can't justify working on it fully until all of the T4 issues have been resolved - again roughly 130 - there's a lot of work left to do still. :) https://issues.apache.org/jira/browse/TAPESTRY My personal development plan is to try and get 4.1.2 out the door once the ognl changes look stable. (ie no reported issues for at least a week or two ) Once that gets done I'll just continue down the path of what I already have been...Slight ajax feature improvements / usage / etc combined
T5 Custom AssetFactory
I am trying to create my own AssetFactory to read assets from a filesystem,
but I'm getting an exception.
My AppModule ~has the following:
public AssetFactory buildMyAssetFactory(@InjectService(ResourceCache)
ResourceCache resourceCache) {
return new MyAssetFactory(resourceCache);
}
public void contributeAssetSource(MappedConfigurationString,
AssetFactory configuration,
@InjectService(MyAssetFactory) AssetFactory myAssetFactory)
{
configuration.add(myassets, myAssetFactory);
}
My page has:
@Inject(myassets:path to file)
private Asset _myFile;
public Asset getMyFile() { return _myFile; }
The factory is currently a clone of the ClasspathAssetFactory (while I
figure things out), except the path it returns is prefixed with
fromMyAssets for testing purposes.
The exception I get when I try to load the page is :
java.lang.RuntimeException
Unable to locate asset 'classpath:path to file' (the file does not exist).
Stack trace
*
org.apache.tapestry.internal.services.AssetSourceImpl.findRelativeAsset(
AssetSourceImpl.java:101)
* org.apache.tapestry.internal.services.AssetSourceImpl.findAsset(
AssetSourceImpl.java:92)
* component init ...
I am not sure why it reads classpath:path to file instead of myassets:path
to file or what approach I should take to solve this issue. Any help is
appreciated :-)
--
Peter Beshai
Computer Science Student
University of Waterloo
Re: T5,page template location ?
2007/3/21, Howard Lewis Ship [EMAIL PROTECTED]: /WEB-INF/test/TestForm.html I know this,but the dreamweaver developer how to design the page?because image directory in root directory. So I think T5 should read page template under root directory not WEB-INF directory. Jun Tsai -- Welcome to China Java Users Group(CNJUG). http://cnjug.dev.java.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5 vs T4 vs Community
On Tue, 20 Mar 2007 18:24:52 -0300, Renat Zubairov [EMAIL PROTECTED] wrote: Let me explain it from _my_ personal point of view. 1. Investments in T4 are lost. Application will not be portable to T5. i can't figure out why investment in a framework will be lost when a new, incompatible version of it is released. tapestry 4.1 will not disappear when t5 is released. t4.x has many useful first- and third-party components (and developers experience) already available, while t5 will take some time to have a similar number, making it not so interesting for serious (i.e, not small, internal ones used to learn it) projects, even having so many wonderful features. :) is there any roadmap (with proposed dates) for t5? thiago hp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5 vs T4 vs Community
Thiago H de Paula Figueiredo wrote: On Tue, 20 Mar 2007 18:24:52 -0300, Renat Zubairov [EMAIL PROTECTED] wrote: Let me explain it from _my_ personal point of view. 1. Investments in T4 are lost. Application will not be portable to T5. i can't figure out why investment in a framework will be lost when a new, incompatible version of it is released. tapestry 4.1 will not disappear when t5 is released. t4.x has many useful first- and third-party components (and developers experience) already available, [...] It's just the perception of most people that there should be continuous evolution instead of a revolution. That has been discussed here before. T5 is called Tapestry, but the term Tapestry is more a brand name, than the name of the product in this case. Personally I don't care about the issue. T5 is something completely new and using it or not is the same question as switching or starting to use another framework. So it's a nice opportunity for new projects, but a switch should not be considered - from my point of view as a user - for stuff that's in production - at least at the present stage. And ... After all it's open source and one should be prepared to participate in the maintenance of such frameworks - there is no vendor guaranteeing anything. It's a voluntary and community effort. If someone is talking about investment then that would mean time - not money - and everybody is free to help with the maintenance while others might move on to something new. Stephan -- http://www.stephan-schwab.com -- View this message in context: http://www.nabble.com/T5-vs-T4-vs-Community-tf3436664.html#a9586744 Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5 tutorial: classes don't exist on package
So after removing the annotations what should we do with the two methods that were annotated: contributeApplicationDefaults() and contributeApplicationFilters? I would guess nobody will call them without the annotations. Thanks, Bogdan Calmac On 3/20/07, Robert Zeigler [EMAIL PROTECTED] wrote: Because the tutorial is currently out of date with respect to the code-base. tapestry-ioc switched to flat namespacing which resulted in not needing Contribute or Id. Robert On Mar 20, 2007, at 3/202:54 PM , acarrara wrote: Hello. On AppModule class of hilo application (Tapestry 5 tutorial) there are some imports: import org.apache.tapestry.ioc.annotations.Contribute; import org.apache.tapestry.ioc.annotations.Id; but these classes (Contribute and Id) aren't on the tapestry-ioc-5.0.3.jarpackage... Where are them? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 5 tutorial: classes don't exist on package
If the annotations were @Contribute(...ApplicationDefaults) and @Contribute(...ApplicationFilters) then the methods will work as expected (without the annotations). Instead of looking for configuration from the annotations, tapestry now determines that same configuration from the actual wording of the method name. That is, void contributeApplicationDefaults() would do the same thing now as @Contribute(...ApplicationDefaults) void contributeFoo() Hope this helps =] On 3/21/07, Bogdan Calmac [EMAIL PROTECTED] wrote: So after removing the annotations what should we do with the two methods that were annotated: contributeApplicationDefaults() and contributeApplicationFilters? I would guess nobody will call them without the annotations. Thanks, Bogdan Calmac On 3/20/07, Robert Zeigler [EMAIL PROTECTED] wrote: Because the tutorial is currently out of date with respect to the code-base. tapestry-ioc switched to flat namespacing which resulted in not needing Contribute or Id. Robert On Mar 20, 2007, at 3/202:54 PM , acarrara wrote: Hello. On AppModule class of hilo application (Tapestry 5 tutorial) there are some imports: import org.apache.tapestry.ioc.annotations.Contribute; import org.apache.tapestry.ioc.annotations.Id; but these classes (Contribute and Id) aren't on the tapestry-ioc-5.0.3.jarpackage... Where are them? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Peter Beshai Computer Science Student University of Waterloo
tapestryforums.com gone?
Hi all...does anyone know the status of the tapestryforums.com website? The forums were somewhat active a few days ago, but the domain registration has now apparently expired. I tried emailing the prior domain name registrant, but no response. Travis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
