Yup, but group ids differ, so I think, that the SXC repo (from codehaus) on GitHub does not yield the actual code.
From the 2013 commit by Romain, I can see an adjustment of the group id from com.envoisolutions.sxc to org.metatype.sxc The list archive does not contain any useful information regarding sxc. Gruß Richard Am Mittwoch, dem 16.02.2022 um 15:23 +0100 schrieb Jean-Louis Monteiro: > Codehaus repo is https://github.com/codehaus/sxc > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Wed, Feb 16, 2022 at 3:21 PM Zowalla, Richard < > richard.zowa...@hs-heilbronn.de> wrote: > > > From a quick scan of our deps, it looks like we are using > > > > org.metatype.sxc artifacts (last release 2013): > > https://mvnrepository.com/artifact/org.metatype.sxc > > > > I wasn't able to find an actual repository, which contains the > > related > > code (and not the artifacts from the codehouse repo...) > > > > Gruß > > Richard > > > > > > Am Mittwoch, dem 16.02.2022 um 15:17 +0100 schrieb Jean-Louis > > Monteiro: > > > We do have some code to generate JAXB accessors. From what I > > > recall, > > > the > > > first time JAXB sees classes, it will bytecode generate the > > > accessors. This > > > is fine for further invocations, but when you read descriptors > > > only > > > once or > > > a few times, it's not worth generating them at runtime. We use > > > SXC to > > > generate them statically. > > > > > > I'm not fully confident in this area, but this is what I recall > > > and > > > what I > > > saw in the code so far > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > > > > > > On Wed, Feb 16, 2022 at 3:08 PM Thomas Andraschko < > > > andraschko.tho...@gmail.com> wrote: > > > > > > > Why do we need SXC? > > > > > > > > Am Mi., 16. Feb. 2022 um 14:49 Uhr schrieb Jean-Louis Monteiro > > > > < > > > > jlmonte...@tomitribe.com>: > > > > > > > > > Hi, > > > > > > > > > > I'm still doing some upgrades with the view to have some > > > > > jakarta > > > > compliant > > > > > builds for TomEE 9.x. > > > > > > > > > > I did some Geronimo upgrades to Jakarta like Geronimo > > > > > Transaction > > > > > (would > > > > > need a release). I'm now looking at SXC which is a layer on > > > > > top > > > > > of JAXB. > > > > It > > > > > hasn't been released for 13 years and therefore it's not > > > > > Jakarta > > > > > compatible. > > > > > > > > > > I looked at https://github.com/codehaus/sxc which is where > > > > > the > > > > > sources > > > > > are. > > > > > But the strange thing is that we seem to be using a non > > > > > released > > > > > version, > > > > > at least not from that source repo. > > > > > > > > > > Does anyone recall? > > > > > Should we fork that repo and do our own sources? > > > > > Should we reach out to the community? > > > > > > > > > > If we can't do something smart, I'll have to add a module on > > > > > our > > > > > deps/ > > > > > module in TomEE to build and do the relocation of the > > > > > package. > > > > > > > > > > -- > > > > > Jean-Louis Monteiro > > > > > http://twitter.com/jlouismonteiro > > > > > http://www.tomitribe.com > > > > >
smime.p7s
Description: S/MIME cryptographic signature
