That blocker maybe?
https://issues.apache.org/jira/browse/TAP5-2391
The last comment makes it seem as if the fix would be a simple one-liner.
> Am 08.03.2017 um 11:45 schrieb Jochen Kemnade :
>
> Hi,
>
> due to TAP5-2575 we'll probably have to release 5.4.2 soon. I'll try to
> address that i
I remember Igor talking about a mongodb integration.. What happened with it?
Having support for mongodb is a good thing but I think making morphia the
default mapper is not the best choice.
We have here some nice integration with the jackson mapper[1], which is not so
much hibernate-like and giv
There's a small problem with the Tapestry tests:
> :tapestry-beanvalidator:test
> Test
> org.apache.tapestry5.beanvalidator.integration.TapestryBeanValidationIntegrationTests
> FAILED
> 6 tests completed, 6 failures
I'm currently in the 5.4-js-rewrite branch but I've had this problem since the
+1 (non-binding)
all system are doing just fine!
best
Christian
Am 01.02.2012 um 10:25 schrieb Ulrich Stärk:
> On 31.01.2012 18:37, Howard Lewis Ship wrote:
>> Howard M. Lewis Ship: +1 (binding)
>>
>> Moved client code to 5.3.2 with no problems; I've also downloaded the
>> source ZIP and verif
Hi,
thought I'd start this thread here (at least as a reminder). It's about the
issue I found with TAP5-1768:
https://issues.apache.org/jira/browse/TAP5-1768?focusedCommentId=13178024&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13178024
Uli wrote that a discussi
ill talk about it a bit later.
>
> Feel free to observe the commits and discuss the implementation ideas.
>
> On Tue, Jan 3, 2012 at 1:12 AM, Christian Riedel
> wrote:
>
>> A ValueEncoder that supports any mapper might be quite hard to accomplish.
>> It's
ybe we can come up with a simple interface comparable to
> ValueEncoder and the user would implement it using any mapper library. I
> think this is a topic for the developer's list.
>
> On Thu, Dec 29, 2011 at 3:00 PM, Christian Riedel
> wrote:
>
>> Hi Igor,
>>
>&g
Well I find it convenient :-)
I also upgraded one of my apps to 5.3.1rc-1 and it all works fine, btw!
Cheers
Christian
Am 09.12.2011 um 23:51 schrieb Massimo Lusetti:
> On Fri, Dec 9, 2011 at 9:30 PM, Christian Riedel
> wrote:
>
>> how about backporting some issues fro
how about backporting some issues from trunk such as:
https://issues.apache.org/jira/browse/TAP5-1780
?
Am 09.12.2011 um 17:43 schrieb Massimo Lusetti:
> On Fri, Dec 9, 2011 at 5:37 PM, Christian Riedel
> wrote:
>
>> I'll see what I can do! :)
>
> BTW did you see c
Why did no one in the ML point me to this easy solution? :-)
Ok, issue closed. So annoying to fall for such counter-intuitive things after
years of coding with Tapestry :-/
Go on with 5.3.1!
Am 09.12.2011 um 17:43 schrieb Massimo Lusetti:
> On Fri, Dec 9, 2011 at 5:37 PM, Christian Rie
Yes, I did. I think I tested this, but not sure atm. I'll provide more info on
this as soon I've got some spare minutes!
Am 09.12.2011 um 17:43 schrieb Massimo Lusetti:
> On Fri, Dec 9, 2011 at 5:37 PM, Christian Riedel
> wrote:
>
>> I'll see what I can do! :
I'll see what I can do! :)
Am 09.12.2011 um 16:12 schrieb Massimo Lusetti:
> On Fri, Dec 9, 2011 at 11:32 AM, Christian Riedel
> wrote:
>
>> can someone have a look at https://issues.apache.org/jira/browse/TAP5-1746 ?
>> If my description to too unclear I could upl
can someone have a look at https://issues.apache.org/jira/browse/TAP5-1746 ?
If my description to too unclear I could upload a demo project as well!
Am 09.12.2011 um 10:50 schrieb Massimo Lusetti:
> Do you think it's time for a 5.3.1 release?
>
> Cheers
> --
> Massimo
> http://meridio.blogspot.
Getting some kind of warning would be nice, though. Maybe you could at least
add a log.warn statement to inform the developer?
Am 05.12.2011 um 02:34 schrieb Taha Hafeez Siddiqi:
> Hi Igor,
>
> I also thought of that but then I settled for this solution because 1) it
> doesn't break 5.2 code
We could make at least a beta or rc-release right now.
I liked the frequent releases of 5.3...
Best,
Christian
Am 24.11.2011 um 17:44 schrieb François Facon:
> Hi Igor
>
> Snapshot version is already on 5.3
> see https://github.com/got5/tapestry5-jquery/blob/master/pom.xml
>
> I guess we will
Christian Riedel: +1 (non-binding)
Am 21.11.2011 um 15:53 schrieb Dragan Sahpaski:
> Dragan Sahpaski: +1 (non-binding)
>
>
>
> On Mon, Nov 21, 2011 at 3:50 PM, Taha Hafeez Siddiqi <
> tawus.tapes...@gmail.com> wrote:
>
>> Taha Hafeez: +1 (non-binding)
&
did you notice this on http://tapestry.apache.org/?
{HTMLcomment}Trigger page export: 18{HTMLcomment}
Am 01.01.2011 um 19:40 schrieb Bob Harner:
> Okay, fixed in the source, should show up in the exported site within a
> couple hours. Thanks for reporting it!
> On Jan 1, 2011 1:34 PM, "Taha Ha
Have you checked the timezone settings of ci and your machines...?
I'd would verify the tests on my computer but I can't run the build. it gives
me an error in line 91:
20:22:11.438 [ERROR] [org.gradle.BuildExceptionReporter] * What went wrong:
20:22:11.439 [ERROR] [org.gradle.BuildExceptionRepo
m 21:52 schrieb Igor Drobiazko:
> It would create a circular dependency.
>
> Отправлено с iPhone
>
> 12.06.2011, в 21:19, Christian Riedel написал(а):
>
>> Don't create more modules! It would be sufficient to put IOCTestCase into
>> tapestry-test, I think... :-)
&
Don't create more modules! It would be sufficient to put IOCTestCase into
tapestry-test, I think... :-)
Am 12.06.2011 um 20:57 schrieb Igor Drobiazko:
> You are right but same applies for org.testng:testng.
>
> However, Gradle's "idea" plugin skips provided dependencies and it results
> in com
> That is the idea, once we finished basic functions defined in GSoC
> proposal, i will try to provide some more features in the future
Nice!
Didn't mean to bash your work, btw... :-)
-
To unsubscribe, e-mail: dev-unsubscr...
Hi Gavin,
great job so far!
>> * Use Tapestry 5.2(.4) instead of 5.1.
better use 5.2.5 :-)
> we have to use Eclipse Dynamic Web Project's
> structure, and i think most web developer will be familiar with this
> structure
Maybe you start a poll in the users list if you are really curious how
congrats, francois! :-)
Am 13.04.2011 um 15:44 schrieb Thiago H. de Paula Figueiredo:
> On Wed, 13 Apr 2011 10:16:24 -0300, François Facon
> wrote:
>
>> Thanks Thiago.
>> We need one more french people to be four like the The Three Musketeers
>> http://en.wikipedia.org/wiki/The_Three_Musketeer
+1
I think that's a good idea! A client of mine recently had issues due to those
checks (root-problem was a bug in the jvm implementation).
Am 15.02.2011 um 00:29 schrieb Howard Lewis Ship:
> I'm starting to wonder whether Tapestry should, in production mode,
> not even check for file changes
tapestry going scrum? finally we get the one-month-release cycle :)
Am 04.01.2011 um 15:29 schrieb Andreas Andreou:
> hmm... ok?
>
> On Tue, Jan 4, 2011 at 16:06, Kevin Menard wrote:
>> Let's do the sprint planning tomorrow (Wed.) instead of today. Ben will
>> be in the office and Eric will be
I started my Windows VM for you - it looks totally messed up IE8 and IE7. I
took the IE-Tester to check IE6, which does not correctly display the
background images (I think due to the lack of proper png support)
Better see yourself:
http://img442.imageshack.us/img442/7104/indexv2.png
I didn't h
Hi Igor,
I'm not sure about the deprecation but generally it's a good idea, I think.
Look at Hibernate and JPA for example. They have kept their annotations and
support the standard ones as well. I like the idea of having the choice...
Cheers
Christian
Am 21.12.2010 um 11:53 schrieb Igor Drob
I've done this a couple of times with m2eclipse:
1. use the svn import instead of m2eclipse import and "Check out as a project
in the workspace" (don't use New Project Wizard). Assuming you call the project
"tapestry-project".
2. right-click-import on tapestry-project, go to "Existing Maven Proj
You can always make bug fix releases, don't you? I'm currently writing two new
applications with 5.2.4 and I didn't recognize any bug :-)
Just make more and smaller steps (releases) to become less anxious!
Am 22.11.2010 um 19:58 schrieb Howard Lewis Ship:
> I'd like to give it a week or two,
Now that 5.2.4 is almost final, don't forget about the bugfix release for 5.1!
:-) Too many apps out there don't implement the workaround for the asset
problem...
Am 20.04.2010 um 14:44 schrieb Sebastian Hennebrueder:
> I don't believe that there is something like well known configuration files
I think it's a good idea... the search engines will be happy if you make sure
the redirects are 301 and not 302!
:-)
Am 16.11.2010 um 17:22 schrieb Kalle Korhonen:
> On Tue, Nov 16, 2010 at 2:20 AM, Christophe Cordenier
> wrote:
>> +1 for URL like
>> http://tapestry.apache.org/stable/apidocs/e
> Since it's still alpha software so there is room to make changes.
> You'll have to get a commiter to on board with making the changes
> though...
>
That's why I'm writing to the dev list :)
> The API as written has a learning curve. Perhaps a mod_rewrite style
> facade would make the curve a l
Am 07.07.2010 um 22:02 schrieb Thiago H. de Paula Figueiredo:
> On Wed, 07 Jul 2010 15:35:51 -0300, Christian Riedel
> wrote:
>
>> Of course, I have to call both methods and see whether the result is null or
>> not. For rewritten incoming requests both decoders wi
be resolved. The problem is, if we strip
> off the locale earlier (providing a new Request object with a changed
> result from getPath()), before the MasterDispatcher, it can confuse
> some of the other logic (particularly, the code that optimizes URLs
> for the current page).
>
>
Am 07.07.2010 um 15:21 schrieb Thiago H. de Paula Figueiredo:
> On Wed, 07 Jul 2010 08:58:51 -0300, Christian Riedel
> wrote:
>
>> Hi,
> Hi!
>
>> is the current replacement of the URLRewriter (LinkTransformer) the final
>> new API for url-rewriting?
>>
Hi,
is the current replacement of the URLRewriter (LinkTransformer) the final new
API for url-rewriting?
I would find some missing things quite useful:
1. A service that parses the request path.
In 5.1 I found it frustrating that there was no proper API within Tapestry to
read out the locale
maybe we should give another option a try: the grey box as in #21 plus the
green as in #23 (or maybe more of the grey panels as you proposed earlier)
Am 18.06.2010 um 17:03 schrieb Howard Lewis Ship:
> I'm torn between the two, but I think #23 has a slight edge over #21.
>
> Vote: #23
>
>
>
#23
http://komiwes.fr/logo-tapestry/index.htm
Am 18.06.2010 um 08:59 schrieb Joachim Van der Auwera:
> Where can the proposals be found?
>
> On 06/18/2010 08:25 AM, Igor Drobiazko wrote:
>> Hello,
>>
>> it looks like the logos are mature enough for voting. I had the impression
>> that most of
nd #21 more awkward.
>>
>> Robert
>>
>> On Jun 16, 2010, at 6/165:22 PM , Andreas Andreou wrote:
>>
>>> on the other hand, i almost hate #23 - the rotated squares miss
>>> stability and the unicorn appears as it's
>>> ready to fall d
I'm just trying to be useful :) maybe someone with a PhD in arts could say
something more powerful to the logo...
Am 17.06.2010 um 09:29 schrieb Massimo Lusetti:
> On Thu, Jun 17, 2010 at 8:19 AM, Christian Riedel
> wrote:
>
>> hm, I find #21 is the instable one... maybe
ted squares miss
> stability and the unicorn appears as it's
> ready to fall down.
> #21 is much better
>
> On Wed, Jun 16, 2010 at 23:21, Christian Riedel
> wrote:
>> i think #23 is really the best now, so vote i'd vote for it, if there's a
>> vote! If
i think #23 is really the best now, so vote i'd vote for it, if there's a vote!
If someone feels that the logo needs a tweak in the future it can be changed it
a little more... All kinds of logos evolve over time, and so does tapestry.
It's a good thing, it tells the viewer this project is very
gt;>> (#7) and 03_03_darkbg (#8).
>>> Green background has been lightly updated on both.
>>> The first version is the cleaned version, i.e. without the grey box.
>>> The other one is a try to transform the bug as a feature. ;)
>>>
>>> On Tue, Ju
The more I look at #7 the more i like it. But it definitely needs some fixes.
That grey box should become a little more visible + the rounded corners to make
the whole logo more stable. Without the box the rotation of the icon will make
the logo look like it's falling apart... well, I would expe
I've got some, too!
Tapestry - more than just a wicket
Tapestry - backwards compatible est 2006
... also major selling points ;)
Or just: Tapestry - Code Less, Live Longer
(but unfortunately we're not selling food here... although...)
I don't like slogans ending with 'more'. They remind me too
plugin/
Am 31.05.2010 um 12:22 schrieb Andreas Andreou:
> i run that build with test disabled - could be affecting javadoc generation?
>
> On Mon, May 31, 2010 at 11:54, Christian Riedel
> wrote:
>> just as a reminder: when you get the copy-process wor
just as a reminder: when you get the copy-process working, don't forget the
javadoc!
http://hudson.zones.apache.org/hudson/view/Tapestry/job/tapestry-5.2-docs/site/apidocs/
cheers
christian
Am 31.05.2010 um 10:40 schrieb Andreas Andreou:
> i've just sent a question to the builds list on the rs
Sounds like advertisement for some AOP-framework :)
Am 26.05.2010 um 20:28 schrieb Piero Sartini:
> 2010/5/26 Howard Lewis Ship :
>> "Why build when you can weave?" :-}
>
> I like it!
> Some variations: "Weave the web!", "Weave your source!", "Weave your apps!"
>
>
Congratulations Igor :)
Am 18.05.2010 um 00:44 schrieb Thiago H. de Paula Figueiredo:
> On Mon, 17 May 2010 14:57:47 -0300, Howard Lewis Ship
> wrote:
>
>> Vote to add committer Igor Drobiazko (drobiazko) to the Tapestry PMC
>> succeeds.
>
> Congratulations for Igor and for the Tapestry proj
As far as I can see, there is on the one side the demand of having the main
site (or the whole docs) under version control and offline editable and on the
other side a wiki-based solution such as confluence would make doc-bug-fixing
very easy and fast... (plus the user-contributions in form of c
> Your solution was looking for two dots... the url I posted had a single dot.
> :)
damn it, didn't read carefully enough :)
i'll look for a better solution then...
-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
[x] confluence
I'd use confluence because:
- documentation can be added on-the-fly
- fixes to older documentation is not dependent on the release of the framework
- the infrastructure is already there
- more contributers could be allowed access to add documentation
- comments by users on document
udes a '.'
>> in the name somewhere.
>>
>
> Seems like a sucky check that could easily be circumvented. Eg:
>
> foo/./bar will have a dot, and give you a directory listing. The browser is
> likely to clean up this request, but that doesn't prevent someone fro
Have you already decided on a solution for the asset protection issue? I think
it was also in progress for 5.2 as well, wasn't it?
Anyway, it's time for a release!
I tested 5.2 on one of my apps and the upgrade was just the switch of the
version number (as promised) :)
Am 04.05.2010 um 10:23 s
d of resolving it (you have to resolve to an asset, and
then resolve the asset to the physical file) was a concern for me.
Robert
On Jan 19, 2010, at 1/194:24 PM , Christian Riedel wrote:
Or you could just resolve the relative path to an absolute path and
apply the existing rule for /path/to/se
Or you could just resolve the relative path to an absolute path and
apply the existing rule for /path/to/secure/resource?
Am 19.01.10 21:21, schrieb Ulrich Stärk:
I see. So all we want to forbid is two consecutive dots in the path
part, i.e. before the last /, right?
Uli
On 19.01.2010 18:45
56 matches
Mail list logo
