Re: Activation Context of the Login page

2009-07-22 Thread Sergey Didenko
Stephan, why do you invalidate the session inside onActivate()?
onActivate is for activating pages. I guess onAction* handlers are
better place for this code.

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



RE: @Secured annotation handling

2009-07-22 Thread Eldred Mullany
Has anyone got come code snippets for me on integrating T5.1.0.5 and
Spring-Tapestry 2.1.0

Thanks

-Original Message-
From: Eldred Mullany 
Sent: Wednesday, July 22, 2009 1:55 PM
To: 'Tapestry users'
Subject: @Secured annotation handling 

Hi All

I am spinning my head here trying to get Spring-Tapestry-security:2.1.0
to work with Tapestry 5.1.0.5 . I have done the upgrade to 2.1.0 and
when place my @secured annotation on the top of my class name is throws
an access denied exception: 

Following that intercept.AbstractSecurityInterceptor could not validate
configuration attributes as the ObjectDefinitionSource did not return a
ConfigAttributeDefinition collection. 

Where am I supposed to configure configuration attributes if any? 

>From what I have read on
http://www.localhost.nu/java/tapestry-spring-security/conf.html. 

Is there referring to the Contributions to the
FilterSecurityInterceptor. 


Thanking you in advance 

Eldred

  


Here is my output screen:  


[WARN] intercept.AbstractSecurityInterceptor Could not validate
configuration attributes as the ObjectDefinitionSource did not return a
ConfigAttributeDefinition collection
[ERROR] billpmts.Bills Render queue error in
BeginRender[billpmts/Bills]: Access is denied
org.apache.tapestry5.ioc.internal.util.TapestryException: Access is
denied
at
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.invoke(
ComponentPageElementImpl.java:948)
at
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.access$
400(ComponentPageElementImpl.java:49)
at
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$Abstrac
tPhase.callback(ComponentPageElementImpl.java:159)
at
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$BeginRe
nderPhase.render(ComponentPageElementImpl.java:211)
at
org.apache.tapestry5.internal.services.RenderQueueImpl.run(RenderQueueIm
pl.java:74)
at
org.apache.tapestry5.internal.services.PageRenderQueueImpl.render(PageRe
nderQueueImpl.java:121)
at
$PageRenderQueue_122a244d649.render($PageRenderQueue_122a244d649.java)
at
$PageRenderQueue_122a244d62b.render($PageRenderQueue_122a244d62b.java)
at
org.apache.tapestry5.internal.services.MarkupRendererTerminator.renderMa
rkup(MarkupRendererTerminator.java:37)
at
org.apache.tapestry5.services.TapestryModule$27.renderMarkup(TapestryMod
ule.java:1748)
at
$MarkupRenderer_122a244d64b.renderMarkup($MarkupRenderer_122a244d64b.jav
a)
at
org.apache.tapestry5.services.TapestryModule$26.renderMarkup(TapestryMod
ule.java:1732)
at
$MarkupRenderer_122a244d64b.renderMarkup($MarkupRenderer_122a244d64b.jav
a)
at
org.apache.tapestry5.services.TapestryModule$25.renderMarkup(TapestryMod
ule.java:1714)
at
$MarkupRenderer_122a244d64b.renderMarkup($MarkupRenderer_122a244d64b.jav
a)
at
org.apache.tapestry5.services.TapestryModule$24.renderMarkup(TapestryMod
ule.java:1700)
at
$MarkupRenderer_122a244d64b.renderMarkup($MarkupRenderer_122a244d64b.jav
a)
at
org.apache.tapestry5.services.TapestryModule$23.renderMarkup(TapestryMod
ule.java:1681)
at
$MarkupRenderer_122a244d64b.renderMarkup($MarkupRenderer_122a244d64b.jav
a)
at
org.apache.tapestry5.services.TapestryModule$22.renderMarkup(TapestryMod
ule.java:1662)
at
$MarkupRenderer_122a244d64b.renderMarkup($MarkupRenderer_122a244d64b.jav
a)
at
$MarkupRenderer_122a244d648.renderMarkup($MarkupRenderer_122a244d648.jav
a)
at
org.apache.tapestry5.internal.services.PageMarkupRendererImpl.renderPage
Markup(PageMarkupRendererImpl.java:64)
at
$PageMarkupRenderer_122a244d645.renderPageMarkup($PageMarkupRenderer_122
a244d645.java)
at
org.apache.tapestry5.internal.services.PageResponseRendererImpl.renderPa
geResponse(PageResponseRendererImpl.java:61)
at
$PageResponseRenderer_122a244d641.renderPageResponse($PageResponseRender
er_122a244d641.java)
at
org.apache.tapestry5.internal.services.PageRenderRequestHandlerImpl.hand
le(PageRenderRequestHandlerImpl.java:63)
at
org.apache.tapestry5.services.TapestryModule$33.handle(TapestryModule.ja
va:1943)
at
$PageRenderRequestHandler_122a244d642.handle($PageRenderRequestHandler_1
22a244d642.java)
at
$PageRenderRequestHandler_122a244d634.handle($PageRenderRequestHandler_1
22a244d634.java)
at
org.apache.tapestry5.internal.services.ComponentRequestHandlerTerminator
.handlePageRender(ComponentRequestHandlerTerminator.java:48)
at
$ComponentRequestHandler_122a244d638.handlePageRender($ComponentRequestH
andler_122a244d638.java)
at
org.apache.tapestry5.internal.services.PageRenderDispatcher.dispatch(Pag
eRenderDispatcher.java:45)
at
$Dispatcher_122a244d639.dispatch($Dispatcher_122a244d639.java)
at
$Dispatcher_122a244d5d6.dispatch($Dispatcher_122a244d5d6.java)
at
org.apache.tapestry5.services.TapestryModule$RequestHandlerTerm

Re: Form component generates invalid xhtml

2009-07-22 Thread Sergey Didenko
Yes, these are the first 2 lines of my Layout component:

"
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://tapestry.apache.org/schema/tapestry_5_1_0.xsd";>
"

On Thu, Jul 23, 2009 at 12:30 AM, Ulrich Stärk wrote:
> Did you set the correct doctype inside your templates?
>

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: T5 - Configuration and .tml Files are Exposed By Tapestry.

2009-07-22 Thread Julian Wood

You can secure the directory listing too:

public static void  
contributeMasterDispatcher(OrderedConfiguration  
configuration) {
configuration.addInstance("DirectoryAsset",  
DirectoryAssetDispatcher.class, "before:Asset");

}

public class DirectoryAssetDispatcher implements Dispatcher {
private AssetResourceLocator assetResourceLocator;
private Context context;

public DirectoryAssetDispatcher(AssetResourceLocator  
assetResourceLocator, Context context) {

this.assetResourceLocator = assetResourceLocator;
this.context = context;
}

public boolean dispatch(Request request, Response response)  
throws IOException {

String path = request.getPath();
if (!path.startsWith(RequestConstants.ASSET_PATH_PREFIX))  
return false;
Resource resource =  
assetResourceLocator.findResourceForPath(path);
if (resource != null &&  
context.getRealFile(resource.getPath()).isDirectory()) {
response.sendError(HttpServletResponse.SC_FORBIDDEN,  
"Directory listing forbidden.");

return true;
} else {
return false;
}
}
}

Regards,

Julian

On Jul 22, 2009, at 12:36 PM, Daniel Jones wrote:



Julian: Thanks for sharing your solution to this problem.  It seems  
like a

good workaround.

Ulrich:  It is good to know that the directory listing has been  
addressed.

Hopefully this security hole will be fixed in the next release.

Daniel


Ulrich Stärk wrote:


There is no directory listing with 5.2-SNAPSHOT but I'm still able to
access the templates and stuff on the classpath.

Uli



-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Form component generates invalid xhtml

2009-07-22 Thread Ulrich Stärk

Did you set the correct doctype inside your templates?

On 22.07.2009 20:27 schrieb Sergey Didenko:

I just encountered that Form generates invalid xhtml 1.0 strict - it
puts "name" attribute to the "form" tag and that is invalid.

'   


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: T5 - Configuration and .tml Files are Exposed By Tapestry.

2009-07-22 Thread Daniel Jones

Julian: Thanks for sharing your solution to this problem.  It seems like a
good workaround.

Ulrich:  It is good to know that the directory listing has been addressed. 
Hopefully this security hole will be fixed in the next release.

Daniel


Ulrich Stärk wrote:
> 
> There is no directory listing with 5.2-SNAPSHOT but I'm still able to 
> access the templates and stuff on the classpath.
> 
> Uli
> 
> On 21.07.2009 03:13 schrieb Daniel Jones:
>> Hello,
>>
>> OK, so here is my problem.
>>
>> In my page template:
>> ${asset:context:assets/images/layout/add.png} 
>>
>> Tapestry generated URL to asset.
>>
>> http://127.0.0.1:8080/assets/ctx/c69b95ec1fef872d/assets/images/layout/add.png
>>
>> If I point my browser at:
>>
>> http://127.0.0.1:8080/assets/ctx/c69b95ec1fef872d/
>>
>> I get a directory listing including my .tml files, I can download these
>> in
>> their raw form.  If I point my browser at http://127.0.0.1:8080/assets/ 
>> I
>> get a directory listing again, this time even more worrying as it
>> contains
>> my hibernate.cfg.xml which can be downloaded exposing the database
>> username
>> and password.
>>
>> How do I fix this.  I used the maven archetype to build the project so
>> the
>> layout looks normal when compared with
>> http://tapestry.apache.org/tapestry5/guide/project-layout.html
>>
>> What am I doing wrong?
>>
>> Any help is much appreciated.
>>
>> Regards,
>> Daniel
>>   
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/T5---Configuration-and-.tml-Files-are-Exposed-By-Tapestry.-tp24580195p24612089.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: users-h...@tapestry.apache.org



Form component generates invalid xhtml

2009-07-22 Thread Sergey Didenko
I just encountered that Form generates invalid xhtml 1.0 strict - it
puts "name" attribute to the "form" tag and that is invalid.

' 

Re: Component Event Context, ValueEncoder & Lifecycle

2009-07-22 Thread Thiago H. de Paula Figueiredo

Em Wed, 22 Jul 2009 13:57:16 -0300, Stefan  escreveu:


Hi,


Hi!


void beginRender(MarkupWriter writer) { 
Link lnk = resources.createEventLink(EVENT_NAME, context);


You should encode the event context before passing it to  
createEventLink(). ;)

Then, in your event handler method, you decode the context.


// should render this: 
writer.element("embed", "type", "image/svg+xml", "width",
width, "height", height, "src", lnk);


SVG! Cool! :)


And, more important to me is to know something about the lifecycles.
How long and "where" life these "passed objects"?


The passed objects are put in the link URL and not store anywhere else.

--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Pop up validation error bubbles

2009-07-22 Thread Sergey Didenko
Sorry, that turned out to be caused by " z-index: 1" property on my content.

Sorry again.

Regards, Sergey.

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Component Event Context, ValueEncoder & Lifecycle

2009-07-22 Thread Stefan

Hi,

i'm currently writing my first component, which should work like this  
one : http://wiki.apache.org/tapestry/Tapestry5HowToCreateASimpleGraphComponent


Everything works fine so far, but:

I have to pass some complex data structures (encapsulated in objects)  
to the component,

doing so:

In the page template:


In the components beginRender method:
void beginRender(MarkupWriter writer) { 
Link lnk = resources.createEventLink(EVENT_NAME, context);

	// should render this: width="280"height="280">

writer.element("embed", "type", "image/svg+xml", "width",
width, "height", height, "src", lnk);
resources.renderInformalParameters(writer);
}

And at least, the corresponding action:
public StreamResponse onRenderGraph(Object... params) {
// the params object now should be the passed myDataStructure
//... rendering stuff
}


This works fine so far, but some things are too unclear to me:
the generated eventlink looks horrible:
"/somepage.component.action/org.localhost.something.package.MyStructure 
$12345"

Is there a way to use a custom ValueEncode to generate a better url?
I do not want to provide my package structure to the client ;)

And, more important to me is to know something about the lifecycles.
How long and "where" life these "passed objects"?

Thanks,
Stefan





smime.p7s
Description: S/MIME cryptographic signature


Re: Return type org.apache.tapestry5.json.JSONObject can not be handled

2009-07-22 Thread Thiago H. de Paula Figueiredo
Em Wed, 22 Jul 2009 13:05:09 -0300, Franz Amador   
escreveu:



I wondered that also, and I'm waiting on an answer.
Does disabling JavaScript make the Ajax stuff invisible to Tapestry?  If  
so, it'd be great to have a better error message.


AJAX is all about using Javascript to update a part of a page without  
refreshing it. ;) Thus, no Javascript, no AJAX.


You can detect if a request is made through AJAX @Injecting Request is  
then invoking request.ixXHR(). Then, all you need is to return a block or  
component or some JSON object if the request is AJAX and return null, a  
page instance, a page class instance or a page name otherwise.


--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Return type org.apache.tapestry5.json.JSONObject can not be handled

2009-07-22 Thread Franz Amador

I wondered that also, and I'm waiting on an answer.

Does disabling JavaScript make the Ajax stuff invisible to Tapestry?  If so, 
it'd be great to have a better error message.




From: Howard Lewis Ship (via Nabble) 
To: Franz Amador 
Sent: Tuesday, July 21, 2009 11:04:05 PM
Subject: Re: Return type org.apache.tapestry5.json.JSONObject can not be  
handled

Is JavaScript disabled for that client's laptop? 

On Tue, Jul 21, 2009 at 10:55 AM, Franz Amador wrote: 

> 
> Our Tapestry5/Dojo web app works just fine everywhere except on one 
> customer's laptop.  There he gets this error: 
> 
> Return type org.apache.tapestry5.json.JSONObject can not be handled. 
> Configured return types are java.lang.Class, java.lang.String, java.net.URL, 
> org.apache.tapestry5.Link, org.apache.tapestry5.StreamResponse, 
> org.apache.tapestry5.runtime.Component. 
> 
> We're using Tapestry 5.1.0.5 on Java 6, the laptop runs the Japanese version 
> of Windows (XP, I assume), and the whole system (our webapp running on 
> Tomcat with Oracle) is installed there.  This configuration works great on 
> our laptops (which aren't Japanese, though I don't know if that's relevant). 
> 
> I'm baffled.  What could possibly have caused the 
> AjaxComponentEventResultProcessor not to be available there (which I assume 
> is the problem)?  Any suggestions very much appreciated. 
> -- 
> View this message in context: 
> http://n2.nabble.com/Return-type-org.apache.tapestry5.json.JSONObject-can-not-be-handled-tp3295186p3295186.html
> Sent from the Tapestry Users mailing list archive at Nabble.com. 
> 
> - 
> To unsubscribe, e-mail: users-unsubscr...@... 
> For additional commands, e-mail: users-h...@... 
> 
> 


-- 
Howard M. Lewis Ship 

Creator of Apache Tapestry 
Director of Open Source Technology at Formos 

- 
To unsubscribe, e-mail: users-unsubscr...@... 
For additional commands, e-mail: users-h...@... 




 
View message @ 
http://n2.nabble.com/Return-type-org.apache.tapestry5.json.JSONObject-can-not-be-handled-tp3295186p3300097.html
 
To unsubscribe from Return type org.apache.tapestry5.json.JSONObject can not be 
handled, click here. 

-- 
View this message in context: 
http://n2.nabble.com/Return-type-org.apache.tapestry5.json.JSONObject-can-not-be-handled-tp3295186p3304209.html
Sent from the Tapestry Users mailing list archive at Nabble.com.


Re: Pop up validation error bubbles

2009-07-22 Thread Howard Lewis Ship
I haven't noticed that; which browser is this an issue for?

Please add an issue to JIRA.

On Wed, Jul 22, 2009 at 7:00 AM, Sergey Didenko wrote:
> I propose to add
>
> .t-error-popup {
>        z-index: 2;
> }
>
> into common Tapestry css. Without it popup errors are semi-hidden
> behind input labels, which looks ugly.
>
> I'm going to create a JIRA issue for that. Any remarks, objections?
>
> Regards, Sergey.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>



-- 
Howard M. Lewis Ship

Creator of Apache Tapestry
Director of Open Source Technology at Formos

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



At OSCON thru Friday

2009-07-22 Thread Howard Lewis Ship
I just arrived at OSCON; if any Tapestry folks are here (despite the
anemic Java track) come and fine me!  I'll be here through Friday.

-- 
Howard M. Lewis Ship

Creator of Apache Tapestry
Director of Open Source Technology at Formos

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Pop up validation error bubbles

2009-07-22 Thread Sergey Didenko
I propose to add

.t-error-popup {
z-index: 2;
}

into common Tapestry css. Without it popup errors are semi-hidden
behind input labels, which looks ugly.

I'm going to create a JIRA issue for that. Any remarks, objections?

Regards, Sergey.

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



RE: T5.1.0.5: StackMapTable format error

2009-07-22 Thread Newham, Cameron
Very odd.

I based my comment on what I observed in the M2 POM editor dependencies
tab...


-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] 
Sent: 22 July 2009 14:22
To: Tapestry users
Subject: Re: T5.1.0.5: StackMapTable format error

Em Wed, 22 Jul 2009 07:40:24 -0300, Newham, Cameron
  
escreveu:

> I note that I found this out from an email sent by Howard in 2007
> addressing a query on StackMapTable error. I find it somewhat
surprising
> that this problem still occurs in 2009. Surely Tapestry 5.1.x should
be
> using the latest Javassist...

It does use the latest Javassist version:  
http://tapestry.apache.org/tapestry5.1/tapestry-core/dependencies.html.
I guess you had messed up dependencies then.

-- 
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

**
 
Experience the British Library online at www.bl.uk
 
The British Library's new interactive Annual Report and Accounts 2007/08 : 
www.bl.uk/knowledge
 
Help the British Library conserve the world's knowledge. Adopt a Book. 
www.bl.uk/adoptabook
 
The Library's St Pancras site is WiFi - enabled
 
*
 
The information contained in this e-mail is confidential and may be legally 
privileged. It is intended for the addressee(s) only. If you are not the 
intended recipient, please delete this e-mail and notify the postmas...@bl.uk : 
The contents of this e-mail must not be disclosed or copied without the 
sender's consent. 
 
The statements and opinions expressed in this message are those of the author 
and do not necessarily reflect those of the British Library. The British 
Library does not take any responsibility for the views of the author. 
 
*

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: T5.1.0.5: StackMapTable format error

2009-07-22 Thread Peter Stavrinides
> I do use ChenilleKit but haven't run into this problem (I presume that's
> because Maven always uses the later version if there is a conflict? 
In my limited experience with Maven that is not the case, I think it may depend 
on a few factors, explicit dependency declarations tend to win out, as does a 
child over a parent appear to take precedence, of course a Maven expert can 
chime in here and correct me if I am wrong.

ChenilleKit works reliably if you use the exclusion and also remove any 
explicit dependencies for javassist and see what version appears.

Cheers,
Peter
 

- Original Message -
From: "Cameron Newham" 
To: "Tapestry users" 
Sent: Wednesday, 22 July, 2009 16:20:38 GMT +02:00 Athens, Beirut, Bucharest, 
Istanbul
Subject: RE: T5.1.0.5: StackMapTable format error

Thanks Peter.

I do use ChenilleKit but haven't run into this problem (I presume that's
because Maven always uses the later version if there is a conflict? And
as I've explicitly brought in the later version of Javassist then that
overrides any earlier versions being included on the classpath)

I do notice that ChenilleKit wants to use Tapestry 5.0.18 and is causing
a conflict there. Is this likely to be updated soon?


-Original Message-
From: p.stavrini...@albourne.com [mailto:p.stavrini...@albourne.com] 
Sent: 22 July 2009 14:07
To: Tapestry users
Subject: Re: T5.1.0.5: StackMapTable format error

Be sure also to include an exclusion if you use ChenilleKit, or you will
run into similar issues. 


org.chenillekit
chenillekit-tapestry
1.0.0


jboss
javassist




Cheers,
Peter

- Original Message -
From: "Cameron Newham" 
To: "Tapestry users" 
Sent: Wednesday, 22 July, 2009 13:40:24 GMT +02:00 Athens, Beirut,
Bucharest, Istanbul
Subject: RE: T5.1.0.5: StackMapTable format error

Thanks Thiago, although it turned out to be because I'm using Java 1.6
and I had an old(ish) version of Javassist being brought in as a
dependency from tapestry-ioc that wants javassist-3.4.GA.

Specifying the latest Javassist (3.8.GA) in my POM solved the problem.

I note that I found this out from an email sent by Howard in 2007
addressing a query on StackMapTable error. I find it somewhat surprising
that this problem still occurs in 2009. Surely Tapestry 5.1.x should be
using the latest Javassist...



-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] 
Sent: 21 July 2009 14:58
To: Tapestry users
Subject: Re: T5.1.0.5: StackMapTable format error

Em Tue, 21 Jul 2009 10:18:21 -0300, Newham, Cameron
  
escreveu:

> Hi,

Hi!

> My Index page comes up fine when running my app from Jetty in Eclipse.
> However, as soon as I attempt to log in and Tapestry tries to go to
the
> app "home" page I get a StackMapTable format error.

Typically, strange errors are caused by having more than one version of

the same library in your classpath. You can also try to recompile all
the  
classes.

-- 
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org


**
 
Experience the British Library online at www.bl.uk
 
The British Library's new interactive Annual Report and Accounts 2007/08
: www.bl.uk/knowledge
 
Help the British Library conserve the world's knowledge. Adopt a Book.
www.bl.uk/adoptabook
 
The Library's St Pancras site is WiFi - enabled
 

*
 
The information contained in this e-mail is confidential and may be
legally privileged. It is intended for the addressee(s) only. If you are
not the intended recipient, please delete this e-mail and notify the
postmas...@bl.uk : The contents of this e-mail must not be disclosed or
copied without the sender's consent. 
 
The statements and opinions expressed in this message are those of the
author and do not necessarily reflect those of the British Library. The
British Library does not take any responsibility for the views of the
author. 
 

*

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org


-

Re: T5.1.0.5: StackMapTable format error

2009-07-22 Thread Thiago H. de Paula Figueiredo
Em Wed, 22 Jul 2009 07:40:24 -0300, Newham, Cameron   
escreveu:



I note that I found this out from an email sent by Howard in 2007
addressing a query on StackMapTable error. I find it somewhat surprising
that this problem still occurs in 2009. Surely Tapestry 5.1.x should be
using the latest Javassist...


It does use the latest Javassist version:  
http://tapestry.apache.org/tapestry5.1/tapestry-core/dependencies.html.

I guess you had messed up dependencies then.

--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: T5.1.0.5: StackMapTable format error

2009-07-22 Thread P . Stavrinides
> Specifying the latest Javassist (3.8.GA) in my POM solved the problem.
> I note that I found this out from an email sent by Howard in 2007
> addressing a query on StackMapTable error. I find it somewhat surprising
> that this problem still occurs in 2009. Surely Tapestry 5.1.x should be
> using the latest Javassist...
FYI Tapestry does use the latest version 'javassist-3.9.0.GA' in fact, some 
other POM is likely to be causing the conflict

Peter

- Original Message -
From: "Cameron Newham" 
To: "Tapestry users" 
Sent: Wednesday, 22 July, 2009 13:40:24 GMT +02:00 Athens, Beirut, Bucharest, 
Istanbul
Subject: RE: T5.1.0.5: StackMapTable format error

Thanks Thiago, although it turned out to be because I'm using Java 1.6
and I had an old(ish) version of Javassist being brought in as a
dependency from tapestry-ioc that wants javassist-3.4.GA.

Specifying the latest Javassist (3.8.GA) in my POM solved the problem.

I note that I found this out from an email sent by Howard in 2007
addressing a query on StackMapTable error. I find it somewhat surprising
that this problem still occurs in 2009. Surely Tapestry 5.1.x should be
using the latest Javassist...



-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] 
Sent: 21 July 2009 14:58
To: Tapestry users
Subject: Re: T5.1.0.5: StackMapTable format error

Em Tue, 21 Jul 2009 10:18:21 -0300, Newham, Cameron
  
escreveu:

> Hi,

Hi!

> My Index page comes up fine when running my app from Jetty in Eclipse.
> However, as soon as I attempt to log in and Tapestry tries to go to
the
> app "home" page I get a StackMapTable format error.

Typically, strange errors are caused by having more than one version of

the same library in your classpath. You can also try to recompile all
the  
classes.

-- 
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

**
 
Experience the British Library online at www.bl.uk
 
The British Library's new interactive Annual Report and Accounts 2007/08 : 
www.bl.uk/knowledge
 
Help the British Library conserve the world's knowledge. Adopt a Book. 
www.bl.uk/adoptabook
 
The Library's St Pancras site is WiFi - enabled
 
*
 
The information contained in this e-mail is confidential and may be legally 
privileged. It is intended for the addressee(s) only. If you are not the 
intended recipient, please delete this e-mail and notify the postmas...@bl.uk : 
The contents of this e-mail must not be disclosed or copied without the 
sender's consent. 
 
The statements and opinions expressed in this message are those of the author 
and do not necessarily reflect those of the British Library. The British 
Library does not take any responsibility for the views of the author. 
 
*

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



RE: T5.1.0.5: StackMapTable format error

2009-07-22 Thread Newham, Cameron
Thanks Peter.

I do use ChenilleKit but haven't run into this problem (I presume that's
because Maven always uses the later version if there is a conflict? And
as I've explicitly brought in the later version of Javassist then that
overrides any earlier versions being included on the classpath)

I do notice that ChenilleKit wants to use Tapestry 5.0.18 and is causing
a conflict there. Is this likely to be updated soon?


-Original Message-
From: p.stavrini...@albourne.com [mailto:p.stavrini...@albourne.com] 
Sent: 22 July 2009 14:07
To: Tapestry users
Subject: Re: T5.1.0.5: StackMapTable format error

Be sure also to include an exclusion if you use ChenilleKit, or you will
run into similar issues. 


org.chenillekit
chenillekit-tapestry
1.0.0


jboss
javassist




Cheers,
Peter

- Original Message -
From: "Cameron Newham" 
To: "Tapestry users" 
Sent: Wednesday, 22 July, 2009 13:40:24 GMT +02:00 Athens, Beirut,
Bucharest, Istanbul
Subject: RE: T5.1.0.5: StackMapTable format error

Thanks Thiago, although it turned out to be because I'm using Java 1.6
and I had an old(ish) version of Javassist being brought in as a
dependency from tapestry-ioc that wants javassist-3.4.GA.

Specifying the latest Javassist (3.8.GA) in my POM solved the problem.

I note that I found this out from an email sent by Howard in 2007
addressing a query on StackMapTable error. I find it somewhat surprising
that this problem still occurs in 2009. Surely Tapestry 5.1.x should be
using the latest Javassist...



-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] 
Sent: 21 July 2009 14:58
To: Tapestry users
Subject: Re: T5.1.0.5: StackMapTable format error

Em Tue, 21 Jul 2009 10:18:21 -0300, Newham, Cameron
  
escreveu:

> Hi,

Hi!

> My Index page comes up fine when running my app from Jetty in Eclipse.
> However, as soon as I attempt to log in and Tapestry tries to go to
the
> app "home" page I get a StackMapTable format error.

Typically, strange errors are caused by having more than one version of

the same library in your classpath. You can also try to recompile all
the  
classes.

-- 
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org


**
 
Experience the British Library online at www.bl.uk
 
The British Library's new interactive Annual Report and Accounts 2007/08
: www.bl.uk/knowledge
 
Help the British Library conserve the world's knowledge. Adopt a Book.
www.bl.uk/adoptabook
 
The Library's St Pancras site is WiFi - enabled
 

*
 
The information contained in this e-mail is confidential and may be
legally privileged. It is intended for the addressee(s) only. If you are
not the intended recipient, please delete this e-mail and notify the
postmas...@bl.uk : The contents of this e-mail must not be disclosed or
copied without the sender's consent. 
 
The statements and opinions expressed in this message are those of the
author and do not necessarily reflect those of the British Library. The
British Library does not take any responsibility for the views of the
author. 
 

*

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Passing data to the same page - Understanding PersistanceContext.FLASH

2009-07-22 Thread Thiago H. de Paula Figueiredo
Em Wed, 22 Jul 2009 05:51:23 -0300, Stephan Windmüller  
 escreveu:



It is really necessary to use a persistent store when all needed data is
transmitted with each submit of the form?


Tapestry does redirect-after-post by default, so some form of persistence  
is needed. You can also use the activation context to pass this  
information back to the page whithout usin @Persist or @SessionState.


You can disable redirect-after-post (documentation at  
http://tapestry.apache.org/tapestry5.1/guide/conf.html), but I don't  
recommend this option.


--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: T5.1.0.5: StackMapTable format error

2009-07-22 Thread P . Stavrinides
Be sure also to include an exclusion if you use ChenilleKit, or you will run 
into similar issues. 


org.chenillekit
chenillekit-tapestry
1.0.0


jboss
javassist




Cheers,
Peter

- Original Message -
From: "Cameron Newham" 
To: "Tapestry users" 
Sent: Wednesday, 22 July, 2009 13:40:24 GMT +02:00 Athens, Beirut, Bucharest, 
Istanbul
Subject: RE: T5.1.0.5: StackMapTable format error

Thanks Thiago, although it turned out to be because I'm using Java 1.6
and I had an old(ish) version of Javassist being brought in as a
dependency from tapestry-ioc that wants javassist-3.4.GA.

Specifying the latest Javassist (3.8.GA) in my POM solved the problem.

I note that I found this out from an email sent by Howard in 2007
addressing a query on StackMapTable error. I find it somewhat surprising
that this problem still occurs in 2009. Surely Tapestry 5.1.x should be
using the latest Javassist...



-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] 
Sent: 21 July 2009 14:58
To: Tapestry users
Subject: Re: T5.1.0.5: StackMapTable format error

Em Tue, 21 Jul 2009 10:18:21 -0300, Newham, Cameron
  
escreveu:

> Hi,

Hi!

> My Index page comes up fine when running my app from Jetty in Eclipse.
> However, as soon as I attempt to log in and Tapestry tries to go to
the
> app "home" page I get a StackMapTable format error.

Typically, strange errors are caused by having more than one version of

the same library in your classpath. You can also try to recompile all
the  
classes.

-- 
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

**
 
Experience the British Library online at www.bl.uk
 
The British Library's new interactive Annual Report and Accounts 2007/08 : 
www.bl.uk/knowledge
 
Help the British Library conserve the world's knowledge. Adopt a Book. 
www.bl.uk/adoptabook
 
The Library's St Pancras site is WiFi - enabled
 
*
 
The information contained in this e-mail is confidential and may be legally 
privileged. It is intended for the addressee(s) only. If you are not the 
intended recipient, please delete this e-mail and notify the postmas...@bl.uk : 
The contents of this e-mail must not be disclosed or copied without the 
sender's consent. 
 
The statements and opinions expressed in this message are those of the author 
and do not necessarily reflect those of the British Library. The British 
Library does not take any responsibility for the views of the author. 
 
*

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



JumpStart 4.3 for T5.1.0.5: old documentation links

2009-07-22 Thread Sergey Didenko
Hi Geoff,

I suggest to change links from T5.0 to T5.1 documentation.

For example on page
http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/input/creatingvalidators1
there are links like "Form Input and Validation" that point to T5.0
docs.

On Thu, Jul 16, 2009 at 8:59 AM, Geoff
Callender wrote:
> JumpStart 4.3 is now available.   It's built on the latest stable release of
> Tapestry: 5.1.0.5.

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: T5.1.0.5 IllegalStateException after invalidating Session

2009-07-22 Thread P . Stavrinides
I still think this is a bug... I see it occasionaly but incosistently between 
containers (jetty and tomcat), I think there is some inconsistency between 2.3 
compliant
and 2.4 compliant Servlet containers when invalidating a session. If you use 
the workaround for 5.1 then change:

if (element.startsWith("aso:")) 
to:
if (element.startsWith("sso:")) 

Kind regards,
Peter

- Original Message -
From: "Kristian Marinkovic" 
To: "Tapestry users" 
Sent: Wednesday, 22 July, 2009 15:31:06 GMT +02:00 Athens, Beirut, Bucharest, 
Istanbul
Subject: RE: T5.1.0.5 IllegalStateException after invalidating Session

in Tapestry 5.0.18 you were able to create a new HttpSession after you 
have
invalidated the old one in the same thread (request). This is not possible 

anymore as the implementation is caching the old session and reusing it 
for subsequent requests. 

as a quick solution: get the HttpSession directly and clear the 
httpSession manually

see also 
http://tapestry-user.markmail.org/search/?q=session+peter#query:session%20peter+page:1+mid:3rnavgdfcjlbvagc+state:results

i'm still not sure if it's a bug or feature

g,
kris




raucha  
22.07.2009 13:04
Bitte antworten an
"Tapestry users" 


An
users@tapestry.apache.org
Kopie

Thema
T5.1.0.5 IllegalStateException after invalidating Session








I try to upgrade an application from 5.0.18 to 5.1.0.5. After invalidating
the Session for the user logout I get the included Exception. Everything
works fine with 5.0.18 and I checked hat I do not invalidate the 
HttpSession
but invalidate the Tapestry Session via the injected
org.apache.tapestry5.services.Request.

The Exception I get:

java.lang.IllegalStateException

*
org.mortbay.jetty.servlet.AbstractSessionManager$Session.setAttribute(AbstractSessionManager.java:1050)
*
org.apache.tapestry5.internal.services.SessionImpl.setAttribute(SessionImpl.java:67)
*
org.apache.tapestry5.internal.services.AbstractSessionPersistentFieldStrategy.postChange(AbstractSessionPersistentFieldStrategy.java:131)
*
org.apache.tapestry5.internal.services.PersistentFieldManagerImpl.postChange(PersistentFieldManagerImpl.java:82)
*
$PersistentFieldManager_122a21dc7f4.postChange($PersistentFieldManager_122a21dc7f4.java)
*
org.apache.tapestry5.internal.structure.PageImpl.persistFieldChange(PageImpl.java:160)
*
org.apache.tapestry5.internal.structure.InternalComponentResourcesImpl.persistFieldChange(InternalComponentResourcesImpl.java:285)
*
de.creditreform.crefoteam.verwaltungsclient.components.Layout._$write_menu(Layout.java)
*
de.creditreform.crefoteam.verwaltungsclient.components.Layout.initMenu(Layout.java:190)
*
de.creditreform.crefoteam.verwaltungsclient.components.Layout.getMenu(Layout.java:143)
*
$PropertyConduit_122a21dc825.get($PropertyConduit_122a21dc825.java)
*
org.apache.tapestry5.internal.bindings.PropBinding.get(PropBinding.java:58)
*
org.apache.tapestry5.internal.structure.InternalComponentResourcesImpl$1.read(InternalComponentResourcesImpl.java:510)
*
org.apache.tapestry5.internal.structure.InternalComponentResourcesImpl$1.read(InternalComponentResourcesImpl.java:496)
*
org.apache.tapestry5.corelib.components.Loop._$read_parameter_source(Loop.java)
* 
org.apache.tapestry5.corelib.components.Loop.setup(Loop.java:312)
*
org.apache.tapestry5.corelib.components.Loop.setupRender(Loop.java)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$SetupRenderPhase.invokeComponent(ComponentPageElementImpl.java:184)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$AbstractPhase.run(ComponentPageElementImpl.java:164)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.invoke(ComponentPageElementImpl.java:933)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.access$400(ComponentPageElementImpl.java:49)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$AbstractPhase.callback(ComponentPageElementImpl.java:159)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$SetupRenderPhase.render(ComponentPageElementImpl.java:189)
*
org.apache.tapestry5.internal.services.RenderQueueImpl.run(RenderQueueImpl.java:74)
*
org.apache.tapestry5.internal.services.PageRenderQueueImpl.render(PageRenderQueueImpl.java:121)
*
$PageRenderQueue_122a21dc889.render($PageRenderQueue_122a21dc889.java)
*
$PageRenderQueue_122a21dc86d.render($PageRenderQueue_122a21dc86d.java)
*
org.apache.tapestry5.internal.services.MarkupRendererTerminator.renderMarkup(MarkupRendererTerminator.java:37)
*
org.apache.tapestry5.services.TapestryModule$27.renderMarkup(TapestryModule.java:1748)
*
$MarkupRenderer_122a21dc88b.renderMarkup($MarkupRenderer_122a21dc88b.java)
*
org.apache.tapestry5.services.TapestryModule$26.renderMarkup(TapestryModule.ja

Application Period for Travel Assistance to ApacheCon US 2009 Opens Soon

2009-07-22 Thread Howard Lewis Ship
The Travel Assistance Committee is taking in applications for those wanting
to attend ApacheCon US 2009 (Oakland) which takes place between the 2nd and
6th November 2009.

The Travel Assistance Committee is looking for people who would like to be
able to attend ApacheCon US 2009 who may need some financial support in
order to get there. There are limited places available, and all applications
will be scored on their individual merit. Applications are open to all open
source developers who feel that their attendance would benefit themselves,
their project(s), the ASF and open source in general.

Financial assistance is available for flights, accommodation, subsistence
and Conference fees either in full or in part, depending on circumstances.
It is intended that all our ApacheCon events are covered, so it may be
prudent for those in Europe and/or Asia to wait until an event closer to
them comes up - you are all welcome to apply for ApacheCon US of course, but
there should be compelling reasons for you to attend an event further away
that your home location for your application to be considered above those
closer to the event location.

More information can be found on the main Apache website at
http://www.apache.org/travel/index.html - where you will also find a link to
the online application and details for submitting.

Applications for applying for travel assistance will open on 27th July 2009
and close of the 17th August 2009.

Good luck to all those that will apply.

Regards,

The Travel Assistance Committee





-- 
Howard M. Lewis Ship

Creator of Apache Tapestry
Director of Open Source Technology at Formos

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



RE: T5.1.0.5 IllegalStateException after invalidating Session

2009-07-22 Thread Kristian Marinkovic
in Tapestry 5.0.18 you were able to create a new HttpSession after you 
have
invalidated the old one in the same thread (request). This is not possible 

anymore as the implementation is caching the old session and reusing it 
for subsequent requests. 

as a quick solution: get the HttpSession directly and clear the 
httpSession manually

see also 
http://tapestry-user.markmail.org/search/?q=session+peter#query:session%20peter+page:1+mid:3rnavgdfcjlbvagc+state:results

i'm still not sure if it's a bug or feature

g,
kris




raucha  
22.07.2009 13:04
Bitte antworten an
"Tapestry users" 


An
users@tapestry.apache.org
Kopie

Thema
T5.1.0.5 IllegalStateException after invalidating Session








I try to upgrade an application from 5.0.18 to 5.1.0.5. After invalidating
the Session for the user logout I get the included Exception. Everything
works fine with 5.0.18 and I checked hat I do not invalidate the 
HttpSession
but invalidate the Tapestry Session via the injected
org.apache.tapestry5.services.Request.

The Exception I get:

java.lang.IllegalStateException

*
org.mortbay.jetty.servlet.AbstractSessionManager$Session.setAttribute(AbstractSessionManager.java:1050)
*
org.apache.tapestry5.internal.services.SessionImpl.setAttribute(SessionImpl.java:67)
*
org.apache.tapestry5.internal.services.AbstractSessionPersistentFieldStrategy.postChange(AbstractSessionPersistentFieldStrategy.java:131)
*
org.apache.tapestry5.internal.services.PersistentFieldManagerImpl.postChange(PersistentFieldManagerImpl.java:82)
*
$PersistentFieldManager_122a21dc7f4.postChange($PersistentFieldManager_122a21dc7f4.java)
*
org.apache.tapestry5.internal.structure.PageImpl.persistFieldChange(PageImpl.java:160)
*
org.apache.tapestry5.internal.structure.InternalComponentResourcesImpl.persistFieldChange(InternalComponentResourcesImpl.java:285)
*
de.creditreform.crefoteam.verwaltungsclient.components.Layout._$write_menu(Layout.java)
*
de.creditreform.crefoteam.verwaltungsclient.components.Layout.initMenu(Layout.java:190)
*
de.creditreform.crefoteam.verwaltungsclient.components.Layout.getMenu(Layout.java:143)
*
$PropertyConduit_122a21dc825.get($PropertyConduit_122a21dc825.java)
*
org.apache.tapestry5.internal.bindings.PropBinding.get(PropBinding.java:58)
*
org.apache.tapestry5.internal.structure.InternalComponentResourcesImpl$1.read(InternalComponentResourcesImpl.java:510)
*
org.apache.tapestry5.internal.structure.InternalComponentResourcesImpl$1.read(InternalComponentResourcesImpl.java:496)
*
org.apache.tapestry5.corelib.components.Loop._$read_parameter_source(Loop.java)
* 
org.apache.tapestry5.corelib.components.Loop.setup(Loop.java:312)
*
org.apache.tapestry5.corelib.components.Loop.setupRender(Loop.java)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$SetupRenderPhase.invokeComponent(ComponentPageElementImpl.java:184)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$AbstractPhase.run(ComponentPageElementImpl.java:164)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.invoke(ComponentPageElementImpl.java:933)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.access$400(ComponentPageElementImpl.java:49)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$AbstractPhase.callback(ComponentPageElementImpl.java:159)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$SetupRenderPhase.render(ComponentPageElementImpl.java:189)
*
org.apache.tapestry5.internal.services.RenderQueueImpl.run(RenderQueueImpl.java:74)
*
org.apache.tapestry5.internal.services.PageRenderQueueImpl.render(PageRenderQueueImpl.java:121)
*
$PageRenderQueue_122a21dc889.render($PageRenderQueue_122a21dc889.java)
*
$PageRenderQueue_122a21dc86d.render($PageRenderQueue_122a21dc86d.java)
*
org.apache.tapestry5.internal.services.MarkupRendererTerminator.renderMarkup(MarkupRendererTerminator.java:37)
*
org.apache.tapestry5.services.TapestryModule$27.renderMarkup(TapestryModule.java:1748)
*
$MarkupRenderer_122a21dc88b.renderMarkup($MarkupRenderer_122a21dc88b.java)
*
org.apache.tapestry5.services.TapestryModule$26.renderMarkup(TapestryModule.java:1732)
*
$MarkupRenderer_122a21dc88b.renderMarkup($MarkupRenderer_122a21dc88b.java)
*
org.apache.tapestry5.services.TapestryModule$25.renderMarkup(TapestryModule.java:1714)
*
$MarkupRenderer_122a21dc88b.renderMarkup($MarkupRenderer_122a21dc88b.java)
*
org.apache.tapestry5.services.TapestryModule$24.renderMarkup(TapestryModule.java:1700)
*
$MarkupRenderer_122a21dc88b.renderMarkup($MarkupRenderer_122a21dc88b.java)
*
org.apache.tapestry5.services.TapestryModule$23.renderMarkup(TapestryModule.java:1681)
*
$MarkupRenderer_122a21dc88b.renderMarkup($MarkupRen

RE: again on webservices

2009-07-22 Thread Henning Petersen
I wouldn't run the web service through Tapestry at all. Instead, register
your web service as a separate servlet inside your application with a
certain path (e.g. "/ws/"), and make sure the Tapestry filter ignores those
paths by a contribution to your app module:

public static void contributeIgnoredPathsFilter(
final Configuration configuration) {
configuration.add("/ws/.*");
}

That will allow T5 and any other servlet to co-exist peacefully. You can
then use the same Spring context you use in T5 with your web service as
well. IMO, running the whole web service through T5 would gain you nothing,
at best.

Kind regards
Henning

-Original Message-
From: Thibaut Gadiolet [mailto:thibaut.gadio...@gmail.com] 
Sent: Tuesday, July 21, 2009 10:09 PM
To: Tapestry users
Subject: Re: again on webservices

Hi folks,

I was browsing nabble looking for something about Axis2 integration when I
found this topic.
So here is my question:

I have a web application based on Tapestry/Hibernate/Spring built by Maven.
My boss asked me to create a new Java Class and make it a Web Service.

So Andrea, how did you make it ?
Someone's got an easy solution to make a T5 page run with Axis ?


Thibaut




On Fri, May 22, 2009 at 4:23 PM, Andrea Chiumenti  wrote:

> I did, I can put a working example online if you want!
> but someone should write something on the wiki, unfortunately I have
> too many projects to bring on and i really don't have time, what I can
> do is to put a working example online.
>
> cheers kiuma
>
> On Wed, May 20, 2009 at 10:47 AM, Alfie Kirkpatrick
>  wrote:
> > If you are after full SOAP web service support it might make more sense
> > to wire in a framework like Axis or Glassfish Metro directly into
> > web.xml and not tie it to Tapestry pages per se.
> >
> > Which does raise a follow up question... has anyone successfully wired
> > Tapestry IOC with a web service framework, so we can have Tapestry
> > control the lifecycle of the web service implementation, inject other
> > services into it, etc, etc?
> >
> > Thanks, Alfie.
> >
> > -Original Message-
> > From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com]
> > Sent: 19 May 2009 22:47
> > To: Tapestry users
> > Subject: Re: again on webservices
> >
> > Em Tue, 19 May 2009 15:57:36 -0300, Andrea Chiumenti 
> >
> > escreveu:
> >
> >> I have a simple question:
> >> may a T5 page behave like a webservice (soap) ?
> >
> > Yes. Why not? :)
> > You can use Tapestry's templating engine to generate the answer or use
> > another code or framework to generate the answer and return it as a
> > StreamResponse.
> >
> > --
> > Thiago H. de Paula Figueiredo
> > Consultor, desenvolvedor e instrutor em Java
> > http://www.arsmachina.com.br/thiago
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



@Secured annotation handling

2009-07-22 Thread Eldred Mullany
Hi All

I am spinning my head here trying to get Spring-Tapestry-security:2.1.0
to work with Tapestry 5.1.0.5 . I have done the upgrade to 2.1.0 and
when place my @secured annotation on the top of my class name is throws
an access denied exception: 

Following that intercept.AbstractSecurityInterceptor could not validate
configuration attributes as the ObjectDefinitionSource did not return a
ConfigAttributeDefinition collection. 

Where am I supposed to configure configuration attributes if any? 

>From what I have read on
http://www.localhost.nu/java/tapestry-spring-security/conf.html. 

Is there referring to the Contributions to the
FilterSecurityInterceptor. 


Thanking you in advance 

Eldred

  


Here is my output screen:  


[WARN] intercept.AbstractSecurityInterceptor Could not validate
configuration attributes as the ObjectDefinitionSource did not return a
ConfigAttributeDefinition collection
[ERROR] billpmts.Bills Render queue error in
BeginRender[billpmts/Bills]: Access is denied
org.apache.tapestry5.ioc.internal.util.TapestryException: Access is
denied
at
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.invoke(
ComponentPageElementImpl.java:948)
at
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.access$
400(ComponentPageElementImpl.java:49)
at
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$Abstrac
tPhase.callback(ComponentPageElementImpl.java:159)
at
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$BeginRe
nderPhase.render(ComponentPageElementImpl.java:211)
at
org.apache.tapestry5.internal.services.RenderQueueImpl.run(RenderQueueIm
pl.java:74)
at
org.apache.tapestry5.internal.services.PageRenderQueueImpl.render(PageRe
nderQueueImpl.java:121)
at
$PageRenderQueue_122a244d649.render($PageRenderQueue_122a244d649.java)
at
$PageRenderQueue_122a244d62b.render($PageRenderQueue_122a244d62b.java)
at
org.apache.tapestry5.internal.services.MarkupRendererTerminator.renderMa
rkup(MarkupRendererTerminator.java:37)
at
org.apache.tapestry5.services.TapestryModule$27.renderMarkup(TapestryMod
ule.java:1748)
at
$MarkupRenderer_122a244d64b.renderMarkup($MarkupRenderer_122a244d64b.jav
a)
at
org.apache.tapestry5.services.TapestryModule$26.renderMarkup(TapestryMod
ule.java:1732)
at
$MarkupRenderer_122a244d64b.renderMarkup($MarkupRenderer_122a244d64b.jav
a)
at
org.apache.tapestry5.services.TapestryModule$25.renderMarkup(TapestryMod
ule.java:1714)
at
$MarkupRenderer_122a244d64b.renderMarkup($MarkupRenderer_122a244d64b.jav
a)
at
org.apache.tapestry5.services.TapestryModule$24.renderMarkup(TapestryMod
ule.java:1700)
at
$MarkupRenderer_122a244d64b.renderMarkup($MarkupRenderer_122a244d64b.jav
a)
at
org.apache.tapestry5.services.TapestryModule$23.renderMarkup(TapestryMod
ule.java:1681)
at
$MarkupRenderer_122a244d64b.renderMarkup($MarkupRenderer_122a244d64b.jav
a)
at
org.apache.tapestry5.services.TapestryModule$22.renderMarkup(TapestryMod
ule.java:1662)
at
$MarkupRenderer_122a244d64b.renderMarkup($MarkupRenderer_122a244d64b.jav
a)
at
$MarkupRenderer_122a244d648.renderMarkup($MarkupRenderer_122a244d648.jav
a)
at
org.apache.tapestry5.internal.services.PageMarkupRendererImpl.renderPage
Markup(PageMarkupRendererImpl.java:64)
at
$PageMarkupRenderer_122a244d645.renderPageMarkup($PageMarkupRenderer_122
a244d645.java)
at
org.apache.tapestry5.internal.services.PageResponseRendererImpl.renderPa
geResponse(PageResponseRendererImpl.java:61)
at
$PageResponseRenderer_122a244d641.renderPageResponse($PageResponseRender
er_122a244d641.java)
at
org.apache.tapestry5.internal.services.PageRenderRequestHandlerImpl.hand
le(PageRenderRequestHandlerImpl.java:63)
at
org.apache.tapestry5.services.TapestryModule$33.handle(TapestryModule.ja
va:1943)
at
$PageRenderRequestHandler_122a244d642.handle($PageRenderRequestHandler_1
22a244d642.java)
at
$PageRenderRequestHandler_122a244d634.handle($PageRenderRequestHandler_1
22a244d634.java)
at
org.apache.tapestry5.internal.services.ComponentRequestHandlerTerminator
.handlePageRender(ComponentRequestHandlerTerminator.java:48)
at
$ComponentRequestHandler_122a244d638.handlePageRender($ComponentRequestH
andler_122a244d638.java)
at
org.apache.tapestry5.internal.services.PageRenderDispatcher.dispatch(Pag
eRenderDispatcher.java:45)
at
$Dispatcher_122a244d639.dispatch($Dispatcher_122a244d639.java)
at
$Dispatcher_122a244d5d6.dispatch($Dispatcher_122a244d5d6.java)
at
org.apache.tapestry5.services.TapestryModule$RequestHandlerTerminator.se
rvice(TapestryModule.java:245)
at
nu.localhost.tapestry5.springsecurity.services.internal.RequestFilterWra
pper$1.doFilter(RequestFilterWrapper.java:60)
at
nu.localhost.tapestry5.springsecurity.services.internal.SpringSecur

T5.1.0.5 IllegalStateException after invalidating Session

2009-07-22 Thread raucha

I try to upgrade an application from 5.0.18 to 5.1.0.5. After invalidating
the Session for the user logout I get the included Exception. Everything
works fine with 5.0.18 and I checked hat I do not invalidate the HttpSession
but invalidate the Tapestry Session via the injected
org.apache.tapestry5.services.Request.

The Exception I get:

java.lang.IllegalStateException

*
org.mortbay.jetty.servlet.AbstractSessionManager$Session.setAttribute(AbstractSessionManager.java:1050)
*
org.apache.tapestry5.internal.services.SessionImpl.setAttribute(SessionImpl.java:67)
*
org.apache.tapestry5.internal.services.AbstractSessionPersistentFieldStrategy.postChange(AbstractSessionPersistentFieldStrategy.java:131)
*
org.apache.tapestry5.internal.services.PersistentFieldManagerImpl.postChange(PersistentFieldManagerImpl.java:82)
*
$PersistentFieldManager_122a21dc7f4.postChange($PersistentFieldManager_122a21dc7f4.java)
*
org.apache.tapestry5.internal.structure.PageImpl.persistFieldChange(PageImpl.java:160)
*
org.apache.tapestry5.internal.structure.InternalComponentResourcesImpl.persistFieldChange(InternalComponentResourcesImpl.java:285)
*
de.creditreform.crefoteam.verwaltungsclient.components.Layout._$write_menu(Layout.java)
*
de.creditreform.crefoteam.verwaltungsclient.components.Layout.initMenu(Layout.java:190)
*
de.creditreform.crefoteam.verwaltungsclient.components.Layout.getMenu(Layout.java:143)
*
$PropertyConduit_122a21dc825.get($PropertyConduit_122a21dc825.java)
*
org.apache.tapestry5.internal.bindings.PropBinding.get(PropBinding.java:58)
*
org.apache.tapestry5.internal.structure.InternalComponentResourcesImpl$1.read(InternalComponentResourcesImpl.java:510)
*
org.apache.tapestry5.internal.structure.InternalComponentResourcesImpl$1.read(InternalComponentResourcesImpl.java:496)
*
org.apache.tapestry5.corelib.components.Loop._$read_parameter_source(Loop.java)
* org.apache.tapestry5.corelib.components.Loop.setup(Loop.java:312)
*
org.apache.tapestry5.corelib.components.Loop.setupRender(Loop.java)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$SetupRenderPhase.invokeComponent(ComponentPageElementImpl.java:184)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$AbstractPhase.run(ComponentPageElementImpl.java:164)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.invoke(ComponentPageElementImpl.java:933)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.access$400(ComponentPageElementImpl.java:49)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$AbstractPhase.callback(ComponentPageElementImpl.java:159)
*
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$SetupRenderPhase.render(ComponentPageElementImpl.java:189)
*
org.apache.tapestry5.internal.services.RenderQueueImpl.run(RenderQueueImpl.java:74)
*
org.apache.tapestry5.internal.services.PageRenderQueueImpl.render(PageRenderQueueImpl.java:121)
*
$PageRenderQueue_122a21dc889.render($PageRenderQueue_122a21dc889.java)
*
$PageRenderQueue_122a21dc86d.render($PageRenderQueue_122a21dc86d.java)
*
org.apache.tapestry5.internal.services.MarkupRendererTerminator.renderMarkup(MarkupRendererTerminator.java:37)
*
org.apache.tapestry5.services.TapestryModule$27.renderMarkup(TapestryModule.java:1748)
*
$MarkupRenderer_122a21dc88b.renderMarkup($MarkupRenderer_122a21dc88b.java)
*
org.apache.tapestry5.services.TapestryModule$26.renderMarkup(TapestryModule.java:1732)
*
$MarkupRenderer_122a21dc88b.renderMarkup($MarkupRenderer_122a21dc88b.java)
*
org.apache.tapestry5.services.TapestryModule$25.renderMarkup(TapestryModule.java:1714)
*
$MarkupRenderer_122a21dc88b.renderMarkup($MarkupRenderer_122a21dc88b.java)
*
org.apache.tapestry5.services.TapestryModule$24.renderMarkup(TapestryModule.java:1700)
*
$MarkupRenderer_122a21dc88b.renderMarkup($MarkupRenderer_122a21dc88b.java)
*
org.apache.tapestry5.services.TapestryModule$23.renderMarkup(TapestryModule.java:1681)
*
$MarkupRenderer_122a21dc88b.renderMarkup($MarkupRenderer_122a21dc88b.java)
*
org.apache.tapestry5.services.TapestryModule$22.renderMarkup(TapestryModule.java:1662)
*
$MarkupRenderer_122a21dc88b.renderMarkup($MarkupRenderer_122a21dc88b.java)
*
$MarkupRenderer_122a21dc888.renderMarkup($MarkupRenderer_122a21dc888.java)
*
org.apache.tapestry5.internal.services.PageMarkupRendererImpl.renderPageMarkup(PageMarkupRendererImpl.java:64)
*
$PageMarkupRenderer_122a21dc885.renderPageMarkup($PageMarkupRenderer_122a21dc885.java)
*
org.apache.tapestry5.internal.services.PageResponseRendererImpl.renderPageResponse(PageResponseRendererImpl.java:61)
*
$PageResponseRenderer_122a21dc881.renderPageResponse($PageR

RE: T5.1.0.5: StackMapTable format error

2009-07-22 Thread Newham, Cameron
Thanks Thiago, although it turned out to be because I'm using Java 1.6
and I had an old(ish) version of Javassist being brought in as a
dependency from tapestry-ioc that wants javassist-3.4.GA.

Specifying the latest Javassist (3.8.GA) in my POM solved the problem.

I note that I found this out from an email sent by Howard in 2007
addressing a query on StackMapTable error. I find it somewhat surprising
that this problem still occurs in 2009. Surely Tapestry 5.1.x should be
using the latest Javassist...



-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] 
Sent: 21 July 2009 14:58
To: Tapestry users
Subject: Re: T5.1.0.5: StackMapTable format error

Em Tue, 21 Jul 2009 10:18:21 -0300, Newham, Cameron
  
escreveu:

> Hi,

Hi!

> My Index page comes up fine when running my app from Jetty in Eclipse.
> However, as soon as I attempt to log in and Tapestry tries to go to
the
> app "home" page I get a StackMapTable format error.

Typically, strange errors are caused by having more than one version of

the same library in your classpath. You can also try to recompile all
the  
classes.

-- 
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

**
 
Experience the British Library online at www.bl.uk
 
The British Library's new interactive Annual Report and Accounts 2007/08 : 
www.bl.uk/knowledge
 
Help the British Library conserve the world's knowledge. Adopt a Book. 
www.bl.uk/adoptabook
 
The Library's St Pancras site is WiFi - enabled
 
*
 
The information contained in this e-mail is confidential and may be legally 
privileged. It is intended for the addressee(s) only. If you are not the 
intended recipient, please delete this e-mail and notify the postmas...@bl.uk : 
The contents of this e-mail must not be disclosed or copied without the 
sender's consent. 
 
The statements and opinions expressed in this message are those of the author 
and do not necessarily reflect those of the British Library. The British 
Library does not take any responsibility for the views of the author. 
 
*

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Is AjaxFormLoop example working for you?

2009-07-22 Thread moonlee

I use AjaxFormLoop-addrow-addrowlink-parameter to dynamic add a row , I want
to fill the row with some defult value which base on the link param user
click. 

for example: 

tml: 

 

  Add a row 



  Add a row 

 


java: 

PersonHolder onAddRow(Object value) { 
// Create a skeleton Person and add it to the displayed list
with a unique key 
Person newPerson = PersonService.findPersonById(value); 
PersonHolder newPersonHolder = new PersonHolder(newPerson,
true, 0 - System.nanoTime()); 
_personHolders.add(newPersonHolder); 

return newPersonHolder; 
} 


Geoff Callender-2 wrote:
> 
> Everyone,
> 
> Please try this quick experiment. I am trying to figure out why it  
> works for some people and not for others.
> 
> The experiment is: go to the following two pages and click on "Add a  
> row"...
> 
> 
> http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/tables/ajaxformloop1
> 
> http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/tables/ajaxformlooptailored1
> 
> Did it work? Please reply here with whether it worked or not, and  
> include whether you are running through a proxy, whether you OS is  
> Windows, and what country you are in.
> 
> Hopefully there's a pattern.
> 
> Thanks,
> 
> Geoff
> 
> P.S. The people who reported a problem say that the blackbird console  
> shows this kind of thing:
> 
> # Communication with the server failed: The rendered content did not  
> include any elements that allow for the positioning of the hidden form  
> field's element.
> # Ajax failure: Status 500 for /jumpstart/examples/tables/ 
> ajaxformlooptailored1 
> .ajaxformloop 
> .rowinjector:inject;jsessionid=3BB5CE5E0D166AC91A4561295B8F5151? 
> t:formcomponentid=examples/tables/ 
> AjaxFormLoopTailored1:personsedit&t:formid=personsedit: The rendered  
> content did not include any elements that allow for the positioning of  
> the hidden form field's element.
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Is-AjaxFormLoop-example-working-for-you--tp24526565p24603337.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: users-h...@tapestry.apache.org



Issue : Initialisation of javascript for form into a tapestry Zone

2009-07-22 Thread De Saint Steban Emmanuel
Is there anybody who can help me with this ?

In the tapestry doc page for the component Zone, I found this :
Not shown here, but fully valid, is to include JavaScript libraries and 
generate initialization JavaScript. This fully consistent with ordinary 
full-page renders.

It said it was fully valid but it doesn't work with me. How can I initialize 
the Javascript for the form.

Many thanks in advance.

Emmanuel

---
De : De Saint Steban Emmanuel
Envoyé : lundi 20 juillet 2009 17:46
À : 'users@tapestry.apache.org'
Objet : Using Form fragment into a tapestry Zone

Hi all,

If someone could help to this issue it will be great.
I want to use a form fragment into a Tapestry Zone. But when the zone is 
updated, the form fragment doesn't work.


// here my form



  
  
fragment1
  


  
  
fragment2
  




// Here code fragment



// Here code fragment






In the server when the form was submited in ajax (with Zone). I reload my Zone 
(myZone) to get a new formulaire, and also show some other stuff in my zone.  
For this I return myZone.getBody().
But when my zone is updated the form fragment doesn't work. I can't change my 
formfragment by clicking in the form Radio.  but in the first time (when I 
refresh the entire page), it's work perfectly.

It seems it was because the init javascript code from tapestry isn't relaoded. 
Because this code is at the end of page and was not reloaded when the zone is 
upadated.

Do you have an id how I could init again the javacript, or enable the form 
fragment.

Many thanks in advance for your help.

Emmanuel



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra 
être recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Origin group liability cannot be triggered 
for the message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: T5 - Configuration and .tml Files are Exposed By Tapestry.

2009-07-22 Thread Ulrich Stärk
There is no directory listing with 5.2-SNAPSHOT but I'm still able to 
access the templates and stuff on the classpath.


Uli

On 21.07.2009 03:13 schrieb Daniel Jones:

Hello,

OK, so here is my problem.

In my page template:
${asset:context:assets/images/layout/add.png} 


Tapestry generated URL to asset.

http://127.0.0.1:8080/assets/ctx/c69b95ec1fef872d/assets/images/layout/add.png

If I point my browser at:

http://127.0.0.1:8080/assets/ctx/c69b95ec1fef872d/

I get a directory listing including my .tml files, I can download these in
their raw form.  If I point my browser at http://127.0.0.1:8080/assets/  I
get a directory listing again, this time even more worrying as it contains
my hibernate.cfg.xml which can be downloaded exposing the database username
and password.

How do I fix this.  I used the maven archetype to build the project so the
layout looks normal when compared with
http://tapestry.apache.org/tapestry5/guide/project-layout.html

What am I doing wrong?

Any help is much appreciated.

Regards,
Daniel
  


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



RE: Passing data to the same page - Understanding PersistanceContext.FLASH

2009-07-22 Thread De Saint Steban Emmanuel


-Message d'origine-
De : Stephan Windmüller [mailto:stephan.windmuel...@cs.tu-dortmund.de]
Envoyé : mercredi 22 juillet 2009 10:50
À : Tapestry users
Objet : Re: Passing data to the same page - Understanding 
PersistanceContext.FLASH

De Saint Steban Emmanuel wrote:

> PersistanceContext.FLASH is storing the object for only one time.
> The data will be deleted after the first access.

Okay, but what is meant by "first access"? Even writing the data with a
debug logger? Or after the onActivate-method is finished? Is there a way
to keep the data in the page and pass it with the next request?

As says in the Tapestry documentation : 
http://tapestry.apache.org/tapestry5/guide/persist.html

flash strategy

The flash strategy stores information in the session as well, just for not very 
long. Values are stored into the session, but then deleted from the session as 
they are first used to restore a page's state.

The flash is typically used to store temporary messages that should only be 
displayed to the user once.

To keep data in the session just use @Persist by default is session persist. If 
you want to force session use @Persist("session")

> Use just @Persist (or if you want to access in all page of your
> application use @ApplicationState

This would break the use of multiple tabs, because I would only have one
store for many pages.

For one store for many page use @ApplicationState (it is store in the session) 
But you can use it in different page.

In each page, juste use

@ApplicationState
private type var;

Juste keep in mind that you can use a type only one time. Tapestry use the type 
to differences the different variable, not the name.

In exemple : You cant have to variable with the same type String. The two 
variable will be the same.

Emmanuel



Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra 
être recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Origin group liability cannot be triggered 
for the message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Passing data to the same page - Understanding PersistanceContext.FLASH

2009-07-22 Thread Stephan Windmüller
Kristian Marinkovic schrieb:

> you can use PersistenceConstants.CLIENT to store all your data 
> on the client side - with all iths pros and cons.

This creates a very long URL. I found no way to force client persistence
into a form.

> another way - when using a form - you can use the onPrepare, 
> onPrepareForRender and onPrepareForSubmit events to load
> the previous created/saved list from a persistent store.

It is really necessary to use a persistent store when all needed data is
transmitted with each submit of the form?

Regards
 Stephan

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Passing data to the same page - Understanding PersistanceContext.FLASH

2009-07-22 Thread Stephan Windmüller
De Saint Steban Emmanuel wrote:

> PersistanceContext.FLASH is storing the object for only one time.
> The data will be deleted after the first access.

Okay, but what is meant by "first access"? Even writing the data with a
debug logger? Or after the onActivate-method is finished? Is there a way
to keep the data in the page and pass it with the next request?

> Use just @Persist (or if you want to access in all page of your
> application use @ApplicationState

This would break the use of multiple tabs, because I would only have one
store for many pages.

- Stephan

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Passing data to the same page - Understanding PersistanceContext.FLASH

2009-07-22 Thread Kristian Marinkovic
you can use PersistenceConstants.CLIENT to store all your data 
on the client side - with all iths pros and cons.

or can store your data in the session wia SESSION or as 
SessionStateObject

another way - when using a form - you can use the onPrepare, 
onPrepareForRender and onPrepareForSubmit events to load
the previous created/saved list from a persistent store.

g,
kris




Stephan Windmüller  
22.07.2009 10:14
Bitte antworten an
"Tapestry users" 


An
Tapestry users 
Kopie

Thema
Re: Passing data to the same page - Understanding PersistanceContext.FLASH







Kristian Marinkovic wrote:

> in your case you'd need the session scope (=default)

But this will break if the user is creating several tasks in multiple
browser tabs.

When I summarize my issue it all comes to the following question: How do
I access data that is stored in objects and submitted completely with a
form after the submit without storing the data in the session?

I refuse to accept that Tapestry cannot handle this. There must be an
error in my code. The task data for example is completely restored with
PersistenceConstants.FLASH, but the List of users is not.

Regards
 Stephan

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org




RE: Passing data to the same page - Understanding PersistanceContext.FLASH

2009-07-22 Thread De Saint Steban Emmanuel
PersistanceContext.FLASH is storing the object for only one time. The data will 
be deleted after the first access.
Use just @Persist (or if you want to access in all page of your application use 
@ApplicationState

Emmanuel





Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? du groupe Atos Origin ne pourra 
?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Origin group liability cannot be triggered 
for the message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: [T5] Problems with commitAfter

2009-07-22 Thread jose luis sanchez

Hi all.
Maybe i missed some info ..
This code was inside a standard T5 page, with a hibernate session injected.

It's curious , because i find no reason for the code not to be commited, 
it's even not giving errors ... not even a rollback.



Ups...Sorry Jose i didn't notice u were using the @CommitAfter inside
ur components.


On Tue, Jul 21, 2009 at 10:55 PM, Howard Lewis Ship wrote:
  

On Tue, Jul 21, 2009 at 12:19 PM, Juan E. Maya wrote:


Hi Jose,

did u remember configure the HibernateTransactionAdviser as described
at the bottom of:
http://tapestry.apache.org/tapestry5/tapestry-hibernate/userguide.html
  

The advisor is only necessary when using @CommitAfter with your own
*services*.  The @CommitAfter annotation works with *components*
automatically.



?


On Tue, Jul 21, 2009 at 9:13 PM, jose luis
sanchez wrote:
  

Hello all.

I'm experiencing weird problems with the @CommitAfter tag ...

Have a hibernate schema, a configuration, and everything ok ( it runs ,
checked ), now, the only WAY of getting a data to be persisted into database
is using a transaction, like this

  @OnEvent(component="addCustomer",value="success")
  Object onSuccess() {
  Customer customer = (Customer) theSession.get(Customer.class,
theSubscription.getId());
  if (customer != null) {
  Transaction tx = theSession.beginTransaction();
  theSession.update(customer);
  tx.commit();
  }
  return null;
  }


Previously, the following did work, but it's not working now .. it just says
ok, it returns a generated Id , ( as seen in logs ) , but does not persist
the info in the table.
  @OnEvent(component="addCustomer",value="success")
  @CommitAfter
  Object onSuccess() {
  Customer customer = (Customer) theSession.get(Customer.class,
theSubscription.getId());
  if (customer != null) {
  theSession.update(customer);
  }
  return null;
  }


The bean is a java bean ( no Tapestry annotation at all, just the hbm.xml
file , unchanged )
Any help ?


My relevant information from hibernate.cfg
May the transaction factory have anything to do with the problem ?

  
  thread
  org.hibernate.transaction.JDBCTransactionFactory

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org


  


--
Howard M. Lewis Ship

Creator of Apache Tapestry
Director of Open Source Technology at Formos

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

  



-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Passing data to the same page - Understanding PersistanceContext.FLASH

2009-07-22 Thread Stephan Windmüller
Kristian Marinkovic wrote:

> in your case you'd need the session scope (=default)

But this will break if the user is creating several tasks in multiple
browser tabs.

When I summarize my issue it all comes to the following question: How do
I access data that is stored in objects and submitted completely with a
form after the submit without storing the data in the session?

I refuse to accept that Tapestry cannot handle this. There must be an
error in my code. The task data for example is completely restored with
PersistenceConstants.FLASH, but the List of users is not.

Regards
 Stephan

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Tapestry 5 Component Report

2009-07-22 Thread Cordenier Christophe
Hello all

I'm actually working on a component library, i would like to generate the 
component reference documentation, but it fails with this error :

Embedded error: Error rendering Maven report: Published parameter 'volatile' 
(from embedded component class org.apache.tapestry5.corelib.components.Grid) 
does not exist.

This is due to an embedded Grid component in one of my components. Is there a 
workaround for this is issue ? (exclude one component from report, provide Grid 
component sources...)

Thanks in advance,
Christophe.



Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage 
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant 
?tre assur?e sur Internet, la responsabilit? du groupe Atos Origin ne pourra 
?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne 
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Origin group liability cannot be triggered 
for the message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.


Re: Passing data to the same page - Understanding PersistanceContext.FLASH

2009-07-22 Thread Kristian Marinkovic
Tapestry 5 handles action requests and page requests. 
action requests identify a certain component or event 
that will be used to process the request. if the component
request has been processed a redirect (= second request)
page request is generated and issued. the flash persistence
strategy is used to store the data between the action request
and the redirect page request. in your case you'd need the
session scope (=default)

search the mailing list for more details 

g,
kris






Stephan Windmüller  
21.07.2009 18:31
Bitte antworten an
"Tapestry users" 


An
Tapestry users 
Kopie

Thema
Passing data to the same page - Understanding PersistanceContext.FLASH







Hello!

On a page I want the user to create a new task and add users to it. The
list of users should be extended with a button "Add another user" and is
displayed through a loop component.

| 
| 
|  
| 
| 
|  
| 
| 
|  
| 
| 
| 
| 
|  
| 
| 

To realize this I annotated the task and the list of users with
@Persist(PersistanceConstants.FLASH)and added a method set(task,
List) to the submit logic of the form.

| @Persist(PersistenceConstants.FLASH)
| @Property
| private Task task;
|
| @Persist(PersistenceConstants.FLASH)
| @Property
| private List users;
|
| void set(Task task, List users) {
|this.task = task;
|this.users = users;
| }

Now when I click the "Add another user" button the task data is
correctly restored and put into the form. Also the first user is
displayed correctly.

| @OnEvent(value = "selected", component = "addUser")
| void addUserObject() {
|users.add(new User());
| 
|users = newUsers;
| 
|newTaskPage.set(task, users);
|nextPage = newTaskPage;
| }

But when I enter another user and press the button "Add another user"
once again, this user is not stored. Instead, the onActivate method
tells me that the list of users is null during activation. Why is that?

On the web I found several instructions on how to pass data to other
pages, but not to the same page.

>From what I understood is that PersistanceConstants.FLASH stores the
data in the session for the next request. This is only correctly set if
I use @InjectPage and a set-method, correct? But why can I use my task
object over several requests and the user list only once?

All I am dealing with are a number of strings which are always part of
the form so I do not need client persistence. How can I store them
correctly?

TIA
 Stephan

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org