Tapestry-security 0.6.3 and tapestry-model 0.6.0 for T5.4 released!

[Kalle Korhonen]

Hey all,

at this time we have two T5.4 compatible release announcements to make.
First tapestry-security 0.6.3:

While working on securing an Ember frontend with Tapestry backend, I
noticed that tynamo-resteasy didn't want to play well with security. I'm
fairly surprised this issue surfaced only now because tapestry-security is
fairly well battle tested. Anyhow, if you've ever had a problem with T5.4
and tapestry-security not being able obtain assigned roles or user identity
from the request, it's time to upgrade.

**Release notes**

- Update to T5.4-rc-1 [#25](
https://github.com/tynamo/tapestry-security/issues/25)
- Store ShiroHttpServletRequest to RequestGlobals before processing [#24](
https://github.com/tynamo/tapestry-security/issues/24)

---
tapestry-model 0.6.0:

Finally, we have an officially compatible release tapestry-model for T5.4
available. We had one long running issue with the changes in tapestry core
and it wasn't until T5.4-rc1 before it was all sorted out. The official
release note is short but there's been lots of great functional changes to
the core.

**Release notes**

- Fix the test suite to use changed form element names [#4](
https://github.com/tynamo/tapestry-model/issues/4)
- 0.5.2 has a dependency on eclipselink [#2](
https://github.com/tynamo/tapestry-model/issues/2)

Happy holidays,
from your friendly Tynamo team

Re: 5.4-rc-1 - problem when *add* a column to a *grid*, but it is working OK in 5.4-beta-26

[Vangel V. Ajanovski]

First of all, I have made a mistake in the subject - it was supposed to 
be 5.4-rc-1


On 14.12.2015 09:18, Chris Poulsen wrote:

show. (If you are not using include, a number of things can go wrong like:
the Degree class may evolved, the hibernate stuff may have added extra
runtime properties that the introspector is picking up, the JDK version may
have changed which means that the introspector behavior may have changed,
new data type analyzers may have been added etc.)
The added property is not a member of this class properties, so I see no 
real reason why including the other properties should matter. But, I do 
get why you are suggesting that.


On the other hand, I would prefer not to use the "include" since it 
polutes the (H)THML with with internal (read: database) details. On the 
other hand, "add" is just a view layer thing, since you add an 
interaction element to the (H)TML.


But, this debate is fruitless, because it does not matter.
I tried using "include", the problem remains.

I guess the real reason for this happening is some incompatibility, 
between some of the libraries, but I have spent many hours to find the 
problem and tried many combinations  without luck. So any ideas towards 
finding a solution would be great.




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Is tapestry plastic incompatible with JEE specs?

[Thiago H de Paula Figueiredo]

On Sat, 12 Dec 2015 16:42:51 -0200, Luca Arzeni  wrote:


Hi Dimitris,


Hi, Luca!

Thanks for the insights about JBoss. I've never used it, so I've learned  
some new stuff today and I thank you for that. :)


I agree with you when you say the problem is caused by JBoss separating  
which classloader can access which classes (or classpaths). Is this  
defined by the Java EE specs? If yes, so yes, Tapestry doesn't support the  
spec fully.


Well, at least you seem to have found a way to avoid this problem, and  
thanks for sharing it. ;)


--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

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

Re: 5.4-rc-1 - problem when *add* a column to a *grid*, but it is working OK in 5.4-beta-26

[Chris Poulsen]

I don't know what you mean by having tried many library combinations. But
Tapestry related libs should all be the same version and without duplicates
in your runtime.

The error you are getting happens because the BeanModel for your grid
already contains a property called "delete".

So if you actually tried using  and got the error, something is really off...

You can try to attach a debugger to either Grid, BeanModelUtils or
BeanModelImpl to see what your generated model contains... or create / bind
a bean model explicitly and debug using that.

-- 
Chris

On Mon, Dec 14, 2015 at 12:04 PM, Vangel V. Ajanovski 
wrote:

> First of all, I have made a mistake in the subject - it was supposed to be
> 5.4-rc-1
>
> On 14.12.2015 09:18, Chris Poulsen wrote:
>
>> show. (If you are not using include, a number of things can go wrong like:
>> the Degree class may evolved, the hibernate stuff may have added extra
>> runtime properties that the introspector is picking up, the JDK version
>> may
>> have changed which means that the introspector behavior may have changed,
>> new data type analyzers may have been added etc.)
>>
> The added property is not a member of this class properties, so I see no
> real reason why including the other properties should matter. But, I do get
> why you are suggesting that.
>
> On the other hand, I would prefer not to use the "include" since it
> polutes the (H)THML with with internal (read: database) details. On the
> other hand, "add" is just a view layer thing, since you add an interaction
> element to the (H)TML.
>
> But, this debate is fruitless, because it does not matter.
> I tried using "include", the problem remains.
>
> I guess the real reason for this happening is some incompatibility,
> between some of the libraries, but I have spent many hours to find the
> problem and tried many combinations  without luck. So any ideas towards
> finding a solution would be great.
>
>

Re: 5.4-rc-1 - problem when *add* a column to a *grid*, but it is working OK in 5.4-beta-26

[Vangel V. Ajanovski]

On 14.12.2015 12:50, Chris Poulsen wrote:

The error you are getting happens because the BeanModel for your grid
already contains a property called "delete".

If I replace
  add="delete"
with
  add="deleteHVUHDVIUDHVS"

I will get a message that the Model already contains "deleteHVUHDVIUDHVS"


So if you actually tried using  and got the error, something is really off...

As I said, I did try that and still get the error.


You can try to attach a debugger to either Grid, BeanModelUtils or
BeanModelImpl to see what your generated model contains... or create / bind
a bean model explicitly and debug using that.

Will try.



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 5.4-rc-1 - problem when *add* a column to a *grid*, but it is working OK in 5.4-beta-26

[Vangel V. Ajanovski]

On 14.12.2015 12:48, Thiago H de Paula Figueiredo wrote:
Have you tried to @Inject BeanModelSource and call 
beanModelSource.createDisplayModel(yourClass.class, messages) and see 
what are the properties (PropertyModel instances) it detects?




So in the tml I know have a random property name:



Calling:
 model = bms.createDisplayModel(Degree.class, messages);
 System.out.println(model.getPropertyNames());
Printout:
 [degreeId, code, title, titleEn, terms, note]

As you see there is no property "deleteuh9uhco9qh98ehv" in the model.

But, the error occurs again:
*Bean editor model for mk.ukim.finki.isis.dossier.entities.Degree 
already contains a property model for property 'deleteuh9uhco9qh98ehv'.*


smime.p7s
Description: S/MIME Cryptographic Signature

Re: 5.4-rc-1 - problem when *add* a column to a *grid*, but it is working OK in 5.4-beta-26

[Thiago H de Paula Figueiredo]

On Mon, 14 Dec 2015 09:04:15 -0200, Vangel V. Ajanovski  
 wrote:



But, this debate is fruitless, because it does not matter.
I tried using "include", the problem remains.


Have you tried to @Inject BeanModelSource and call  
beanModelSource.createDisplayModel(yourClass.class, messages) and see what  
are the properties (PropertyModel instances) it detects?


--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

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

Re: 5.4-ga-1 - problem when *add* a column to a *grid*, but it is working OK in 5.4-beta-26

[Chris Poulsen]

Hi,

I don't know if there is an issue with the GA, but you are relying on
introspection to find your bean properties; that is asking for trouble IMO.

Always use property whitelisting to achieve a stable set of properties for
your grids. Basically make sure to "include" the properties you want to
show. (If you are not using include, a number of things can go wrong like:
the Degree class may evolved, the hibernate stuff may have added extra
runtime properties that the introspector is picking up, the JDK version may
have changed which means that the introspector behavior may have changed,
new data type analyzers may have been added etc.)

-- 
Chris



On Mon, Dec 14, 2015 at 2:31 AM, Vangel V. Ajanovski 
wrote:

> When adding a new column to a grid like this:
>
> 
> 
> delete
> 
> 
>
> I am getting an
> org.apache.tapestry5.ioc.internal.OperationException
> Render queue error in CleanupRender[admin/DegreeList:grid]: Bean editor
> model for mk.ukim.finki.isis.dossier.entities.Degree already contains a
> property model for property 'delete'.
>
> The error occurs on 5.4-rc-1, but not on 5.4-beta-26.
> The same piece of code has been working without such a problem with
> previous versions for the last 3 years at least.
>
> Java:
> openjdk version "1.8.0_66"
> OpenJDK Runtime Environment (build 1.8.0_66-b17)
> OpenJDK 64-Bit Server VM (build 25.66-b17, mixed mode)
>
> Source where problem occurs:
>
> https://develop.finki.ukim.mk/projects/isis/browser/trunk/src/main/resources/mk/ukim/finki/isis/dossier/pages/admin/DegreeList.tml
>
> https://develop.finki.ukim.mk/projects/isis/browser/trunk/src/main/java/mk/ukim/finki/isis/dossier/pages/admin/DegreeList.java
>
> Project pom.xml:
> https://develop.finki.ukim.mk/projects/isis/browser/trunk/pom.xml
>
>