Re: Hibernate validator
+1! FYI, see http://opensource.atlassian.com/projects/hibernate/browse/HV-44 . Good luck! Olle 2008/5/18 Toby Hobson [EMAIL PROTECTED]: Hi I was thinking of integrating the hibernate-validator with T5's validation framework (or trying to!) so I can re-use the validation rules I have already defined on my model (kinda like JBoss seam). Firstly is anyone else working on anything like this? Secondly do you think this would be useful to the Tapestry community? Thanks Toby -- Olle Hallin M.Sc. +46 70 6653071 [EMAIL PROTECTED] www.hit.se
Re: T5: Exception Handling
Hi Filip,
Thanks for your answer. I understand now.
But one final question. How does your redirectService looks like?
Leon
Filip S. Adamsen wrote:
Hi Leon,
How to override server error pages depends on what server you're
using. As far as I'm aware it's unfortunately not possible to use
Tapestry pages as server error pages - if I'm wrong here, I'd really
like to know how to do it. :)
What I mean by turning the RequestExceptionHandler into a pipeline is
that I've overridden the original service with my own that uses a
pipeline.
http://tapestry.apache.org/tapestry5/tapestry-ioc/pipeline.html
So I define my filter:
public interface RequestExceptionFilter {
void handleRequestException(Throwable exception,
RequestExceptionHandler handler)
throws IOException;
}
Then I create a new RequestExceptionHandler as a pipeline:
public static RequestExceptionHandler
buildImprovedRequestExceptionHandler(
ListRequestExceptionFilter configuration,
@InjectService(RequestExceptionHandler)
RequestExceptionHandler requestExceptionHandler,
PipelineBuilder builder,
Logger logger
) {
return builder.build(
logger,
RequestExceptionHandler.class,
RequestExceptionFilter.class,
configuration,
requestExceptionHandler
);
}
I then contribute this to AliasOverrides to replace the default
RequestExceptionHandler:
public static void contributeAliasOverrides(
ConfigurationAliasContribution configuration,
@InjectService(ImprovedRequestExceptionHandler)
RequestExceptionHandler requestExceptionHandler
) {
configuration.add(AliasContribution.create(RequestExceptionHandler.class,
requestExceptionHandler));
}
I can then contribute filters to the pipeline like this:
public static void contributeImprovedRequestExceptionHandler(
OrderedConfigurationRequestExceptionFilter configuration,
RequestExceptionErrorFilter requestExceptionErrorFilter
) {
configuration.add(Error, requestExceptionErrorFilter);
}
Where RequestExceptionErrorFilter looks like this:
public class RequestExceptionErrorFilter
implements RequestExceptionFilter {
private final RedirectService redirectService;
private final SecurityService securityService;
private final Logger logger;
public RequestExceptionErrorFilter(RedirectService
redirectService, SecurityService securityService, Logger logger) {
this.redirectService = redirectService;
this.securityService = securityService;
this.logger = logger;
}
public void handleRequestException(Throwable exception,
RequestExceptionHandler handler)
throws IOException {
if (securityService.isProductionModeEnabled()) {
logger.error(Exception during request, exception);
redirectService.sendRedirect(ErrorIndex.class, false);
}
else {
handler.handleRequestException(exception);
}
}
}
RedirectService and SecurityService are my own classes. They just make
some things easier for me. As you can see I show an error page when
I'm in production but invoke the next filter in the pipeline if I'm
not. You could contribute more filters if needed.
I've been wanting to contribute a strategy filter before this one
allowing to do different things depending on the type of exception
thrown, but haven't had the time nor need to do so yet.
http://tapestry.apache.org/tapestry5/tapestry-ioc/strategy.html
Anyhow, hope this helps - if not, you know where to ask. :)
-Filip
On 2008-05-16 17:37, Leon Derks wrote:
Thanks Peter,
Your original question in the post is also what I would like to know.
Do you now know how to override server error pages(404, 505 etc)?
And I don't understand what Flip means with :I've turned the
RequestExceptionHandler service into a pipeline.
Can you show me some code of how to do this?
Leon
Peter Stavrinides wrote:
Hi Leon
I posted a number of questions to the list about this topic, but got
only a few perls. One of them was this post, particularly Filip's
answer:
http://www.mail-archive.com/users@tapestry.apache.org/msg21914.html
Also see this page, for how to override Tapestry's error page with
your own friendly error page:
http://wiki.apache.org/tapestry/Tapestry5ExceptionPage
I am not sure what you are trying to do, but would suggest you
familiarize yourself a bit more with Tapestry's error reporting
mechanisms, which imho are incredibly powerful and easy to use.
Hope this helps,
Peter
- Original Message -
From: Leon Derks [EMAIL PROTECTED]
To: Tapestry users users@tapestry.apache.org
Sent: Friday, 16 May, 2008 1:35:19 PM GMT +02:00 Athens, Beirut,
Bucharest, Istanbul
Subject: T5: Exception Handling
Hello
What is the best way to handle exceptions in Tapestry 5?
I want to show some kind of general error page, when an exception
occurs.
At the moment I have a onException method in my BasePage class. But
for some
Override service injection
Hi,
I'm still trying to work around something I'm not really sure on how
to solve :)
My contribution looks like this:
public static void contributeHttpServletRequestHandler(
OrderedConfigurationHttpServletRequestFilter configuration,
@InjectService(HttpSessionContextIntegrationFilter)
HttpServletRequestFilter httpSessionContextIntegrationFilter,
@InjectService(AuthenticationProcessingFilter)
HttpServletRequestFilter authenticationProcessingFilter,
[snip...]
) {
configuration.add(acegiHttpSessionContextIntegrationFilter,
httpSessionContextIntegrationFilter, before:acegi*);
configuration.add(acegiAuthenticationProcessingFilter,
authenticationProcessingFilter);
[snip...]
}
As currently it's not possible to override on the OrderedContribution
itself, I was thinking on how to solve it at the injected part
instead. As there are several services implementing
HttpServletRequestFilter I must inject via name, but how can I
override that? Inject a string value with the name of the service and
look up the service without using method properties injection?
--
regards,
Robin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Override service injection
have you tried contributing an alias for your named service?
take a look at
http://tapestry.apache.org/tapestry5/tapestry-core/guide/alias.html
g,
kris
Robin Helgelin [EMAIL PROTECTED]
19.05.2008 10:09
Bitte antworten an
Tapestry users users@tapestry.apache.org
An
Tapestry users users@tapestry.apache.org
Kopie
Thema
Override service injection
Hi,
I'm still trying to work around something I'm not really sure on how
to solve :)
My contribution looks like this:
public static void contributeHttpServletRequestHandler(
OrderedConfigurationHttpServletRequestFilter configuration,
@InjectService(HttpSessionContextIntegrationFilter)
HttpServletRequestFilter httpSessionContextIntegrationFilter,
@InjectService(AuthenticationProcessingFilter)
HttpServletRequestFilter authenticationProcessingFilter,
[snip...]
) {
configuration.add(acegiHttpSessionContextIntegrationFilter,
httpSessionContextIntegrationFilter, before:acegi*);
configuration.add(acegiAuthenticationProcessingFilter,
authenticationProcessingFilter);
[snip...]
}
As currently it's not possible to override on the OrderedContribution
itself, I was thinking on how to solve it at the injected part
instead. As there are several services implementing
HttpServletRequestFilter I must inject via name, but how can I
override that? Inject a string value with the name of the service and
look up the service without using method properties injection?
--
regards,
Robin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Override service injection
On Mon, May 19, 2008 at 10:20 AM, Kristian Marinkovic [EMAIL PROTECTED] wrote: have you tried contributing an alias for your named service? take a look at http://tapestry.apache.org/tapestry5/tapestry-core/guide/alias.html Yes, but wouldn't that break as several services implements the same interface? -- regards, Robin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5: Exception Handling
Just a little side note:
Filip is right, you can't use a Tapestry page for these, but that is probably
the correct behavior as this is a different type of error (an exception to the
rule if you like) which the server needs to handle by explicitly interrupting a
request/response and generating a new one on the server in accordance with the
error condition... For example a page not found has little to do with your
Tapestry application, but the server is still being addressed and needs to
respond. So you wouldn't want a Tapestry to handle these IMHO, but that doesn't
stop tapestry apps from making use of them when required! (using
response.sendError)
To configure:
You would simply use a standard JSP / HTML error page, and wire it in your
web.xml. I am using Tomcat and it works great... works on Jetty too. The only
error page/s I can't get to override perfectly are 401 and 503, but I have
found some workarounds for these.
503 is a service unavailable/ under maintenance error and will occur when the
server is running but the application is not, so wouldn't make sense using it
in your app anyhow. I found Tomcat is a little deficient here, see:
http://www.nabble.com/Error-Page-Question-td16153138.html (if anyone has solved
this please share).For the 401 authentication error, I simply use a 403
forbidden instead, but I can get away with this as I am using forms
authentication.
I had thought about putting some of this stuff on the wiki... as yet I haven't
because error handling can be very scenario specific. Anyway here is a short
example of how to configure your server error page:
Add to web.xml:
error-page
error-code404/error-code
location/error404.jsp/location
/error-page
error404.jsp: (Important - create this file in /webapp) and NOT in
/webapp/WEB-INF
%@ page isErrorPage=true %
html xmlns:t=http://tapestry.apache.org/schema/tapestry_5_0_0.xsd;
head
titleError 404 Page Not Found/title
/head
body
h1Page Not Found/h1br/br/
div
We apologise for any inconvenience, but the resource you have
specified cannot be found, please check the URL is typed correctly.
br/br/
If you require assistance please contact client support. To continue a
href=JavaScript:history.go(-1)return to the previous page/a.br/br/
/div
/body
/html
As simple as that...
Cheers,
Peter.
- Original Message -
From: Filip S. Adamsen [EMAIL PROTECTED]
To: Tapestry users users@tapestry.apache.org
Sent: Sunday, 18 May, 2008 1:39:31 AM GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: T5: Exception Handling
Hi Leon,
How to override server error pages depends on what server you're using.
As far as I'm aware it's unfortunately not possible to use Tapestry
pages as server error pages - if I'm wrong here, I'd really like to know
how to do it. :)
What I mean by turning the RequestExceptionHandler into a pipeline is
that I've overridden the original service with my own that uses a pipeline.
http://tapestry.apache.org/tapestry5/tapestry-ioc/pipeline.html
So I define my filter:
public interface RequestExceptionFilter {
void handleRequestException(Throwable exception,
RequestExceptionHandler handler)
throws IOException;
}
Then I create a new RequestExceptionHandler as a pipeline:
public static RequestExceptionHandler
buildImprovedRequestExceptionHandler(
ListRequestExceptionFilter configuration,
@InjectService(RequestExceptionHandler) RequestExceptionHandler
requestExceptionHandler,
PipelineBuilder builder,
Logger logger
) {
return builder.build(
logger,
RequestExceptionHandler.class,
RequestExceptionFilter.class,
configuration,
requestExceptionHandler
);
}
I then contribute this to AliasOverrides to replace the default
RequestExceptionHandler:
public static void contributeAliasOverrides(
ConfigurationAliasContribution configuration,
@InjectService(ImprovedRequestExceptionHandler)
RequestExceptionHandler requestExceptionHandler
) {
configuration.add(AliasContribution.create(RequestExceptionHandler.class,
requestExceptionHandler));
}
I can then contribute filters to the pipeline like this:
public static void contributeImprovedRequestExceptionHandler(
OrderedConfigurationRequestExceptionFilter configuration,
RequestExceptionErrorFilter requestExceptionErrorFilter
) {
configuration.add(Error, requestExceptionErrorFilter);
}
Where RequestExceptionErrorFilter looks like this:
public class RequestExceptionErrorFilter
implements RequestExceptionFilter {
private final RedirectService redirectService;
private final SecurityService securityService;
private final Logger logger;
public RequestExceptionErrorFilter(RedirectService redirectService,
SecurityService securityService, Logger logger) {
this.redirectService = redirectService;
Re: Little confused
I would definitely avoid using this:
private Matafuego matafuego = new Matafuego();
This is the correct way to initialize beans for forms
void onPrepare(){
if (matafuego == null)
matafuego = new Matafuego();
}
You shouldn't use/need a @Persist, at best a @Persist(flash) if you post to
the same page.
- Original Message -
From: Manuel Corrales [EMAIL PROTECTED]
To: Tapestry users users@tapestry.apache.org
Sent: Sunday, 18 May, 2008 5:33:58 PM GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Little confused
Hi Filip, i have no @Property annotation on my Tapestry version. What
version are you using?
On Sat, May 17, 2008 at 7:55 PM, Filip S. Adamsen [EMAIL PROTECTED] wrote:
Hi,
I've found the following pattern to work very well - at least I use it
everywhere on several sites in production with no problems. :)
@Property
private Item item;
// I have a form in my template with t:id=add
void onPrepareFromAdd() {
if (null == item) item = new Item();
}
void onSuccessFromAdd() {
// go about my business with the item
...
// I'd normally return here, but since you need
// something done in onSubmit...
}
Object onSubmitFromAdd() {
// do what you need to do
return ...;
}
I sometimes persist the item if needed.
Hope this helps.
-Filip
On 2008-05-17 16:01, Manuel Corrales wrote:
Hi, here is my problem. I have a bean on my java page, but i am not using
the beaneditorform component to create a new one. Acording to Alexander
book, the beaneditorform component can handle the initialization of the
bean, so you dont have to create one. As i am not using this component,
should i define the bean with a sentence like this:
private Matafuego matafuego = new Matafuego();
or should i create the new instance on the onActivate method?
I tryied the first approach, but the bean is always the same (i guess
because of the page pooling mechanism). What is the right approach to
this?
Thanks very much.
-
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: Override service injection
On Mon, May 19, 2008 at 10:20 AM, Kristian Marinkovic [EMAIL PROTECTED] wrote: have you tried contributing an alias for your named service? take a look at http://tapestry.apache.org/tapestry5/tapestry-core/guide/alias.html Actually I manage to solve this via aliases by splitting my service into several small services. -- regards, Robin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
T5: Ajax periodic update
Hi list,
I'd like to know if there is a simple way to perform a periodic Ajax update
request.
I've invented hacked a solution using the Ajax.PeriodicalUpdater from
prototype.js. It involves putting an ActionLink on the page, giving it a
client id, making it invisible to the user (with display: none), and then
making a new Ajax.PeriodicalUpdater using the a.href from the ActionLink.
The result of this call is a string containing the content generated by the
Block element, which I must then parse. If I do not manipulate the
response, the Zone will contain something like { content : blah blah blah
}.
I'm not crazy about my solution, and, moreover, it results in a mysterious
403 Forbidden reply on some platforms.
Otherwise, having great fun with T5. Keep up the excellent work!
Regards,
Marc
--
View this message in context:
http://www.nabble.com/T5%3A-Ajax-periodic-update-tp17315174p17315174.html
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: Error serializing component action for component Gears:loop:
Hello You can take a look at the 'volatile' parameter of loop component. Default is false. Christophe. -Message d'origine- De : Leon Derks [mailto:[EMAIL PROTECTED] Envoyé : lundi 19 mai 2008 13:51 À : Tapestry users Objet : Error serializing component action for component Gears:loop: Hello I did get the error :Error serializing component action for component Gears:loop: When I add implements Serializable to my Gear class everything works fine. But I have also other objects that I looped throught with a t:type=loop but these objects didn't need an implements Serializable. So what makes it that my Gear object needs an implements Serializable ? All my other objects are extending BaseEntity and the Gear is extending Product (which again extends BaseEntity). Leon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dispatcher doesn't get called in default start page
I've registered a Dispatcher class which works just fine except when the page name is not specified in the URL. So, if i put http://localhost:8080/mycontext/start the Dispatcher is called like expected, but if i access http://localhost:8080/mycontext/ although the same start page shows up the Dispatcher isn't executed at all. Is this expected behaviour or maybe a bug ? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dispatcher doesn't get called in default start page
Hi, This is probably correct. The handling of 'mapping' your app's default page is also accomplished by a dispatcher. I /think/ its name is 'RootDispatcher' but don't quote me on that - look for details in TapestryModule. If you want your dispatcher to fire first you'll need to place it :before the root. chris Hugo Palma wrote: I've registered a Dispatcher class which works just fine except when the page name is not specified in the URL. So, if i put http://localhost:8080/mycontext/start the Dispatcher is called like expected, but if i access http://localhost:8080/mycontext/ although the same start page shows up the Dispatcher isn't executed at all. Is this expected behaviour or maybe a bug ? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://thegodcode.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dispatcher doesn't get called in default start page
Yep, using before:RootPath as a constraint when registering my Dispatcher did the trick. Thanks. Chris Lewis wrote: Hi, This is probably correct. The handling of 'mapping' your app's default page is also accomplished by a dispatcher. I /think/ its name is 'RootDispatcher' but don't quote me on that - look for details in TapestryModule. If you want your dispatcher to fire first you'll need to place it :before the root. chris Hugo Palma wrote: I've registered a Dispatcher class which works just fine except when the page name is not specified in the URL. So, if i put http://localhost:8080/mycontext/start the Dispatcher is called like expected, but if i access http://localhost:8080/mycontext/ although the same start page shows up the Dispatcher isn't executed at all. Is this expected behaviour or maybe a bug ? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Form with errors
Hi, i have a left menu with a link (Add new Item). When i press the link, i go to a form to create a new Item. If i have some server side validation error, the error messages are shown on the screen, but the issue is that if i press the Add new Item from the left menu, the form does not clean itself, i mean the errors are still there and the form have the values i was entering. Is this the right behavior? How can i do to get a new clean form each time i press the link? Thanks in advance!
Re: T5: Exception Handling
On 5/19/08, Peter Stavrinides [EMAIL PROTECTED] wrote: To configure: You would simply use a standard JSP / HTML error page, and wire it in your web.xml. I am using Tomcat and it works great... works on Jetty too. Something I've done once is to setup a 404.html page that redirects to a Tapestry page via Javascript, including the original URL so I can log it. ;) -- Thiago - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5: Exception Handling
Hi,
It looks like this:
public interface RedirectService {
void sendRedirect(Class? pageClass, boolean override, Object...
context);
}
Implemented as:
public class RedirectServiceImpl
implements RedirectService {
private final ComponentClassResolver componentClassResolver;
private final ComponentSource componentSource;
private final Response response;
public RedirectServiceImpl(ComponentClassResolver
componentClassResolver, ComponentSource componentSource,
Response response) {
this.componentClassResolver = componentClassResolver;
this.componentSource = componentSource;
this.response = response;
}
public void sendRedirect(Class? pageClass, boolean override,
Object... context) {
String pageName =
componentClassResolver.resolvePageClassNameToPageName(pageClass.getCanonicalName());
Link link =
componentSource.getPage(pageName).getComponentResources().createPageLink(pageName,
false, context);
try {
response.sendRedirect(link);
}
catch (IOException ex) {
throw new RuntimeException(IOException while redirecting, ex);
}
}
}
-Filip
Leon Derks skrev:
Hi Filip,
Thanks for your answer. I understand now.
But one final question. How does your redirectService looks like?
Leon
Filip S. Adamsen wrote:
Hi Leon,
How to override server error pages depends on what server you're
using. As far as I'm aware it's unfortunately not possible to use
Tapestry pages as server error pages - if I'm wrong here, I'd really
like to know how to do it. :)
What I mean by turning the RequestExceptionHandler into a pipeline is
that I've overridden the original service with my own that uses a
pipeline.
http://tapestry.apache.org/tapestry5/tapestry-ioc/pipeline.html
So I define my filter:
public interface RequestExceptionFilter {
void handleRequestException(Throwable exception,
RequestExceptionHandler handler)
throws IOException;
}
Then I create a new RequestExceptionHandler as a pipeline:
public static RequestExceptionHandler
buildImprovedRequestExceptionHandler(
ListRequestExceptionFilter configuration,
@InjectService(RequestExceptionHandler)
RequestExceptionHandler requestExceptionHandler,
PipelineBuilder builder,
Logger logger
) {
return builder.build(
logger,
RequestExceptionHandler.class,
RequestExceptionFilter.class,
configuration,
requestExceptionHandler
);
}
I then contribute this to AliasOverrides to replace the default
RequestExceptionHandler:
public static void contributeAliasOverrides(
ConfigurationAliasContribution configuration,
@InjectService(ImprovedRequestExceptionHandler)
RequestExceptionHandler requestExceptionHandler
) {
configuration.add(AliasContribution.create(RequestExceptionHandler.class,
requestExceptionHandler));
}
I can then contribute filters to the pipeline like this:
public static void contributeImprovedRequestExceptionHandler(
OrderedConfigurationRequestExceptionFilter configuration,
RequestExceptionErrorFilter requestExceptionErrorFilter
) {
configuration.add(Error, requestExceptionErrorFilter);
}
Where RequestExceptionErrorFilter looks like this:
public class RequestExceptionErrorFilter
implements RequestExceptionFilter {
private final RedirectService redirectService;
private final SecurityService securityService;
private final Logger logger;
public RequestExceptionErrorFilter(RedirectService
redirectService, SecurityService securityService, Logger logger) {
this.redirectService = redirectService;
this.securityService = securityService;
this.logger = logger;
}
public void handleRequestException(Throwable exception,
RequestExceptionHandler handler)
throws IOException {
if (securityService.isProductionModeEnabled()) {
logger.error(Exception during request, exception);
redirectService.sendRedirect(ErrorIndex.class, false);
}
else {
handler.handleRequestException(exception);
}
}
}
RedirectService and SecurityService are my own classes. They just make
some things easier for me. As you can see I show an error page when
I'm in production but invoke the next filter in the pipeline if I'm
not. You could contribute more filters if needed.
I've been wanting to contribute a strategy filter before this one
allowing to do different things depending on the type of exception
thrown, but haven't had the time nor need to do so yet.
http://tapestry.apache.org/tapestry5/tapestry-ioc/strategy.html
Anyhow, hope this helps - if not, you know where to ask. :)
-Filip
On 2008-05-16 17:37, Leon Derks wrote:
Thanks Peter,
Your original question in the post is also what I would like to know.
Do you now know how to override server error pages(404, 505 etc)?
And I don't
Re: T5: Exception Handling
Now why hadn't I thought of that... :D Thanks! -Filip Thiago HP skrev: On 5/19/08, Peter Stavrinides [EMAIL PROTECTED] wrote: To configure: You would simply use a standard JSP / HTML error page, and wire it in your web.xml. I am using Tomcat and it works great... works on Jetty too. Something I've done once is to setup a 404.html page that redirects to a Tapestry page via Javascript, including the original URL so I can log it. ;) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5: Exception Handling
On 5/19/08, Filip S. Adamsen [EMAIL PROTECTED] wrote: Now why hadn't I thought of that... :D Sometimes, a solution is so simple that we unconciously search for more complicated ones . . . :) Thanks! You're welcome! -- Thiago - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5: Exception Handling
Given that a JSP is basically a servlet, why not do something like % response.include(request.getContextPath() + /MyTapestryErrorPage); % from your jsp exception page btw I can't remember - can you map an exception handler to a servlet in web.xml? Toby - Original Message From: Thiago HP [EMAIL PROTECTED] To: Tapestry users users@tapestry.apache.org Sent: Monday, 19 May, 2008 2:52:02 PM Subject: Re: T5: Exception Handling On 5/19/08, Peter Stavrinides [EMAIL PROTECTED] wrote: To configure: You would simply use a standard JSP / HTML error page, and wire it in your web.xml. I am using Tomcat and it works great... works on Jetty too. Something I've done once is to setup a 404.html page that redirects to a Tapestry page via Javascript, including the original URL so I can log it. ;) -- Thiago - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Form - asyn submission with file upload
After trying to async submit a form with a file upload field for a few hours I trolled around the message board and JIRA and ran across this: http://issues.apache.org/jira/browse/TAPESTRY-1348 Is trying to async submit a form with a file upload field a DEAD END? We tried to add the IFrame transport mechanism . . . however this did not trigger the request. Looking at the code it appears that the IFrame transport mechanism does not support async submissions etc. The tacos bug system has a related bug that mentions other changes that may be necessary to fix this: http://tacoscomponents.jot.com/BugReporter/Bug62 Has anyone been able to successfully async submit a form with a file upload field? Carlos
T5: how to get hold of an id in a loop component?
Hi,
I have a loop with elements from type Card.
Initially the loop shows as many (same) images as there are in the Vector
cardsLayout.
If I click on one of these pictures I would like to show the card's text in
place of this picture.
Something like:
if image at position of card with id=4 gets clicked, show all other images like
before, but show at position with id=4
a text instead of this image.
Is there some use of if/else possible? Or what would be the aproach of getting
hold of the clicked element?
span t:type=loop t:source=cardsLayout t:value=card
t:actionlink t:context=card.id t:id=turnCard
span class=background24img
src=bilder/deckblatt24.jpg //span
!-- on the clicked id I want to show this instead of
the image:
span class=background24${card.text}/span
--
/t:actionlink
/span
I also tried to use some javascript but for some reason the javascript code
gets ignored..
It is only my first week learning tapestry so please excuse me if I miss
something obviously..
thanks for helping!
Juliane
_
Unbegrenzter Speicherplatz für Ihr E-Mail Postfach? Jetzt aktivieren!
http://freemail.web.de/club/landingpage.htm/?mc=02
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: getting ClassFactory is matched by 2 services After upgrade from 5.06 - 5.0.11
Add the injection point (i.e., the constructor parameter) add either the @Builtin or the @ComponentLayer annotation. This marker annotation will select the correct implementation: either the general ClassFactory (used by the IoC container) or the one used when working with component code. You probably want @Builtin. On Sun, May 18, 2008 at 6:40 AM, Britske [EMAIL PROTECTED] wrote: After upgrading tapestry from 5.0.6 to 5.0.11 I'm getting the following error: Caused by: java.lang.RuntimeException: Service interface org.apache.tapestry.ioc.services.ClassFactory is matched by 2 services: ClassFactory, ComponentClassFactory. Automatic dependency resolution requires that exactly one service implement the interface. I'm getting the error (I think), I'm just not sure where to look to change it. For instance, I have nothing defined in my AppModule that could be the cause. Anyone? Thanks, Britske -- View this message in context: http://www.nabble.com/getting-ClassFactory-is-matched-by-2-services-After-upgrade-from-5.06--%3E-5.0.11-tp17303089p17303089.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Instability in Tapestry 5.0.12-SNAPSHOT
A few people have noticed some significant changes in Tapestry 5.0.12-SNAPSHOT. What's going on is a limited number of interface and package renames to support deploying Tapestry 3 or 4 and Tapestry 5 in the same web application (WAR). Most of the conflicts were related Tapestry annotations in T4 vs. T5. The org.apache.tapestry.annotations package was renamed to org.apache.tapestry.annotation (for T5) so as not to conflict with the same named package, and overalapping annotation class names, from T4. I'm still experimenting, but this dual headed deployment will be the best upgrade path from T3/T4 to T5. I expect to follow up with new T5 tools to make sharing data between the apps easier. Sorry for the disruption this late in the game. The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5: how to get hold of an id in a loop component?
I'm sure there are many ways of doing this but here is an idea:
Page.java
@Persist(flash)
private Card selectedCard // or you could use the primary key if your Object
has one
@Property
private Card card // this is the current card the loop is processing
void onActionFromSelectCard(Card card) {
selectedCard = card;
}
boolean isCardSelected() {
return card.equals(selectedCard) // or card.getId().equals(id)
}
The loop:
t:loop source=cards value=card
t:if test=cardSelected
// do something special
/t:test
t:unless cardSelected
// do something normal
/t:test
/t:loop
The action link
t:actionLink t:id=selectCard t:context=cardclick me/t:actionLink
Here's how it works:
When the loop iterates through the cards it sets the card property to card it
is currently processing, so we can compare the current card in the loop with
the card the user selected and see if they match. One important point - T5 uses
a redirect-after-post mechanism so we need to persist the selected card between
requests, otherwise the user would select the card the the browser would sent a
new GET request and T would reset the selectedCard property.
It is only my first week learning tapestry so please excuse me if I miss
something obviously..
Dont worry .. I'm also learning!
Toby
- Original Message
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: users@tapestry.apache.org
Sent: Monday, 19 May, 2008 3:45:20 PM
Subject: T5: how to get hold of an id in a loop component?
Hi,
I have a loop with elements from type Card.
Initially the loop shows as many (same) images as there are in the Vector
cardsLayout.
If I click on one of these pictures I would like to show the card's text in
place of this picture.
Something like:
if image at position of card with id=4 gets clicked, show all other images like
before, but show at position with id=4
a text instead of this image.
Is there some use of if/else possible? Or what would be the aproach of getting
hold of the clicked element?
span t:type=loop t:source=cardsLayout t:value=card
t:actionlink t:context=card.id t:id=turnCard
span class=background24img src=bilder/deckblatt24.jpg
//span
!-- on the clicked id I want to show this instead of the image:
span class=background24${card.text}/span
--
/t:actionlink
/span
I also tried to use some javascript but for some reason the javascript code
gets ignored..
It is only my first week learning tapestry so please excuse me if I miss
something obviously..
thanks for helping!
Juliane
_
Unbegrenzter Speicherplatz für Ihr E-Mail Postfach? Jetzt aktivieren!
http://freemail.web.de/club/landingpage.htm/?mc=02
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Instability in Tapestry 5.0.12-SNAPSHOT
+1 org.apache.tapestry5. Refactor once, have piece of mind forever. On Mon, May 19, 2008 at 9:57 AM, Howard Lewis Ship [EMAIL PROTECTED] wrote: A few people have noticed some significant changes in Tapestry 5.0.12-SNAPSHOT. What's going on is a limited number of interface and package renames to support deploying Tapestry 3 or 4 and Tapestry 5 in the same web application (WAR). Most of the conflicts were related Tapestry annotations in T4 vs. T5. The org.apache.tapestry.annotations package was renamed to org.apache.tapestry.annotation (for T5) so as not to conflict with the same named package, and overalapping annotation class names, from T4. I'm still experimenting, but this dual headed deployment will be the best upgrade path from T3/T4 to T5. I expect to follow up with new T5 tools to make sharing data between the apps easier. Sorry for the disruption this late in the game. The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind - 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: Instability in Tapestry 5.0.12-SNAPSHOT
+1 org.apache.tapestry5. Less margin for confusion, as the difference between package names wouldn't be hust a 's' letter. The more explicit, the better. Thiago - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Instability in Tapestry 5.0.12-SNAPSHOT
I'd rather suggest org.apache.tapestry.t5 or .v5. Entirely an aesthetic thing, but just putting it out there. Clearly there's no semantic difference. Christian. On 19-May-08, at 11:02 , Massimo Lusetti wrote: On Mon, May 19, 2008 at 4:57 PM, Howard Lewis Ship [EMAIL PROTECTED] wrote: The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. I would say yes. -- Massimo http://meridio.blogspot.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: Instability in Tapestry 5.0.12-SNAPSHOT
+1 org.apache.tapestry5... now or nevern! :) this will make it much easier to add new t5 pages to existing t4 applications. Thiago HP [EMAIL PROTECTED] 19.05.2008 17:10 Bitte antworten an Tapestry users users@tapestry.apache.org An Tapestry users users@tapestry.apache.org Kopie Thema Re: Instability in Tapestry 5.0.12-SNAPSHOT +1 org.apache.tapestry5. Less margin for confusion, as the difference between package names wouldn't be hust a 's' letter. The more explicit, the better. Thiago - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Instability in Tapestry 5.0.12-SNAPSHOT
Tapestry group, is org.apache.tapestry more different version: v3, v4 and v5. Because v5 version is 5.0.4, 5.0.5, ... and 5.0.11. Then: org.apache.tapestry.v3, org.apache.tapestry.v4 and org.apache.tapestry.v5 I am speaking OPINION! -- Regards, Estevam Henrique Portela Mota e Silva Handicapped Auditory = deaf [EMAIL PROTECTED] / [EMAIL PROTECTED] Programmer Java and Tapestry Brazil - Fortaleza / CE On Mon, May 19, 2008 at 12:16 PM, Kristian Marinkovic [EMAIL PROTECTED] wrote: +1 org.apache.tapestry5... now or nevern! :) this will make it much easier to add new t5 pages to existing t4 applications. Thiago HP [EMAIL PROTECTED] 19.05.2008 17:10 Bitte antworten an Tapestry users users@tapestry.apache.org An Tapestry users users@tapestry.apache.org Kopie Thema Re: Instability in Tapestry 5.0.12-SNAPSHOT +1 org.apache.tapestry5. Less margin for confusion, as the difference between package names wouldn't be hust a 's' letter. The more explicit, the better. Thiago - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Instability in Tapestry 5.0.12-SNAPSHOT
my vote for org.apache.tapestry5 2008/5/19 Howard Lewis Ship [EMAIL PROTECTED]: A few people have noticed some significant changes in Tapestry 5.0.12-SNAPSHOT. What's going on is a limited number of interface and package renames to support deploying Tapestry 3 or 4 and Tapestry 5 in the same web application (WAR). Most of the conflicts were related Tapestry annotations in T4 vs. T5. The org.apache.tapestry.annotations package was renamed to org.apache.tapestry.annotation (for T5) so as not to conflict with the same named package, and overalapping annotation class names, from T4. I'm still experimenting, but this dual headed deployment will be the best upgrade path from T3/T4 to T5. I expect to follow up with new T5 tools to make sharing data between the apps easier. Sorry for the disruption this late in the game. The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- with regards Sven Homburg http://tapestry5-components.googlecode.com
Re: Instability in Tapestry 5.0.12-SNAPSHOT
For what its worth: +1: org.apache.tapestry5 On Mon, May 19, 2008 at 4:42 PM, Sven Homburg [EMAIL PROTECTED] wrote: my vote for org.apache.tapestry5 2008/5/19 Howard Lewis Ship [EMAIL PROTECTED]: A few people have noticed some significant changes in Tapestry 5.0.12-SNAPSHOT. What's going on is a limited number of interface and package renames to support deploying Tapestry 3 or 4 and Tapestry 5 in the same web application (WAR). Most of the conflicts were related Tapestry annotations in T4 vs. T5. The org.apache.tapestry.annotations package was renamed to org.apache.tapestry.annotation (for T5) so as not to conflict with the same named package, and overalapping annotation class names, from T4. I'm still experimenting, but this dual headed deployment will be the best upgrade path from T3/T4 to T5. I expect to follow up with new T5 tools to make sharing data between the apps easier. Sorry for the disruption this late in the game. The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- with regards Sven Homburg http://tapestry5-components.googlecode.com
Re: Instability in Tapestry 5.0.12-SNAPSHOT
According to java package naming conventions [1] the package name should reflect the domain of the developing organization which is org.apache.tapestry and not org.apache.tapestry5. These conventions are there for a purpose (in this case to ensure uniqueness of package names by using DNS names which are unique) and should be followed. +1 for org.apache.tapestry.v5 or similar Uli [1] http://java.sun.com/docs/books/jls/third_edition/html/packages.html#7.7 Howard Lewis Ship schrieb: A few people have noticed some significant changes in Tapestry 5.0.12-SNAPSHOT. What's going on is a limited number of interface and package renames to support deploying Tapestry 3 or 4 and Tapestry 5 in the same web application (WAR). Most of the conflicts were related Tapestry annotations in T4 vs. T5. The org.apache.tapestry.annotations package was renamed to org.apache.tapestry.annotation (for T5) so as not to conflict with the same named package, and overalapping annotation class names, from T4. I'm still experimenting, but this dual headed deployment will be the best upgrade path from T3/T4 to T5. I expect to follow up with new T5 tools to make sharing data between the apps easier. Sorry for the disruption this late in the game. The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Instability in Tapestry 5.0.12-SNAPSHOT
I think org.apache.tapestry5 or org.apache.tapestry.v5 (or similar) carries no or little difference in technical difficulty when it comes to refactoring existing T5 apps. For that reason, I personally will happily accept either way, as long as refactoring happens at the root level of package hierarchy. However, the point made by Urlich is a good one. On Mon, May 19, 2008 at 10:54 AM, Ulrich Stärk [EMAIL PROTECTED] wrote: According to java package naming conventions [1] the package name should reflect the domain of the developing organization which is org.apache.tapestry and not org.apache.tapestry5. These conventions are there for a purpose (in this case to ensure uniqueness of package names by using DNS names which are unique) and should be followed. +1 for org.apache.tapestry.v5 or similar Uli [1] http://java.sun.com/docs/books/jls/third_edition/html/packages.html#7.7 Howard Lewis Ship schrieb: A few people have noticed some significant changes in Tapestry 5.0.12-SNAPSHOT. What's going on is a limited number of interface and package renames to support deploying Tapestry 3 or 4 and Tapestry 5 in the same web application (WAR). Most of the conflicts were related Tapestry annotations in T4 vs. T5. The org.apache.tapestry.annotations package was renamed to org.apache.tapestry.annotation (for T5) so as not to conflict with the same named package, and overalapping annotation class names, from T4. I'm still experimenting, but this dual headed deployment will be the best upgrade path from T3/T4 to T5. I expect to follow up with new T5 tools to make sharing data between the apps easier. Sorry for the disruption this late in the game. The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. - 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: Form with errors
Hi
1. For error message: My practice is to clean the form in page's cleanupRender
phase.
Page.java
@Component
private Form form;
void cleanupRender() {
form.clearErrors();// clear error message
}
After then, if you reenter the page, error message would be gone.
2. For form value still exists: I think you have persist your model, right? So
it is persisted in Session by default.
Hope that helps.
Thanks!
DH
- Original Message -
From: Manuel Corrales [EMAIL PROTECTED]
To: Tapestry users users@tapestry.apache.org
Sent: Monday, May 19, 2008 9:36 PM
Subject: Form with errors
Hi, i have a left menu with a link (Add new Item). When i press the link, i
go to a form to create a new Item. If i have some server side validation
error, the error messages are shown on the screen, but the issue is that if
i press the Add new Item from the left menu, the form does not clean itself,
i mean the errors are still there and the form have the values i was
entering. Is this the right behavior? How can i do to get a new clean form
each time i press the link?
Thanks in advance!
Re: getting ClassFactory is matched by 2 services After upgrade from 5.06 - 5.0.11
I do not quite understand where to put the annotation. I haven't got any code where I'm referencing a classloader explicitly. I must be something missing here?.. Howard Lewis Ship wrote: Add the injection point (i.e., the constructor parameter) add either the @Builtin or the @ComponentLayer annotation. This marker annotation will select the correct implementation: either the general ClassFactory (used by the IoC container) or the one used when working with component code. You probably want @Builtin. On Sun, May 18, 2008 at 6:40 AM, Britske [EMAIL PROTECTED] wrote: After upgrading tapestry from 5.0.6 to 5.0.11 I'm getting the following error: Caused by: java.lang.RuntimeException: Service interface org.apache.tapestry.ioc.services.ClassFactory is matched by 2 services: ClassFactory, ComponentClassFactory. Automatic dependency resolution requires that exactly one service implement the interface. I'm getting the error (I think), I'm just not sure where to look to change it. For instance, I have nothing defined in my AppModule that could be the cause. Anyone? Thanks, Britske -- View this message in context: http://www.nabble.com/getting-ClassFactory-is-matched-by-2-services-After-upgrade-from-5.06--%3E-5.0.11-tp17303089p17303089.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/getting-ClassFactory-is-matched-by-2-services-After-upgrade-from-5.06--%3E-5.0.11-tp17303089p17323208.html 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: Instability in Tapestry 5.0.12-SNAPSHOT
On May 19, 2008, at 10:57 AM, Howard Lewis Ship wrote: The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. +1 on this. Unfortunately, I was too busy getting married to participate in the discussion. Renaming across the board guarantees no future conflicts. It would make things marginally less confusing in IDEs when actively working on both T4 T5 apps. -- Kevin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Instability in Tapestry 5.0.12-SNAPSHOT
+1 on org.apache.tapestry.t5. T5 is a widely used acronym both in the mailing lists and many web posts. Dario. On Mon, May 19, 2008 at 12:14 PM, Tomasz Dziurko [EMAIL PROTECTED] wrote: +1 on org.apache.tapestry5 -- Tomasz Dziurko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Punctuality is the virtue of the bored. Evelyn Waugh.
Re: T5: Exception Handling
Directly adding a tapestry url also works error-page error-code404/error-code location/NotFound.html/location /error-page That was in T4 that used the servlet (instead of filter) approach... perhaps it also works in T5. On Mon, May 19, 2008 at 5:35 PM, Toby Hobson [EMAIL PROTECTED] wrote: Given that a JSP is basically a servlet, why not do something like % response.include(request.getContextPath() + /MyTapestryErrorPage); % from your jsp exception page btw I can't remember - can you map an exception handler to a servlet in web.xml? Toby - Original Message From: Thiago HP [EMAIL PROTECTED] To: Tapestry users users@tapestry.apache.org Sent: Monday, 19 May, 2008 2:52:02 PM Subject: Re: T5: Exception Handling On 5/19/08, Peter Stavrinides [EMAIL PROTECTED] wrote: To configure: You would simply use a standard JSP / HTML error page, and wire it in your web.xml. I am using Tomcat and it works great... works on Jetty too. Something I've done once is to setup a 404.html page that redirects to a Tapestry page via Javascript, including the original URL so I can log it. ;) -- Thiago - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Form - asyn submission with file upload
See http://trac.dojotoolkit.org/ticket/524 Unfortunately, dojo decided to skip support for XML return types for IframeIO (which is needed for file uploads) due to problems with making it cross-browser. What this basically means for Tapestry is that async submit of forms having files cannot return the expected xml responses... however, i believe that the requests do actually take place - how did you enable the IFrame transport? Another idea (i think someone had mentioned doing this in this ML) is to have a separate form just for the uploads or (even better) investigate how to integrate one of those flash uploaders... On Mon, May 19, 2008 at 5:43 PM, Carlos F [EMAIL PROTECTED] wrote: After trying to async submit a form with a file upload field for a few hours I trolled around the message board and JIRA and ran across this: http://issues.apache.org/jira/browse/TAPESTRY-1348 Is trying to async submit a form with a file upload field a DEAD END? We tried to add the IFrame transport mechanism . . . however this did not trigger the request. Looking at the code it appears that the IFrame transport mechanism does not support async submissions etc. The tacos bug system has a related bug that mentions other changes that may be necessary to fix this: http://tacoscomponents.jot.com/BugReporter/Bug62 Has anyone been able to successfully async submit a form with a file upload field? Carlos -- Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Instability in Tapestry 5.0.12-SNAPSHOT
But, it's a short-hand for Tapestry5. So, what does tapestry.t5 gain you that tapestry5 doesn't? -- Kevin On May 19, 2008, at 1:25 PM, Darío Vasconcelos wrote: +1 on org.apache.tapestry.t5. T5 is a widely used acronym both in the mailing lists and many web posts. Dario. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Form - asyn submission with file upload
Andreas, thanks for the reply! -- how did you enable the IFrame transport? i added dojo.require(dojo.io.IframeIO); to a script file. However, this was insufficient. IframeTransport.canHandle() fails for two reasons: - the response type that tapestry was requesting was text/xml - and as the bug you emailed me notes, that is not a supported format for the IframeIO - it also appears that the IframeIO also requires the call to be synchronous. tapestry passes the request as async. This might be a little naive, but can I avoid the problems the IFrame has with text/xml by specify that the response should come as JSON? Carlos Andreas Andreou [EMAIL PROTECTED] wrote: See Unfortunately, dojo decided to skip support for XML return types for IframeIO (which is needed for file uploads) due to problems with making it cross-browser. What this basically means for Tapestry is that async submit of forms having files cannot return the expected xml responses... however, i believe that the requests do actually take place - how did you enable the IFrame transport? Another idea (i think someone had mentioned doing this in this ML) is to have a separate form just for the uploads or (even better) investigate how to integrate one of those flash uploaders... On Mon, May 19, 2008 at 5:43 PM, Carlos F wrote: After trying to async submit a form with a file upload field for a few hours I trolled around the message board and JIRA and ran across this: http://issues.apache.org/jira/browse/TAPESTRY-1348 Is trying to async submit a form with a file upload field a DEAD END? We tried to add the IFrame transport mechanism . . . however this did not trigger the request. Looking at the code it appears that the IFrame transport mechanism does not support async submissions etc. The tacos bug system has a related bug that mentions other changes that may be necessary to fix this: http://tacoscomponents.jot.com/BugReporter/Bug62 Has anyone been able to successfully async submit a form with a file upload field? Carlos -- Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Instability in Tapestry 5.0.12-SNAPSHOT
Looks like I am alone but I don't like the idea of putting version numbers into package names. In the highly unlikely case that there will be a tapestry 6 (not for technical but solely for marketing reasons ;-)) it might confuse developers. Are the classes in tapestry5 still valid or not? Only developers who will run tapestry4 and 5 in one webapplication might have the problem of distinguishing between the packages. I guess that they are the minority and it might be reasonable for them to read the class comments if they are in doubt which package belongs to which tapestry version. so -1 for a tapestry5 or v5. my 2cents, Markus On Mon, May 19, 2008 at 9:58 PM, Blower, Andy [EMAIL PROTECTED] wrote: I agree. -Original Message- From: Massimo Lusetti [mailto:[EMAIL PROTECTED] Sent: 19 May 2008 16:02 To: Tapestry users Subject: Re: Instability in Tapestry 5.0.12-SNAPSHOT On Mon, May 19, 2008 at 4:57 PM, Howard Lewis Ship [EMAIL PROTECTED] wrote: The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. I would say yes. -- Massimo http://meridio.blogspot.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using t5-components
Toby,
You should just be able to add the following to your pom.xml in the
appropriate places:
repository
idt5components/id
nameT5Components Maven Repository/name
url
http://87.193.218.134:8080/t5components/maven-repository
/url
/repository
dependency
groupIdorg.apache.tapestry/groupId
artifactIdt5c-contrib/artifactId
version0.5.11/version
/dependency
dependency
groupIdorg.apache.tapestry/groupId
artifactIdt5c-commons/artifactId
version0.5.11/version
/dependency
Zack
Sven Homburg wrote:
looks like the jars not copied in your WEB-INF/lib directory
2008/5/17 Toby Hobson [EMAIL PROTECTED]:
Hi
I'm looking at the t5-components project and I am trying to use the
PagedLoop component. I've added the commons and contrib dependencies and
the
repo to my pom.xml and they are now on my classpath. But when I try to
use
li t:type=t5components/PagedLoop source=images value=photo
${photo.name}
/li
Tapestry complains that it can't find a component called
t5components/PagedLoop. Do I have to somehow tell T5 where to find the
new
components?
Thanks
Toby
--
with regards
Sven Homburg
http://tapestry5-components.googlecode.com
-
best regards
Sven
--
View this message in context:
http://www.nabble.com/Using-t5-components-tp17292957p17328675.html
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: Instability in Tapestry 5.0.12-SNAPSHOT
I'm not sure that this would be considerably different from how things are generally done anyway. A class added in JDK5 is expected to work in 6+. Granted there's not a different package for each Java release, but I doubt it would cause as much confusion as you think. Actually, now that I think about it more, I wish Sun would use version numbers in its naming convention. Perhaps it's my COM background showing through, but it's exceedingly annoying how they just change interfaces. It is impossible to compile some SQL code on Java5 Java6 due to interface changes in the same named interface. -- Kevin On 5/19/08 5:20 PM, Markus Joschko [EMAIL PROTECTED] wrote: Looks like I am alone but I don't like the idea of putting version numbers into package names. In the highly unlikely case that there will be a tapestry 6 (not for technical but solely for marketing reasons ;-)) it might confuse developers. Are the classes in tapestry5 still valid or not? Only developers who will run tapestry4 and 5 in one webapplication might have the problem of distinguishing between the packages. I guess that they are the minority and it might be reasonable for them to read the class comments if they are in doubt which package belongs to which tapestry version. so -1 for a tapestry5 or v5. my 2cents, Markus On Mon, May 19, 2008 at 9:58 PM, Blower, Andy [EMAIL PROTECTED] wrote: I agree. -Original Message- From: Massimo Lusetti [mailto:[EMAIL PROTECTED] Sent: 19 May 2008 16:02 To: Tapestry users Subject: Re: Instability in Tapestry 5.0.12-SNAPSHOT On Mon, May 19, 2008 at 4:57 PM, Howard Lewis Ship [EMAIL PROTECTED] wrote: The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. I would say yes. -- Massimo http://meridio.blogspot.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] - 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: Instability in Tapestry 5.0.12-SNAPSHOT
You have a point, but: You form a unique package name by first having (or belonging to an organization that has) an Internet domain name, such as sun.com. You then reverse this name, component by component, to obtain, in this example, com.sun, and use this as a prefix for your package names, using a convention developed within your organization to further administer package names. So using org.apache as a prefix takes care of that. Besides, I don't see any other project with the name Tapestry 5 joining the ASF... +1 on org.apache.tapestry5 -Filip On 2008-05-19 17:54, Ulrich Stärk wrote: According to java package naming conventions [1] the package name should reflect the domain of the developing organization which is org.apache.tapestry and not org.apache.tapestry5. These conventions are there for a purpose (in this case to ensure uniqueness of package names by using DNS names which are unique) and should be followed. +1 for org.apache.tapestry.v5 or similar Uli [1] http://java.sun.com/docs/books/jls/third_edition/html/packages.html#7.7 Howard Lewis Ship schrieb: A few people have noticed some significant changes in Tapestry 5.0.12-SNAPSHOT. What's going on is a limited number of interface and package renames to support deploying Tapestry 3 or 4 and Tapestry 5 in the same web application (WAR). Most of the conflicts were related Tapestry annotations in T4 vs. T5. The org.apache.tapestry.annotations package was renamed to org.apache.tapestry.annotation (for T5) so as not to conflict with the same named package, and overalapping annotation class names, from T4. I'm still experimenting, but this dual headed deployment will be the best upgrade path from T3/T4 to T5. I expect to follow up with new T5 tools to make sharing data between the apps easier. Sorry for the disruption this late in the game. The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. - 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: Instability in Tapestry 5.0.12-SNAPSHOT
I'm with Markus. Personally, I'm kind of shocked this is even under consideration. Versioning your package structure is a band-aid to the real problem, which is people not being able to control their class-loaders. If you deploy your Tapestry 4 app in one WAR and your Tapestry 5 app in another WAR then this should not be an issue. Per the portability section of the JavaEE spec, the classloaders of WARs should be entirely independent. In my mind, the only people this applies to are people who have deviated from the JavaEE spec, and I don't really see why we should make exceptions for them. People commonly have several differing versions of Log4J and XML parsers within their application server, there's no reason to make an exception for Tapestry. -1 for org.tapestry.apache.v5.0.12 -Original Message- From: Markus Joschko [mailto:[EMAIL PROTECTED] Sent: Monday, May 19, 2008 5:20 PM To: Tapestry users Subject: Re: Instability in Tapestry 5.0.12-SNAPSHOT Looks like I am alone but I don't like the idea of putting version numbers into package names. In the highly unlikely case that there will be a tapestry 6 (not for technical but solely for marketing reasons ;-)) it might confuse developers. Are the classes in tapestry5 still valid or not? Only developers who will run tapestry4 and 5 in one webapplication might have the problem of distinguishing between the packages. I guess that they are the minority and it might be reasonable for them to read the class comments if they are in doubt which package belongs to which tapestry version. so -1 for a tapestry5 or v5. my 2cents, Markus On Mon, May 19, 2008 at 9:58 PM, Blower, Andy [EMAIL PROTECTED] wrote: I agree. -Original Message- From: Massimo Lusetti [mailto:[EMAIL PROTECTED] Sent: 19 May 2008 16:02 To: Tapestry users Subject: Re: Instability in Tapestry 5.0.12-SNAPSHOT On Mon, May 19, 2008 at 4:57 PM, Howard Lewis Ship [EMAIL PROTECTED] wrote: The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. I would say yes. -- Massimo http://meridio.blogspot.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] - 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: Instability in Tapestry 5.0.12-SNAPSHOT
I've been using Tapestry since v3. I have a Web suite (for lack of better terminology) with a T4 public app and a T5 management app, using Cayenne ROP to link between the two. Yet, I cannot think of a situation in which I would ever have what you're looking at below. I'm not saying it's not valid, but I need some concrete examples. Thanks, Kevin On 5/19/08 3:39 PM, Estevam Henrique Portela Mota e Silva [EMAIL PROTECTED] wrote: Hi, examples q 2 differences directory of the tapestry: (example) - 1 -- Org.apache.tapestry (sources) -- org.apache.tapestry3 (sources) -- Org.apache.tapestry4 (sources) -- org.apache.tapestry5 (example) - 2 -- Org.apache.tapestry (sources) -- org.apache.tapestry.v3 (sources) -- Org.apache.tapestry.v4 (sources) -- org.apache.tapestry.v5 Then path of directory of tapestry is easy ... I chose example 2. *+1 org.apache.tapestry.v5* If path differences, org.apache.tapestry + org.apache.tapestry5 are confused separate version * Voting org.apache.tapestry.v5* - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Instability in Tapestry 5.0.12-SNAPSHOT
This is a bit of a red herring. I can understand the reluctance from one perspective, but it might help to think of it not as tapestry v3, v4, and v5, but as first-web-framework, another-web-framework, a- different-web-framework. They're not the same, though they are similar in some architectural features. They're built on a different architectural basis. One may have evolved from the other conceptually, but the code-base did not evolve from the previous code=base, so it's absolutely appropriate to use a different package. Christian. On 19-May-08, at 17:20 , Markus Joschko wrote: Looks like I am alone but I don't like the idea of putting version numbers into package names. In the highly unlikely case that there will be a tapestry 6 (not for technical but solely for marketing reasons ;-)) it might confuse developers. Are the classes in tapestry5 still valid or not? Only developers who will run tapestry4 and 5 in one webapplication might have the problem of distinguishing between the packages. I guess that they are the minority and it might be reasonable for them to read the class comments if they are in doubt which package belongs to which tapestry version. so -1 for a tapestry5 or v5. my 2cents, Markus On Mon, May 19, 2008 at 9:58 PM, Blower, Andy [EMAIL PROTECTED] wrote: I agree. -Original Message- From: Massimo Lusetti [mailto:[EMAIL PROTECTED] Sent: 19 May 2008 16:02 To: Tapestry users Subject: Re: Instability in Tapestry 5.0.12-SNAPSHOT On Mon, May 19, 2008 at 4:57 PM, Howard Lewis Ship [EMAIL PROTECTED] wrote: The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. I would say yes. -- Massimo http://meridio.blogspot.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] - 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: Instability in Tapestry 5.0.12-SNAPSHOT
markus, i voted for package renaming like org.apache.tapestry5 but i go even conform with your mind. if i read the reason for the package renaming, i was relay alienated for that, but on the other side, i am not sure, its more easier for some tap4 user to migrate slowly to tap5. but i am not sure, in our real fast spinning world, if there are much developer they say i migrate tommorow and belive their own mind voice. 2008/5/19 Markus Joschko [EMAIL PROTECTED]: Looks like I am alone but I don't like the idea of putting version numbers into package names. In the highly unlikely case that there will be a tapestry 6 (not for technical but solely for marketing reasons ;-)) it might confuse developers. Are the classes in tapestry5 still valid or not? Only developers who will run tapestry4 and 5 in one webapplication might have the problem of distinguishing between the packages. I guess that they are the minority and it might be reasonable for them to read the class comments if they are in doubt which package belongs to which tapestry version. so -1 for a tapestry5 or v5. my 2cents, Markus On Mon, May 19, 2008 at 9:58 PM, Blower, Andy [EMAIL PROTECTED] wrote: I agree. -Original Message- From: Massimo Lusetti [mailto:[EMAIL PROTECTED] Sent: 19 May 2008 16:02 To: Tapestry users Subject: Re: Instability in Tapestry 5.0.12-SNAPSHOT On Mon, May 19, 2008 at 4:57 PM, Howard Lewis Ship [EMAIL PROTECTED] wrote: The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. I would say yes. -- Massimo http://meridio.blogspot.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- with regards Sven Homburg http://tapestry5-components.googlecode.com
Re: Instability in Tapestry 5.0.12-SNAPSHOT
I'm not against a package rename but against the version number. The only benefit of putting a version number in, is to help tap4 users now. But who will care about tap4 in 2 years? The version number will still be in the code base by then. If the official version number of tapestry is changing from 5 to 2011 or whatsoever, developers will at best be irritated by the tapestry5 package names On Mon, May 19, 2008 at 11:41 PM, Sven Homburg [EMAIL PROTECTED] wrote: markus, i voted for package renaming like org.apache.tapestry5 but i go even conform with your mind. if i read the reason for the package renaming, i was relay alienated for that, but on the other side, i am not sure, its more easier for some tap4 user to migrate slowly to tap5. but i am not sure, in our real fast spinning world, if there are much developer they say i migrate tommorow and belive their own mind voice. 2008/5/19 Markus Joschko [EMAIL PROTECTED]: Looks like I am alone but I don't like the idea of putting version numbers into package names. In the highly unlikely case that there will be a tapestry 6 (not for technical but solely for marketing reasons ;-)) it might confuse developers. Are the classes in tapestry5 still valid or not? Only developers who will run tapestry4 and 5 in one webapplication might have the problem of distinguishing between the packages. I guess that they are the minority and it might be reasonable for them to read the class comments if they are in doubt which package belongs to which tapestry version. so -1 for a tapestry5 or v5. my 2cents, Markus On Mon, May 19, 2008 at 9:58 PM, Blower, Andy [EMAIL PROTECTED] wrote: I agree. -Original Message- From: Massimo Lusetti [mailto:[EMAIL PROTECTED] Sent: 19 May 2008 16:02 To: Tapestry users Subject: Re: Instability in Tapestry 5.0.12-SNAPSHOT On Mon, May 19, 2008 at 4:57 PM, Howard Lewis Ship [EMAIL PROTECTED] wrote: The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. I would say yes. -- Massimo http://meridio.blogspot.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- with regards Sven Homburg http://tapestry5-components.googlecode.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Instability in Tapestry 5.0.12-SNAPSHOT
Actually, I think it's aimed at people that want to use both T4 and T5 in the same WAR. For example, I have a set of data objects in one package shared between a T4 and a T5 app. I'm not about to rewrite that T4 app, os that's a non-starter. Unfortunately, this also means I can't use any T5 annotations on those DOs, which is a shame considering how much simpler it could make things in the T5 app. Now, I'm not looking for the annotations to do anything in the T4 app, but with a clashing names, it's not even possible. I suspect others will have similar transitional issues while moving to T5. -- Kevin On 5/19/08 5:39 PM, Joel Wiegman [EMAIL PROTECTED] wrote: I'm with Markus. Personally, I'm kind of shocked this is even under consideration. Versioning your package structure is a band-aid to the real problem, which is people not being able to control their class-loaders. If you deploy your Tapestry 4 app in one WAR and your Tapestry 5 app in another WAR then this should not be an issue. Per the portability section of the JavaEE spec, the classloaders of WARs should be entirely independent. In my mind, the only people this applies to are people who have deviated from the JavaEE spec, and I don't really see why we should make exceptions for them. People commonly have several differing versions of Log4J and XML parsers within their application server, there's no reason to make an exception for Tapestry. -1 for org.tapestry.apache.v5.0.12 -Original Message- From: Markus Joschko [mailto:[EMAIL PROTECTED] Sent: Monday, May 19, 2008 5:20 PM To: Tapestry users Subject: Re: Instability in Tapestry 5.0.12-SNAPSHOT Looks like I am alone but I don't like the idea of putting version numbers into package names. In the highly unlikely case that there will be a tapestry 6 (not for technical but solely for marketing reasons ;-)) it might confuse developers. Are the classes in tapestry5 still valid or not? Only developers who will run tapestry4 and 5 in one webapplication might have the problem of distinguishing between the packages. I guess that they are the minority and it might be reasonable for them to read the class comments if they are in doubt which package belongs to which tapestry version. so -1 for a tapestry5 or v5. my 2cents, Markus On Mon, May 19, 2008 at 9:58 PM, Blower, Andy [EMAIL PROTECTED] wrote: I agree. -Original Message- From: Massimo Lusetti [mailto:[EMAIL PROTECTED] Sent: 19 May 2008 16:02 To: Tapestry users Subject: Re: Instability in Tapestry 5.0.12-SNAPSHOT On Mon, May 19, 2008 at 4:57 PM, Howard Lewis Ship [EMAIL PROTECTED] wrote: The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. I would say yes. -- Massimo http://meridio.blogspot.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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
T5 cross-form validation
Hi According to the T5 site: After the fields have done their processing, the Form emits avalidate event. This is a chance to perform cross-form validationthat can't be described declaratively. I understood this to mean that a validate event will be fired after the individual fields have been validated, but it seems this is not the case. I have found that validate events are fired for each of the fields on the form but not for the form itself so I need to put my cross-form validation in my success handler. Not a big problem but I think the docs should be clarified. Personally I think it would be useful to fire a validate event after the individual fields have been validated. Toby
Re: Instability in Tapestry 5.0.12-SNAPSHOT
Again, the differences between T3, T4, and T5 are not really versions in the typical sense. They're different architectural bases. You might call them three different web frameworks entirely. So there should be no reason technically for them to overlap, and they should have three different packages. You might as well have them by three different codenames, at which point you have org.apache.tapestry.trout org.apache.tapestry.tuna org.apache.tapestry.tilapia Different frameworks, all under the Tapestry project. The fact that org.apache.tapestry.yellowtail shows up in four years should have no bearing on the other three. (again, not that it will, just making a point) Christian. On 19-May-08, at 17:59 , Markus Joschko wrote: I'm not against a package rename but against the version number. The only benefit of putting a version number in, is to help tap4 users now. But who will care about tap4 in 2 years? The version number will still be in the code base by then. If the official version number of tapestry is changing from 5 to 2011 or whatsoever, developers will at best be irritated by the tapestry5 package names On Mon, May 19, 2008 at 11:41 PM, Sven Homburg [EMAIL PROTECTED] wrote: markus, i voted for package renaming like org.apache.tapestry5 but i go even conform with your mind. if i read the reason for the package renaming, i was relay alienated for that, but on the other side, i am not sure, its more easier for some tap4 user to migrate slowly to tap5. but i am not sure, in our real fast spinning world, if there are much developer they say i migrate tommorow and belive their own mind voice. 2008/5/19 Markus Joschko [EMAIL PROTECTED]: Looks like I am alone but I don't like the idea of putting version numbers into package names. In the highly unlikely case that there will be a tapestry 6 (not for technical but solely for marketing reasons ;-)) it might confuse developers. Are the classes in tapestry5 still valid or not? Only developers who will run tapestry4 and 5 in one webapplication might have the problem of distinguishing between the packages. I guess that they are the minority and it might be reasonable for them to read the class comments if they are in doubt which package belongs to which tapestry version. so -1 for a tapestry5 or v5. my 2cents, Markus On Mon, May 19, 2008 at 9:58 PM, Blower, Andy [EMAIL PROTECTED] wrote: I agree. -Original Message- From: Massimo Lusetti [mailto:[EMAIL PROTECTED] Sent: 19 May 2008 16:02 To: Tapestry users Subject: Re: Instability in Tapestry 5.0.12-SNAPSHOT On Mon, May 19, 2008 at 4:57 PM, Howard Lewis Ship [EMAIL PROTECTED] wrote: The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. I would say yes. -- Massimo http://meridio.blogspot.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- with regards Sven Homburg http://tapestry5-components.googlecode.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: Help with Tapestry 3.4 and Stale Link Error
Anyone out there on the list? Sorry this is not a Tapestry 5 issue, but could you please point me to an earlier discussion on this issue, if you know of one. This is really frustrating me. Thanks -- Best regards, Davidmailto:[EMAIL PROTECTED] __ Sunday, May 18, 2008, 11:01:30 AM, you wrote: Hello Users, I just cannot figure this one out. It seems like this error just started out of nowhere. Of course this is probably not the case, but no changes I made seem to contribute to this error. anyway. I can get the following stale link error simply by clicking the form's search button a few times, without even modifying any search parameters. __ You have clicked on a stale link. Rewind of form SharedSummary/$SharedSummaryComponent.$Form expected allocated id #50 to be '$If$28', but was 'vdatepicker$1' (requested by component SharedSummary/$SharedSummaryComponent.objectList.docsRecdDate.vdatepicker). This is most likely the result of using your browser's back button, but can also be an application error. You may continue by returning to the application's home page. I have a simple search form with text field and select list parameters on top of the page, and a list of results on the bottom. I have a search and reset imagesubmit on the top of the page. Click search a few times gives the error. I am doing the data retrieval in the formSubmit(IRequestCycle cycle) method. When I hit the error, it doesn't even get to this spot. The trace shows that the pageBeginRender is fired once, then the error occurs, before any search is done. This makes no sense to me. I realize this is an old problem and I am using an old version, but any advice is GREATLY appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5 cross-form validation
Problem fixed ... it appears the form doesn't emit a validate event, it emits a validateForm event! Toby - Original Message From: Toby Hobson [EMAIL PROTECTED] To: tapestry users@tapestry.apache.org Sent: Monday, 19 May, 2008 11:17:44 PM Subject: T5 cross-form validation Hi According to the T5 site: After the fields have done their processing, the Form emits avalidate event. This is a chance to perform cross-form validationthat can't be described declaratively. I understood this to mean that a validate event will be fired after the individual fields have been validated, but it seems this is not the case. I have found that validate events are fired for each of the fields on the form but not for the form itself so I need to put my cross-form validation in my success handler. Not a big problem but I think the docs should be clarified. Personally I think it would be useful to fire a validate event after the individual fields have been validated. Toby
Re: Tapestry users declined for the first time in 3 years, says this researh site ...
I was just googling around the Internet for people with Wicket problems and I ran across this highly obnoxious post and felt I should comment. If the research was real, the poster would have linked to it. In fact, nobody has any real basis short of a widespread statistical survey for assessing the number of users of open source frameworks. Since I highly doubt anyone cares enough to do such an expensive survey, we can safely assume the poster is not only an anti-social ass but also a liar. And he is certainly not a friend of the Wicket or open source communities, as posts like this are damaging to everyone involved. In case I'm not making this clear enough Rob Smeets: KNOCK IT OFF ALREADY! Open-source technologies should not be thought of as some kind of popularity contest. There are great technologies that languish in relative obscurity and mediocre ones that everyone seems to use. It is also objectively a healthy thing to have good alternatives as we don't live in a one-size-fits-all world. Tapestry is a solid framework with a long history, lots of users and plenty of development activity. I don't think Wicket or anything else will kill it and there's no reason to think it won't continue to flourish. Certainly it has been innovative for many years and is a cut above most of the rest... and honestly anything that helps to put a nail in the coffin of Struts is good for Java. Best, Jonathan Locke, Founder of Wicket Rob Smeets wrote: Hi guys, I don't mean to cause any depression or controversy but I saw this research results and thought you might want to know. Because this makes me worry about the future of Tapestry. According to the research, Tapestry users declined drastically by 45% for the first time in 3 years. I was very surprised because of the hype and sound bytes from Howard and co. surrounding Tapestry 5. I understand users of Wicket grew by 55% whereas GWT grew by 85%. According to the source, Adobe Flex users grew by 91% and that seems huge to me but warrants it of course. Even Howard admits Flex is one of the best. I think I agree with this research just by looking at the traffic here on the Tapestry list as well as responses on Howard's blog site on all topics regarding Tapestry. What do you think? Yours friendly, Rob -- View this message in context: http://www.nabble.com/Tapestry-users-declined-for-the-first-time-in-3-years%2C-says-this-researh-site-...-tp17016042p17330503.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
where can i get the referrence?
where can i get the referrence about tapestry? for example,the referrence about annotation,component,etc. thanks. -- View this message in context: http://www.nabble.com/where-can-i-get-the-referrence--tp17333433p17333433.html 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: Instability in Tapestry 5.0.12-SNAPSHOT
if T5 willBeCompatibleWith T(5+n) andT5 shouldWorkWith T(5-n) then rename T(5-n) annotations packages; else if T5 willBeNotCompatibleWith T(5+n) then rename all Tapestry packages; Marcus
