Re: Problem with Korma and clj-soap
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 your help everyone, I hope your holidays are pleasant! -- 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, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Problem with Korma and clj-soap
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 is the default log level, Axis2 proceeds to constantly dump logs out to console. It seems broken in that state and no programmer in their right mind will go and try to digest a WSDL when the console is filling up with hundreds of lines of DEBUG spewing out with what looks like stack-traces. So the real answer was, I should have ignored the screaming logs and tried things anyway. You can fix it two ways, both of which involve providing your own log4j.xml: 1) You can set root log level to anything above DEBUG (INFO, for example.) 2) You can add two new loggers to contain the screaming server logs: org.apache.axis2 and org.apache.axiom at, again at any log level above DEBUG. Hope this helps! -- 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, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Problem with Korma and clj-soap
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 (clj-soaphttps://bitbucket.org/taka2ru/clj-soap, check!) Unfortunately I'm having tooling issues putting the two together. The first problem, I'm pretty sure, was simply a Clojure version mismatch: I and Korma were using Clojure 1.3 and alj-soap was using 1.2-- so I checked out the clj-soap source and updated the libraries (Clojure to 1.3, the Axis2 libraries to their latest) and ran the tests to make sure all was still working-- it was. So I pushed the 'new' clj-soap to clojars as [org.clojars.crenshawda/clj-soap 0.1.2] and tried again. Much to my chagrin I started getting seemingly endless byzantine DEBUG log traces spewed out into the repl when I try to start the soap server. If I comment Korma out of the project.clj, lein deps, and lein repl the same thing works like a charm. I also checked out each of Korma's dependencies individually and ran the same serve function and it worked (the log4j dep made it complin, but it still served just fine.) I'm not exactly sure WHAT is causing the collision between Korma and clj-soap, but it's damaging my calm at this point. :) I have a gut feeling that it's somehow logging related, but I don't know why it would cause clj-soap to flip out so badly. To recreate my scenario, start a new project and add these dependencies to the project.clj: [org.clojure/clojure 1.3.0] ;; if is isn't already there by default, I want to use 1.3 [korma 0.3.0-apha4] [org.clojars.crenshawda/clj-soap 0.1.2] ;; use [clj-soap 0.1.1] if you want to see what I was talking about with the 1.2/1.3 mismatch Since Axis2 (what clj-soap is build upon) requires compiled classes to serve soap, you'll probably have to define a service in a clj file so 'lein repl' will pre-compile it for convenience sake. You can use this: (soap/defservice service.Hello (hello ^String [^String s] (str Hello Yourself))) So when you start your repl you should have classes/services/Hello.class in your classes/ directory. After you have to invoke clj-soap's serve function: (serve service.Hello) ... nd you should have a lovely logging wreck in your repl. I'd be happier if I could at least figure out WHY it happens when I put Korma in my dependencies. Sorry for the wall of text, but I figure too much info is usually better than not enough. :) -- 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, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Clojure-in-CommonLisp?
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 language in such a way that users of Lisp can directly access Java libraries and vice versa. Sounds familliar? :) Clojure - Java - CLforJava -- 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, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: SQL Korma Missing Pred
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, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
SQL Korma Missing Pred
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:
$= (select table (where {:id [= 1]}))
$= CompilerException java.lang.RuntimeException: No such var:
korma.internal.sql/pred-=, compiling:(NO_SOURCE_PATH:46)
Perhaps I'm missing something but all the rest of the pred-vars are there,
that specific one is missing. I wanted to ask before I bother someone with
a ticket.
Thanks,
Dennis
--
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, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
Re: Using Clojure to Generate Java Source?
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 ticket to finding a new place of employment. :) I'll try and make the case with him and our mutual boss for letting me work with interop until we get some time to re-develop a pure-Java solution. I don't expect the pace of development to slow down and perhaps proximity to elegance will make an impression. I have to respect that it's his project, but I definitely cringing at re-developing this thing imperatively. -- 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, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: producing Blub code and vv.
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 Java code (or to other languages.) I feel companies use different tools all the time as long as it results in efficient generation of their lingua franca (Java, Python, Ruby, etc.) They switch languages very rarely because it takes a revolution in philosophy to unseat a considerable investment in a particular language. If Clojure could translate itself into other languages the adoption argument would be reduced to getting someone to let you use anther tool to auto-generate boilerplate (the same way IDEs might generate Java getter/setters.) Only this tool would come with lots of parenthesis and a REPL, among other things. ClojureScript being a prime example of Clojure 'speaking' another language. This type of feature is probably only useful as a bridge between now and when everyone in the future talks in reverse polish notation. However, I think comfortable proximity to Clojure's elegance and efficiency would help other developers slowly become acclimated to, and even secretly curious about a new way of thinking. -- 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, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Using Clojure to Generate Java Source?
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 Java (eg. interop is not an option since he wants the source to be pure Java.) Is there any way to prevent my head exploding from hand-translating my Clojure code into Java? I'm sure it's possible to generate Java source since we heard Rich's amusing anecdote about using Clojure to write reams of Java boilerplate instead of doing himself. Is there a precedent or even an existing library for translation from Clojure into Java source though? I'd like to be able to use the code I've got without a long, painful devolution. More importantly, I want to be able to continue developing in Clojure and just compile it to Java source and check that in. Thanks, Dennis -- 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, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: clearly, I'm too dense to upgrade slime/swank/clojure-mode... help?
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, 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, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Release.Next Version Number
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 the ecosystem surrounding a language is another concern in the semantic versioning equation that can't be sufficiently be expressed by the existing scheme, there should be a another digit(s) or a whole other semantic version system for it (e.g. 1.2.0.0 or perhaps 0.1.0_2.0.0 for Clojure 2.0 with a basic, whatever that may mean, ecosystem surrounding it.) My points may also be a moot point, since it seems to make this SemVer compatible we might have to call it SemVer 1.1.0, or 2.0 depending on how people thought the extra digit(s) would affect the compatibility with the SemVer spec as it stands. (Is it SemVer 1.0.0 right now?) All this being said, I like the idea of semantic versioning and I wish more languages/software at least attempted some sort of version number scheme transparency. #(+ 1 %) to semantic versioning. TL;DR Can an ecosystem be properly versioned? Can that version be cleanly expressed by the current SemVer scheme? -- 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, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Release.Next Version Number
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 language having the agility to do radical things to make itself better in a way that Java no longer posses. So 1.3 still has its advantages. Clojure always has the choice to stay the transition to semantic versioning until Rich feels that it's at a place that semantic versioning makes sense. I believe I've thought myself in a circle and need some hammock time on this. -- 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, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
