Re: Possible fix for resolving classpath schemas issues....
Craig, Any chance you could retest this with 2.2.7-SNAPSHOT? I added some code to escape the URL's better (convert spaces to %20 and other fun things) last week some time. Thus, this may now be fixed already. That said, I took the example off the jira again and reran it in a directory with a space and with my m2 repo moved into a director with a space and didn't have any issues.I did a grep for "classpath" and didn't really see anything other than in your spring beans.Thus, I'm not sure where that protocol would have come from. Is there a full stack trace? Dan On Thu February 4 2010 7:03:09 pm Craig Tataryn wrote: > ... when XSDs are held within jar files that have a space in their path. > > Here is the scenario: Dan did a patch for an issue I logged [1] > involving the proper resolution of XSDs held in a separate maven > module (or any jar on the classpath for that matter) instead of the > XSDs existing directly in the module where cxf-codegen-plugin is being > invoked. It worked great for me, but oddly enough only when I invoked > an "mvn clean install" from the parent project. If I went down into > the actual module that was setup for cxf-codegen-plugin and try to > clean install, it would bomb with: > > --- > -- org.apache.maven.lifecycle.LifecycleExecutionException: > Thrown by JAXB > > : unknown protocol: classpath > > . > . > Caused by: java.net.MalformedURLException: unknown protocol: classpath > at java.net.URL.(URL.java:574) > at java.net.URL.(URL.java:464) > at java.net.URL.(URL.java:413) > at > org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) > at > org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at > org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at > org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > at > com.sun.tools.xjc.reader.internalizer.DOMForest.parse(DOMForest.java:394) > > --- > - > > I debugged like crazy, found where things were going wrong. I found a > bug [2] which kind of described the problem, i.e. a jar on the > classpath you are trying to get a resource URL for has a space in it's > path. So what I did was I changed my Maven repo from D:\Documents and > Settings\ to D:\m2repo, a path without spaces. Lo and behold, > everything worked peachy after that. > > So, attached is an attempt at a patch to URIResolver in order to fix > the problem. That being said, I have no way to test this patch in > order to see if it works. Why? Because if I make the fix myself to > the 2.2.6 code on my system, then mvn clean install a new version into > my local repo, then run a debug session when it gets to > AbstractWrapperWSDLLocator.getImportInputSource, the parentLocation > parameter doesn't include a classpath:/ prefix, instead it just > contains the relative path found within the XSD, and I get a > "FileNotFound" type error. No clue why. > > People on Windows (because of the m2 repo being under Documents and > Settings by default; a path containing spaces) would definitely face > the problem I'm trying to solve. I'm not completely sure if it's JDK > vendor related, but on my project I'm using IBM jvm, here's my > environment: > > - > $ mvn --version > Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) > Java version: 1.6.0 > Java home: D:\Program Files\IBM\RAD75\jdk\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch: > "x86" Family: "windows" > - > > So, if anyone would be so kind as to try to replicate the problem, > then apply the patch and see if the problem is resolved, that would be > great. > > Steps to reproduce: > 1) download the sample project from the JIRA issue [1] > 2) crack open the pom.xml file from CXFSchemaRefProblemPom, update the > cxf versions to 2.2.6 > 3) crack open the pom.xml from CXFSchemaRefProblemWar and comment out > all the extraargs except for -verbose > 4) "mvn clean install" from CXFSchemaRefProblemPom, should build cleanly > 5) "mvn clean install -e" from CXFSchemaRefProblemWar, you should get > the classpath protocol error > 6) apply my patch, install the change locally, try step 5 again. > > Thanks, > > Craig > > [1] - https://issues.apache.org/jira/browse/CXF-2599 > [2] - http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6506304 -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
threadlocal leak on shared_factory?
Hello, I have built out a REST service that relies on the JAXBElementProvider for writing the response. However, I didn't explicitly add the JAXBElementProvider into provider configuration: I was relying on the ProviderFactory.SHARED_FACTORY for supplying the JAXBElementProvider as the message writer. Everything functionally works fine but occasionally encounter OOM exceptions with the heap dump clearly pointing to large amounts of memory being held onto in the threadlocalproxy. After further investigation, it looks to me like the SHARED_FACTORY never registers its providers when they are used, so clearThreadLocalProxies are NEVER called on them. If i explicitly add the JAXBElementProvider the issues seems to have resolved the issue: Has anyone else had problems with this happening? Can someone more familiar with the code base comment on this potential defect? It looks to me like maybe a simple fix could be to make sure handleMapper((List)candidates, ep, type, m); even if the SHARED_FACTORY is used. -- View this message in context: http://old.nabble.com/threadlocal-leak-on-shared_factory--tp27555162p27555162.html Sent from the cxf-dev mailing list archive at Nabble.com.
Re: How to reset 'stem' to 'exact' in ServletDestination
Honestly, it doesn't look like the ServletTransportFactory ever looks at the context match strategy. Only the jetty stuff does. Thus, you would need to update the ServletTransportFactory to take that into account. Dan On Wed February 10 2010 3:34:34 pm Sergey Beryozkin wrote: > Hi > > > > I'm playing with a custom MessageObserver implementation showing how to > redirect requests to either SOAP or JAXRS endpoint > > sharing a 'virtual' address, that is we have a > jaxws:endpoint/@address=/a/b and jaxrs:server/@address=/a with the JAXRS > root resource having > > a '/b' @Path. > > > > I need to ensure that a SOAP ServletDestination does not get selected by > ServletController when non-SOAP requests are coming in. > > For it to happen, I need to ensure the SOAP destination has the 'exact' > contextMatch strategy. > > > > But I really can not figure how to do it. > > Configuring httpconf:destination in Spring does not make a difference. > > What can be done here ? Any hints will be appreciated > > > > Thanks, Sergey -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
Re: Generating Javadoc from xsd:sequence/xsd:element documentation
On a side note, I'm not sure if this is of use to anyone else but I built an XJC plugin that allows you to have generated classes of your choice extend or implement another class. So for instance, we have a bunch of top level classes which are generated by xsds, however they don't extend from a common type and we don't have control over the schemas. So I tell the plugin that certain classes should have a super type, and when the class gets generated it winds up with a fresh implements or extends section depending on the supertype chosen... The format of the plugin's config file is: super.type=generated.type1[, generated.type2, generated.type3,...] In my case: eclaims.model.EClaimsRequest=org.hl7.v3.FICRIN600106CA,org.hl7.v3.FICRIN620106CA,org.hl7.v3.FICRIN100206CA,org.hl7.v3.FICRIN600104CA,org.hl7.v3.FICRIN620104CA,org.hl7.v3.FICRIN100204CA eclaims.model.EClaimsResponse=org.hl7.v3.FICRIN610106CA,org.hl7.v3.FICRIN610104CA,org.hl7.v3.FICRIN630106CA,org.hl7.v3.FICRIN630206CA,org.hl7.v3.FICRIN630104CA,org.hl7.v3.FICRIN630204CA,org.hl7.v3.FICRIN110306CA,org.hl7.v3.FICRIN110304CA EClaimsRequest/Response are simply an interfaces (without any methods) that allows us to pass those underlying generated HL7 types around to our service methods instead of them accepting java.lang.Object. At runtime, if need be, the type has to be checked if something special needs to be done with it, but that could probably done smarter. Craig. On Thu, Feb 11, 2010 at 12:02 PM, Daniel Kulp wrote: > On Thu February 11 2010 5:22:12 am Andreas Veithen wrote: >> Dan, >> >> I read your comment on JAXB issue 172 [1]. Did you ever get feedback >> from the guy who said that he had an xjc plugin to generate >> getter/setter Javadoc from xsd:sequence/xsd:element >> annotations/documentations? > > Nope. :-( I'll follow up with another comment. Now that we've pulled > the xjc plugins out into a subproject (I still need to update the web site), > it should be easier to get contributions like this. > > > Dan > > > >> >> Andreas >> >> [1] https://jaxb.dev.java.net/issues/show_bug.cgi?id=172 > > -- > Daniel Kulp > dk...@apache.org > http://www.dankulp.com/blog > -- Craig Tataryn site: http://www.basementcoders.com/ podcast:http://feeds.feedburner.com/TheBasementCoders irc: ThaDon on freenode #basementcoders, ##wicket, #papernapkin twitter: craiger
Re: Generating Javadoc from xsd:sequence/xsd:element documentation
On Thu February 11 2010 5:22:12 am Andreas Veithen wrote: > Dan, > > I read your comment on JAXB issue 172 [1]. Did you ever get feedback > from the guy who said that he had an xjc plugin to generate > getter/setter Javadoc from xsd:sequence/xsd:element > annotations/documentations? Nope. :-(I'll follow up with another comment. Now that we've pulled the xjc plugins out into a subproject (I still need to update the web site), it should be easier to get contributions like this. Dan > > Andreas > > [1] https://jaxb.dev.java.net/issues/show_bug.cgi?id=172 -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
Re: Apache Licensed JAX-RS Spec API JAR
+1 to the sandbox. Thanks Bryant. We should probably go ahead and create a separate part of the tree and stub out some of the 1.1 interfaces/changes as well. -Nick Bryant Luk To dev@cxf.apache.org 02/11/2010 09:08 cc AMwink-...@incubator.apache.org, Rick McGuire Subject Please respond to Re: Apache Licensed JAX-RS Spec API wink-...@incubato JAR r.apache.org I did some work on this since most of the stuff is just interfaces/annotations and that's fairly easy, and I can contribute my initial stab at this. I didn't JavaDoc it but that's something that can be added. If no one minds, I'll put it in the CXF sandbox. On Thu, Feb 11, 2010 at 8:46 AM, Daniel Kulp wrote: > On Thu February 11 2010 5:42:08 am Rick McGuire wrote: >> On 2/10/2010 4:07 PM, Bryant Luk wrote: >> > Hi, >> > >> > We (some followers to Wink dev mailing list) were wondering if the CXF >> > dev community would be interested in helping to contribute/consume a >> > JAX-RS 1.0/1.1 API JAR for Geronimo's spec jars that were Apache >> > licensed. I couldn't find an Apache licensed version of the JSR-311 >> > spec. I see other communities that have implemented JSR specs are >> > using Apache licensed of their specs. I don't know the exact >> > procedure to contribute a spec api jar to Geronimo, but I don't think >> > this would take too much effort considering that most of the JAX-RS >> > spec is annotation/interface based with very few actual classes. >> >> Creating a JAX-RS spec jar is definitely in our plans, but it just >> hasn't happened yet because we haven't started looking at integrating >> this support yet. We even have a Jira open for this particular task: >> >> http://issues.apache.org/jira/browse/GERONIMO-5095 >> >> If you'd like to contribute code for this, the easiest way would be to >> attach a patch to that Jira issue. > > Either that or if people wanted to collaborate on it, create a directory in: > https://svn.apache.org/repos/asf/cxf/sandbox/ > and work on it and then have the Geronimo folks move it to specs when its > "ready". > > The CXF sandbox is open to all Apache committers. The JAX-WS 2.2 spec jar > was initially created that way. Dims and I worked in the sandbox till it was > more or less ready. > > THAT said, for CXF on trunk and using Java 6, we've gone back to using the in- > jdk versions of stuff if at all possible. (which wouldn't apply to jax-rs > obviously) One reason is that the Sun stuff is much better javadoc'd and > we've had some developers complain about that when working in IDE's. To > switch from Sun's version, that is something that would need to be addressed > as well. > > Dan > > > >> >> Rick >> >> > On Wed, Feb 10, 2010 at 2:50 PM, Davanum Srinivas > wrote: >> >> Got it. i mis-remembered seeing a jax-rs api jar from geronimo. Looks >> >> like CXF uses the CDDL jar as well. May be we should ping them to see >> >> if they would be interested. >> >> >> >> +1 from me. >> >> >> >> -- dims >> >> >> >> On Wed, Feb 10, 2010 at 3:44 PM, Nicholas L Gallardo >> >> >> >> wrote: >> >>> +1 from me Bryant. >> >>> >> >>> There isn't a JSR spec for JAX-RS available in Geronimo as of yet. I >> >>> don't know where they've come from in the past, but I'm assuming >> >>> they've been contributed by the relevant technical teams/communities. >> >>> >> >>> The API jar currently in the maven repo is CDDL licensed. >> >>> >> >>> -Nick >> >>> >> >>> >> >>> >> >>> Davanum Srinivas ---02/10/2010 02:40:56 PM---Why can't we use the JSR >> >>> spec from geronimo? :) >> >>> >> >>> Davanum Srinivas >> >>> >> >>> 02/10/2010 02:40 PM >> >>> >> >>> Please respond to >> >>> wink-...@incubator.apache.org >> >>> >> >>> To >> >>> wink-...@incubator.apache.org >> >>> cc >> >>> >> >>> Subject >> >>> Re: Apache Licensed JAX-RS Spec API JAR >> >>> Why can't we use the JSR spec from geronimo? :) >> >>> >> >>> -- dims >> >>> >> >>> On Wed, Feb 10, 2010 at 3:32 PM, Bryant Luk > wrote: >> Hi, >> >> I see that several Apache projects based on JSR specs have geronimo >> (Apache
Re: Apache Licensed JAX-RS Spec API JAR
I did some work on this since most of the stuff is just interfaces/annotations and that's fairly easy, and I can contribute my initial stab at this. I didn't JavaDoc it but that's something that can be added. If no one minds, I'll put it in the CXF sandbox. On Thu, Feb 11, 2010 at 8:46 AM, Daniel Kulp wrote: > On Thu February 11 2010 5:42:08 am Rick McGuire wrote: >> On 2/10/2010 4:07 PM, Bryant Luk wrote: >> > Hi, >> > >> > We (some followers to Wink dev mailing list) were wondering if the CXF >> > dev community would be interested in helping to contribute/consume a >> > JAX-RS 1.0/1.1 API JAR for Geronimo's spec jars that were Apache >> > licensed. I couldn't find an Apache licensed version of the JSR-311 >> > spec. I see other communities that have implemented JSR specs are >> > using Apache licensed of their specs. I don't know the exact >> > procedure to contribute a spec api jar to Geronimo, but I don't think >> > this would take too much effort considering that most of the JAX-RS >> > spec is annotation/interface based with very few actual classes. >> >> Creating a JAX-RS spec jar is definitely in our plans, but it just >> hasn't happened yet because we haven't started looking at integrating >> this support yet. We even have a Jira open for this particular task: >> >> http://issues.apache.org/jira/browse/GERONIMO-5095 >> >> If you'd like to contribute code for this, the easiest way would be to >> attach a patch to that Jira issue. > > Either that or if people wanted to collaborate on it, create a directory in: > https://svn.apache.org/repos/asf/cxf/sandbox/ > and work on it and then have the Geronimo folks move it to specs when its > "ready". > > The CXF sandbox is open to all Apache committers. The JAX-WS 2.2 spec jar > was initially created that way. Dims and I worked in the sandbox till it was > more or less ready. > > THAT said, for CXF on trunk and using Java 6, we've gone back to using the in- > jdk versions of stuff if at all possible. (which wouldn't apply to jax-rs > obviously) One reason is that the Sun stuff is much better javadoc'd and > we've had some developers complain about that when working in IDE's. To > switch from Sun's version, that is something that would need to be addressed > as well. > > Dan > > > >> >> Rick >> >> > On Wed, Feb 10, 2010 at 2:50 PM, Davanum Srinivas > wrote: >> >> Got it. i mis-remembered seeing a jax-rs api jar from geronimo. Looks >> >> like CXF uses the CDDL jar as well. May be we should ping them to see >> >> if they would be interested. >> >> >> >> +1 from me. >> >> >> >> -- dims >> >> >> >> On Wed, Feb 10, 2010 at 3:44 PM, Nicholas L Gallardo >> >> >> >> wrote: >> >>> +1 from me Bryant. >> >>> >> >>> There isn't a JSR spec for JAX-RS available in Geronimo as of yet. I >> >>> don't know where they've come from in the past, but I'm assuming >> >>> they've been contributed by the relevant technical teams/communities. >> >>> >> >>> The API jar currently in the maven repo is CDDL licensed. >> >>> >> >>> -Nick >> >>> >> >>> >> >>> >> >>> Davanum Srinivas ---02/10/2010 02:40:56 PM---Why can't we use the JSR >> >>> spec from geronimo? :) >> >>> >> >>> Davanum Srinivas >> >>> >> >>> 02/10/2010 02:40 PM >> >>> >> >>> Please respond to >> >>> wink-...@incubator.apache.org >> >>> >> >>> To >> >>> wink-...@incubator.apache.org >> >>> cc >> >>> >> >>> Subject >> >>> Re: Apache Licensed JAX-RS Spec API JAR >> >>> Why can't we use the JSR spec from geronimo? :) >> >>> >> >>> -- dims >> >>> >> >>> On Wed, Feb 10, 2010 at 3:32 PM, Bryant Luk > wrote: >> Hi, >> >> I see that several Apache projects based on JSR specs have geronimo >> (Apache licensed) versions of the spec. Should we also consider >> contributing one for JAX-RS 1.0 and 1.1? I don't see one in the Maven >> repository that's Apache licensed. >> >> Thanks. >> >>> >> >>> -- >> >>> Davanum Srinivas :: http://davanum.wordpress.com >> >> >> >> -- >> >> Davanum Srinivas :: http://davanum.wordpress.com > > -- > Daniel Kulp > dk...@apache.org > http://www.dankulp.com/blog >
Re: Apache Licensed JAX-RS Spec API JAR
On Thu February 11 2010 5:42:08 am Rick McGuire wrote: > On 2/10/2010 4:07 PM, Bryant Luk wrote: > > Hi, > > > > We (some followers to Wink dev mailing list) were wondering if the CXF > > dev community would be interested in helping to contribute/consume a > > JAX-RS 1.0/1.1 API JAR for Geronimo's spec jars that were Apache > > licensed. I couldn't find an Apache licensed version of the JSR-311 > > spec. I see other communities that have implemented JSR specs are > > using Apache licensed of their specs. I don't know the exact > > procedure to contribute a spec api jar to Geronimo, but I don't think > > this would take too much effort considering that most of the JAX-RS > > spec is annotation/interface based with very few actual classes. > > Creating a JAX-RS spec jar is definitely in our plans, but it just > hasn't happened yet because we haven't started looking at integrating > this support yet. We even have a Jira open for this particular task: > > http://issues.apache.org/jira/browse/GERONIMO-5095 > > If you'd like to contribute code for this, the easiest way would be to > attach a patch to that Jira issue. Either that or if people wanted to collaborate on it, create a directory in: https://svn.apache.org/repos/asf/cxf/sandbox/ and work on it and then have the Geronimo folks move it to specs when its "ready". The CXF sandbox is open to all Apache committers.The JAX-WS 2.2 spec jar was initially created that way. Dims and I worked in the sandbox till it was more or less ready. THAT said, for CXF on trunk and using Java 6, we've gone back to using the in- jdk versions of stuff if at all possible. (which wouldn't apply to jax-rs obviously) One reason is that the Sun stuff is much better javadoc'd and we've had some developers complain about that when working in IDE's. To switch from Sun's version, that is something that would need to be addressed as well. Dan > > Rick > > > On Wed, Feb 10, 2010 at 2:50 PM, Davanum Srinivas wrote: > >> Got it. i mis-remembered seeing a jax-rs api jar from geronimo. Looks > >> like CXF uses the CDDL jar as well. May be we should ping them to see > >> if they would be interested. > >> > >> +1 from me. > >> > >> -- dims > >> > >> On Wed, Feb 10, 2010 at 3:44 PM, Nicholas L Gallardo > >> > >> wrote: > >>> +1 from me Bryant. > >>> > >>> There isn't a JSR spec for JAX-RS available in Geronimo as of yet. I > >>> don't know where they've come from in the past, but I'm assuming > >>> they've been contributed by the relevant technical teams/communities. > >>> > >>> The API jar currently in the maven repo is CDDL licensed. > >>> > >>> -Nick > >>> > >>> > >>> > >>> Davanum Srinivas ---02/10/2010 02:40:56 PM---Why can't we use the JSR > >>> spec from geronimo? :) > >>> > >>> Davanum Srinivas > >>> > >>> 02/10/2010 02:40 PM > >>> > >>> Please respond to > >>> wink-...@incubator.apache.org > >>> > >>> To > >>> wink-...@incubator.apache.org > >>> cc > >>> > >>> Subject > >>> Re: Apache Licensed JAX-RS Spec API JAR > >>> Why can't we use the JSR spec from geronimo? :) > >>> > >>> -- dims > >>> > >>> On Wed, Feb 10, 2010 at 3:32 PM, Bryant Luk wrote: > Hi, > > I see that several Apache projects based on JSR specs have geronimo > (Apache licensed) versions of the spec. Should we also consider > contributing one for JAX-RS 1.0 and 1.1? I don't see one in the Maven > repository that's Apache licensed. > > Thanks. > >>> > >>> -- > >>> Davanum Srinivas :: http://davanum.wordpress.com > >> > >> -- > >> Davanum Srinivas :: http://davanum.wordpress.com -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
Re: Apache Licensed JAX-RS Spec API JAR
Eoghan, That's still not Apache licensed.It's just the Sun jar/code repackaged with OSGi stuff.The only thing Apache licensed in there is the new FactoryFinder. If SMX is calling the resulting jars Apache licensed, that's a REAL concern. They aren't. Dan On Thu February 11 2010 8:47:59 am Eoghan Glynn wrote: > Have you considered just using the ServiceMix versions of the JSR-311 spec? > > Code here: > http://svn.apache.org/repos/asf/servicemix/smx4/specs/trunk/jsr311-api-1.0/ > http://svn.apache.org/repos/asf/servicemix/smx4/specs/trunk/jsr311-api-1.1/ > > Artefacts here: > http://repo2.maven.org/maven2/org/apache/servicemix/specs/org.apache.servic > emix.specs.jsr311-api-1.0/ > http://repo2.maven.org/maven2/org/apache/servicemix/specs/org.apache.servi > cemix.specs.jsr311-api-1.1/ > > These are Apache licensed. > > Cheers, > Eoghan > > On 11 February 2010 10:42, Rick McGuire wrote: > > On 2/10/2010 4:07 PM, Bryant Luk wrote: > >> Hi, > >> > >> We (some followers to Wink dev mailing list) were wondering if the CXF > >> dev community would be interested in helping to contribute/consume a > >> JAX-RS 1.0/1.1 API JAR for Geronimo's spec jars that were Apache > >> licensed. I couldn't find an Apache licensed version of the JSR-311 > >> spec. I see other communities that have implemented JSR specs are > >> using Apache licensed of their specs. I don't know the exact > >> procedure to contribute a spec api jar to Geronimo, but I don't think > >> this would take too much effort considering that most of the JAX-RS > >> spec is annotation/interface based with very few actual classes. > > > > Creating a JAX-RS spec jar is definitely in our plans, but it just hasn't > > happened yet because we haven't started looking at integrating this > > support yet. We even have a Jira open for this particular task: > > > > http://issues.apache.org/jira/browse/GERONIMO-5095 > > > > If you'd like to contribute code for this, the easiest way would be to > > attach a patch to that Jira issue. > > > > Rick > > > > On Wed, Feb 10, 2010 at 2:50 PM, Davanum Srinivas > > > >> wrote: > >>> Got it. i mis-remembered seeing a jax-rs api jar from geronimo. Looks > >>> like CXF uses the CDDL jar as well. May be we should ping them to see > >>> if they would be interested. > >>> > >>> +1 from me. > >>> > >>> -- dims > >>> > >>> On Wed, Feb 10, 2010 at 3:44 PM, Nicholas L Gallardo > >>> > >>> wrote: > +1 from me Bryant. > > There isn't a JSR spec for JAX-RS available in Geronimo as of yet. I > don't know where they've come from in the past, but I'm assuming > they've been contributed by the relevant technical teams/communities. > > The API jar currently in the maven repo is CDDL licensed. > > -Nick > > > > Davanum Srinivas ---02/10/2010 02:40:56 PM---Why can't we use the JSR > spec from geronimo? :) > > Davanum Srinivas > > 02/10/2010 02:40 PM > > Please respond to > wink-...@incubator.apache.org > > To > wink-...@incubator.apache.org > cc > > Subject > Re: Apache Licensed JAX-RS Spec API JAR > Why can't we use the JSR spec from geronimo? :) > > -- dims > > On Wed, Feb 10, 2010 at 3:32 PM, Bryant Luk > > wrote: > > Hi, > > > > I see that several Apache projects based on JSR specs have geronimo > > (Apache licensed) versions of the spec. Should we also consider > > contributing one for JAX-RS 1.0 and 1.1? I don't see one in the > > Maven repository that's Apache licensed. > > > > Thanks. > > -- > Davanum Srinivas :: http://davanum.wordpress.com > >>> > >>> -- > >>> Davanum Srinivas :: http://davanum.wordpress.com -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
Re: Apache Licensed JAX-RS Spec API JAR
Hi Eoghan, the resulting artifact has an OSGI Locator embedded. This may not be that bad in itself, but it includes some extra bits which non-OSGI consumers won't need and as briefly discussed on the Jersey list, it will 'force' all OSGI users which will depend on it to rely on a specific solution (which is good but it is a specific one nonetheless) to do with the use of the OsgiLocator... cheers, Sergey Have you considered just using the ServiceMix versions of the JSR-311 spec? Code here: http://svn.apache.org/repos/asf/servicemix/smx4/specs/trunk/jsr311-api-1.0/ http://svn.apache.org/repos/asf/servicemix/smx4/specs/trunk/jsr311-api-1.1/ Artefacts here: http://repo2.maven.org/maven2/org/apache/servicemix/specs/org.apache.servicemix.specs.jsr311-api-1.0/ http://repo2.maven.org/maven2/org/apache/servicemix/specs/org.apache.servicemix.specs.jsr311-api-1.1/ These are Apache licensed. Cheers, Eoghan On 11 February 2010 10:42, Rick McGuire wrote: On 2/10/2010 4:07 PM, Bryant Luk wrote: Hi, We (some followers to Wink dev mailing list) were wondering if the CXF dev community would be interested in helping to contribute/consume a JAX-RS 1.0/1.1 API JAR for Geronimo's spec jars that were Apache licensed. I couldn't find an Apache licensed version of the JSR-311 spec. I see other communities that have implemented JSR specs are using Apache licensed of their specs. I don't know the exact procedure to contribute a spec api jar to Geronimo, but I don't think this would take too much effort considering that most of the JAX-RS spec is annotation/interface based with very few actual classes. Creating a JAX-RS spec jar is definitely in our plans, but it just hasn't happened yet because we haven't started looking at integrating this support yet. We even have a Jira open for this particular task: http://issues.apache.org/jira/browse/GERONIMO-5095 If you'd like to contribute code for this, the easiest way would be to attach a patch to that Jira issue. Rick On Wed, Feb 10, 2010 at 2:50 PM, Davanum Srinivas wrote: Got it. i mis-remembered seeing a jax-rs api jar from geronimo. Looks like CXF uses the CDDL jar as well. May be we should ping them to see if they would be interested. +1 from me. -- dims On Wed, Feb 10, 2010 at 3:44 PM, Nicholas L Gallardo wrote: +1 from me Bryant. There isn't a JSR spec for JAX-RS available in Geronimo as of yet. I don't know where they've come from in the past, but I'm assuming they've been contributed by the relevant technical teams/communities. The API jar currently in the maven repo is CDDL licensed. -Nick Davanum Srinivas ---02/10/2010 02:40:56 PM---Why can't we use the JSR spec from geronimo? :) Davanum Srinivas 02/10/2010 02:40 PM Please respond to wink-...@incubator.apache.org To wink-...@incubator.apache.org cc Subject Re: Apache Licensed JAX-RS Spec API JAR Why can't we use the JSR spec from geronimo? :) -- dims On Wed, Feb 10, 2010 at 3:32 PM, Bryant Luk wrote: Hi, I see that several Apache projects based on JSR specs have geronimo (Apache licensed) versions of the spec. Should we also consider contributing one for JAX-RS 1.0 and 1.1? I don't see one in the Maven repository that's Apache licensed. Thanks. -- Davanum Srinivas :: http://davanum.wordpress.com -- Davanum Srinivas :: http://davanum.wordpress.com
Re: Apache Licensed JAX-RS Spec API JAR
Have you considered just using the ServiceMix versions of the JSR-311 spec? Code here: http://svn.apache.org/repos/asf/servicemix/smx4/specs/trunk/jsr311-api-1.0/ http://svn.apache.org/repos/asf/servicemix/smx4/specs/trunk/jsr311-api-1.1/ Artefacts here: http://repo2.maven.org/maven2/org/apache/servicemix/specs/org.apache.servicemix.specs.jsr311-api-1.0/ http://repo2.maven.org/maven2/org/apache/servicemix/specs/org.apache.servicemix.specs.jsr311-api-1.1/ These are Apache licensed. Cheers, Eoghan On 11 February 2010 10:42, Rick McGuire wrote: > On 2/10/2010 4:07 PM, Bryant Luk wrote: > >> Hi, >> >> We (some followers to Wink dev mailing list) were wondering if the CXF >> dev community would be interested in helping to contribute/consume a >> JAX-RS 1.0/1.1 API JAR for Geronimo's spec jars that were Apache >> licensed. I couldn't find an Apache licensed version of the JSR-311 >> spec. I see other communities that have implemented JSR specs are >> using Apache licensed of their specs. I don't know the exact >> procedure to contribute a spec api jar to Geronimo, but I don't think >> this would take too much effort considering that most of the JAX-RS >> spec is annotation/interface based with very few actual classes. >> >> > > Creating a JAX-RS spec jar is definitely in our plans, but it just hasn't > happened yet because we haven't started looking at integrating this support > yet. We even have a Jira open for this particular task: > > http://issues.apache.org/jira/browse/GERONIMO-5095 > > If you'd like to contribute code for this, the easiest way would be to > attach a patch to that Jira issue. > > Rick > > > On Wed, Feb 10, 2010 at 2:50 PM, Davanum Srinivas >> wrote: >> >> >>> Got it. i mis-remembered seeing a jax-rs api jar from geronimo. Looks >>> like CXF uses the CDDL jar as well. May be we should ping them to see >>> if they would be interested. >>> >>> +1 from me. >>> >>> -- dims >>> >>> On Wed, Feb 10, 2010 at 3:44 PM, Nicholas L Gallardo >>> wrote: >>> >>> +1 from me Bryant. There isn't a JSR spec for JAX-RS available in Geronimo as of yet. I don't know where they've come from in the past, but I'm assuming they've been contributed by the relevant technical teams/communities. The API jar currently in the maven repo is CDDL licensed. -Nick Davanum Srinivas ---02/10/2010 02:40:56 PM---Why can't we use the JSR spec from geronimo? :) Davanum Srinivas 02/10/2010 02:40 PM Please respond to wink-...@incubator.apache.org To wink-...@incubator.apache.org cc Subject Re: Apache Licensed JAX-RS Spec API JAR Why can't we use the JSR spec from geronimo? :) -- dims On Wed, Feb 10, 2010 at 3:32 PM, Bryant Luk wrote: > Hi, > > I see that several Apache projects based on JSR specs have geronimo > (Apache licensed) versions of the spec. Should we also consider > contributing one for JAX-RS 1.0 and 1.1? I don't see one in the Maven > repository that's Apache licensed. > > Thanks. > > > -- Davanum Srinivas :: http://davanum.wordpress.com >>> >>> >>> -- >>> Davanum Srinivas :: http://davanum.wordpress.com >>> >>> >>> >> >> > >
Re: Apache Licensed JAX-RS Spec API JAR
On 2/10/2010 4:07 PM, Bryant Luk wrote: Hi, We (some followers to Wink dev mailing list) were wondering if the CXF dev community would be interested in helping to contribute/consume a JAX-RS 1.0/1.1 API JAR for Geronimo's spec jars that were Apache licensed. I couldn't find an Apache licensed version of the JSR-311 spec. I see other communities that have implemented JSR specs are using Apache licensed of their specs. I don't know the exact procedure to contribute a spec api jar to Geronimo, but I don't think this would take too much effort considering that most of the JAX-RS spec is annotation/interface based with very few actual classes. Creating a JAX-RS spec jar is definitely in our plans, but it just hasn't happened yet because we haven't started looking at integrating this support yet. We even have a Jira open for this particular task: http://issues.apache.org/jira/browse/GERONIMO-5095 If you'd like to contribute code for this, the easiest way would be to attach a patch to that Jira issue. Rick On Wed, Feb 10, 2010 at 2:50 PM, Davanum Srinivas wrote: Got it. i mis-remembered seeing a jax-rs api jar from geronimo. Looks like CXF uses the CDDL jar as well. May be we should ping them to see if they would be interested. +1 from me. -- dims On Wed, Feb 10, 2010 at 3:44 PM, Nicholas L Gallardo wrote: +1 from me Bryant. There isn't a JSR spec for JAX-RS available in Geronimo as of yet. I don't know where they've come from in the past, but I'm assuming they've been contributed by the relevant technical teams/communities. The API jar currently in the maven repo is CDDL licensed. -Nick Davanum Srinivas ---02/10/2010 02:40:56 PM---Why can't we use the JSR spec from geronimo? :) Davanum Srinivas 02/10/2010 02:40 PM Please respond to wink-...@incubator.apache.org To wink-...@incubator.apache.org cc Subject Re: Apache Licensed JAX-RS Spec API JAR Why can't we use the JSR spec from geronimo? :) -- dims On Wed, Feb 10, 2010 at 3:32 PM, Bryant Luk wrote: Hi, I see that several Apache projects based on JSR specs have geronimo (Apache licensed) versions of the spec. Should we also consider contributing one for JAX-RS 1.0 and 1.1? I don't see one in the Maven repository that's Apache licensed. Thanks. -- Davanum Srinivas :: http://davanum.wordpress.com -- Davanum Srinivas :: http://davanum.wordpress.com
Generating Javadoc from xsd:sequence/xsd:element documentation
Dan, I read your comment on JAXB issue 172 [1]. Did you ever get feedback from the guy who said that he had an xjc plugin to generate getter/setter Javadoc from xsd:sequence/xsd:element annotations/documentations? Andreas [1] https://jaxb.dev.java.net/issues/show_bug.cgi?id=172
