Has anybody used yada with tomcat instead of aleph?

I have been experimenting with this and I have found my :servlet-context is going missing from the request.

hey @edwardk as far as I know yada has a hard dependency on aleph for the moment

@imre i think that's incorrect

hi @imre, i know only it is only targeted on aleph, that's why i would call it an experiment... it works for the most part

I don't think it even pulls in aleph as a dependency

apologies, you are right

no but as i understand it's developed against aleph

you learn something new every day

yes, because it is built on the manifold library

aleph is also built against that, so it just happens to be easier to coordinate the two libraries

you can use manifold's functions to coerce your streams into compatible stuff, like channels

it works out of the box with aleph but i have had to jump through a few hoops to fit it to the lein-ring plugin and tomcat

is lein-ring using jetty?

just trying to understand what happens to the original ring request really.

yes, it will fire up jetty

but you can also build a war that can be deployed on tomcat

unfortunately i'm stuck with tomcat for the moment and i need to use some elements from the tomcat servlet-context

it's a bit ugly tbh, but i was keen to play with yada.. not sure at this point if the amount of hacking needed is too great

i'm not familiar with tomcat unfortunately

but afaik aleph is pretty much the only server to use with yada right now

you could use catacumba, but they have some functionality overlaps

the selling point of yada is full async all the way down

I think you lose that with jetty/tomcat

yes, very true. i am quite honestly trying to get some hands-on experience with yada despite the fact that stack i am required to use defeats much of the advantage

although it is still very nice to define the resources once and get the swagger almost for free

I quite like the resource model as well

malcolm mentioned that yada isn't quite production ready yet

its still in its early stages

i'm sure as it matures compatibility issues would be ironed out, but I doubt that's priority

but because everything is data in yada I believe its relatively simple to introspect the ring handlers generated from your resource

Here's an example

@jethroksy: thanks for that, i've figured it out now

the value passed into the :response function contains a :request element

:servlet-context is in there

:thumbsup:

The dependency on aleph isn't ideological or anything, it's just that I have to manage my time carefully and it's quicker right now to target one async server.

Also, yada is no longer in its early stages, it's a proper beta now, nothing substantial will change between now and the official 1.1 release in a few weeks time.

After 1.1 I will gather feedback from users about priorities and definitely look into other web server options - most Java webservers have Servlet async support, and pedestal has made good use of that. I also want to support Immutant. Doing all this will slow down yada development but I feel it will be better to support more deployment options in the future.

btw. the idiomatic way to serve resources now is (yada dir).

I'm considering renaming the 'request-context' ctx to environment env, Om Next does this.

Wonder if anyone has any opinion on this - it won't change any functionality

@edwardk: I'd be very interested to know how your experiment goes