Change Jaxb Generated File Encoding Per project (non maven) in Netbeans











up vote
0
down vote

favorite












I have the following issue:



I have a non maven project in NetBeans 8.2 wich has utf-8 encoding



(as shown with - right click on projetct properties).



In project I have created JaxB xml bindig and so some sources are generatd in generated folder.



However gerenreted sources are not using utf-8 and so I got




error: unmappable character for encoding UTF-8




if I try to complile.



If I chnage netbeans_default_options in (netbeans etcnetbeans.conf) so that it copntains the line -J-Dfile.encoding=UTF-8 the problem for the particular project is solved - everything compiles fine.



But this breaks the rest of my projects which are not utf-8.



I am looking for the solution that will not impact the rest of my projects.



Thanks.










share|improve this question




























    up vote
    0
    down vote

    favorite












    I have the following issue:



    I have a non maven project in NetBeans 8.2 wich has utf-8 encoding



    (as shown with - right click on projetct properties).



    In project I have created JaxB xml bindig and so some sources are generatd in generated folder.



    However gerenreted sources are not using utf-8 and so I got




    error: unmappable character for encoding UTF-8




    if I try to complile.



    If I chnage netbeans_default_options in (netbeans etcnetbeans.conf) so that it copntains the line -J-Dfile.encoding=UTF-8 the problem for the particular project is solved - everything compiles fine.



    But this breaks the rest of my projects which are not utf-8.



    I am looking for the solution that will not impact the rest of my projects.



    Thanks.










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have the following issue:



      I have a non maven project in NetBeans 8.2 wich has utf-8 encoding



      (as shown with - right click on projetct properties).



      In project I have created JaxB xml bindig and so some sources are generatd in generated folder.



      However gerenreted sources are not using utf-8 and so I got




      error: unmappable character for encoding UTF-8




      if I try to complile.



      If I chnage netbeans_default_options in (netbeans etcnetbeans.conf) so that it copntains the line -J-Dfile.encoding=UTF-8 the problem for the particular project is solved - everything compiles fine.



      But this breaks the rest of my projects which are not utf-8.



      I am looking for the solution that will not impact the rest of my projects.



      Thanks.










      share|improve this question















      I have the following issue:



      I have a non maven project in NetBeans 8.2 wich has utf-8 encoding



      (as shown with - right click on projetct properties).



      In project I have created JaxB xml bindig and so some sources are generatd in generated folder.



      However gerenreted sources are not using utf-8 and so I got




      error: unmappable character for encoding UTF-8




      if I try to complile.



      If I chnage netbeans_default_options in (netbeans etcnetbeans.conf) so that it copntains the line -J-Dfile.encoding=UTF-8 the problem for the particular project is solved - everything compiles fine.



      But this breaks the rest of my projects which are not utf-8.



      I am looking for the solution that will not impact the rest of my projects.



      Thanks.







      java netbeans encoding ant jaxb






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 2 days ago

























      asked 2 days ago









      Plirkee

      2,5971723




      2,5971723
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          The solution was adding the following



          <arg value="-encoding"/>
          <arg value="UTF-8"/>


          into the ant script
          inside
          xml_binding_build



          so that the resulting xjc would look like this



          <xjc package="mypackage" destdir="build/generated/jaxbCache/mypackage" catalog="catalog.xml">
          <classpath>
          <pathelement location="${src.dir}"/>
          <pathelement path="${jaxbwiz.xjcrun.classpath}"/>
          </classpath>
          <arg value="-xmlschema"/>
          <arg value="-encoding"/>
          <arg value="UTF-8"/>
          <schema file="xml-resources/jaxb/mypackage/mypackage.xsd"/>
          <depends file="xml-resources/jaxb/mypackage/mypackage.xsd"/>
          <produces dir="build/generated/jaxbCache/mypackage"/>
          </xjc>


          Ofcourse the xml_binding_build.xml is generated (automatically) and normally should not be edited by hand.



          However this workatround is enough for me and it is better than converting every project to utf-8.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53373173%2fchange-jaxb-generated-file-encoding-per-project-non-maven-in-netbeans%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            The solution was adding the following



            <arg value="-encoding"/>
            <arg value="UTF-8"/>


            into the ant script
            inside
            xml_binding_build



            so that the resulting xjc would look like this



            <xjc package="mypackage" destdir="build/generated/jaxbCache/mypackage" catalog="catalog.xml">
            <classpath>
            <pathelement location="${src.dir}"/>
            <pathelement path="${jaxbwiz.xjcrun.classpath}"/>
            </classpath>
            <arg value="-xmlschema"/>
            <arg value="-encoding"/>
            <arg value="UTF-8"/>
            <schema file="xml-resources/jaxb/mypackage/mypackage.xsd"/>
            <depends file="xml-resources/jaxb/mypackage/mypackage.xsd"/>
            <produces dir="build/generated/jaxbCache/mypackage"/>
            </xjc>


            Ofcourse the xml_binding_build.xml is generated (automatically) and normally should not be edited by hand.



            However this workatround is enough for me and it is better than converting every project to utf-8.






            share|improve this answer

























              up vote
              0
              down vote













              The solution was adding the following



              <arg value="-encoding"/>
              <arg value="UTF-8"/>


              into the ant script
              inside
              xml_binding_build



              so that the resulting xjc would look like this



              <xjc package="mypackage" destdir="build/generated/jaxbCache/mypackage" catalog="catalog.xml">
              <classpath>
              <pathelement location="${src.dir}"/>
              <pathelement path="${jaxbwiz.xjcrun.classpath}"/>
              </classpath>
              <arg value="-xmlschema"/>
              <arg value="-encoding"/>
              <arg value="UTF-8"/>
              <schema file="xml-resources/jaxb/mypackage/mypackage.xsd"/>
              <depends file="xml-resources/jaxb/mypackage/mypackage.xsd"/>
              <produces dir="build/generated/jaxbCache/mypackage"/>
              </xjc>


              Ofcourse the xml_binding_build.xml is generated (automatically) and normally should not be edited by hand.



              However this workatround is enough for me and it is better than converting every project to utf-8.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                The solution was adding the following



                <arg value="-encoding"/>
                <arg value="UTF-8"/>


                into the ant script
                inside
                xml_binding_build



                so that the resulting xjc would look like this



                <xjc package="mypackage" destdir="build/generated/jaxbCache/mypackage" catalog="catalog.xml">
                <classpath>
                <pathelement location="${src.dir}"/>
                <pathelement path="${jaxbwiz.xjcrun.classpath}"/>
                </classpath>
                <arg value="-xmlschema"/>
                <arg value="-encoding"/>
                <arg value="UTF-8"/>
                <schema file="xml-resources/jaxb/mypackage/mypackage.xsd"/>
                <depends file="xml-resources/jaxb/mypackage/mypackage.xsd"/>
                <produces dir="build/generated/jaxbCache/mypackage"/>
                </xjc>


                Ofcourse the xml_binding_build.xml is generated (automatically) and normally should not be edited by hand.



                However this workatround is enough for me and it is better than converting every project to utf-8.






                share|improve this answer












                The solution was adding the following



                <arg value="-encoding"/>
                <arg value="UTF-8"/>


                into the ant script
                inside
                xml_binding_build



                so that the resulting xjc would look like this



                <xjc package="mypackage" destdir="build/generated/jaxbCache/mypackage" catalog="catalog.xml">
                <classpath>
                <pathelement location="${src.dir}"/>
                <pathelement path="${jaxbwiz.xjcrun.classpath}"/>
                </classpath>
                <arg value="-xmlschema"/>
                <arg value="-encoding"/>
                <arg value="UTF-8"/>
                <schema file="xml-resources/jaxb/mypackage/mypackage.xsd"/>
                <depends file="xml-resources/jaxb/mypackage/mypackage.xsd"/>
                <produces dir="build/generated/jaxbCache/mypackage"/>
                </xjc>


                Ofcourse the xml_binding_build.xml is generated (automatically) and normally should not be edited by hand.



                However this workatround is enough for me and it is better than converting every project to utf-8.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 2 days ago









                Plirkee

                2,5971723




                2,5971723






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53373173%2fchange-jaxb-generated-file-encoding-per-project-non-maven-in-netbeans%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

                    SQL update select statement

                    WPF add header to Image with URL pettitions [duplicate]