Re: Code Coverage link on Tap homepage doesn't work anymore
I guess this should be re-enabled in the Gradle build - this shows one of Tapestry's qualities. When I show Tapestry I always mention the 92% coverage. Chris Am 23.11.2011 19:29, schrieb Howard Lewis Ship: > Actually, the cobertura link was part of the Maven build, something we > lost in the switch to Gradle. We can update the link to point to 5.2, > where the report was still active. > > On Mon, Nov 21, 2011 at 11:42 AM, derkoe > wrote: >> Link "See Tapestry's code coverage report" on Tapestry home page leads to >> http://tapestry.apache.org/current/tapestry-core/cobertura/index.html which >> results in a 404. >> >> JIRA? Or can somebody fix that quickly? >> >> -- >> Chris >> >> -- >> View this message in context: >> http://tapestry.1045711.n5.nabble.com/Code-Coverage-link-on-Tap-homepage-doesn-t-work-anymore-tp5011461p5011461.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 >> >> > > > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [TYNAMO] Exception Handling
got it, same as me. Nicolás.-
Re: [TYNAMO] Exception Handling
** ** THIS IS A WARNING MESSAGE ONLY ** ** YOU DO NOT NEED TO RESEND YOUR MESSAGE ** ** The original message was received at Wed, 22 Jun 2011 08:26:07 -0400 from user-0cdfs5f.cable.mindspring.com [24.215.240.175] - Transcript of session follows - ... while talking to mail.codehaus.org.: >>> RCPT To: <<< 451 IP 66.114.74.12 is UCEPROTECT-Level 1 listed. See http://www.uceprotect.net/rblcheck.php?ipr=66.114.74.12 ... Deferred: 451 IP 66.114.74.12 is UCEPROTECT-Level 1 listed. See http://www.uceprotect.net/rblcheck.php?ipr=66.114.74.12 Warning: message still undelivered after 4 hours Will keep trying until message is 5 days old Reporting-MTA: dns; mail1.aceinnovative.com Arrival-Date: Wed, 22 Jun 2011 08:26:07 -0400 Final-Recipient: RFC822; u...@tynamo.codehaus.org Action: delayed Status: 4.3.0 Remote-MTA: DNS; mail.codehaus.org Diagnostic-Code: SMTP; 451 IP 66.114.74.12 is UCEPROTECT-Level 1 listed. See http://www.uceprotect.net/rblcheck.php?ipr=66.114.74.12 Last-Attempt-Date: Wed, 22 Jun 2011 12:38:23 -0400 From: Lenny Primak Date: June 22, 2011 8:26:06 AM EDT To: "u...@tynamo.codehaus.org" Subject: Re: [tynamo-user] Re: Maven Checksum Failure with Tynamo JPA / Security On Nov 24, 2011, at 1:39 PM, Lenny Primak wrote: > The Tynamo list has never worked for me. It seems that it works for some > users and not others. I get a bounced E-mail when I send it to the tynamo > list. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [TYNAMO] Exception Handling
The Tynamo list has never worked for me. It seems that it works for some users and not others. I get a bounced E-mail when I send it to the tynamo list. On Nov 24, 2011, at 1:36 PM, Nicolas Barrera wrote: > Hi Ale, > > thanks for the help, so you say that tynamo's mailing list should be > working alright but just for moment to moment is down? then i 'll be > retrying to post there. > > About what you answered me... > > i 've finally avoided the problem overriding the isAllowRemove method > calling one of the bean's specific method which tells me if it has children > relationship, then instead of the delete link I print a "you can't delete" > message. > > About what you suggested... I can file a Jira issue no problem (and post > the patch if I can), but let me be sure that I understand your proposal..., > > > You 'd like to modify Tynamo's Show page's method onActionFromDelete > catching up a JDBCBatchException or something like that? > > I was thinking about that and I would catch an HibernateException and > return a link to the same page..., what I 'm not sure is about the way to > report the error to the end user... > is there any component which shows an overlay/modal with the error message? > Anyway the HibernateException could be any error not only this kind of > database error. > > well about the second error on my second mail, it was something else I was > doing wrong that I could solve, and the difference between Locality and > Sucursal was just me trying to translate my class names :S > > > if the tynamo list is up, then i will continue this thread there, > > thanks again, and I 'll wait for your comments on my ideas about the patch. > > cheers, > > Nicolás.- > > > On Thu, Nov 24, 2011 at 1:54 PM, Alejandro Scandroli < > alejandroscandr...@gmail.com> wrote: > >> Hi Nicolás >> >>> >>> - Am I obliged to make a custom page in order to catch up that exception >>> and show the user a friendly message? (something like "hey!, you can't >>> delete this locality as it's referenced by other persons") >>> >> >> No really, you can catch the exception in your own Show.java page >> overriding (onActionFromDelete). You can also try some other (weird >> bidirectional) mapping alternatives, but I think the cleanest option >> is the custom page. >> I think this could be a nice thing to add by default, since it >> could be a very common issue. Do you mind filing a JIRA issue for it? >> (a patch would be wonderful btw) >> >>> - I 've read about the tynamo-exceptionpage module which I think it will >>> catch up the error, but will show a generic error message per exception I >>> register am I right? >>> >> >> That's exactly right! >> >>> (….) >>> the result is that after I create a new Locality, it forwards to the show >>> locality page but before rendering this error shows up: >>> >>> org.apache.tapestry5.internal.services.RenderQueueException >> >> I don't know what could be wrong here. I need for info. >> The only thing weird I see is that if the page name is LocalityShow, >> the getType() method should return Class instead of >> Class >> >> >> BTW, you are not the first reporting problems with tynamo's user list, >> but still can figure out why sometimes doesn't work. I will try >> (again) to send a test email later. >> >> Thanks and welcome. >> >> Saludos. >> Alejandro. >> >> - >> 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: [TYNAMO] Exception Handling
Hi Ale, thanks for the help, so you say that tynamo's mailing list should be working alright but just for moment to moment is down? then i 'll be retrying to post there. About what you answered me... i 've finally avoided the problem overriding the isAllowRemove method calling one of the bean's specific method which tells me if it has children relationship, then instead of the delete link I print a "you can't delete" message. About what you suggested... I can file a Jira issue no problem (and post the patch if I can), but let me be sure that I understand your proposal..., You 'd like to modify Tynamo's Show page's method onActionFromDelete catching up a JDBCBatchException or something like that? I was thinking about that and I would catch an HibernateException and return a link to the same page..., what I 'm not sure is about the way to report the error to the end user... is there any component which shows an overlay/modal with the error message? Anyway the HibernateException could be any error not only this kind of database error. well about the second error on my second mail, it was something else I was doing wrong that I could solve, and the difference between Locality and Sucursal was just me trying to translate my class names :S if the tynamo list is up, then i will continue this thread there, thanks again, and I 'll wait for your comments on my ideas about the patch. cheers, Nicolás.- On Thu, Nov 24, 2011 at 1:54 PM, Alejandro Scandroli < alejandroscandr...@gmail.com> wrote: > Hi Nicolás > > > > > - Am I obliged to make a custom page in order to catch up that exception > > and show the user a friendly message? (something like "hey!, you can't > > delete this locality as it's referenced by other persons") > > > >No really, you can catch the exception in your own Show.java page > overriding (onActionFromDelete). You can also try some other (weird > bidirectional) mapping alternatives, but I think the cleanest option > is the custom page. > I think this could be a nice thing to add by default, since it > could be a very common issue. Do you mind filing a JIRA issue for it? > (a patch would be wonderful btw) > > > - I 've read about the tynamo-exceptionpage module which I think it will > > catch up the error, but will show a generic error message per exception I > > register am I right? > > > >That's exactly right! > > > (….) > > the result is that after I create a new Locality, it forwards to the show > > locality page but before rendering this error shows up: > > > > org.apache.tapestry5.internal.services.RenderQueueException > > I don't know what could be wrong here. I need for info. > The only thing weird I see is that if the page name is LocalityShow, > the getType() method should return Class instead of > Class > > > BTW, you are not the first reporting problems with tynamo's user list, > but still can figure out why sometimes doesn't work. I will try > (again) to send a test email later. > > Thanks and welcome. > > Saludos. > Alejandro. > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
Re: [TYNAMO] Exception Handling
Hi Nicolás > > - Am I obliged to make a custom page in order to catch up that exception > and show the user a friendly message? (something like "hey!, you can't > delete this locality as it's referenced by other persons") > No really, you can catch the exception in your own Show.java page overriding (onActionFromDelete). You can also try some other (weird bidirectional) mapping alternatives, but I think the cleanest option is the custom page. I think this could be a nice thing to add by default, since it could be a very common issue. Do you mind filing a JIRA issue for it? (a patch would be wonderful btw) > - I 've read about the tynamo-exceptionpage module which I think it will > catch up the error, but will show a generic error message per exception I > register am I right? > That's exactly right! > (….) > the result is that after I create a new Locality, it forwards to the show > locality page but before rendering this error shows up: > > org.apache.tapestry5.internal.services.RenderQueueException I don't know what could be wrong here. I need for info. The only thing weird I see is that if the page name is LocalityShow, the getType() method should return Class instead of Class BTW, you are not the first reporting problems with tynamo's user list, but still can figure out why sometimes doesn't work. I will try (again) to send a test email later. Thanks and welcome. Saludos. Alejandro. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: TAP5-1425
..my fix for this was to type-coerce the path into a resource and call
.exists() on it.
the runtime exception was thrown from the assetSource.getExpandedAsset method
in this case.
Am 24.11.2011 um 09:04 schrieb Ville:
> Hi,
>
> https://issues.apache.org/jira/browse/TAP5-1425 was fixed, but it breaks a
> lot of existing functionality.
>
> Resource has method exists(), but what is the point of this method if the
> service throws RuntimeException when loading resources that doesn't exist?
>
> This is from Tap5Jquery:
> if(this.assetSource.getExpandedAsset(path).getResource().exists()) {
>return this.assetSource.getExpandedAsset(path);
> }
> return null;
>
> Do we now have to catch RuntimeException and return null if such is thrown?
> We should atleast have ResourceNotFoundRuntimeException?
>
> - Ville
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/TAP5-1425-tp5019523p5019523.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
>
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Fwd: Default values for a grid : concept erroneus ?
On Thu, 24 Nov 2011 08:17:55 -0200, Jose Luis Sanchez wrote: Well, struts 1.x, but since 2009 i'm using tap5.x Hehehe, I was right. :) So, what are your recomendations ? Which is the default/recommended Tapestry5 behaviour ? I always get the data before rendering In this case, I don't think there's a recommended behavior, as it won't make any difference in performance or memory usage. Just do what do you think it's more appropriate in each case. I usually only get data before rendering when it's used in more than one place. Anyway, you can use @Cached in the method and its result will be evaluated just once inside a request. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Fwd: Default values for a grid : concept erroneus ?
Well, struts 1.x, but since 2009 i'm using tap5.x So, what are your recomendations ? Which is the default/recommended Tapestry5 behaviour ? I always get the data before rendering .. which WIKI/DOC do you recommend me to take a look at ? On Thu, 24 Nov 2011 07:27:42 -0200, Jose Luis Sanchez wrote: thanks .. that worked :) Are you a previous user of Struts, WebWork or some other request-oriented Web framework? Your previous code made me think that, as you got all data before rendering starts. Component-oriented frameworks like Tapestry, JSF and Wicket don't need that. :) -- *Jose Luis Sanchez* Senior Developer *E-mail*: joseluis.sanc...@m-centric.com *Phone* : +34 91 277 03 16 mCentric mobilising imagination c/ Jose Echegaray, 8 Building 3 28230 Las Rozas (Madrid). SPAIN. This message may contain confidential information or privileged material, and is intended only for the individual(s) named. If you are not in the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Fwd: Default values for a grid : concept erroneus ?
On Thu, 24 Nov 2011 07:27:42 -0200, Jose Luis Sanchez wrote: thanks .. that worked :) Are you a previous user of Struts, WebWork or some other request-oriented Web framework? Your previous code made me think that, as you got all data before rendering starts. Component-oriented frameworks like Tapestry, JSF and Wicket don't need that. :) -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Fwd: Default values for a grid : concept erroneus ?
thanks .. that worked :)
Hi!
Never persist search results: persist the parameters. ;)
Besides that, I'd remove the transactions field and make the
getTransactions() method look like this:
public List getTransactions() {
return (List)
theSession.createCriteria(Transaction.class)
.add(Restrictions.eq("msisdn", userInfo.getMsisdn()))
.add(Restrictions.not(Restrictions.in("transactionType",
INVALID_TRANSACTION_TYPES)))
.add(Restrictions.ge("transactionDate", startDate(fromDate)))
.add(Restrictions.le("transactionDate", endDate(toDate)))
.add(Restrictions.ge("partitionDate",
Integer.parseInt(tformatter.format(fromDate
.add(Restrictions.le("partitionDate",
Integer.parseInt(tformatter.format(toDate
.addOrder(Order.asc("id")).list();
}
--
*Jose Luis Sanchez*
Senior Developer
*E-mail*: joseluis.sanc...@m-centric.com
*Phone* : +34 91 277 03 16
mCentric mobilising imagination
c/ Jose Echegaray, 8 Building 3
28230 Las Rozas (Madrid). SPAIN.
This message may contain confidential information or privileged
material, and is intended only for the individual(s) named. If you are
not in the named addressee you should not disseminate, distribute or
copy this e-mail. Please notify the sender immediately by e-mail if you
have received this e-mail by mistake and delete this e-mail from your
system E-mail transmission cannot be guaranteed to be secured or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The sender
therefore does not accept liability for any errors or omissions in the
contents of this message which arise as a result of e-mail transmission.
If verification is required please request a hard-copy version.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
TAP5-1425
Hi,
https://issues.apache.org/jira/browse/TAP5-1425 was fixed, but it breaks a
lot of existing functionality.
Resource has method exists(), but what is the point of this method if the
service throws RuntimeException when loading resources that doesn't exist?
This is from Tap5Jquery:
if(this.assetSource.getExpandedAsset(path).getResource().exists()) {
return this.assetSource.getExpandedAsset(path);
}
return null;
Do we now have to catch RuntimeException and return null if such is thrown?
We should atleast have ResourceNotFoundRuntimeException?
- Ville
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/TAP5-1425-tp5019523p5019523.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
