Re: Tapestry vs Spring MVC + REST + Angular

[JumpStart]

Totally agree. 

Most recently I’ve built an extensive tablet app using T5.4 + PhoneGap. 

It’s massively AJAX, but I didn’t have to think about it very much - thanks to 
Zones.

It employs only 5 pages instead of a few hundred - thanks to components and 
Zones. SPA without pain!

The small amount of custom JavaScript is done as components and is beautiful 
(I'd never before thought that possible) - thanks to T5.4 using RequireJS.

It runs so fast - fast enough to fool most into believing it is a native app - 
thanks to Zones, RequireJS, and T5.4’s asset handling (and AWS)!

But most of all, it has been a joy to build, and it has let me focus on the 
domain most of the time, which I can’t say is true of any other framework I’ve 
used (not even GWT).

Tapestry, and especially Tapestry 5.4, I take my hat off to you.

Geoff

> On 29 Jul 2016, at 8:38 PM, Qbyte Consulting  
> wrote:
> 
> After years of Tapestry focus I finally got around to checking out how
> others are building web apps these days. Spring MVC + REST and Angular seem
> to be flavours of the day and can create some quite slick solutions. These
> approaches are still full of boilerplate code, but things are looking a lot
> better than the early days of Struts.
> 
> So far as I can see Tapestry and maybe GWT are still the only one stop shop
> for cutting out the boiler plate code and having a focus on domain driven
> design with components instead of these pattern centric low level
> approaches.


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

Re: Tapestry 5.3.6 not recognising named queries

[Jay Ginete]

Assuming your using JPA, is the Entity class explicitly mapped in the
persistence.xml? I've had a problem similar to this is if just do a package
mapping instead of explicitly mapping each class.

On Mon, Aug 1, 2016 at 10:01 PM, Qbyte Consulting  wrote:

> Hi,
>
> I have a Maven dependency tree like this:
> Entity Classes
> DAO Layer
> DAO Consumer (Tynamo resteasy layer)
>
> java.lang.IllegalArgumentException: NamedQuery of name:
> EUser.findByUsername not found.
>
> In my consumer project everything runs, I can see the entity classes
> registering in JPA and my DAO is wired up, but somehow the named queries
> aren't available. Any ideas why?
>
> I thought if I referenced the Entity Classes dependency directly in my
> consumer layer that it may help because if I access the Entity Classes as a
> direct dependency they work.
>
> John
>
> [EL Config]: metadata: 2016-08-01
> 14:51:09.96--ServerSession(27246127)--Thread(Thread[main,5,main])--The
> alias name for the entity class [class EUser] is being defaulted to: EUser.
>



-- 


[image: Jay Ginete on about.me]

Jay Ginete
about.me/jay.ginete
  

Re: Tapestry launch a JEE 7 webservice?

[Kalle Korhonen]

Yes, use tapestry-resteasy (http://www.tynamo.org/tapestry-resteasy+guide/).
You wouldn't need an explicit subclass of Application, but you'd configure
your resources with:

@Contribute(javax.ws.rs.core.Application.class)
public static void configureRestResources(Configuration
singletons,
YourRestResource yourRestResource, ... ) {
singletons.add(yourRestResource);
// optionally... CorsFeature implements javax.ws.rs.core.Feature
etc.
singletons.add(new corsFeature());
singletons.add(new JacksonConfig());
singletons.add(new JsonExceptionMapper());
}

Kalle


On Mon, Aug 1, 2016 at 3:27 AM, Qbyte Consulting 
wrote:

> I am attempting to combine a JPA layer built on Tapestry 5.3.6 with a
> RESTful webservice built for JEE 7.
>
> The web service is configured in code:
> public class ApplicationConfig extends Application
>
> However Tapestry JPA is configured with the servlet filter in web.xml:
> org.apache.tapestry5.TapestryFilter
>
> I'm actually wanting to deploy on Jetty and not use a JEE container. How
> can I combine these 2 approaches?
>
> Is there are way to get my AppModule to get Tapestry to serve the web
> services?
>
> thanks,
> John
>

Tapestry 5.3.6 not recognising named queries

[Qbyte Consulting]

Hi,

I have a Maven dependency tree like this:
Entity Classes
DAO Layer
DAO Consumer (Tynamo resteasy layer)

java.lang.IllegalArgumentException: NamedQuery of name:
EUser.findByUsername not found.

In my consumer project everything runs, I can see the entity classes
registering in JPA and my DAO is wired up, but somehow the named queries
aren't available. Any ideas why?

I thought if I referenced the Entity Classes dependency directly in my
consumer layer that it may help because if I access the Entity Classes as a
direct dependency they work.

John

[EL Config]: metadata: 2016-08-01
14:51:09.96--ServerSession(27246127)--Thread(Thread[main,5,main])--The
alias name for the entity class [class EUser] is being defaulted to: EUser.

Tapestry launch a JEE 7 webservice?

[Qbyte Consulting]

I am attempting to combine a JPA layer built on Tapestry 5.3.6 with a
RESTful webservice built for JEE 7.

The web service is configured in code:
public class ApplicationConfig extends Application

However Tapestry JPA is configured with the servlet filter in web.xml:
org.apache.tapestry5.TapestryFilter

I'm actually wanting to deploy on Jetty and not use a JEE container. How
can I combine these 2 approaches?

Is there are way to get my AppModule to get Tapestry to serve the web
services?

thanks,
John