[jibx-devs] [jira] (JIBX-471) Compatability with apklib?

2012-01-04 Thread Malachi de AElfweald (JIRA)

[ 
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?

2012-01-04 Thread Don Corley (JIRA)

[ 
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