[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
[ https://jira.codehaus.org/browse/JIBX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=287706#comment-287706 ] Malachi de AElfweald commented on JIBX-471: --- Looks like that worked. I'll attach the assembly file that worked. As a side note, the dependencies to use it now look like: dependency groupIdnet.goldenspiral.eitr/groupId artifactIdEitr/artifactId version1.0-SNAPSHOT/version typeapklib/type /dependency dependency groupIdnet.goldenspiral.eitr/groupId artifactIdEitr/artifactId version1.0-SNAPSHOT/version typejar/type classifierbinding/classifier /dependency Compatability with apklib? -- Key: JIBX-471 URL: https://jira.codehaus.org/browse/JIBX-471 Project: JiBX Issue Type: Improvement Components: maven plugin Affects Versions: JiBX 1.2.3 Reporter: Malachi de AElfweald Assignee: Don Corley Priority: Minor Attachments: eitr.zip I am trying to define the schema (using the schema-codegen) in an apklib module (using maven-android-plugin). The resulting apklib does not contain any of the auto-generated code. As a result, the actual APK can not access any of the pre-generated source. And since the apklib is not extracted, it isn't re-generatating the source. I tried attaching both the jar and the apklib, but that caused loads of problems. Tried excluding many of the transitive dependencies, but no luck. Ideal solution: apklib contains the autogenerated *.java (including JiBX_binding*.java) so that it will recompile in the Android APK or, still acceptable plugin is able to generate and bind to XSDs contained in the apklib -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
[ https://jira.codehaus.org/browse/JIBX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malachi de AElfweald updated JIBX-471: -- Attachment: binding.xml attaching assembly 'binding.xml' file Compatability with apklib? -- Key: JIBX-471 URL: https://jira.codehaus.org/browse/JIBX-471 Project: JiBX Issue Type: Improvement Components: maven plugin Affects Versions: JiBX 1.2.3 Reporter: Malachi de AElfweald Assignee: Don Corley Priority: Minor Attachments: binding.xml, eitr.zip I am trying to define the schema (using the schema-codegen) in an apklib module (using maven-android-plugin). The resulting apklib does not contain any of the auto-generated code. As a result, the actual APK can not access any of the pre-generated source. And since the apklib is not extracted, it isn't re-generatating the source. I tried attaching both the jar and the apklib, but that caused loads of problems. Tried excluding many of the transitive dependencies, but no luck. Ideal solution: apklib contains the autogenerated *.java (including JiBX_binding*.java) so that it will recompile in the Android APK or, still acceptable plugin is able to generate and bind to XSDs contained in the apklib -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
[ https://jira.codehaus.org/browse/JIBX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malachi de AElfweald resolved JIBX-471. --- Resolution: Not A Bug workaround found Compatability with apklib? -- Key: JIBX-471 URL: https://jira.codehaus.org/browse/JIBX-471 Project: JiBX Issue Type: Improvement Components: maven plugin Affects Versions: JiBX 1.2.3 Reporter: Malachi de AElfweald Assignee: Don Corley Priority: Minor Attachments: binding.xml, eitr.zip I am trying to define the schema (using the schema-codegen) in an apklib module (using maven-android-plugin). The resulting apklib does not contain any of the auto-generated code. As a result, the actual APK can not access any of the pre-generated source. And since the apklib is not extracted, it isn't re-generatating the source. I tried attaching both the jar and the apklib, but that caused loads of problems. Tried excluding many of the transitive dependencies, but no luck. Ideal solution: apklib contains the autogenerated *.java (including JiBX_binding*.java) so that it will recompile in the Android APK or, still acceptable plugin is able to generate and bind to XSDs contained in the apklib -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
[ https://jira.codehaus.org/browse/JIBX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=287718#comment-287718 ] Don Corley commented on JIBX-471: - Nice! Don Compatability with apklib? -- Key: JIBX-471 URL: https://jira.codehaus.org/browse/JIBX-471 Project: JiBX Issue Type: Improvement Components: maven plugin Affects Versions: JiBX 1.2.3 Reporter: Malachi de AElfweald Assignee: Don Corley Priority: Minor Attachments: binding.xml, eitr.zip I am trying to define the schema (using the schema-codegen) in an apklib module (using maven-android-plugin). The resulting apklib does not contain any of the auto-generated code. As a result, the actual APK can not access any of the pre-generated source. And since the apklib is not extracted, it isn't re-generatating the source. I tried attaching both the jar and the apklib, but that caused loads of problems. Tried excluding many of the transitive dependencies, but no luck. Ideal solution: apklib contains the autogenerated *.java (including JiBX_binding*.java) so that it will recompile in the Android APK or, still acceptable plugin is able to generate and bind to XSDs contained in the apklib -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
[ https://jira.codehaus.org/browse/JIBX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=287415#comment-287415 ] Malachi de AElfweald commented on JIBX-471: --- Hi Don, I am not sure I completely follow. I realize that I can use JiBX as a jar dependency. Unfortunately, that does not allow for any Android resources to be included. IE: In order to use R.id.something (or in my case R.raw.xsdname and R.raw.xmlname) it has to be an apklib project, not a jar project. Android library projects do not include *.class, only source files which get recompiled in the APK (http://developer.android.com/guide/developing/projects/index.html). I do have a bug opened with the maven-android-plugin team as well http://code.google.com/p/maven-android-plugin/issues/detail?id=235 I looked at the jibxapp example, and I do not believe that does what I am trying to do (ie: Isolate the XML, XSD, XML Management code, etc) since all the logic is embedded in the APK itself. I'd like to keep this open while we try to find a solution that works. If we could autogenerate the source for the binding classes (not just the class files), maybe we put the source files in the apklib and then a standard compile in the APK would compile them as well? Compatability with apklib? -- Key: JIBX-471 URL: https://jira.codehaus.org/browse/JIBX-471 Project: JiBX Issue Type: Improvement Components: maven plugin Affects Versions: JiBX 1.2.3 Reporter: Malachi de AElfweald Assignee: Don Corley Priority: Minor Attachments: eitr.zip I am trying to define the schema (using the schema-codegen) in an apklib module (using maven-android-plugin). The resulting apklib does not contain any of the auto-generated code. As a result, the actual APK can not access any of the pre-generated source. And since the apklib is not extracted, it isn't re-generatating the source. I tried attaching both the jar and the apklib, but that caused loads of problems. Tried excluding many of the transitive dependencies, but no luck. Ideal solution: apklib contains the autogenerated *.java (including JiBX_binding*.java) so that it will recompile in the Android APK or, still acceptable plugin is able to generate and bind to XSDs contained in the apklib -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
[ https://jira.codehaus.org/browse/JIBX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=287480#comment-287480 ] Don Corley commented on JIBX-471: - Malachi, Generating the source for the binding classes would not work, because the class files have to be modified by the JiBX binding processor before they are converted to dex files. Maybe you can separate the class and resource files, ie., include a pre-processed jar file AND a separate apklib file with the schema, etc. I'll be interested in how you solve this! Good Luck! Don Compatability with apklib? -- Key: JIBX-471 URL: https://jira.codehaus.org/browse/JIBX-471 Project: JiBX Issue Type: Improvement Components: maven plugin Affects Versions: JiBX 1.2.3 Reporter: Malachi de AElfweald Assignee: Don Corley Priority: Minor Attachments: eitr.zip I am trying to define the schema (using the schema-codegen) in an apklib module (using maven-android-plugin). The resulting apklib does not contain any of the auto-generated code. As a result, the actual APK can not access any of the pre-generated source. And since the apklib is not extracted, it isn't re-generatating the source. I tried attaching both the jar and the apklib, but that caused loads of problems. Tried excluding many of the transitive dependencies, but no luck. Ideal solution: apklib contains the autogenerated *.java (including JiBX_binding*.java) so that it will recompile in the Android APK or, still acceptable plugin is able to generate and bind to XSDs contained in the apklib -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
[ https://jira.codehaus.org/browse/JIBX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=287247#comment-287247 ] Don Corley commented on JIBX-471: - Malachi, Yikes, this is a tough one. Your pom is very complicated. The apklib goal must be new, because I couldn't find any examples and the documentation is very brief. It looks to me that an apklib packages the raw resources such as source files, images, etc. This will not work with jibx, since you need to include the jibx-processed class files. You have a few alternative solutions: 1. Use your Eitr-1.0-SNAPSHOT.jar. Is is a valid Android library project with valid jibx class files. 2. Bind your schema using the standard jibx-maven-plugin as a separate project and include it in your android project. Your class files will be converted to .dex files on the android package phase. You can find a nice example of this in our source repository at: https://github.com/jibx/schema-library/tree/master/schema-utilities/examples/android/jibxapp 3. You may want to get some help from the apklib authors. jibx is running correctly. Please close this bug when you get a chance. Good Luck! Don Compatability with apklib? -- Key: JIBX-471 URL: https://jira.codehaus.org/browse/JIBX-471 Project: JiBX Issue Type: Improvement Components: maven plugin Affects Versions: JiBX 1.2.3 Reporter: Malachi de AElfweald Assignee: Don Corley Priority: Minor Attachments: eitr.zip I am trying to define the schema (using the schema-codegen) in an apklib module (using maven-android-plugin). The resulting apklib does not contain any of the auto-generated code. As a result, the actual APK can not access any of the pre-generated source. And since the apklib is not extracted, it isn't re-generatating the source. I tried attaching both the jar and the apklib, but that caused loads of problems. Tried excluding many of the transitive dependencies, but no luck. Ideal solution: apklib contains the autogenerated *.java (including JiBX_binding*.java) so that it will recompile in the Android APK or, still acceptable plugin is able to generate and bind to XSDs contained in the apklib -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
Malachi de AElfweald created JIBX-471: - Summary: Compatability with apklib? Key: JIBX-471 URL: https://jira.codehaus.org/browse/JIBX-471 Project: JiBX Issue Type: Improvement Components: maven plugin Affects Versions: JiBX 1.2.3 Reporter: Malachi de AElfweald Priority: Minor I am trying to define the schema (using the schema-codegen) in an apklib module (using maven-android-plugin). The resulting apklib does not contain any of the auto-generated code. As a result, the actual APK can not access any of the pre-generated source. And since the apklib is not extracted, it isn't re-generatating the source. I tried attaching both the jar and the apklib, but that caused loads of problems. Tried excluding many of the transitive dependencies, but no luck. Ideal solution: apklib contains the autogenerated *.java (including JiBX_binding*.java) so that it will recompile in the Android APK or, still acceptable plugin is able to generate and bind to XSDs contained in the apklib -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
[ https://jira.codehaus.org/browse/JIBX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Corley reassigned JIBX-471: --- Assignee: Don Corley Compatability with apklib? -- Key: JIBX-471 URL: https://jira.codehaus.org/browse/JIBX-471 Project: JiBX Issue Type: Improvement Components: maven plugin Affects Versions: JiBX 1.2.3 Reporter: Malachi de AElfweald Assignee: Don Corley Priority: Minor I am trying to define the schema (using the schema-codegen) in an apklib module (using maven-android-plugin). The resulting apklib does not contain any of the auto-generated code. As a result, the actual APK can not access any of the pre-generated source. And since the apklib is not extracted, it isn't re-generatating the source. I tried attaching both the jar and the apklib, but that caused loads of problems. Tried excluding many of the transitive dependencies, but no luck. Ideal solution: apklib contains the autogenerated *.java (including JiBX_binding*.java) so that it will recompile in the Android APK or, still acceptable plugin is able to generate and bind to XSDs contained in the apklib -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
[ https://jira.codehaus.org/browse/JIBX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=287021#comment-287021 ] Don Corley commented on JIBX-471: - Malachi, Can you (zip and) attach your project to this issue. I need to recreate the bug before I can figure out a solution. Thanks, Don Compatability with apklib? -- Key: JIBX-471 URL: https://jira.codehaus.org/browse/JIBX-471 Project: JiBX Issue Type: Improvement Components: maven plugin Affects Versions: JiBX 1.2.3 Reporter: Malachi de AElfweald Assignee: Don Corley Priority: Minor I am trying to define the schema (using the schema-codegen) in an apklib module (using maven-android-plugin). The resulting apklib does not contain any of the auto-generated code. As a result, the actual APK can not access any of the pre-generated source. And since the apklib is not extracted, it isn't re-generatating the source. I tried attaching both the jar and the apklib, but that caused loads of problems. Tried excluding many of the transitive dependencies, but no luck. Ideal solution: apklib contains the autogenerated *.java (including JiBX_binding*.java) so that it will recompile in the Android APK or, still acceptable plugin is able to generate and bind to XSDs contained in the apklib -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
[ https://jira.codehaus.org/browse/JIBX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=287041#comment-287041 ] Malachi de AElfweald commented on JIBX-471: --- I was just trying to do http://jibx.sourceforge.net/fromcode/bindgen-example3.html as an apklib Specifically, I created an apklib (http://code.google.com/p/maven-android-plugin/wiki/ApkLib) with the xsd on your example then tried to put your test xml in the APK itself. If you do a JAR project, then the generated classes are there. If you do an APKLIB project, then the generated sources are not there. Maybe this is the wrong approach? I am just trying to figure out the correct way to use JiBX with APKLIB? I'll attach the zip (without the keystore,proguard,hg,etc) Compatability with apklib? -- Key: JIBX-471 URL: https://jira.codehaus.org/browse/JIBX-471 Project: JiBX Issue Type: Improvement Components: maven plugin Affects Versions: JiBX 1.2.3 Reporter: Malachi de AElfweald Assignee: Don Corley Priority: Minor Attachments: eitr.zip I am trying to define the schema (using the schema-codegen) in an apklib module (using maven-android-plugin). The resulting apklib does not contain any of the auto-generated code. As a result, the actual APK can not access any of the pre-generated source. And since the apklib is not extracted, it isn't re-generatating the source. I tried attaching both the jar and the apklib, but that caused loads of problems. Tried excluding many of the transitive dependencies, but no luck. Ideal solution: apklib contains the autogenerated *.java (including JiBX_binding*.java) so that it will recompile in the Android APK or, still acceptable plugin is able to generate and bind to XSDs contained in the apklib -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
[ https://jira.codehaus.org/browse/JIBX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malachi de AElfweald updated JIBX-471: -- Attachment: eitr.zip trying to use jibx inside an apklib Compatability with apklib? -- Key: JIBX-471 URL: https://jira.codehaus.org/browse/JIBX-471 Project: JiBX Issue Type: Improvement Components: maven plugin Affects Versions: JiBX 1.2.3 Reporter: Malachi de AElfweald Assignee: Don Corley Priority: Minor Attachments: eitr.zip I am trying to define the schema (using the schema-codegen) in an apklib module (using maven-android-plugin). The resulting apklib does not contain any of the auto-generated code. As a result, the actual APK can not access any of the pre-generated source. And since the apklib is not extracted, it isn't re-generatating the source. I tried attaching both the jar and the apklib, but that caused loads of problems. Tried excluding many of the transitive dependencies, but no luck. Ideal solution: apklib contains the autogenerated *.java (including JiBX_binding*.java) so that it will recompile in the Android APK or, still acceptable plugin is able to generate and bind to XSDs contained in the apklib -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
