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
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 v
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/s
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 solut
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
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
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, Danie
+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
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. :-(
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 co
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
>
>
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:
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
13 matches
Mail list logo
