Re: [PR] CXFXJC-47: XJC DefaultValue plugin uses JAXBElement that does not have a default constructor [cxf-xjc-utils]
marcelhdl commented on PR #129: URL: https://github.com/apache/cxf-xjc-utils/pull/129#issuecomment-2162384855 @reta thanks for the quick response. I hope so too. Do you need some support with backporting the fix? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Apache CXF Fediz jars compatibility with jakarta ee 9
Hi, We are upgrading to Tomcat 10.x. We observed that in the latest 1.6.2 version, fediz-core jar , fediz-tomcat jars etc are still using javax which is not compatible with jakarta ee 9 specifications. Can you please let us know when the official release will be available for the above jars which are jakarta ee 9 compatible from Apache cxf Fediz Thanks, Sai Charan Teja -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. smime.p7s Description: S/MIME Cryptographic Signature
Re: Apache CXF Fediz jars compatibility with jakarta ee 9
Please see https://issues.apache.org/jira/browse/FEDIZ-257 I take from the comments on the card that the community needs to step up and help Fediz towards CXF 4.0 / Jakarta support. On Wed, Jun 12, 2024 at 8:12 AM Sai Charan Teja Pratti wrote: > > Hi, > > We are upgrading to Tomcat 10.x. We observed that in the latest 1.6.2 > version, fediz-core jar , fediz-tomcat jars etc are still using javax which > is not compatible with jakarta ee 9 specifications. > > Can you please let us know when the official release will be available for > the above jars which are jakarta ee 9 compatible from Apache cxf Fediz > > Thanks, > Sai Charan Teja > > This electronic communication and the information and any files transmitted > with it, or attached to it, are confidential and are intended solely for the > use of the individual or entity to whom it is addressed and may contain > information that is confidential, legally privileged, protected by privacy > laws, or otherwise restricted from disclosure to anyone else. If you are not > the intended recipient or the person responsible for delivering the e-mail to > the intended recipient, you are hereby notified that any use, copying, > distributing, dissemination, forwarding, printing, or copying of this e-mail > is strictly prohibited. If you received this e-mail in error, please return > the e-mail to the sender, delete it from your computer, and destroy any > printed copy of it.
Re: [PR] CXFXJC-47: XJC DefaultValue plugin uses JAXBElement that does not have a default constructor [cxf-xjc-utils]
reta commented on PR #129: URL: https://github.com/apache/cxf-xjc-utils/pull/129#issuecomment-2162841208 > I hope so too. Do you need some support with backporting the No, thank you @marcelhdl , it is already in 4.0.x and 3.3.x branches -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump jakarta.servlet:jakarta.servlet-api from 6.0.0 to 6.1.0 [cxf]
reta closed pull request #1920: Bump jakarta.servlet:jakarta.servlet-api from 6.0.0 to 6.1.0 URL: https://github.com/apache/cxf/pull/1920 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.maven.plugins:maven-dependency-plugin from 3.6.1 to 3.7.0 [cxf]
reta merged PR #1921: URL: https://github.com/apache/cxf/pull/1921 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump jakarta.servlet:jakarta.servlet-api from 6.0.0 to 6.1.0 [cxf]
dependabot[bot] commented on PR #1920: URL: https://github.com/apache/cxf/pull/1920#issuecomment-2163019541 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump org.eclipse.jdt:org.eclipse.jdt.core from 3.37.0 to 3.38.0 [cxf-xjc-utils]
dependabot[bot] opened a new pull request, #154: URL: https://github.com/apache/cxf-xjc-utils/pull/154 Bumps [org.eclipse.jdt:org.eclipse.jdt.core](https://github.com/eclipse-jdt/eclipse.jdt.core) from 3.37.0 to 3.38.0. Commits See full diff in https://github.com/eclipse-jdt/eclipse.jdt.core/commits";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: Deprecate aegis databinding ?
Thanks for letting us know. It sounds like it's good to extend the life support of Aegis for several releases. On Tue, Jun 4, 2024 at 3:54 PM Vassilis Virvilis wrote: > Hi Jim, > > Here are some bugs / discussions with some test cases that have been fixed > (or workaround-ed) over the years. > >1. SOAP: Aegis databinding Collection of derived classes: >https://lists.apache.org/thread/rp73ym9f64vpvng057d55mtj3wnznr80 >2. SortedMap is not returned when another unrelated method exists in >the interface: https://issues.apache.org/jira/browse/CXF-4605 >3. SortedMap is returned as HashMap: >https://issues.apache.org/jira/browse/CXF-4534 >4. Aegis cannot handle nested map inheritance: >https://issues.apache.org/jira/browse/CXF-3526 > > I do not remember the specifics but I have been burned by the other > serializers and the Pavlov reflexes is all I have left. > > The jaxrs - (now jakarta.rs) is able to transmit these kind of type (with > some hand holding) and I have some prototypes that are working. Furthermore > the receipt from java programs has not been verified - only from browsers > (Resty-GWT again with hand holding and custom patches). > > My problem is time. Scheduling a full migration from Aegis to jax-rs is a > very serious undertaking. > > So I would certainly appreciate the extension of life support of Aegis. > > Hope that helps. > > Vassilis > > > On 6/3/24 4:24 AM, Jim Ma wrote: > > Hi Vassilis, > Thanks for your input . It's good to know that there is still some usage > that jaxb or xmlbeans can't nicely handle. > I am curious to know more details about this use case about transfering Map > Of Maps or Map of Collections. > Could you please paste a test case or some code snippet to have a look ? > > Thanks, > Jim > > > On Mon, Apr 29, 2024 at 5:46 PM Vassilis Virvilis > > wrote: > > > I am using it. > > Although I plan to move to JAX-RS. However, I can't be sure about the > scheduling... > > Aegis is the simplest and most versatile databinding for java first > development in my opinion. > > The others (jax-ws, jaxb and xmlbeans) never worked for me when I had to > transfer > Map Of Maps or Map of Collections. > > I just wanted to give you my one datapoint. I understand that the > developers will have to weigh > carrying around a databinding vs its existing usage vs the development > effort required. > > Vassilis > > On 4/22/24 6:06 AM, Jim Ma wrote: > > Hi all, > I am not sure if it's the time to deprecate some old cxf things that no > > one > > is using, so I write to get your thoughts/ideas here. > The first I can think of is aegis databinding. Is the aegis databinding > still used by CXF users ? Is it a good time to deprecate and remove in > > the > > future release ? > > Thanks, > Jim > > > > -- > > __ > > Vassilis Virvilis Ph.D. > Head of IT > Biovista Inc. > > Stay tuned > www: http://www.biovista.com > LinkedIn: https://www.linkedin.com/company/biovista > Twitter: https://twitter.com/BiovistaInc/ >Vizit https://twitter.com/BiovistaVizit/ > Facebook: https://www.facebook.com/biovistainc >Vizit (research): https://www.facebook.com/BiovistaVizit > YouTube: https://www.youtube.com/user/BiovistaInc > > -- > US Offices > 2421 Ivy Road > Charlottesville, VA 22903 > USA > T: +1.434.971.1141 > F: +1.434.971.1144 > > European Offices > 34 Rodopoleos Street > Ellinikon, Athens 16777 > GREECE > T: +30.210.9629848 > F: +30.210.9647606 > > Biovista is a privately held biotechnology company that finds novel uses for > existing drugs, and profiles their side effects using their mechanism of > action. Biovista develops its own pipeline of drugs in CNS, oncology, > auto-immune and rare diseases. Biovista is collaborating with > biopharmaceutical companies on indication expansion and de-risking of their > portfolios and with the FDA on adverse event prediction. > > >
Re: Deprecate aegis databinding ?
That would be ideal (the opposite to catastrophic in this case) for me. I will let you know if I manage to migrate cxf-rs. Thanks a lot. On 6/13/24 4:34 AM, Jim Ma wrote: Thanks for letting us know. It sounds like it's good to extend the life support of Aegis for several releases. On Tue, Jun 4, 2024 at 3:54 PM Vassilis Virvilis wrote: Hi Jim, Here are some bugs / discussions with some test cases that have been fixed (or workaround-ed) over the years. 1. SOAP: Aegis databinding Collection of derived classes: https://lists.apache.org/thread/rp73ym9f64vpvng057d55mtj3wnznr80 2. SortedMap is not returned when another unrelated method exists in the interface: https://issues.apache.org/jira/browse/CXF-4605 3. SortedMap is returned as HashMap: https://issues.apache.org/jira/browse/CXF-4534 4. Aegis cannot handle nested map inheritance: https://issues.apache.org/jira/browse/CXF-3526 I do not remember the specifics but I have been burned by the other serializers and the Pavlov reflexes is all I have left. The jaxrs - (now jakarta.rs) is able to transmit these kind of type (with some hand holding) and I have some prototypes that are working. Furthermore the receipt from java programs has not been verified - only from browsers (Resty-GWT again with hand holding and custom patches). My problem is time. Scheduling a full migration from Aegis to jax-rs is a very serious undertaking. So I would certainly appreciate the extension of life support of Aegis. Hope that helps. Vassilis On 6/3/24 4:24 AM, Jim Ma wrote: Hi Vassilis, Thanks for your input . It's good to know that there is still some usage that jaxb or xmlbeans can't nicely handle. I am curious to know more details about this use case about transfering Map Of Maps or Map of Collections. Could you please paste a test case or some code snippet to have a look ? Thanks, Jim On Mon, Apr 29, 2024 at 5:46 PM Vassilis Virvilis wrote: I am using it. Although I plan to move to JAX-RS. However, I can't be sure about the scheduling... Aegis is the simplest and most versatile databinding for java first development in my opinion. The others (jax-ws, jaxb and xmlbeans) never worked for me when I had to transfer Map Of Maps or Map of Collections. I just wanted to give you my one datapoint. I understand that the developers will have to weigh carrying around a databinding vs its existing usage vs the development effort required. Vassilis On 4/22/24 6:06 AM, Jim Ma wrote: Hi all, I am not sure if it's the time to deprecate some old cxf things that no one is using, so I write to get your thoughts/ideas here. The first I can think of is aegis databinding. Is the aegis databinding still used by CXF users ? Is it a good time to deprecate and remove in the future release ? Thanks, Jim -- __ Vassilis Virvilis Ph.D. Head of IT Biovista Inc. Stay tuned www: http://www.biovista.com LinkedIn: https://www.linkedin.com/company/biovista Twitter: https://twitter.com/BiovistaInc/ Vizit https://twitter.com/BiovistaVizit/ Facebook: https://www.facebook.com/biovistainc Vizit (research): https://www.facebook.com/BiovistaVizit YouTube: https://www.youtube.com/user/BiovistaInc -- US Offices 2421 Ivy Road Charlottesville, VA 22903 USA T: +1.434.971.1141 F: +1.434.971.1144 European Offices 34 Rodopoleos Street Ellinikon, Athens 16777 GREECE T: +30.210.9629848 F: +30.210.9647606 Biovista is a privately held biotechnology company that finds novel uses for existing drugs, and profiles their side effects using their mechanism of action. Biovista develops its own pipeline of drugs in CNS, oncology, auto-immune and rare diseases. Biovista is collaborating with biopharmaceutical companies on indication expansion and de-risking of their portfolios and with the FDA on adverse event prediction. -- __ Vassilis Virvilis Ph.D. Head of IT Biovista Inc. Stay tuned www: http://www.biovista.com LinkedIn: https://www.linkedin.com/company/biovista Twitter: https://twitter.com/BiovistaInc/ Vizit https://twitter.com/BiovistaVizit/ Facebook: https://www.facebook.com/biovistainc Vizit (research): https://www.facebook.com/BiovistaVizit YouTube: https://www.youtube.com/user/BiovistaInc -- US Offices 2421 Ivy Road Charlottesville, VA 22903 USA T: +1.434.971.1141 F: +1.434.971.1144 European Offices 34 Rodopoleos Street Ellinikon, Athens 16777 GREECE T: +30.210.9629848 F: +30.210.9647606 Biovista is a privately held biotechnology company that finds novel uses for existing drugs, and profiles their side effects using their mechanism of action. Biovista develops its own pipeline of drugs in CNS, oncology, auto-immune and rare diseases. Biovista is collaborating with biopharmaceutical companies on indication expansion and de-risking of their portfolios and with the FDA on adverse event prediction.