7 Replies Latest reply on Jun 3, 2008 9:10 AM by Jonathan Halliday

    XTS + txbridge licensing

    Rob Barnes Newbie

      Currently we have a closed source J2EE appliaction which runs on the 'community' (for want of a better word) version of JBoss.

      If we decided to use XTS as our part of our solution on the community version of jboss, how does this affect our J2EE application?

      Would we have to make the J2EE application open source?

      Or would we only have to publish any changes we have to make to XTS?

      Or would our application have to become open source unless we paid for an EAP support contract?

        • 1. Re: XTS + txbridge licensing
          Jonathan Halliday Master

          [ I'm not a lawyer. This is not an official Red Hat statement. etc, etc ]

          GPL is viral, so you would have to release your app source as well as any XTS changes.

          The EAP subscription thing is a red herring, since XTS is not yet part of the platform anyhow.

          • 2. Re: XTS + txbridge licensing
            Rob Barnes Newbie

            So commercially, until this becomes part of the EAP, it cannot be used for a closed source secure proprietery application.

            When is the next release of the EAP scheduled? Is this likely within the next 6 months?

            Will the XTS code ever be relicenced unde rthe LGPL?

            • 3. Re: XTS + txbridge licensing
              Jonathan Halliday Master

              > So commercially, until this becomes part of the EAP, it cannot be used for a closed source secure proprietery application.

              correct

              > When is the next release of the EAP scheduled? Is this likely within the next 6 months?

              You want the official answer from product management or the one based on my opinion as a developer? :-)

              > Will the XTS code ever be relicenced unde rthe LGPL?

              Lets just say I'm currently looking for a tool that can do global search and replace on blocks of text across a source tree.

              • 4. Re: XTS + txbridge licensing
                Rob Barnes Newbie

                Well, both from a developer and from product management. :)

                At some point in the future we will need to make a decision to use this tech or not, but without a doubt we need to use WS-AT for .NET interop. It would be helpful to get a bit of a roadmap (no guarantees - I understand!)

                • 5. Re: XTS + txbridge licensing
                  Jonathan Halliday Master

                  > without a doubt we need to use WS-AT for .NET interop

                  Do you need 1.0 or 1.1 of the spec and do you have any preference or requirements with regard to the web services stack at the JBoss end?

                  • 6. Re: XTS + txbridge licensing
                    Rob Barnes Newbie

                    Not many preferences. We knocked up a proof of concept using the Bistro demo and a fairly vanilla JBoss 4.2.2, the XTS 4.2.3.SP7 libs for a transaction initiated by the MS DTC, I assume this was using JbossWS. Fow now, this met our requirements for simple atomic transactions across web service calls.

                    We don't anticipate doing anything more complex in this regard.

                    • 7. Re: XTS + txbridge licensing
                      Jonathan Halliday Master

                      Hmm well in that case you should probably be ok running on JBossAS 5.0 in a six month timeframe, but I'd allow a bit of extra time if you need the EAP 5.0 i.e. a support agreement, which you probably do in order to pass on that level of assurance to your own customers.