Eeyup, that seems to do the trick! It complains about proper initialization
and Axis2 no longer logs to stdout, but I can serve soap again!
I now just need to find a way to harmonize the logging from Korma and the
logging that Axis2 provides. But that's an exercise left to the OP. :)
Thanks for
For the for the record and in case anyone has run into something similar,
I've fixed my problem and come to an understanding of it's nature...
First, the why:
As it turns out, Axis2, et. al defaults to yelling on the DEBUG log4j level
for it's activity logs. Thus, if the root appender says DEBUG
So I'm trying to create a drop-in implementation of a SOAP webservice with
Clojure. Naturally I look into libraries that accomplish the different
bits. I need something to do SQL work with a relational db
(Kormahttps://github.com/ibdknox/korma,
check!) and I need to present a SOAP interface
I haven't dealt with CL in quite a while, but there is this (which I was
involved with in my undergrad at CofC):
http://clforjava.org/
CLforJava may be helpful since it is, a totally new version of the Common
Lisp language that runs on the Java Virtual Machine and is intertwined with
the Java
So it does, thanks!
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group,
Let me start by saying, I'm loving this SQLKorma, it feels like just the
right amount of syntax. And there's exec-raw for super fast integration
into an project with existing SQL statements.
However, while kicking the tires I ran into a weird problem, every
predicate works except =, eg:
$=
Thanks for the advice and support everyone! I'm not hopeful at being able to
sway him to a parenthetical language through logic (I've tried!)
Additionally, I definitely would not consider throwing out unmaintainable
decompiled Java code on the sly. That, as Nicolas pointed out, would be the
Nice article in the wiki link, the logic rings pretty true for me. Clojure
is a truly powerful language and I don't want for any higher-level
facilities with it yet. :)
That said, it would probably mean great strides in the industry if elegant
Clojure code could be translated to comprehensible
I'm in a bit of a bind-- I've written some really nice Clojure code for
dealing with Genomic sequences that works as well or better than the
reference implementation we currently use where I work. However, the the
hierarchy has recently changed and my new boss is requiring me to have all
code in
I have a problem with swank with an upgrade recently, clojure1.3-alpha5
works, clojure-1.3alpha6 does not, to my knowledge-- which Clojure version
are you using in your project?
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group,
What makes an ecosystem '1.x' vs '2.x' etc. needs to be quantifiable
to make a standard out of it. To quote Peter Drucker, What gets
measured gets managed. Are there any solid examples of languages that
would constitute a good canonical spectrum for ecosystem versions and
why?
It seems like if
Inc is probably a better way to say that, yeah.
I also agree with David that 2.0 has a popular connotation of
shiny-ness that came with the whole infamous Web 2.0 branding
phenomenon.
I am now at conflict internally, because I'd like to see Clojure
widely adopted, but I like the idea of the
12 matches
Mail list logo
