[jibx-devs] [jira] (JIBX-496) JiBX 1.2.5 eclipse plugin contains old version string
Don Corley resolved JIBX-496 as Fixed JiBX 1.2.5 eclipse plugin contains old version string Thanks for fixing this Mike! Change By: Don Corley (24/Mar/13 3:21 AM) Resolution: Fixed Fix Version/s: JiBX 1.2.5 Status: Open Resolved This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-489) Support m2e 1.2
Don Corley commented on JIBX-489 Support m2e 1.2 Julian, I updated the plugin at the same time another plugin was installed, so my plugin got deleted. Try again, I fixed it now. Don This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-465) JiBX core needs to be tested with jdk1.7
Don Corley closed JIBX-465 as Fixed JiBX core needs to be tested with jdk1.7 1.2.5 is now available for download on sourceforge. 1.2.5 is now available in maven central. Eclipse plugin available soon. Change By: Don Corley (08/Mar/13 1:05 PM) Resolution: Fixed Fix Version/s: JiBX 1.2.5 Status: Open Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-489) Support m2e 1.2
Don Corley resolved JIBX-489 as Fixed Support m2e 1.2 The eclipse m2e connector has been updated to work with m2e versions 1.2+. The connector is now available at the jibx eclipse update site: http://jibx.sourceforge.net/eclipse Change By: Don Corley (04/Mar/13 10:11 AM) Resolution: Fixed Fix Version/s: JiBX 1.2.5 Status: Open Resolved This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-494) Add opentravel version 2012B to schema-library
Don Corley resolved JIBX-494 as Fixed Add opentravel version 2012B to schema-library 2012B message support added Change By: Don Corley (14/Feb/13 2:30 PM) Resolution: Fixed Status: Open Resolved This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-494) Add opentravel version 2012B to schema-library
Don Corley created JIBX-494 Add opentravel version 2012B to schema-library Issue Type: Bug Assignee: Unassigned Created: 31/Jan/13 1:23 PM Description: Add opentravel version 2012B to schema-library and push to the maven repo Project: JiBX Priority: Major Reporter: Don Corley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-493) Change JiBX databinding class to CXF version
Don Corley resolved JIBX-493 as Fixed Change JiBX databinding class to CXF version Replaced databinding with cxf build-in version 5abe0d06ba7823aeb9b8ba90a835a2627098a689 Change By: Don Corley (31/Jan/13 1:21 PM) Resolution: Fixed Status: Open Resolved This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-493) Change JiBX databinding class to CXF version
Don Corley created JIBX-493 Change JiBX databinding class to CXF version Issue Type: Bug Assignee: Don Corley Components: maven plugin Created: 30/Jan/13 5:13 PM Description: Now that the JiBX databinding module is included with CXF, remove the JiBX databinding module from all rest and soap service modules. Due Date: 31/Jan/13 12:00 AM Project: JiBX Priority: Minor Reporter: Don Corley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-490) jibx-maven-plugin should be threadsafe
Don Corley assigned JIBX-490 to Don Corley jibx-maven-plugin should be threadsafe Change By: Don Corley (09/Jan/13 1:50 AM) Assignee: Don Corley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-489) Support m2e 1.2
Don Corley assigned JIBX-489 to Don Corley Support m2e 1.2 Change By: Don Corley (12/Dec/12 4:29 AM) Assignee: Don Corley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-488) While unmarshiling this tag 2012-11-07T10:26:15, the datetime is converting into ist however the application is on box which is on bst time..
Don Corley commented on JIBX-488 While unmarshiling this tag 2012-11-07T10:26:15, the datetime is converting into ist however the application is on box which is on bst time.. Lookman, The problem you have is in your schema definition, not JiBX. Typically, the schema definition will include the GMT offset. For example, TimeStamp="2008-09-02T03:52:40.327-07:00" is how you would specify a time using the opentravel schema. Note the time zone information at the end. If your schema requires the IST time zone, you will have to manually convert the time in your application before setting or retrieving it from your schema. Please close this bug. Thanks, Don This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-484) JiBX doesn't work with collection for Flexible="true"
Don Corley resolved JIBX-484 as Fixed JiBX doesn't work with collection for Flexible="true" Ankur, Thanks for the fix! Change By: Don Corley (05/Oct/12 8:42 AM) Resolution: Fixed Status: Open Resolved This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-311) maven-jibx-plugin 1.2 Binding Error due to issue with Value Object
Don Corley commented on JIBX-311 maven-jibx-plugin 1.2 Binding Error due to issue with Value Object Bruce, Have you tried this with the current version of JiBX? Don This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-482) Eclipse plugin ignores jibx-maven-plugin schema binding settings
Don Corley commented on JIBX-482 Eclipse plugin ignores jibx-maven-plugin schema binding settings Oliver, Remember, the eclipse plugin is totally separate from the maven plugin. The eclipse plugin is meant to run against an eclipse project. If you try to configure the JiBX eclipse plugin with this maven project file you will be running JiBX twice. This example should be run under eclipse with the m2eclipse plugin and the JiBX m2e connector installed. >From eclipse, turn OFF the JiBX eclipse plugin and try selecting run -> maven install. This should build your project correctly. Sorry it took so long to respond, but I handle the maven plugin and you classified this as an eclipse plugin issue. Don This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-483) Inheritance fails to correctly bind when working with precompiled bindings
Don Corley commented on JIBX-483 Inheritance fails to correctly bind when working with precompiled bindings Rajeev, Why don't you make your life easier and use maven for you multi-schema project. Maven handles this problem easily. Take a look at this sample multi-schema project: https://github.com/jibx/maven-plugin/tree/master/test-suite/base-binding-test This project has three schemas: person <- address <- company and a simple marshal/unmarshal example. Please close this bug if this solves your problem. Don This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-478) Support m2e 1.1
Don Corley resolved JIBX-478 as Fixed Support m2e 1.1 eclipse Juno users! The m2e version 1.1 connector for JiBX is now available at our plugin site: http://jibx.sourceforge.net/eclipse/ Don Change By: Don Corley (13/Jul/12 6:47 PM) Resolution: Fixed Fix Version/s: JiBX 1.2.4 Status: Open Resolved This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-416) Plugin dependency resolving fails
Don Corley commented on JIBX-416 Plugin dependency resolving fails Benoît, Yes JiBX uses some eclipse jars. We upgraded to the latest eclipse versions and made sure they were in maven central. Are you having any problems? Don This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-434) JiBX does not generate Java from XSD files with correct encoding
[
https://jira.codehaus.org/browse/JIBX-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298991#comment-298991
]
Don Corley commented on JIBX-434:
-
Christian,
I created a git branch that should fix this problem.
Can you please test it to make sure it works.
I deployed this fix to maven central using an non-release version number.
Please update your poms to version 1.2.4.3 as follows:
org.jibx
jibx-run
1.2.4.3
-and-
org.jibx
jibx-maven-plugin
1.2.4.3
...
Tell me (and close this bug) if this works for you.
Dennis - Can you do a code review for me (one simple change):
https://github.com/jibx/core/compare/master...utf8
Thanks,
Don
> JiBX does not generate Java from XSD files with correct encoding
> -
>
> Key: JIBX-434
> URL: https://jira.codehaus.org/browse/JIBX-434
> Project: JiBX
> Issue Type: Bug
> Components: CodeGen
>Affects Versions: JiBX 1.2.2
> Environment: Windows Server 2008 R2
>Reporter: Christian Callsen
>Assignee: Don Corley
>
> Per email conversation (see bottom for request to file bug here):
> ---
> Hello there,
> I have several XSD files with danish national characters in it that I include
> in my own XSD file (here's one of them:
> http://rep.oio.dk/ebxml/xml/schemas/dkcc/2003/02/13/DKCC_CountryIdentificationCode.xsd).
>
> When the JiBX CodeGen tool v1.2.2 runs on it (from maven via
> maven-jibx-plugin v1.2.2) the output file is not UTF-8 even though I've set
> project.build.outputEncoding to UTF-8. I've checked the source, and the
> SourceBuilder.java line 325 seems suspicious:
> FileWriter fwrit = new FileWriter(file);
> According to the maven plugin guide, one needs to be careful around
> FileWriter instantiation and file encodings. Would it be possible to respect
> the maven-requested encoding or by adding a flag to control the encoding
> written to the file?
> I've tried setting file.encoding and project.build.sourceEncoding in pom.xml,
> and supplied -Dfile.encoding=UTF-8. No luck. I've tried turning off javadoc
> and annotations via:
> false
> false
> in pom.xml. Still no luck.
> Any pointers/workarounds?
> ---
> Hi Christian,
> Don is handling all the Maven issue for JiBX, so hopefully he can comment on
> this.
> Sorry for the delay in responding to this. In general, it's best to ask this
> type of question on the JiBX users list (or enter a Jira bug report).
> - Dennis
> ---
> Christian,
> I tried generating code for this schema and all the special characters look
> fine. I have attached the generated java source files.
> You may want to check your default java encoding. Here is a great article:
> http://stackoverflow.com/questions/361975/setting-the-default-java-character-encoding
> If you can supply a schema definition that is not generating code correctly,
> that would be a great help.
> Don
> ---
> Hey Don,
> My problem could be that I'm running this under Windows Server 2008, in
> CP1252 locale. Which locale and OS did you try out the test on? I'm attaching
> a ZIP of the generated sources I get. Notice the generated class
> _CountryIdentificationSchemeType.java - there are comments that contain
> danish national characters, but the file's not in UTF-8 encoding :-(
> according to Notepad++ (it says ANSI).
> Below's a snippet from pom.xml, showing you how I invoke the
> maven-jibx-plugin.
>
> org.jibx
> maven-jibx-plugin
> ${jibx.plugin.version}
>
>
> target/generated-sources/src/main/java/
>
> binding.xml
>
> true
> false
>
>
>
>
> generate-java-code-from-schema
> generate-sources
>
>
> schema-codegen
>
>
>
> ${generated.sources.directory}
>
> ${webapp.directory}/WEB-INF/xsd
> true
>
>
[jibx-devs] [jira] (JIBX-434) JiBX does not generate Java from XSD files with correct encoding
[
https://jira.codehaus.org/browse/JIBX-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley reassigned JIBX-434:
---
Assignee: Don Corley
> JiBX does not generate Java from XSD files with correct encoding
> -
>
> Key: JIBX-434
> URL: https://jira.codehaus.org/browse/JIBX-434
> Project: JiBX
> Issue Type: Bug
> Components: CodeGen
>Affects Versions: JiBX 1.2.2
> Environment: Windows Server 2008 R2
>Reporter: Christian Callsen
>Assignee: Don Corley
>
> Per email conversation (see bottom for request to file bug here):
> ---
> Hello there,
> I have several XSD files with danish national characters in it that I include
> in my own XSD file (here's one of them:
> http://rep.oio.dk/ebxml/xml/schemas/dkcc/2003/02/13/DKCC_CountryIdentificationCode.xsd).
>
> When the JiBX CodeGen tool v1.2.2 runs on it (from maven via
> maven-jibx-plugin v1.2.2) the output file is not UTF-8 even though I've set
> project.build.outputEncoding to UTF-8. I've checked the source, and the
> SourceBuilder.java line 325 seems suspicious:
> FileWriter fwrit = new FileWriter(file);
> According to the maven plugin guide, one needs to be careful around
> FileWriter instantiation and file encodings. Would it be possible to respect
> the maven-requested encoding or by adding a flag to control the encoding
> written to the file?
> I've tried setting file.encoding and project.build.sourceEncoding in pom.xml,
> and supplied -Dfile.encoding=UTF-8. No luck. I've tried turning off javadoc
> and annotations via:
> false
> false
> in pom.xml. Still no luck.
> Any pointers/workarounds?
> ---
> Hi Christian,
> Don is handling all the Maven issue for JiBX, so hopefully he can comment on
> this.
> Sorry for the delay in responding to this. In general, it's best to ask this
> type of question on the JiBX users list (or enter a Jira bug report).
> - Dennis
> ---
> Christian,
> I tried generating code for this schema and all the special characters look
> fine. I have attached the generated java source files.
> You may want to check your default java encoding. Here is a great article:
> http://stackoverflow.com/questions/361975/setting-the-default-java-character-encoding
> If you can supply a schema definition that is not generating code correctly,
> that would be a great help.
> Don
> ---
> Hey Don,
> My problem could be that I'm running this under Windows Server 2008, in
> CP1252 locale. Which locale and OS did you try out the test on? I'm attaching
> a ZIP of the generated sources I get. Notice the generated class
> _CountryIdentificationSchemeType.java - there are comments that contain
> danish national characters, but the file's not in UTF-8 encoding :-(
> according to Notepad++ (it says ANSI).
> Below's a snippet from pom.xml, showing you how I invoke the
> maven-jibx-plugin.
>
> org.jibx
> maven-jibx-plugin
> ${jibx.plugin.version}
>
>
> target/generated-sources/src/main/java/
>
> binding.xml
>
> true
> false
>
>
>
>
> generate-java-code-from-schema
> generate-sources
>
>
> schema-codegen
>
>
>
> ${generated.sources.directory}
>
> ${webapp.directory}/WEB-INF/xsd
> true
>
>
> file.xsd
>
>
>
> test
>
> false
>
> false
>
>
>
>
>
[jibx-devs] [jira] (JIBX-480) Jibx Maven plugin version 1.2.4 is unusable due to SNAPSHOT dependencies in the release version
[
https://jira.codehaus.org/browse/JIBX-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-480.
-
Resolution: Fixed
Fix Version/s: JiBX 1.2.4
Use version 1.2.4.5 in your pom files:
org.jibx
jibx-run
1.2.4.5
-and-
org.jibx
jibx-maven-plugin
1.2.4.5
...
Don
> Jibx Maven plugin version 1.2.4 is unusable due to SNAPSHOT dependencies in
> the release version
> ---
>
> Key: JIBX-480
> URL: https://jira.codehaus.org/browse/JIBX-480
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Reporter: David Boden
>Assignee: Don Corley
>Priority: Blocker
> Fix For: JiBX 1.2.4
>
>
> Affects Version: 1.2.4 - I can't set this in Jira because this version number
> hasn't been setup by an administrator.
> The snapshot dependencies can be seen within the deployed pom:
> http://search.maven.org/remotecontent?filepath=org/jibx/maven-jibx-plugin/1.2.4/maven-jibx-plugin-1.2.4.pom
>
> ${project.groupId}
> jibx-tools
> 1.2.4-SNAPSHOT
>
>
> ${project.groupId}
> jibx-bind
> 1.2.4-SNAPSHOT
>
--
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
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-480) Jibx Maven plugin version 1.2.4 is unusable due to SNAPSHOT dependencies in the release version
[
https://jira.codehaus.org/browse/JIBX-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298350#comment-298350
]
Don Corley commented on JIBX-480:
-
Oh man, I can't believe this got through.
That's really strange!
I wonder why maven changed the other dependencies on release, but not these two.
Didn't catch this in my testing, since there is a valid 1.2.4-SNAPSHOT in the
maven snapshot repo.
Give me about a week to see if there are any other issues and I'll do another
release.
Thanks!
Don
> Jibx Maven plugin version 1.2.4 is unusable due to SNAPSHOT dependencies in
> the release version
> ---
>
> Key: JIBX-480
> URL: https://jira.codehaus.org/browse/JIBX-480
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Reporter: David Boden
>Assignee: Don Corley
>Priority: Blocker
>
> Affects Version: 1.2.4 - I can't set this in Jira because this version number
> hasn't been setup by an administrator.
> The snapshot dependencies can be seen within the deployed pom:
> http://search.maven.org/remotecontent?filepath=org/jibx/maven-jibx-plugin/1.2.4/maven-jibx-plugin-1.2.4.pom
>
> ${project.groupId}
> jibx-tools
> 1.2.4-SNAPSHOT
>
>
> ${project.groupId}
> jibx-bind
> 1.2.4-SNAPSHOT
>
--
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
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-480) Jibx Maven plugin version 1.2.4 is unusable due to SNAPSHOT dependencies in the release version
[
https://jira.codehaus.org/browse/JIBX-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley reassigned JIBX-480:
---
Assignee: Don Corley
> Jibx Maven plugin version 1.2.4 is unusable due to SNAPSHOT dependencies in
> the release version
> ---
>
> Key: JIBX-480
> URL: https://jira.codehaus.org/browse/JIBX-480
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Reporter: David Boden
>Assignee: Don Corley
>Priority: Blocker
>
> Affects Version: 1.2.4 - I can't set this in Jira because this version number
> hasn't been setup by an administrator.
> The snapshot dependencies can be seen within the deployed pom:
> http://search.maven.org/remotecontent?filepath=org/jibx/maven-jibx-plugin/1.2.4/maven-jibx-plugin-1.2.4.pom
>
> ${project.groupId}
> jibx-tools
> 1.2.4-SNAPSHOT
>
>
> ${project.groupId}
> jibx-bind
> 1.2.4-SNAPSHOT
>
--
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
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-446) org.jibx.runtime.JiBXException: Expected "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS" end tag, found "{http://www.opentravel.org/OTA/2003/05}Success" start
[
https://jira.codehaus.org/browse/JIBX-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-446.
-
Resolution: Fixed
> org.jibx.runtime.JiBXException: Expected
> "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS"; end tag, found
> "{http://www.opentravel.org/OTA/2003/05}Success"; start tag (line 2, col 126)
>
>
> Key: JIBX-446
> URL: https://jira.codehaus.org/browse/JIBX-446
> Project: JiBX
> Issue Type: Bug
> Components: CodeGen
>Affects Versions: JiBX 1.2.3
> Environment: Windows XP, Apache Ant 1.7, Tomcat 5.5, Java 5
>Reporter: Maulik Kayastha
>Assignee: Don Corley
>Priority: Blocker
> Labels: Jibx, exception, runtime
> Attachments: binding.xml, response.xml
>
>
> Hi,
> While unmarshalling response xml, I am getting exception as below -
> org.jibx.runtime.JiBXException: Expected
> "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS"; end tag, found
> "{http://www.opentravel.org/OTA/2003/05}Success"; start tag (line 2, col 126)
> I have attached binding.xml and response.xml(which I am trying to unmarshall)
> for the reference.
> code to unmarshall response document:
> private Object unmarshallJibxMessage(Document responseDocument) throws
> CommsException
>{
> DOMImplementationLS domImplementation =
> (DOMImplementationLS) responseDocument.getImplementation();
> LSSerializer lsSerializer = domImplementation.createLSSerializer();
> String xml = lsSerializer.writeToString(responseDocument);
> try
> {
> IBindingFactory factory =
> BindingDirectory.getFactory("binding",
> "org.jibx.opentravel.ota._2003._05");
> IUnmarshallingContext unMarshallingContext =
> factory.createUnmarshallingContext();
> unMarshallingContext.setDocument(new StringReader(xml));
> return unMarshallingContext.unmarshalElement();
> }
> catch (JiBXException e)
> {
> LOG.error("JIBX Unmarshalling Exception", e);
> throw new CommsException("JIBX Unmarshalling Exception", e);
> }
>}
> Please let me know if any further information is required.
--
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
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-419) Inconsistent classpaths when using a base binding file in CodeGen
[ https://jira.codehaus.org/browse/JIBX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Corley resolved JIBX-419. - Resolution: Fixed Assignee: Don Corley (was: Dennis Sosnoski) Added patch for 1.2.4 release > Inconsistent classpaths when using a base binding file in CodeGen > - > > Key: JIBX-419 > URL: https://jira.codehaus.org/browse/JIBX-419 > Project: JiBX > Issue Type: Bug > Components: CodeGen >Affects Versions: JiBX 1.2.2 > Environment: Java 1.6 >Reporter: Don Corley >Assignee: Don Corley > Attachments: codegen.patch, test.zip > > > Dennis, > I'm having a problem using codegen with based binding (which I need for the > schema-library). > Since I'm calling codegen from java, I can't change the classpath or my > current directory and I can only specify relative paths. > I have to use -t (target dir) which specifies the source and binding file > location. -i requires a path from my working location, but the generated > binding file ends up specifying the this link to the base binding file as > relative to the compile root. > Just unzip this file, change line 1 to point to your core/lib and run it... > it fails on the third codegen. > Take a look at the in person-binding.xml > Thanks, > Don > My test schema looks like this > person.xsd <- address.xsd <- company.xsd -- 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 -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-478) Support m2e 1.1
[
https://jira.codehaus.org/browse/JIBX-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296252#comment-296252
]
Don Corley commented on JIBX-478:
-
Ian,
It looks like this is just a dependency problem.
The fix should be pretty simple. I'll fix this as soon as m2e v1.1 is released
to avoid doing this twice.
If you need this now, try using the JiBX 1.2.4-SNAPSHOT. Instructions are here:
http://jibx.sourceforge.net/maven-jibx-plugin/snapshots.html
Email me a reminder when m2e v1.1 is release and I have this fixed in a snap.
Don
> Support m2e 1.1
> ---
>
> Key: JIBX-478
> URL: https://jira.codehaus.org/browse/JIBX-478
> Project: JiBX
> Issue Type: Improvement
> Components: eclipse-plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Ian Brandt
>Assignee: Don Corley
>Priority: Minor
>
> I wanted to test out the upcoming m2e 1.1 release from
> http://download.eclipse.org/technology/m2e/milestones/1.1, and found that
> there is a conflict with the m2e connector for JiBX:
> {noformat}
> Your original request has been modified.
> "m2e - Maven Integration for Eclipse" is already installed, so an update
> will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: m2e - Maven Integration for Eclipse
> 1.1.0.20120320-0058 (org.eclipse.m2e.feature.feature.group
> 1.1.0.20120320-0058)
> Software currently installed: m2e connector for JiBX 1.2.3.201107241325
> (org.jibx.m2e.feature.feature.group 1.2.3.201107241325)
> Only one of the following can be installed at once:
> Embedded Maven Runtime Bundle 1.0.0.20110607-2117
> (org.eclipse.m2e.maven.runtime 1.0.0.20110607-2117)
> Embedded Maven Runtime Bundle 1.1.0.20120315-0501
> (org.eclipse.m2e.maven.runtime 1.1.0.20120315-0501)
> Embedded Maven Runtime Bundle 1.0.200.20111228-1245
> (org.eclipse.m2e.maven.runtime 1.0.200.20111228-1245)
> Embedded Maven Runtime Bundle 1.1.0.20111210-0902
> (org.eclipse.m2e.maven.runtime 1.1.0.20111210-0902)
> Embedded Maven Runtime Bundle 1.1.0.2007-2227
> (org.eclipse.m2e.maven.runtime 1.1.0.2007-2227)
> Embedded Maven Runtime Bundle 1.1.0.20120130-1133
> (org.eclipse.m2e.maven.runtime 1.1.0.20120130-1133)
> Embedded Maven Runtime Bundle 1.0.100.20110804-1717
> (org.eclipse.m2e.maven.runtime 1.0.100.20110804-1717)
> Cannot satisfy dependency:
> From: m2e - Maven Integration for Eclipse 1.1.0.20120320-0058
> (org.eclipse.m2e.feature.feature.group 1.1.0.20120320-0058)
> To: org.eclipse.m2e.maven.runtime [1.1.0.20120315-0501]
> Cannot satisfy dependency:
> From: m2e connector for JiBX 1.2.3.201107241325
> (org.jibx.m2e.feature.feature.group 1.2.3.201107241325)
> To: org.jibx.m2e.plugin [1.2.3.201107241325]
> Cannot satisfy dependency:
> From: m2e connector for JiBX 1.2.3.201107241325 (org.jibx.m2e.plugin
> 1.2.3.201107241325)
> To: bundle org.eclipse.m2e.maven.runtime [1.0.0,1.1.0)
> {noformat}
--
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
--
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-478) Support m2e 1.1
[
https://jira.codehaus.org/browse/JIBX-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley reassigned JIBX-478:
---
Assignee: Don Corley
> Support m2e 1.1
> ---
>
> Key: JIBX-478
> URL: https://jira.codehaus.org/browse/JIBX-478
> Project: JiBX
> Issue Type: Improvement
> Components: eclipse-plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Ian Brandt
>Assignee: Don Corley
>Priority: Minor
>
> I wanted to test out the upcoming m2e 1.1 release from
> http://download.eclipse.org/technology/m2e/milestones/1.1, and found that
> there is a conflict with the m2e connector for JiBX:
> {noformat}
> Your original request has been modified.
> "m2e - Maven Integration for Eclipse" is already installed, so an update
> will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: m2e - Maven Integration for Eclipse
> 1.1.0.20120320-0058 (org.eclipse.m2e.feature.feature.group
> 1.1.0.20120320-0058)
> Software currently installed: m2e connector for JiBX 1.2.3.201107241325
> (org.jibx.m2e.feature.feature.group 1.2.3.201107241325)
> Only one of the following can be installed at once:
> Embedded Maven Runtime Bundle 1.0.0.20110607-2117
> (org.eclipse.m2e.maven.runtime 1.0.0.20110607-2117)
> Embedded Maven Runtime Bundle 1.1.0.20120315-0501
> (org.eclipse.m2e.maven.runtime 1.1.0.20120315-0501)
> Embedded Maven Runtime Bundle 1.0.200.20111228-1245
> (org.eclipse.m2e.maven.runtime 1.0.200.20111228-1245)
> Embedded Maven Runtime Bundle 1.1.0.20111210-0902
> (org.eclipse.m2e.maven.runtime 1.1.0.20111210-0902)
> Embedded Maven Runtime Bundle 1.1.0.2007-2227
> (org.eclipse.m2e.maven.runtime 1.1.0.2007-2227)
> Embedded Maven Runtime Bundle 1.1.0.20120130-1133
> (org.eclipse.m2e.maven.runtime 1.1.0.20120130-1133)
> Embedded Maven Runtime Bundle 1.0.100.20110804-1717
> (org.eclipse.m2e.maven.runtime 1.0.100.20110804-1717)
> Cannot satisfy dependency:
> From: m2e - Maven Integration for Eclipse 1.1.0.20120320-0058
> (org.eclipse.m2e.feature.feature.group 1.1.0.20120320-0058)
> To: org.eclipse.m2e.maven.runtime [1.1.0.20120315-0501]
> Cannot satisfy dependency:
> From: m2e connector for JiBX 1.2.3.201107241325
> (org.jibx.m2e.feature.feature.group 1.2.3.201107241325)
> To: org.jibx.m2e.plugin [1.2.3.201107241325]
> Cannot satisfy dependency:
> From: m2e connector for JiBX 1.2.3.201107241325 (org.jibx.m2e.plugin
> 1.2.3.201107241325)
> To: bundle org.eclipse.m2e.maven.runtime [1.0.0,1.1.0)
> {noformat}
--
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
--
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-468) Allow JibX to find additional schema XSDs in third party JAR
[ https://jira.codehaus.org/browse/JIBX-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Corley resolved JIBX-468. - Resolution: Not A Bug jibx-maven-plugin's already has the capability to package bindings for dependent schema. > Allow JibX to find additional schema XSDs in third party JAR > > > Key: JIBX-468 > URL: https://jira.codehaus.org/browse/JIBX-468 > Project: JiBX > Issue Type: New Feature > Components: CodeGen >Affects Versions: JiBX 1.2.3 > Environment: Maven 3, latest JIBx >Reporter: gregory bonk >Assignee: Don Corley > > We are interested in moving from JAXB to JibX. Our problem is that it > appears that JibX will not lookfor/resove XSDs in other third party JARs or > on the classpath. A third party provides us a JAR file with schema XSDs that > we import into our main XSD with ' When the code gen is running in JibX it can't find the XSD becuase it's in a > JAR. The maven-jaxb2-plugin lets us supply a list of JAR files that then are > searched when there's an import that can't be resolved locally. > We would like this functionality to be implemented into the Maven 2 JiBX > Plugin. Doesn't have to be quite as fancy, just that we need a classpath > option as well and a server URI. > See how they do it in JAXb: > http://confluence.highsource.org/display/MJIIP/User+Guide#UserGuide-Usingcatalogs -- 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 -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-472) Unable to import collada spec
[ https://jira.codehaus.org/browse/JIBX-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290533#comment-290533 ] Don Corley commented on JIBX-472: - Malachi, The WC3 mathml schema is massive. In my experience, even the best schema contains errors. Remember, JiBX is not perfect. It does a great job of processing schema, but some perfectly valid (and usually obscure) schema definitions can't be processed. Here is what I suggest: The mathml schema is nicely segmented. Try to process each mathml schema separately. You have already selected the best schema binding tool to use when you want to segment your code. Take a look at our simple example of a modular schema binding on a web based schema definition here in our source repository: https://github.com/jibx/maven-plugin/tree/master/test-suite/simple-web-schema-test . Every once in a while you will run into an error. For example, the error that you list above is JiBX complaining that there is an empty statement in the schema (which there is at line 20, column 13) NOTE: The line is question will not be the 20th line is a web browser, you will need to select display-source in your browser to see the raw xsd file. Why the schema author didn't just include that line as a comment is anyone's guess. The solution to this problem is to comment out this line. I would suggest using an XSLT transformation so you can use it on future schema. A nice example of XSLT transformation on a web-based schema can be found in our source repository here: https://github.com/jibx/schema-library/tree/master/net.webservicex As a programmer, I'm sure you have had to go through this kind of process a million times. I hope this helps! Don > Unable to import collada spec > - > > Key: JIBX-472 > URL: https://jira.codehaus.org/browse/JIBX-472 > Project: JiBX > Issue Type: Bug > Components: CodeGen >Affects Versions: JiBX 1.2.3 >Reporter: Malachi de AElfweald > Attachments: collada_errors.txt > > > Tried to run schema gen against > http://www.khronos.org/files/collada_schema_1_5 [renamed to > collada_schema_1_5.xsd] > It came up with some errors (see attachment) > I looked at the first one: > FATAL codegen.CodeGen - Either 'namespace' or 'schemaLocation' value required > for import at (line 20, col 13, in > http://www.w3.org/Math/XMLSchema/mathml2/common/common-attribs.xsd) > Which I did not understand since the reference xsd says: > http://www.w3.org/2001/XMLSchema"; > xmlns="http://www.w3.org/1998/Math/MathML"; > xmlns:xlink="http://www.w3.org/1999/xlink"; > targetNamespace="http://www.w3.org/1998/Math/MathML"; > elementFormDefault="qualified"> > And the line number it is complaining about is: > -- 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 -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-446) org.jibx.runtime.JiBXException: Expected "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS" end tag, found "{http://www.opentravel.org/OTA/2003/05}Success" start
[
https://jira.codehaus.org/browse/JIBX-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288554#comment-288554
]
Don Corley commented on JIBX-446:
-
Maulik,
What version of the OTA spec are you using... 2006A or 2006B? Are you using the
stock schema or are there any changes?
It would help greatly if you can you attach a simple project (to this bug
report) with a short code example that fails with the same error. In your code
you could create an object, marshal it to xml, then display the xml. Probably
less than 40 lines of code.
The 'Success' tag is used on almost every opentravel return message. I'm not
sure which message you are using. Perhaps you could use a simple return message
such as OTA_PingRS in your example.
Thanks,
Don
> org.jibx.runtime.JiBXException: Expected
> "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS"; end tag, found
> "{http://www.opentravel.org/OTA/2003/05}Success"; start tag (line 2, col 126)
>
>
> Key: JIBX-446
> URL: https://jira.codehaus.org/browse/JIBX-446
> Project: JiBX
> Issue Type: Bug
> Components: CodeGen
>Affects Versions: JiBX 1.2.3
> Environment: Windows XP, Apache Ant 1.7, Tomcat 5.5, Java 5
>Reporter: Maulik Kayastha
>Assignee: Don Corley
>Priority: Blocker
> Labels: Jibx, exception, runtime
> Attachments: binding.xml, response.xml
>
>
> Hi,
> While unmarshalling response xml, I am getting exception as below -
> org.jibx.runtime.JiBXException: Expected
> "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS"; end tag, found
> "{http://www.opentravel.org/OTA/2003/05}Success"; start tag (line 2, col 126)
> I have attached binding.xml and response.xml(which I am trying to unmarshall)
> for the reference.
> code to unmarshall response document:
> private Object unmarshallJibxMessage(Document responseDocument) throws
> CommsException
>{
> DOMImplementationLS domImplementation =
> (DOMImplementationLS) responseDocument.getImplementation();
> LSSerializer lsSerializer = domImplementation.createLSSerializer();
> String xml = lsSerializer.writeToString(responseDocument);
> try
> {
> IBindingFactory factory =
> BindingDirectory.getFactory("binding",
> "org.jibx.opentravel.ota._2003._05");
> IUnmarshallingContext unMarshallingContext =
> factory.createUnmarshallingContext();
> unMarshallingContext.setDocument(new StringReader(xml));
> return unMarshallingContext.unmarshalElement();
> }
> catch (JiBXException e)
> {
> LOG.error("JIBX Unmarshalling Exception", e);
> throw new CommsException("JIBX Unmarshalling Exception", e);
> }
>}
> Please let me know if any further information is required.
--
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
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] (JIBX-416) Plugin dependency resolving fails
[
https://jira.codehaus.org/browse/JIBX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288553#comment-288553
]
Don Corley commented on JIBX-416:
-
Petr,
Some time ago, maven recommended renaming maven plugins using the
xxx-maven-plugin naming scheme.
We adopted this scheme, but we still support the old maven-jibx-plugin name so
we don't break any existing projects.
Both plugins are exactly the same.
Hope this clears any confusion.
Don
> Plugin dependency resolving fails
> -
>
> Key: JIBX-416
> URL: https://jira.codehaus.org/browse/JIBX-416
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2
>Reporter: Antti Koivisto
>Assignee: Don Corley
> Fix For: JiBX 1.2.3
>
> Attachments: maven-jibx-plugin-problematic-build-log-cleaned.txt.txt
>
>
> I'm having a really hard time using the maven jibx plugin. Initially I got
> this same build failure in W7 with Maven 3, but it went away.
> In our Bamboo environment that uses Maven 2, the problem persists:
> {code}
> Missing:
> --
> 1) org.eclipse.equinox:registry:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.equinox:registry:jar:3.3.1
> 2) org.eclipse.core:resources:jar:3.4.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:resources:jar:3.4.0
> 3) org.eclipse.core:jobs:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.core:jobs:jar:3.3.1
> 4) org.eclipse.core:commands:jar:3.3.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=commands -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=commands
> -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse:text:jar:3.3.0-v20070606-0010
> 4) org.eclipse.core:commands:jar:3.3.0
> 5) org.eclipse:osgi:jar:3.3.2
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.ecli
[jibx-devs] [jira] (JIBX-471) Compatability with apklib?
[ https://jira.codehaus.org/browse/JIBX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=287592#comment-287592 ] Don Corley commented on JIBX-471: - Malachi, There has to be an easier way to solve your problem. Have you tried to split the jibx code and your resources into two different projects: - An apklib project with your resources - A jibx jar file with the precompiled class file Include these two in your main project and it should work. 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-tabpanel&focusedCommentId=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-470) Supplied root object of class com.mycompany.domain.Currency cannot be marshalled without top-level mapping
[ https://jira.codehaus.org/browse/JIBX-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287335#comment-287335 ] Don Corley commented on JIBX-470: - Yes, You are correct that you can't unmarshal an object that is not the top-level schema object. If you think about it, there is no reference to the top level object that contains the namespace, etc. from a lower level object. You have two ways to solve this problem. 1. Break your schema into smaller schema where any point where you need to unmarshal objects is a top-level schema def. JiBX handles references to other schema nicely. You may want to take a look at some simple schema and samples in the JiBX schema library at: http://jibx.sourceforge.net/schema-library/site.html#jibx.org 2. Unmarshal your schema to dom and use a Document Fragment to extract and transform your model to xml. Hope this helps! Don > Supplied root object of class com.mycompany.domain.Currency cannot be > marshalled without top-level mapping > -- > > Key: JIBX-470 > URL: https://jira.codehaus.org/browse/JIBX-470 > Project: JiBX > Issue Type: Bug >Affects Versions: JiBX 1.2.3 > Environment: Java7; Solaris 10; maven3 >Reporter: Harshit > > Hi, I have a use-case where I need to generate Java Objects from XSD and then > these objects interact with a component which "takes-in" XML and returns back > XML (requires marshalling and unmarshalling of domain object) > I am able to successfully generate domain objects from XSD by using JiBx's > maven codegen plugin. Also I then compiled the sources and ran the > compile-time binder on these objects (again using the maven plugin). I then > packaged these enhanced class-files into jar file. > Now, when I am trying to marshal one of these domain objects into XML, I am > getting the following error: > --- > Caused by: org.jibx.runtime.JiBXException: Supplied root object of class > com.mycompany.domain.Currency cannot be marshalled without top-level mapping > at > org.jibx.runtime.impl.MarshallingContext.marshalRoot(MarshallingContext.java:1023) > at > org.jibx.runtime.impl.MarshallingContext.marshalDocument(MarshallingContext.java:1041) > --- > Being a beginner, I am not able to understand what is the error that JiBx is > trying to convey mean and hence not able to fix this. > Could you please help me know if I am missing something? > Thanks in advance! -- 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 -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ 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-tabpanel&focusedCommentId=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-445) Missing eclipse dependencies when running schema-codegen goal with custom classes
[
https://jira.codehaus.org/browse/JIBX-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-445.
-
Resolution: Fixed
We now use current eclipse libs.
> Missing eclipse dependencies when running schema-codegen goal with custom
> classes
> -
>
> Key: JIBX-445
> URL: https://jira.codehaus.org/browse/JIBX-445
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Jan De Moerloose
>Assignee: Don Corley
>
> When trying to run schema-codegen with a custom NameConverter, maven misses
> an eclipse dependency:
> 1) org.eclipse.core:runtime:jar:3.5.0
> I was able to make it run by adding the following dependencies manually:
>
> org.eclipse.equinox
> preferences
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.equinox.preferences_3.3.0.v20100503.jar
>
>
> org.eclipse.equinox
> common
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.equinox.common_3.6.0.v20100503.jar
>
>
> org.eclipse.core
> contenttype
> 3.4.1
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.contenttype_3.4.100.v20100505-1235.jar
>
>
> org.eclipse.core
> jobs
> 3.5.1
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.jobs_3.5.1.R36x_v20100824.jar
>
>
> org.eclipse.core
> resources
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.resources_3.6.0.R36x_v20100825-0600.jar
>
>
> org.eclipse.core
> runtime
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.runtime_3.6.0.v20100505.jar
>
--
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-470) Supplied root object of class com.mycompany.domain.Currency cannot be marshalled without top-level mapping
[ https://jira.codehaus.org/browse/JIBX-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287024#comment-287024 ] Don Corley commented on JIBX-470: - I always like to start with a working example when I first use software. Take a look at the source code in this simple example from our repository: https://github.com/jibx/maven-plugin/blob/master/test-suite/org.jibx.test.gen/src/test/java/org/jibx/samples/flight/AppTest.java All it does is create a java object, marshal it to xml and then unmarshal it to a new java object. If this helps, please close this bug. Good Luck! Don > Supplied root object of class com.mycompany.domain.Currency cannot be > marshalled without top-level mapping > -- > > Key: JIBX-470 > URL: https://jira.codehaus.org/browse/JIBX-470 > Project: JiBX > Issue Type: Bug >Affects Versions: JiBX 1.2.3 > Environment: Java7; Solaris 10; maven3 >Reporter: Harshit > > Hi, I have a use-case where I need to generate Java Objects from XSD and then > these objects interact with a component which "takes-in" XML and returns back > XML (requires marshalling and unmarshalling of domain object) > I am able to successfully generate domain objects from XSD by using JiBx's > maven codegen plugin. Also I then compiled the sources and ran the > compile-time binder on these objects (again using the maven plugin). I then > packaged these enhanced class-files into jar file. > Now, when I am trying to marshal one of these domain objects into XML, I am > getting the following error: > --- > Caused by: org.jibx.runtime.JiBXException: Supplied root object of class > com.mycompany.domain.Currency cannot be marshalled without top-level mapping > at > org.jibx.runtime.impl.MarshallingContext.marshalRoot(MarshallingContext.java:1023) > at > org.jibx.runtime.impl.MarshallingContext.marshalDocument(MarshallingContext.java:1041) > --- > Being a beginner, I am not able to understand what is the error that JiBx is > trying to convey mean and hence not able to fix this. > Could you please help me know if I am missing something? > Thanks in advance! -- 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-tabpanel&focusedCommentId=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: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] Assigned: (JIBX-468) Allow JibX to find additional schema XSDs in third party JAR
[ https://jira.codehaus.org/browse/JIBX-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Corley reassigned JIBX-468: --- Assignee: Don Corley > Allow JibX to find additional schema XSDs in third party JAR > > > Key: JIBX-468 > URL: https://jira.codehaus.org/browse/JIBX-468 > Project: JiBX > Issue Type: New Feature > Components: CodeGen >Affects Versions: JiBX 1.2.3 > Environment: Maven 3, latest JIBx >Reporter: gregory bonk >Assignee: Don Corley > > We are interested in moving from JAXB to JibX. Our problem is that it > appears that JibX will not lookfor/resove XSDs in other third party JARs or > on the classpath. A third party provides us a JAR file with schema XSDs that > we import into our main XSD with ' When the code gen is running in JibX it can't find the XSD becuase it's in a > JAR. The maven-jaxb2-plugin lets us supply a list of JAR files that then are > searched when there's an import that can't be resolved locally. > We would like this functionality to be implemented into the Maven 2 JiBX > Plugin. Doesn't have to be quite as fancy, just that we need a classpath > option as well and a server URI. > See how they do it in JAXb: > http://confluence.highsource.org/display/MJIIP/User+Guide#UserGuide-Usingcatalogs -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-468) Allow JibX to find additional schema XSDs in third party JAR
[ https://jira.codehaus.org/browse/JIBX-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285306#comment-285306 ] Don Corley commented on JIBX-468: - Gregory, Klaus' workaround is a great solution. As an alternative, you might look into the jibx-maven-plugin's ability to package bindings for dependent schema. Take a look at the instructions here: http://jibx.sourceforge.net/maven-jibx-plugin/modular-codegen.html You can find two good examples in our source repo: https://github.com/jibx/maven-plugin/tree/master/test-suite/base-binding-test One example uses public schemas (available at a url), the other embeds schema in your maven project. This should solve your problem! Don > Allow JibX to find additional schema XSDs in third party JAR > > > Key: JIBX-468 > URL: https://jira.codehaus.org/browse/JIBX-468 > Project: JiBX > Issue Type: New Feature > Components: CodeGen >Affects Versions: JiBX 1.2.3 > Environment: Maven 3, latest JIBx >Reporter: gregory bonk > > We are interested in moving from JAXB to JibX. Our problem is that it > appears that JibX will not lookfor/resove XSDs in other third party JARs or > on the classpath. A third party provides us a JAR file with schema XSDs that > we import into our main XSD with ' When the code gen is running in JibX it can't find the XSD becuase it's in a > JAR. The maven-jaxb2-plugin lets us supply a list of JAR files that then are > searched when there's an import that can't be resolved locally. > We would like this functionality to be implemented into the Maven 2 JiBX > Plugin. Doesn't have to be quite as fancy, just that we need a classpath > option as well and a server URI. > See how they do it in JAXb: > http://confluence.highsource.org/display/MJIIP/User+Guide#UserGuide-Usingcatalogs -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-416) Plugin dependency resolving fails
[
https://jira.codehaus.org/browse/JIBX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285302#comment-285302
]
Don Corley commented on JIBX-416:
-
Ever,
Sorry, I mean it is fixed in the next version: 1.2.4. Until we release, use the
1.2.4-SNAPSHOT version.
Instructions on using a snapshot version are here:
http://jibx.sourceforge.net/maven-jibx-plugin/snapshots.html
This should work!
Don
> Plugin dependency resolving fails
> -
>
> Key: JIBX-416
> URL: https://jira.codehaus.org/browse/JIBX-416
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2
>Reporter: Antti Koivisto
>Assignee: Don Corley
> Fix For: JiBX 1.2.3
>
> Attachments: maven-jibx-plugin-problematic-build-log-cleaned.txt.txt
>
>
> I'm having a really hard time using the maven jibx plugin. Initially I got
> this same build failure in W7 with Maven 3, but it went away.
> In our Bamboo environment that uses Maven 2, the problem persists:
> {code}
> Missing:
> --
> 1) org.eclipse.equinox:registry:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.equinox:registry:jar:3.3.1
> 2) org.eclipse.core:resources:jar:3.4.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:resources:jar:3.4.0
> 3) org.eclipse.core:jobs:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.core:jobs:jar:3.3.1
> 4) org.eclipse.core:commands:jar:3.3.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=commands -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=commands
> -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse:text:jar:3.3.0-v20070606-0010
> 4) org.eclipse.core:commands:jar:3.3.0
> 5) org.eclipse:osgi:jar:3.3.2
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runt
[jibx-devs] [jira] Resolved: (JIBX-454) ClassNotFoundException: org.eclipse.core.runtime.jobs.ISchedulingRule when running jibx-maven-plugin:1.2.3 (schema-codegen) with customizations
[
https://jira.codehaus.org/browse/JIBX-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-454.
-
Resolution: Fixed
Great. I updated all our dependent code to the current version. This must have
fix this problem.
Thanks Klaus.
> ClassNotFoundException: org.eclipse.core.runtime.jobs.ISchedulingRule when
> running jibx-maven-plugin:1.2.3 (schema-codegen) with customizations
> ---
>
> Key: JIBX-454
> URL: https://jira.codehaus.org/browse/JIBX-454
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Klaus Claszen
>Assignee: Don Corley
>Priority: Minor
> Attachments: jibx-customization-test.zip
>
>
> We are building sources from a wsdl file using the jibx-maven-plugin:1.2.3.
> The generated classes should implement Serializable, thus we added a
> customization to the plugin configuration.
> {code}
>
> org.jibx
> jibx-maven-plugin
> 1.2.3
>
>
> generate-java-code-from-schema
> generate-sources
>
> schema-codegen
>
>
>
> src/main/resources/wsdl
>
>
> src/main/config/custom-jibx-codegen.xml
>
> true
>
> target/generated-jibx-sources
>
>
>
> compile-binding
> process-classes
>
> bind
>
>
>
> target/generated-jibx-sources
> true
> true
> true
>
>
>
>
> {code}
> Running this plugin (with -X flag) results in the following error
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.core.runtime.jobs.ISchedulingRule
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
> ... 68 more
> {code}
> We found that - as a workaround - adding the following dependencies to the
> plugin section resolves the missing class.
> {code}
>
> org.eclipse.core
> contenttype
> [3.0.0,)
>
>
> org.eclipse.core
> jobs
> [3.0.0,)
>
>
> org.eclipse.equinox
> preferences
> [3.0.0,)
>
>
> org.apache.felix
> org.osgi.compendium
> [1.0.0,)
>
> {code}
> We first added
> {code}
>
> org.jibx
> jibx-run
> 1.2.3
>
>
> org.jibx
> jibx-extras
> 1.2.3
>
> {code}
> to our project dependencies but that did not solve the problem.
> The behaviour can be reproduced with the attached test project.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Created: (JIBX-465) JiBX core needs to be tested with jdk1.7
JiBX core needs to be tested with jdk1.7 Key: JIBX-465 URL: https://jira.codehaus.org/browse/JIBX-465 Project: JiBX Issue Type: Bug Components: core Affects Versions: JiBX 1.2.3 Environment: jdk1.7_01 Reporter: Don Corley Assignee: Dennis Sosnoski The JiBX core build fails under jdk1.7. > ant roundtrip: [echo] Roundtripping the document using binding... [java] Exception in thread "main" java.lang.VerifyError: Expecting a stackmap frame at branch target 12 in method org.jibx.starter.Customer.JiBX_binding_newinstance_1_0(Lorg/jibx/starter/Customer;Lorg/jibx/runtime/impl/UnmarshallingContext;)Lorg/jibx/starter/Customer; at offset 1 [java] at java.lang.Class.getDeclaredFields0(Native Method) [java] at java.lang.Class.privateGetDeclaredFields(Class.java:2308) [java] at java.lang.Class.getDeclaredField(Class.java:1897) [java] at org.jibx.runtime.BindingDirectory.getBindingList(BindingDirectory.java:68) [java] at org.jibx.runtime.BindingDirectory.getFactory(BindingDirectory.java:211) [java] at org.jibx.extras.TestRoundtrip.runTest(TestRoundtrip.java:81) [java] at org.jibx.extras.TestRoundtrip.main(TestRoundtrip.java:144) BUILD FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-458) CodeGen cannot generate binding XMLs for schemas which reference other schemas
[ https://jira.codehaus.org/browse/JIBX-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Corley resolved JIBX-458. - Resolution: Fixed Fix Version/s: JiBX 1.2.3 See modular-codegen example in the maven plugin documentation to see how handle multiple schema. > CodeGen cannot generate binding XMLs for schemas which reference other schemas > -- > > Key: JIBX-458 > URL: https://jira.codehaus.org/browse/JIBX-458 > Project: JiBX > Issue Type: Bug > Components: CodeGen >Affects Versions: JiBX 1.2.3 > Environment: Mac OS X 10.6.8, java version "1.6.0_26" > Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-10M3425) > Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode) >Reporter: James Athey >Assignee: Don Corley > Fix For: JiBX 1.2.3 > > > If CodeGen is run on a schema which references another schema, it fails to > generate binding XMLs (after code generation) with an error like the > following: > Loaded and validated 1 specified schema(s) and 1 referenced schema(s) > Error: Error accessing included binding with path > "schemas_pvisionBinding.xml": directory>/schemas_pvisionBinding.xml (No such file or directory); on include > element at (source unknown) > Error: Error accessing included binding with path > "protocol_geolocBinding.xml": directory>/protocol_geolocBinding.xml (No such file or directory); on include > element at (source unknown) > Exception in thread "main" org.jibx.runtime.JiBXException: Terminating due to > errors in bindings > at org.jibx.schema.codegen.CodeGen.writeBindings(CodeGen.java:1618) > at org.jibx.schema.codegen.CodeGen.generate(CodeGen.java:1808) > at org.jibx.schema.codegen.CodeGen.main(CodeGen.java:2202) > The two schemas in this example are "pvision.xsd" and "geoloc.xsd"; > pvision.xsd references geoloc.xsd. It is possible (though cumbersome) to > work around this bug by generating the code and binding XMLs in two steps. > 1. Generate the code for the referenced schema, using the -b switch to set a > different filename for the generated bindings XML. > 2. Generate the code for the referencing schema, using the -i switch to pull > in the bindings XML from the previous step. > This workaround rapidly becomes onerous when more than two schemas are > involved. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-460) Error during code generation when class to modify is in an external artifact
[
https://jira.codehaus.org/browse/JIBX-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-460.
-
Resolution: Not A Bug
Fix Version/s: JiBX 1.2.3
Dimitri,
I'll see if I can get Dennis to improve the error message when he starts his
1.2.4 changes.
The error message is at:
org.jibx.binding.def.StringConversion [line:393]
I think adding a comment to the error that the class to be modified must be in
the same project would help.
Thanks,
Don
> Error during code generation when class to modify is in an external artifact
>
>
> Key: JIBX-460
> URL: https://jira.codehaus.org/browse/JIBX-460
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2, JiBX 1.2.3
> Environment: Fedora Core 14, x86_64, Java 1.6.0_22, maven 3.0.2
>Reporter: Dimitri Koussa
>Assignee: Don Corley
>Priority: Minor
> Fix For: JiBX 1.2.3
>
> Attachments: jibx-bind-error-test.tar.gz, jibx-bind-error-test.zip
>
>
> I've set up a minimal maven project that reproduces this problem.
> Unpack and run "mvn -e package".
> If I move the enum to project "c" then it works without any issue.
> The error I get is
> {noformat}
> Caused by: org.jibx.runtime.JiBXException:
> *** Error during code generation for file 'binding.xml' - please enter a bug
> report for this error in Jira if the problem is not listed as fixed on the
> online status page ***
> at org.jibx.binding.Utility.loadBinding(Utility.java:350)
> at org.jibx.binding.Utility.loadFileBinding(Utility.java:420)
> at org.jibx.binding.Compile.compile(Compile.java:217)
> at
> org.jibx.maven.AbstractBaseBindingMojo.compile(AbstractBaseBindingMojo.java:152)
> ... 22 more
> Caused by: org.jibx.runtime.JiBXException: Serializer AnEnum._jibx_serialize
> not found
> at
> org.jibx.binding.def.StringConversion.setSerializer(StringConversion.java:393)
> at
> org.jibx.binding.def.ObjectStringConversion.derive(ObjectStringConversion.java:423)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalValue(BindingBuilder.java:837)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalStructureChildren(BindingBuilder.java:1035)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalMapping(BindingBuilder.java:1847)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalMappings(BindingBuilder.java:1170)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalBindingDefinition(BindingBuilder.java:2169)
> at org.jibx.binding.Utility.loadBinding(Utility.java:300)
> {noformat}
> Seems to be similar to JIBX-287 but couldn't be sure as the error message was
> different.
> Let me know if you need any further information.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Assigned: (JIBX-460) Error during code generation when class to modify is in an external artifact
[
https://jira.codehaus.org/browse/JIBX-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley reassigned JIBX-460:
---
Assignee: Don Corley
> Error during code generation when class to modify is in an external artifact
>
>
> Key: JIBX-460
> URL: https://jira.codehaus.org/browse/JIBX-460
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2, JiBX 1.2.3
> Environment: Fedora Core 14, x86_64, Java 1.6.0_22, maven 3.0.2
>Reporter: Dimitri Koussa
>Assignee: Don Corley
>Priority: Minor
> Attachments: jibx-bind-error-test.tar.gz, jibx-bind-error-test.zip
>
>
> I've set up a minimal maven project that reproduces this problem.
> Unpack and run "mvn -e package".
> If I move the enum to project "c" then it works without any issue.
> The error I get is
> {noformat}
> Caused by: org.jibx.runtime.JiBXException:
> *** Error during code generation for file 'binding.xml' - please enter a bug
> report for this error in Jira if the problem is not listed as fixed on the
> online status page ***
> at org.jibx.binding.Utility.loadBinding(Utility.java:350)
> at org.jibx.binding.Utility.loadFileBinding(Utility.java:420)
> at org.jibx.binding.Compile.compile(Compile.java:217)
> at
> org.jibx.maven.AbstractBaseBindingMojo.compile(AbstractBaseBindingMojo.java:152)
> ... 22 more
> Caused by: org.jibx.runtime.JiBXException: Serializer AnEnum._jibx_serialize
> not found
> at
> org.jibx.binding.def.StringConversion.setSerializer(StringConversion.java:393)
> at
> org.jibx.binding.def.ObjectStringConversion.derive(ObjectStringConversion.java:423)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalValue(BindingBuilder.java:837)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalStructureChildren(BindingBuilder.java:1035)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalMapping(BindingBuilder.java:1847)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalMappings(BindingBuilder.java:1170)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalBindingDefinition(BindingBuilder.java:2169)
> at org.jibx.binding.Utility.loadBinding(Utility.java:300)
> {noformat}
> Seems to be similar to JIBX-287 but couldn't be sure as the error message was
> different.
> Let me know if you need any further information.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-460) Error during code generation when class to modify is in an external artifact
[
https://jira.codehaus.org/browse/JIBX-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282882#comment-282882
]
Don Corley commented on JIBX-460:
-
Dimitri,
I don't think this project can work as it is set up.
Remember, JiBX actually changes your class files.
The error you are getting is JiBX saying that it can't change a class in
project B while it is building project C.
It is impossible to change the classes of an external maven project that has
already been built.
You can however, reference another JiBX class that has already been built.
I think you need to refactor these projects so each project is an independent
JiBX build.
Hope this helps.
Don
> Error during code generation when class to modify is in an external artifact
>
>
> Key: JIBX-460
> URL: https://jira.codehaus.org/browse/JIBX-460
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2, JiBX 1.2.3
> Environment: Fedora Core 14, x86_64, Java 1.6.0_22, maven 3.0.2
>Reporter: Dimitri Koussa
>Priority: Minor
> Attachments: jibx-bind-error-test.tar.gz, jibx-bind-error-test.zip
>
>
> I've set up a minimal maven project that reproduces this problem.
> Unpack and run "mvn -e package".
> If I move the enum to project "c" then it works without any issue.
> The error I get is
> {noformat}
> Caused by: org.jibx.runtime.JiBXException:
> *** Error during code generation for file 'binding.xml' - please enter a bug
> report for this error in Jira if the problem is not listed as fixed on the
> online status page ***
> at org.jibx.binding.Utility.loadBinding(Utility.java:350)
> at org.jibx.binding.Utility.loadFileBinding(Utility.java:420)
> at org.jibx.binding.Compile.compile(Compile.java:217)
> at
> org.jibx.maven.AbstractBaseBindingMojo.compile(AbstractBaseBindingMojo.java:152)
> ... 22 more
> Caused by: org.jibx.runtime.JiBXException: Serializer AnEnum._jibx_serialize
> not found
> at
> org.jibx.binding.def.StringConversion.setSerializer(StringConversion.java:393)
> at
> org.jibx.binding.def.ObjectStringConversion.derive(ObjectStringConversion.java:423)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalValue(BindingBuilder.java:837)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalStructureChildren(BindingBuilder.java:1035)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalMapping(BindingBuilder.java:1847)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalMappings(BindingBuilder.java:1170)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalBindingDefinition(BindingBuilder.java:2169)
> at org.jibx.binding.Utility.loadBinding(Utility.java:300)
> {noformat}
> Seems to be similar to JIBX-287 but couldn't be sure as the error message was
> different.
> Let me know if you need any further information.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-445) Missing eclipse dependencies when running schema-codegen goal with custom classes
[
https://jira.codehaus.org/browse/JIBX-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282881#comment-282881
]
Don Corley commented on JIBX-445:
-
Jan,
I updated all the dependency versions (even eclipse).
The new code is ready to be tested. Version 1.2.4-SNAPSHOT.
Instructions on using a snapshot version are here:
http://jibx.sourceforge.net/maven-jibx-plugin/snapshots.html
Please test using your project and close this bug if this fixes your problem.
Thanks,
Don
> Missing eclipse dependencies when running schema-codegen goal with custom
> classes
> -
>
> Key: JIBX-445
> URL: https://jira.codehaus.org/browse/JIBX-445
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Jan De Moerloose
>Assignee: Don Corley
>
> When trying to run schema-codegen with a custom NameConverter, maven misses
> an eclipse dependency:
> 1) org.eclipse.core:runtime:jar:3.5.0
> I was able to make it run by adding the following dependencies manually:
>
> org.eclipse.equinox
> preferences
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.equinox.preferences_3.3.0.v20100503.jar
>
>
> org.eclipse.equinox
> common
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.equinox.common_3.6.0.v20100503.jar
>
>
> org.eclipse.core
> contenttype
> 3.4.1
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.contenttype_3.4.100.v20100505-1235.jar
>
>
> org.eclipse.core
> jobs
> 3.5.1
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.jobs_3.5.1.R36x_v20100824.jar
>
>
> org.eclipse.core
> resources
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.resources_3.6.0.R36x_v20100825-0600.jar
>
>
> org.eclipse.core
> runtime
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.runtime_3.6.0.v20100505.jar
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-454) ClassNotFoundException: org.eclipse.core.runtime.jobs.ISchedulingRule when running jibx-maven-plugin:1.2.3 (schema-codegen) with customizations
[
https://jira.codehaus.org/browse/JIBX-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282215#comment-282215
]
Don Corley commented on JIBX-454:
-
Claus,
I haven't forgotten you. I'll take a look at this soon.
Don
> ClassNotFoundException: org.eclipse.core.runtime.jobs.ISchedulingRule when
> running jibx-maven-plugin:1.2.3 (schema-codegen) with customizations
> ---
>
> Key: JIBX-454
> URL: https://jira.codehaus.org/browse/JIBX-454
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Klaus Claszen
>Assignee: Don Corley
>Priority: Minor
> Attachments: jibx-customization-test.zip
>
>
> We are building sources from a wsdl file using the jibx-maven-plugin:1.2.3.
> The generated classes should implement Serializable, thus we added a
> customization to the plugin configuration.
> {code}
>
> org.jibx
> jibx-maven-plugin
> 1.2.3
>
>
> generate-java-code-from-schema
> generate-sources
>
> schema-codegen
>
>
>
> src/main/resources/wsdl
>
>
> src/main/config/custom-jibx-codegen.xml
>
> true
>
> target/generated-jibx-sources
>
>
>
> compile-binding
> process-classes
>
> bind
>
>
>
> target/generated-jibx-sources
> true
> true
> true
>
>
>
>
> {code}
> Running this plugin (with -X flag) results in the following error
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.core.runtime.jobs.ISchedulingRule
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
> ... 68 more
> {code}
> We found that - as a workaround - adding the following dependencies to the
> plugin section resolves the missing class.
> {code}
>
> org.eclipse.core
> contenttype
> [3.0.0,)
>
>
> org.eclipse.core
> jobs
> [3.0.0,)
>
>
> org.eclipse.equinox
> preferences
> [3.0.0,)
>
>
> org.apache.felix
> org.osgi.compendium
> [1.0.0,)
>
> {code}
> We first added
> {code}
>
> org.jibx
> jibx-run
> 1.2.3
>
>
> org.jibx
> jibx-extras
> 1.2.3
>
> {code}
> to our project dependencies but that did not solve the problem.
> The behaviour can be reproduced with the attached test project.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-460) Error during code generation when class to modify is in an external artifact
[
https://jira.codehaus.org/browse/JIBX-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282214#comment-282214
]
Don Corley commented on JIBX-460:
-
Dimitri,
I'm have a problem untarring your file.
Could you re-attach your project as a zip file.
Can anyone else extract these files?
Thanks,
Don
> Error during code generation when class to modify is in an external artifact
>
>
> Key: JIBX-460
> URL: https://jira.codehaus.org/browse/JIBX-460
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2, JiBX 1.2.3
> Environment: Fedora Core 14, x86_64, Java 1.6.0_22, maven 3.0.2
>Reporter: Dimitri Koussa
>Priority: Minor
> Attachments: jibx-bind-error-test.tar.gz
>
>
> I've set up a minimal maven project that reproduces this problem.
> Unpack and run "mvn -e package".
> If I move the enum to project "c" then it works without any issue.
> The error I get is
> {noformat}
> Caused by: org.jibx.runtime.JiBXException:
> *** Error during code generation for file 'binding.xml' - please enter a bug
> report for this error in Jira if the problem is not listed as fixed on the
> online status page ***
> at org.jibx.binding.Utility.loadBinding(Utility.java:350)
> at org.jibx.binding.Utility.loadFileBinding(Utility.java:420)
> at org.jibx.binding.Compile.compile(Compile.java:217)
> at
> org.jibx.maven.AbstractBaseBindingMojo.compile(AbstractBaseBindingMojo.java:152)
> ... 22 more
> Caused by: org.jibx.runtime.JiBXException: Serializer AnEnum._jibx_serialize
> not found
> at
> org.jibx.binding.def.StringConversion.setSerializer(StringConversion.java:393)
> at
> org.jibx.binding.def.ObjectStringConversion.derive(ObjectStringConversion.java:423)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalValue(BindingBuilder.java:837)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalStructureChildren(BindingBuilder.java:1035)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalMapping(BindingBuilder.java:1847)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalMappings(BindingBuilder.java:1170)
> at
> org.jibx.binding.def.BindingBuilder.unmarshalBindingDefinition(BindingBuilder.java:2169)
> at org.jibx.binding.Utility.loadBinding(Utility.java:300)
> {noformat}
> Seems to be similar to JIBX-287 but couldn't be sure as the error message was
> different.
> Let me know if you need any further information.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-445) Missing eclipse dependencies when running schema-codegen goal with custom classes
[
https://jira.codehaus.org/browse/JIBX-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282213#comment-282213
]
Don Corley commented on JIBX-445:
-
Jon,
Thanks for pointing this out. I kind of figured that these eclipse dependencies
would be needed.
I tested JiBX with the current version of these eclipse artifacts (From the
indigo plugin directory), and everything seemed to work.
Here is my problem... Anybody have any ideas?
I need to include about 10 eclipse jars to make JiBX work. Unfortunately,
eclipse stopped uploading their artifacts to maven central in 2007. Using these
old jars cause all kinds of problems. The most current artifacts are only in
their (P2) eclipse plugin directories.
Is there a way to use the latest eclipse artifacts from a plugin location in a
maven project?
Thanks!
Don
> Missing eclipse dependencies when running schema-codegen goal with custom
> classes
> -
>
> Key: JIBX-445
> URL: https://jira.codehaus.org/browse/JIBX-445
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Jan De Moerloose
>Assignee: Don Corley
>
> When trying to run schema-codegen with a custom NameConverter, maven misses
> an eclipse dependency:
> 1) org.eclipse.core:runtime:jar:3.5.0
> I was able to make it run by adding the following dependencies manually:
>
> org.eclipse.equinox
> preferences
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.equinox.preferences_3.3.0.v20100503.jar
>
>
> org.eclipse.equinox
> common
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.equinox.common_3.6.0.v20100503.jar
>
>
> org.eclipse.core
> contenttype
> 3.4.1
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.contenttype_3.4.100.v20100505-1235.jar
>
>
> org.eclipse.core
> jobs
> 3.5.1
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.jobs_3.5.1.R36x_v20100824.jar
>
>
> org.eclipse.core
> resources
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.resources_3.6.0.R36x_v20100825-0600.jar
>
>
> org.eclipse.core
> runtime
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.runtime_3.6.0.v20100505.jar
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-457) default target directory for generated code, target directory doesn't work
[
https://jira.codehaus.org/browse/JIBX-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-457.
-
Resolution: Fixed
> default target directory for generated code, target directory doesn't work
> --
>
> Key: JIBX-457
> URL: https://jira.codehaus.org/browse/JIBX-457
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
> Environment: Maven 2.2.1, JDK 5 Update 22
>Reporter: Mathias Wiegard
>Assignee: Don Corley
> Fix For: JiBX 1.2.3
>
> Attachments: test.zip
>
>
> the default target directoy for the generated source ist
> target/generated-sources. This isn't conform to the Maven default convention.
> This causes problems e.g. in my Intellij Editor. Could you please change the
> folder to target/generated-sources/jibx, please?
> I also tried a workaround to manually set the target directory by hand:
>
> generate-java-code-from-schema
>
> schema-codegen
>
>
>
> ${project.build.directory}/generated-sources/jibx
>
>
> com.bmw.swll6.business.vkc.kv.integration.transfer
>
>
>
> This also doesn't work (Jibx says that this folder is not writeable).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Updated: (JIBX-457) default target directory for generated code, target directory doesn't work
[
https://jira.codehaus.org/browse/JIBX-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley updated JIBX-457:
Attachment: test.zip
Mathias,
Yes, this is a bug. I had written some code that didn't work with windows
pathnames. I fixed it in JIBX-429.
To fix your project, just use the snapshot code for the jibx-maven-plugin. To
do this, change your jibx-maven-plug version to 1.2.4-SNAPSHOT. Also, add these
lines to your pom.xml file:
sonatype-nexus-snapshots
Sonatype Nexus Snapshots
https://oss.sonatype.org/content/repositories/snapshots
true
I've included a sample project in case this doesn't work.
Thanks for sticking with this!
Close this bug if this works for you.
Don
> default target directory for generated code, target directory doesn't work
> --
>
> Key: JIBX-457
> URL: https://jira.codehaus.org/browse/JIBX-457
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
> Environment: Maven 2.2.1, JDK 5 Update 22
>Reporter: Mathias Wiegard
>Assignee: Don Corley
> Fix For: JiBX 1.2.3
>
> Attachments: test.zip
>
>
> the default target directoy for the generated source ist
> target/generated-sources. This isn't conform to the Maven default convention.
> This causes problems e.g. in my Intellij Editor. Could you please change the
> folder to target/generated-sources/jibx, please?
> I also tried a workaround to manually set the target directory by hand:
>
> generate-java-code-from-schema
>
> schema-codegen
>
>
>
> ${project.build.directory}/generated-sources/jibx
>
>
> com.bmw.swll6.business.vkc.kv.integration.transfer
>
>
>
> This also doesn't work (Jibx says that this folder is not writeable).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-458) CodeGen cannot generate binding XMLs for schemas which reference other schemas
[ https://jira.codehaus.org/browse/JIBX-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279063#comment-279063 ] Don Corley commented on JIBX-458: - James, Version 1.2.3 of JiBX came with a huge improvement in handing multiple schema. The jibx-maven-plugin now has the capability of including schema that are packaged in a separate (maven) project. You can find the instructions here: http://jibx.sourceforge.net/jibx-maven-plugin/modular-codegen.html There are two comprehensive examples in the source repository. If your schema is publicly available (on the web), look at this example: http://jibx.svn.sourceforge.net/viewvc/jibx/trunk/plugins/maven-plugin/test-suite/web-schema-test/ If you include your schema in your (maven) projects, check this example out: http://jibx.svn.sourceforge.net/viewvc/jibx/trunk/plugins/maven-plugin/test-suite/simple-web-schema-test/ If you are developing a binding for a public schema, please consider including it in the JiBX Schema Library, http://jibx.sourceforge.net/schema-library Please close this bug if this fixes your problem. Thanks, Don Corley > CodeGen cannot generate binding XMLs for schemas which reference other schemas > -- > > Key: JIBX-458 > URL: https://jira.codehaus.org/browse/JIBX-458 > Project: JiBX > Issue Type: Bug > Components: CodeGen >Affects Versions: JiBX 1.2.3 > Environment: Mac OS X 10.6.8, java version "1.6.0_26" > Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-10M3425) > Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode) >Reporter: James Athey >Assignee: Don Corley > > If CodeGen is run on a schema which references another schema, it fails to > generate binding XMLs (after code generation) with an error like the > following: > Loaded and validated 1 specified schema(s) and 1 referenced schema(s) > Error: Error accessing included binding with path > "schemas_pvisionBinding.xml": directory>/schemas_pvisionBinding.xml (No such file or directory); on include > element at (source unknown) > Error: Error accessing included binding with path > "protocol_geolocBinding.xml": directory>/protocol_geolocBinding.xml (No such file or directory); on include > element at (source unknown) > Exception in thread "main" org.jibx.runtime.JiBXException: Terminating due to > errors in bindings > at org.jibx.schema.codegen.CodeGen.writeBindings(CodeGen.java:1618) > at org.jibx.schema.codegen.CodeGen.generate(CodeGen.java:1808) > at org.jibx.schema.codegen.CodeGen.main(CodeGen.java:2202) > The two schemas in this example are "pvision.xsd" and "geoloc.xsd"; > pvision.xsd references geoloc.xsd. It is possible (though cumbersome) to > work around this bug by generating the code and binding XMLs in two steps. > 1. Generate the code for the referenced schema, using the -b switch to set a > different filename for the generated bindings XML. > 2. Generate the code for the referencing schema, using the -i switch to pull > in the bindings XML from the previous step. > This workaround rapidly becomes onerous when more than two schemas are > involved. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Assigned: (JIBX-458) CodeGen cannot generate binding XMLs for schemas which reference other schemas
[ https://jira.codehaus.org/browse/JIBX-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Corley reassigned JIBX-458: --- Assignee: Don Corley > CodeGen cannot generate binding XMLs for schemas which reference other schemas > -- > > Key: JIBX-458 > URL: https://jira.codehaus.org/browse/JIBX-458 > Project: JiBX > Issue Type: Bug > Components: CodeGen >Affects Versions: JiBX 1.2.3 > Environment: Mac OS X 10.6.8, java version "1.6.0_26" > Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-10M3425) > Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode) >Reporter: James Athey >Assignee: Don Corley > > If CodeGen is run on a schema which references another schema, it fails to > generate binding XMLs (after code generation) with an error like the > following: > Loaded and validated 1 specified schema(s) and 1 referenced schema(s) > Error: Error accessing included binding with path > "schemas_pvisionBinding.xml": directory>/schemas_pvisionBinding.xml (No such file or directory); on include > element at (source unknown) > Error: Error accessing included binding with path > "protocol_geolocBinding.xml": directory>/protocol_geolocBinding.xml (No such file or directory); on include > element at (source unknown) > Exception in thread "main" org.jibx.runtime.JiBXException: Terminating due to > errors in bindings > at org.jibx.schema.codegen.CodeGen.writeBindings(CodeGen.java:1618) > at org.jibx.schema.codegen.CodeGen.generate(CodeGen.java:1808) > at org.jibx.schema.codegen.CodeGen.main(CodeGen.java:2202) > The two schemas in this example are "pvision.xsd" and "geoloc.xsd"; > pvision.xsd references geoloc.xsd. It is possible (though cumbersome) to > work around this bug by generating the code and binding XMLs in two steps. > 1. Generate the code for the referenced schema, using the -b switch to set a > different filename for the generated bindings XML. > 2. Generate the code for the referencing schema, using the -i switch to pull > in the bindings XML from the previous step. > This workaround rapidly becomes onerous when more than two schemas are > involved. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-457) default target directory for generated code, target directory doesn't work
[
https://jira.codehaus.org/browse/JIBX-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-457.
-
Resolution: Fixed
Mathias,
Klaus is correct.
You will have to use the new jibx-maven-plugin, not the old maven-jibx-plug.
The code has been merged so either plugin will work the the next JiBX release.
Thanks,
Don
> default target directory for generated code, target directory doesn't work
> --
>
> Key: JIBX-457
> URL: https://jira.codehaus.org/browse/JIBX-457
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
> Environment: Maven 2.2.1, JDK 5 Update 22
>Reporter: Mathias Wiegard
>Assignee: Don Corley
> Fix For: JiBX 1.2.3
>
>
> the default target directoy for the generated source ist
> target/generated-sources. This isn't conform to the Maven default convention.
> This causes problems e.g. in my Intellij Editor. Could you please change the
> folder to target/generated-sources/jibx, please?
> I also tried a workaround to manually set the target directory by hand:
>
> generate-java-code-from-schema
>
> schema-codegen
>
>
>
> ${project.build.directory}/generated-sources/jibx
>
>
> com.bmw.swll6.business.vkc.kv.integration.transfer
>
>
>
> This also doesn't work (Jibx says that this folder is not writeable).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops? How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-457) default target directory for generated code, target directory doesn't work
[
https://jira.codehaus.org/browse/JIBX-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-457.
-
Resolution: Fixed
Fix Version/s: JiBX 1.2.3
Mathias,
I cannot change the default generated-sources directory because it would break
all of our current user's projects.
You can set your generated-sources directory by setting the
param in you project. Your plugin config will look
something like this:
org.jibx
jibx-maven-plugin
1.2.3
generate-java-code-from-schema
schema-codegen
${project.build.directory}/generated-sources/jibx
compile-binding
bind
${project.build.directory}/generated-sources/jibx
Note that I am using the new jibx-maven-plugin. You can find the documentation
here:
http://www.jibx.org/jibx-maven-plugin
This should fix your problem!
Don
> default target directory for generated code, target directory doesn't work
> --
>
> Key: JIBX-457
> URL: https://jira.codehaus.org/browse/JIBX-457
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
> Environment: Maven 2.2.1, JDK 5 Update 22
>Reporter: Mathias Wiegard
>Assignee: Don Corley
> Fix For: JiBX 1.2.3
>
>
> the default target directoy for the generated source ist
> target/generated-sources. This isn't conform to the Maven default convention.
> This causes problems e.g. in my Intellij Editor. Could you please change the
> folder to target/generated-sources/jibx, please?
> I also tried a workaround to manually set the target directory by hand:
>
> generate-java-code-from-schema
>
> schema-codegen
>
>
>
> ${project.build.directory}/generated-sources/jibx
>
>
> com.bmw.swll6.business.vkc.kv.integration.transfer
>
>
>
> This also doesn't work (Jibx says that this folder is not writeable).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the
BlackBerry® mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry® DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Assigned: (JIBX-457) default target directory for generated code, target directory doesn't work
[
https://jira.codehaus.org/browse/JIBX-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley reassigned JIBX-457:
---
Assignee: Don Corley
> default target directory for generated code, target directory doesn't work
> --
>
> Key: JIBX-457
> URL: https://jira.codehaus.org/browse/JIBX-457
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
> Environment: Maven 2.2.1, JDK 5 Update 22
>Reporter: Mathias Wiegard
>Assignee: Don Corley
>
> the default target directoy for the generated source ist
> target/generated-sources. This isn't conform to the Maven default convention.
> This causes problems e.g. in my Intellij Editor. Could you please change the
> folder to target/generated-sources/jibx, please?
> I also tried a workaround to manually set the target directory by hand:
>
> generate-java-code-from-schema
>
> schema-codegen
>
>
>
> ${project.build.directory}/generated-sources/jibx
>
>
> com.bmw.swll6.business.vkc.kv.integration.transfer
>
>
>
> This also doesn't work (Jibx says that this folder is not writeable).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the
BlackBerry® mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry® DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-454) ClassNotFoundException: org.eclipse.core.runtime.jobs.ISchedulingRule when running jibx-maven-plugin:1.2.3 (schema-codegen) with customizations
[
https://jira.codehaus.org/browse/JIBX-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=278943#comment-278943
]
Don Corley commented on JIBX-454:
-
Klaus,
Now we're getting somewhere. Can you give me the configuration of your Nexus
repository so I can recreate this bug. I believe it would be in your
~/.m2/settings.xml file.
I really hate to add back these eclipse dependencies if I don't have to.
Thanks again!
Don
> ClassNotFoundException: org.eclipse.core.runtime.jobs.ISchedulingRule when
> running jibx-maven-plugin:1.2.3 (schema-codegen) with customizations
> ---
>
> Key: JIBX-454
> URL: https://jira.codehaus.org/browse/JIBX-454
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Klaus Claszen
>Assignee: Don Corley
>Priority: Minor
> Attachments: jibx-customization-test.zip
>
>
> We are building sources from a wsdl file using the jibx-maven-plugin:1.2.3.
> The generated classes should implement Serializable, thus we added a
> customization to the plugin configuration.
> {code}
>
> org.jibx
> jibx-maven-plugin
> 1.2.3
>
>
> generate-java-code-from-schema
> generate-sources
>
> schema-codegen
>
>
>
> src/main/resources/wsdl
>
>
> src/main/config/custom-jibx-codegen.xml
>
> true
>
> target/generated-jibx-sources
>
>
>
> compile-binding
> process-classes
>
> bind
>
>
>
> target/generated-jibx-sources
> true
> true
> true
>
>
>
>
> {code}
> Running this plugin (with -X flag) results in the following error
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.core.runtime.jobs.ISchedulingRule
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
> ... 68 more
> {code}
> We found that - as a workaround - adding the following dependencies to the
> plugin section resolves the missing class.
> {code}
>
> org.eclipse.core
> contenttype
> [3.0.0,)
>
>
> org.eclipse.core
> jobs
> [3.0.0,)
>
>
> org.eclipse.equinox
> preferences
> [3.0.0,)
>
>
> org.apache.felix
> org.osgi.compendium
> [1.0.0,)
>
> {code}
> We first added
> {code}
>
> org.jibx
> jibx-run
> 1.2.3
>
>
> org.jibx
> jibx-extras
> 1.2.3
>
> {code}
> to our project dependencies but that did not solve the problem.
> The behaviour can be reproduced with the attached test project.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the
BlackBerry® mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry® DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-454) ClassNotFoundException: org.eclipse.core.runtime.jobs.ISchedulingRule when running jibx-maven-plugin:1.2.3 (schema-codegen) with customizations
[
https://jira.codehaus.org/browse/JIBX-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=278585#comment-278585
]
Don Corley commented on JIBX-454:
-
Klaus,
Thanks for reporting this error. I need a little help reproducing it so I can
find the problem.
I did a 'mvn -X install' on your test project and it built successfully on my
system.
One of our biggest headaches has been problems with eclipse dependencies. Since
eclipse stopped adding their artifacts to maven about four years ago we have
had a huge problem calling this outdated code, especially on systems that use
the newer equinox code.
Could you try to reproduce this bug using our current snapshot code.
Just change the jibx-version to 1.2.4-SNAPSHOT in your project and add these
lines to your POM:
sonatype-snapshots
http://oss.sonatype.org/content/repositories/snapshots/
If this works, please notify me.
If this doesn't work, could you give me a little more information about your
software environment?
O/S, maven version, etc.
Thanks,
Don
> ClassNotFoundException: org.eclipse.core.runtime.jobs.ISchedulingRule when
> running jibx-maven-plugin:1.2.3 (schema-codegen) with customizations
> ---
>
> Key: JIBX-454
> URL: https://jira.codehaus.org/browse/JIBX-454
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Klaus Claszen
>Assignee: Don Corley
>Priority: Minor
> Attachments: jibx-customization-test.zip
>
>
> We are building sources from a wsdl file using the jibx-maven-plugin:1.2.3.
> The generated classes should implement Serializable, thus we added a
> customization to the plugin configuration.
> {code}
>
> org.jibx
> jibx-maven-plugin
> 1.2.3
>
>
> generate-java-code-from-schema
> generate-sources
>
> schema-codegen
>
>
>
> src/main/resources/wsdl
>
>
> src/main/config/custom-jibx-codegen.xml
>
> true
>
> target/generated-jibx-sources
>
>
>
> compile-binding
> process-classes
>
> bind
>
>
>
> target/generated-jibx-sources
> true
> true
> true
>
>
>
>
> {code}
> Running this plugin (with -X flag) results in the following error
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.core.runtime.jobs.ISchedulingRule
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
> ... 68 more
> {code}
> We found that - as a workaround - adding the following dependencies to the
> plugin section resolves the missing class.
> {code}
>
> org.eclipse.core
> contenttype
> [3.0.0,)
>
>
> org.eclipse.core
> jobs
> [3.0.0,)
>
>
> org.eclipse.equinox
> preferences
> [3.0.0,)
>
>
> org.apache.felix
> org.osgi.compendium
> [1.0.0,)
>
> {code}
> We first added
> {code}
>
> org.jibx
> jibx-run
> 1.2.3
>
>
> org.jibx
> jibx-extras
> 1.2.3
>
> {code}
> to our project dependencies but that did not solve the problem.
> The behaviour can be reproduced with the attached test project.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops? How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-de
[jibx-devs] [jira] Assigned: (JIBX-454) ClassNotFoundException: org.eclipse.core.runtime.jobs.ISchedulingRule when running jibx-maven-plugin:1.2.3 (schema-codegen) with customizations
[
https://jira.codehaus.org/browse/JIBX-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley reassigned JIBX-454:
---
Assignee: Don Corley
> ClassNotFoundException: org.eclipse.core.runtime.jobs.ISchedulingRule when
> running jibx-maven-plugin:1.2.3 (schema-codegen) with customizations
> ---
>
> Key: JIBX-454
> URL: https://jira.codehaus.org/browse/JIBX-454
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Klaus Claszen
>Assignee: Don Corley
>Priority: Minor
> Attachments: jibx-customization-test.zip
>
>
> We are building sources from a wsdl file using the jibx-maven-plugin:1.2.3.
> The generated classes should implement Serializable, thus we added a
> customization to the plugin configuration.
> {code}
>
> org.jibx
> jibx-maven-plugin
> 1.2.3
>
>
> generate-java-code-from-schema
> generate-sources
>
> schema-codegen
>
>
>
> src/main/resources/wsdl
>
>
> src/main/config/custom-jibx-codegen.xml
>
> true
>
> target/generated-jibx-sources
>
>
>
> compile-binding
> process-classes
>
> bind
>
>
>
> target/generated-jibx-sources
> true
> true
> true
>
>
>
>
> {code}
> Running this plugin (with -X flag) results in the following error
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.core.runtime.jobs.ISchedulingRule
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
> ... 68 more
> {code}
> We found that - as a workaround - adding the following dependencies to the
> plugin section resolves the missing class.
> {code}
>
> org.eclipse.core
> contenttype
> [3.0.0,)
>
>
> org.eclipse.core
> jobs
> [3.0.0,)
>
>
> org.eclipse.equinox
> preferences
> [3.0.0,)
>
>
> org.apache.felix
> org.osgi.compendium
> [1.0.0,)
>
> {code}
> We first added
> {code}
>
> org.jibx
> jibx-run
> 1.2.3
>
>
> org.jibx
> jibx-extras
> 1.2.3
>
> {code}
> to our project dependencies but that did not solve the problem.
> The behaviour can be reproduced with the attached test project.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-451) Property name has to be for bind goal.
[
https://jira.codehaus.org/browse/JIBX-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-451.
-
Resolution: Fixed
Fix Version/s: JiBX 1.2.3
Klaus,
I have already fixed this in the source repo. This fix will be included in the
JiBX 1.2.4 release.
Thanks for reporting this.
Don
> Property name has to be for bind
> goal.
> --
>
> Key: JIBX-451
> URL: https://jira.codehaus.org/browse/JIBX-451
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Klaus Claszen
>Assignee: Don Corley
>Priority: Minor
> Fix For: JiBX 1.2.3
>
>
> I tried to run the bind goal with the
> [documented|http://jibx.sourceforge.net/maven-jibx-plugin/bind-mojo.html#schemaBindingDirectory]
> configuration property ** (which replaces the
> deprecated ** property) like this:
> {code}
>
> org.jibx
> maven-jibx-plugin
> 1.2.3
>
>
> generate-java-code-from-schema
> generate-sources
>
> schema-codegen
>
>
>
> src/main/resources
>
>
> foobar.xsd
>
> true
>
> target/generated-jibx-sources
>
>
>
> compile-binding
> process-classes
>
> bind
>
>
>
> target/generated-jibx-sources
>
>
> binding.xml
>
> true
> true
> true
>
>
>
>
> {code}
> This did not work. A look at the maven debug configuration output shows, that
> the expected property name is **.
> {noformat}
> [DEBUG]
> ---
> [DEBUG] Goal: org.jibx:maven-jibx-plugin:1.2.3:bind (compile-binding)
> [DEBUG] Style: Regular
> [DEBUG] Configuration:
>
>default-value="src/main/config">${bindingDirectory}
> ${directory}
> ${excludeSchemaBindings}
> ${excludes}
> ${includeBaseBindings}
>
>
> binding.xml${includeSchemaBindings}
> ${includes}
> true
> ${modules}
> ${multi-module}
> ${project}
> true
> ${verbose}
> true
>
> [DEBUG]
> ---
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Assigned: (JIBX-451) Property name has to be for bind goal.
[
https://jira.codehaus.org/browse/JIBX-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley reassigned JIBX-451:
---
Assignee: Don Corley
> Property name has to be for bind
> goal.
> --
>
> Key: JIBX-451
> URL: https://jira.codehaus.org/browse/JIBX-451
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Klaus Claszen
>Assignee: Don Corley
>Priority: Minor
>
> I tried to run the bind goal with the
> [documented|http://jibx.sourceforge.net/maven-jibx-plugin/bind-mojo.html#schemaBindingDirectory]
> configuration property ** (which replaces the
> deprecated ** property) like this:
> {code}
>
> org.jibx
> maven-jibx-plugin
> 1.2.3
>
>
> generate-java-code-from-schema
> generate-sources
>
> schema-codegen
>
>
>
> src/main/resources
>
>
> foobar.xsd
>
> true
>
> target/generated-jibx-sources
>
>
>
> compile-binding
> process-classes
>
> bind
>
>
>
> target/generated-jibx-sources
>
>
> binding.xml
>
> true
> true
> true
>
>
>
>
> {code}
> This did not work. A look at the maven debug configuration output shows, that
> the expected property name is **.
> {noformat}
> [DEBUG]
> ---
> [DEBUG] Goal: org.jibx:maven-jibx-plugin:1.2.3:bind (compile-binding)
> [DEBUG] Style: Regular
> [DEBUG] Configuration:
>
>default-value="src/main/config">${bindingDirectory}
> ${directory}
> ${excludeSchemaBindings}
> ${excludes}
> ${includeBaseBindings}
>
>
> binding.xml${includeSchemaBindings}
> ${includes}
> true
> ${modules}
> ${multi-module}
> ${project}
> true
> ${verbose}
> true
>
> [DEBUG]
> ---
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-450) Property name has to be for schema-codegen goal.
[
https://jira.codehaus.org/browse/JIBX-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-450.
-
Resolution: Fixed
Fix Version/s: JiBX 1.2.3
Please change your plugin name from maven-jibx-plugin to jibx-maven-plugin in
your project (The new maven standard for plugins).
Actually, is the correct parameter name.
The new maven plugin is called jibx-maven-plugin and version 1.2.3 works
correctly.
This bug has also been been fixed and will be included in the 1.2.4 release of
the old maven-jibx-plugin.
Thanks!
Don
> Property name has to be for schema-codegen
> goal.
> ---
>
> Key: JIBX-450
> URL: https://jira.codehaus.org/browse/JIBX-450
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Klaus Claszen
>Assignee: Don Corley
>Priority: Minor
> Fix For: JiBX 1.2.3
>
>
> I tried to run the schema-codegen goal with the
> [documented|http://jibx.sourceforge.net/maven-jibx-plugin/schema-codegen-mojo.html#schemaLocation]
> configuration property ** (which replaces the deprecated
> ** property) like this:
> {noformat}
>
> org.jibx
> maven-jibx-plugin
> 1.2.3
>
>
> generate-java-code-from-schema
> generate-sources
>
> schema-codegen
>
>
>
> src/main/resources
>
>
> foobar.xsd
>
> true
>
> target/generated-jibx-sources
>
>
>
> compile-binding
> process-classes
>
> bind
>
>
>
> target/generated-jibx-sources
>
>
> binding.xml
>
> true
> true
> true
>
>
>
>
> {noformat}
> This did not work. A look at the maven debug configuration output shows, that
> the expected property name is **.
> {noformat}
> [DEBUG]
> ---
> [DEBUG] Goal: org.jibx:maven-jibx-plugin:1.2.3:schema-codegen
> (generate-java-code-from-schema)
> [DEBUG] Style: Regular
> [DEBUG] Configuration:
>
> ${customizations}
> ${directory}
> ${excludeSchemaBindings}
> ${excludeSchemas}
> ${excludes}
> ${includeBaseBindings}
> ${includeBindings}
> ${includeSchemaBindings}
>
>
> foobar.xsd${includeSchemas}
> ${includes}
> ${modules}
> ${multi-module}
> ${project}
>default-value="src/main/config">${schemaDirectory}
>default-value="target/generated-sources">target/generated-jibx-sources
> true
>
> [DEBUG]
> ---
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
uberSVN's rich system and user administration capabilities and model
configuration take the hassle out of deploying and managing Subversion and
the tools developers use with it. Learn more about uberSVN and get a free
download at: http://p.sf.net/sfu/wandisco-dev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Assigned: (JIBX-450) Property name has to be for schema-codegen goal.
[
https://jira.codehaus.org/browse/JIBX-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley reassigned JIBX-450:
---
Assignee: Don Corley
> Property name has to be for schema-codegen
> goal.
> ---
>
> Key: JIBX-450
> URL: https://jira.codehaus.org/browse/JIBX-450
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Klaus Claszen
>Assignee: Don Corley
>Priority: Minor
>
> I tried to run the schema-codegen goal with the
> [documented|http://jibx.sourceforge.net/maven-jibx-plugin/schema-codegen-mojo.html#schemaLocation]
> configuration property ** (which replaces the deprecated
> ** property) like this:
> {noformat}
>
> org.jibx
> maven-jibx-plugin
> 1.2.3
>
>
> generate-java-code-from-schema
> generate-sources
>
> schema-codegen
>
>
>
> src/main/resources
>
>
> foobar.xsd
>
> true
>
> target/generated-jibx-sources
>
>
>
> compile-binding
> process-classes
>
> bind
>
>
>
> target/generated-jibx-sources
>
>
> binding.xml
>
> true
> true
> true
>
>
>
>
> {noformat}
> This did not work. A look at the maven debug configuration output shows, that
> the expected property name is **.
> {noformat}
> [DEBUG]
> ---
> [DEBUG] Goal: org.jibx:maven-jibx-plugin:1.2.3:schema-codegen
> (generate-java-code-from-schema)
> [DEBUG] Style: Regular
> [DEBUG] Configuration:
>
> ${customizations}
> ${directory}
> ${excludeSchemaBindings}
> ${excludeSchemas}
> ${excludes}
> ${includeBaseBindings}
> ${includeBindings}
> ${includeSchemaBindings}
>
>
> foobar.xsd${includeSchemas}
> ${includes}
> ${modules}
> ${multi-module}
> ${project}
>default-value="src/main/config">${schemaDirectory}
>default-value="target/generated-sources">target/generated-jibx-sources
> true
>
> [DEBUG]
> ---
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
uberSVN's rich system and user administration capabilities and model
configuration take the hassle out of deploying and managing Subversion and
the tools developers use with it. Learn more about uberSVN and get a free
download at: http://p.sf.net/sfu/wandisco-dev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-440) Multi-module build does not use bindings from referenced modules
[ https://jira.codehaus.org/browse/JIBX-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Corley resolved JIBX-440. - Resolution: Fixed Fix Version/s: JiBX 1.2.3 > Multi-module build does not use bindings from referenced modules > > > Key: JIBX-440 > URL: https://jira.codehaus.org/browse/JIBX-440 > Project: JiBX > Issue Type: Bug > Components: BindGen, maven plugin >Affects Versions: JiBX 1.2.3 >Reporter: Alexandros Karypidis >Assignee: Don Corley > Fix For: JiBX 1.2.3 > > Attachments: prj.zip > > > A maven project contains two modules (module1 and module2). Module1 contains > some bindings. Module2 contains some extra bindings, that build upon those of > module1. > In a multi-module build, one should only reference the bindings of module1. > However, it appears as if one must repeat them. > To reproduce, run "mvn process-classes" for the attached sample project. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-446) org.jibx.runtime.JiBXException: Expected "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS" end tag, found "{http://www.opentravel.org/OTA/2003/05}Succ
[
https://jira.codehaus.org/browse/JIBX-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-446.
-
Resolution: Fixed
> org.jibx.runtime.JiBXException: Expected
> "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS"; end tag, found
> "{http://www.opentravel.org/OTA/2003/05}Success"; start tag (line 2, col 126)
>
>
> Key: JIBX-446
> URL: https://jira.codehaus.org/browse/JIBX-446
> Project: JiBX
> Issue Type: Bug
> Components: CodeGen
>Affects Versions: JiBX 1.2.3
> Environment: Windows XP, Apache Ant 1.7, Tomcat 5.5, Java 5
>Reporter: Maulik Kayastha
>Assignee: Don Corley
>Priority: Blocker
> Labels: Jibx, exception, runtime
> Attachments: binding.xml, response.xml
>
>
> Hi,
> While unmarshalling response xml, I am getting exception as below -
> org.jibx.runtime.JiBXException: Expected
> "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS"; end tag, found
> "{http://www.opentravel.org/OTA/2003/05}Success"; start tag (line 2, col 126)
> I have attached binding.xml and response.xml(which I am trying to unmarshall)
> for the reference.
> code to unmarshall response document:
> private Object unmarshallJibxMessage(Document responseDocument) throws
> CommsException
>{
> DOMImplementationLS domImplementation =
> (DOMImplementationLS) responseDocument.getImplementation();
> LSSerializer lsSerializer = domImplementation.createLSSerializer();
> String xml = lsSerializer.writeToString(responseDocument);
> try
> {
> IBindingFactory factory =
> BindingDirectory.getFactory("binding",
> "org.jibx.opentravel.ota._2003._05");
> IUnmarshallingContext unMarshallingContext =
> factory.createUnmarshallingContext();
> unMarshallingContext.setDocument(new StringReader(xml));
> return unMarshallingContext.unmarshalElement();
> }
> catch (JiBXException e)
> {
> LOG.error("JIBX Unmarshalling Exception", e);
> throw new CommsException("JIBX Unmarshalling Exception", e);
> }
>}
> Please let me know if any further information is required.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-448) Add m2e marketplace enhancements to jibx-maven-plugin
[ https://jira.codehaus.org/browse/JIBX-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Corley resolved JIBX-448. - Resolution: Fixed Fix Version/s: JiBX 1.2.3 First attempt. Added basic functionality. > Add m2e marketplace enhancements to jibx-maven-plugin > - > > Key: JIBX-448 > URL: https://jira.codehaus.org/browse/JIBX-448 > Project: JiBX > Issue Type: New Feature >Reporter: Don Corley >Assignee: Don Corley > Fix For: JiBX 1.2.3 > > > Add m2e marketplace enhancements to jibx-maven-plugin > See: > http://wiki.eclipse.org/M2E_Extension_Development > wiki https://github.com/hwellmann/m2eclipse-extras/wiki > https://github.com/hwellmann/m2eclipse-extras/tree/master/p2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-445) Missing eclipse dependencies when running schema-codegen goal with custom classes
[
https://jira.codehaus.org/browse/JIBX-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-445.
-
Resolution: Fixed
No more eclipse dependencies.
> Missing eclipse dependencies when running schema-codegen goal with custom
> classes
> -
>
> Key: JIBX-445
> URL: https://jira.codehaus.org/browse/JIBX-445
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Jan De Moerloose
>Assignee: Don Corley
>
> When trying to run schema-codegen with a custom NameConverter, maven misses
> an eclipse dependency:
> 1) org.eclipse.core:runtime:jar:3.5.0
> I was able to make it run by adding the following dependencies manually:
>
> org.eclipse.equinox
> preferences
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.equinox.preferences_3.3.0.v20100503.jar
>
>
> org.eclipse.equinox
> common
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.equinox.common_3.6.0.v20100503.jar
>
>
> org.eclipse.core
> contenttype
> 3.4.1
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.contenttype_3.4.100.v20100505-1235.jar
>
>
> org.eclipse.core
> jobs
> 3.5.1
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.jobs_3.5.1.R36x_v20100824.jar
>
>
> org.eclipse.core
> resources
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.resources_3.6.0.R36x_v20100825-0600.jar
>
>
> org.eclipse.core
> runtime
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.runtime_3.6.0.v20100505.jar
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks & Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Created: (JIBX-448) Add m2e marketplace enhancements to jibx-maven-plugin
Add m2e marketplace enhancements to jibx-maven-plugin - Key: JIBX-448 URL: https://jira.codehaus.org/browse/JIBX-448 Project: JiBX Issue Type: New Feature Reporter: Don Corley Assignee: Don Corley Add m2e marketplace enhancements to jibx-maven-plugin See: http://wiki.eclipse.org/M2E_Extension_Development wiki https://github.com/hwellmann/m2eclipse-extras/wiki https://github.com/hwellmann/m2eclipse-extras/tree/master/p2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-446) org.jibx.runtime.JiBXException: Expected "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS" end tag, found "{http://www.opentravel.org/OTA/2003/05}Suc
[
https://jira.codehaus.org/browse/JIBX-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=273192#comment-273192
]
Don Corley commented on JIBX-446:
-
Maulik,
What version of the OTA spec are you using... 2010B, 2010A, etc? Are you using
the stock schema or are there any changes?
Can you attach your code... or even better create a very simplified project
that fails with the same error.
I would also recommend simplifying your response xml to isolate this problem.
Cheers,
Don
> org.jibx.runtime.JiBXException: Expected
> "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS"; end tag, found
> "{http://www.opentravel.org/OTA/2003/05}Success"; start tag (line 2, col 126)
>
>
> Key: JIBX-446
> URL: https://jira.codehaus.org/browse/JIBX-446
> Project: JiBX
> Issue Type: Bug
> Components: CodeGen
>Affects Versions: JiBX 1.2.3
> Environment: Windows XP, Apache Ant 1.7, Tomcat 5.5, Java 5
>Reporter: Maulik Kayastha
>Priority: Blocker
> Labels: Jibx, exception, runtime
> Attachments: binding.xml, response.xml
>
>
> Hi,
> While unmarshalling response xml, I am getting exception as below -
> org.jibx.runtime.JiBXException: Expected
> "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS"; end tag, found
> "{http://www.opentravel.org/OTA/2003/05}Success"; start tag (line 2, col 126)
> I have attached binding.xml and response.xml(which I am trying to unmarshall)
> for the reference.
> code to unmarshall response document:
> private Object unmarshallJibxMessage(Document responseDocument) throws
> CommsException
>{
> DOMImplementationLS domImplementation =
> (DOMImplementationLS) responseDocument.getImplementation();
> LSSerializer lsSerializer = domImplementation.createLSSerializer();
> String xml = lsSerializer.writeToString(responseDocument);
> try
> {
> IBindingFactory factory =
> BindingDirectory.getFactory("binding",
> "org.jibx.opentravel.ota._2003._05");
> IUnmarshallingContext unMarshallingContext =
> factory.createUnmarshallingContext();
> unMarshallingContext.setDocument(new StringReader(xml));
> return unMarshallingContext.unmarshalElement();
> }
> catch (JiBXException e)
> {
> LOG.error("JIBX Unmarshalling Exception", e);
> throw new CommsException("JIBX Unmarshalling Exception", e);
> }
>}
> Please let me know if any further information is required.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Assigned: (JIBX-446) org.jibx.runtime.JiBXException: Expected "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS" end tag, found "{http://www.opentravel.org/OTA/2003/05}Succ
[
https://jira.codehaus.org/browse/JIBX-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley reassigned JIBX-446:
---
Assignee: Don Corley
> org.jibx.runtime.JiBXException: Expected
> "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS"; end tag, found
> "{http://www.opentravel.org/OTA/2003/05}Success"; start tag (line 2, col 126)
>
>
> Key: JIBX-446
> URL: https://jira.codehaus.org/browse/JIBX-446
> Project: JiBX
> Issue Type: Bug
> Components: CodeGen
>Affects Versions: JiBX 1.2.3
> Environment: Windows XP, Apache Ant 1.7, Tomcat 5.5, Java 5
>Reporter: Maulik Kayastha
>Assignee: Don Corley
>Priority: Blocker
> Labels: Jibx, exception, runtime
> Attachments: binding.xml, response.xml
>
>
> Hi,
> While unmarshalling response xml, I am getting exception as below -
> org.jibx.runtime.JiBXException: Expected
> "{http://www.opentravel.org/OTA/2003/05}TH_PackageSearchRS"; end tag, found
> "{http://www.opentravel.org/OTA/2003/05}Success"; start tag (line 2, col 126)
> I have attached binding.xml and response.xml(which I am trying to unmarshall)
> for the reference.
> code to unmarshall response document:
> private Object unmarshallJibxMessage(Document responseDocument) throws
> CommsException
>{
> DOMImplementationLS domImplementation =
> (DOMImplementationLS) responseDocument.getImplementation();
> LSSerializer lsSerializer = domImplementation.createLSSerializer();
> String xml = lsSerializer.writeToString(responseDocument);
> try
> {
> IBindingFactory factory =
> BindingDirectory.getFactory("binding",
> "org.jibx.opentravel.ota._2003._05");
> IUnmarshallingContext unMarshallingContext =
> factory.createUnmarshallingContext();
> unMarshallingContext.setDocument(new StringReader(xml));
> return unMarshallingContext.unmarshalElement();
> }
> catch (JiBXException e)
> {
> LOG.error("JIBX Unmarshalling Exception", e);
> throw new CommsException("JIBX Unmarshalling Exception", e);
> }
>}
> Please let me know if any further information is required.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-439) Jibx bindings not compiling separately in a Maven Multi Module project
[ https://jira.codehaus.org/browse/JIBX-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Corley resolved JIBX-439. - Resolution: Fixed Fixed will be included in 1.2.4 code. > Jibx bindings not compiling separately in a Maven Multi Module project > -- > > Key: JIBX-439 > URL: https://jira.codehaus.org/browse/JIBX-439 > Project: JiBX > Issue Type: Bug >Reporter: Umang Singh >Assignee: Don Corley >Priority: Blocker > > I have a project which is split in service & web module. So there are three > poms. Now when we package the poms the TestNG test cases run fine but when we > try to individually run the test cases it gives binding exception as below : > Caused by: org.jibx.runtime.JiBXException: Unable to access binding > information for class com.hilton.search.ws.response.GeocodeResponse > Make sure the binding has been compiled > at > org.jibx.runtime.BindingDirectory.getBindingList(BindingDirectory.java:75) > at > org.jibx.runtime.BindingDirectory.getFactory(BindingDirectory.java:211) > at > com.hilton.search.ws.rest.JibxHttpMessageConverter.afterPropertiesSet(JibxHttpMessageConverter.java:106) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1469) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1409) > ... 83 more > Caused by: java.lang.NoSuchFieldException: JiBX_bindingList > at java.lang.Class.getDeclaredField(Unknown Source) > at > org.jibx.runtime.BindingDirectory.getBindingList(BindingDirectory.java:68) > The Binding compiler plugin & its configuration is in service pom & the class > is also in the service module so this should not be an issue. > Could somebody help me on this as early as possible -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-445) Missing eclipse dependencies when running schema-codegen goal with custom classes
[
https://jira.codehaus.org/browse/JIBX-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=273190#comment-273190
]
Don Corley commented on JIBX-445:
-
Jan,
I've removed the eclipse dependencies from the jibx-maven-plugin and deployed
the new code to the maven snapshot repository. I'm pretty sure this code was
there to fix a very old eclipse OSGi dependency conflict.
This should fix your problem since I removed all the eclipse dependencies from
the jibx plugin.
Please give it a shot and see this fixes your problems.
To use the snapshot version, just change your jibx (plugin and dependency)
versions from 1.2.3 to 1.2.4-SNAPSHOT and include this xml in your maven
project file:
sonatype-snapshots
http://oss.sonatype.org/content/repositories/snapshots/
If this works, please close this bug!
Thanks,
Don
> Missing eclipse dependencies when running schema-codegen goal with custom
> classes
> -
>
> Key: JIBX-445
> URL: https://jira.codehaus.org/browse/JIBX-445
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Jan De Moerloose
>Assignee: Don Corley
>
> When trying to run schema-codegen with a custom NameConverter, maven misses
> an eclipse dependency:
> 1) org.eclipse.core:runtime:jar:3.5.0
> I was able to make it run by adding the following dependencies manually:
>
> org.eclipse.equinox
> preferences
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.equinox.preferences_3.3.0.v20100503.jar
>
>
> org.eclipse.equinox
> common
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.equinox.common_3.6.0.v20100503.jar
>
>
> org.eclipse.core
> contenttype
> 3.4.1
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.contenttype_3.4.100.v20100505-1235.jar
>
>
> org.eclipse.core
> jobs
> 3.5.1
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.jobs_3.5.1.R36x_v20100824.jar
>
>
> org.eclipse.core
> resources
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.resources_3.6.0.R36x_v20100825-0600.jar
>
>
> org.eclipse.core
> runtime
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.runtime_3.6.0.v20100505.jar
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Assigned: (JIBX-445) Missing eclipse dependencies when running schema-codegen goal with custom classes
[
https://jira.codehaus.org/browse/JIBX-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley reassigned JIBX-445:
---
Assignee: Don Corley
> Missing eclipse dependencies when running schema-codegen goal with custom
> classes
> -
>
> Key: JIBX-445
> URL: https://jira.codehaus.org/browse/JIBX-445
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Jan De Moerloose
>Assignee: Don Corley
>
> When trying to run schema-codegen with a custom NameConverter, maven misses
> an eclipse dependency:
> 1) org.eclipse.core:runtime:jar:3.5.0
> I was able to make it run by adding the following dependencies manually:
>
> org.eclipse.equinox
> preferences
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.equinox.preferences_3.3.0.v20100503.jar
>
>
> org.eclipse.equinox
> common
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.equinox.common_3.6.0.v20100503.jar
>
>
> org.eclipse.core
> contenttype
> 3.4.1
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.contenttype_3.4.100.v20100505-1235.jar
>
>
> org.eclipse.core
> jobs
> 3.5.1
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.jobs_3.5.1.R36x_v20100824.jar
>
>
> org.eclipse.core
> resources
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.resources_3.6.0.R36x_v20100825-0600.jar
>
>
> org.eclipse.core
> runtime
> 3.6.0
> system
>
> ${eclipse.home}/plugins/org.eclipse.core.runtime_3.6.0.v20100505.jar
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-416) Plugin dependency resolving fails
[
http://jira.codehaus.org/browse/JIBX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270695#comment-270695
]
Don Corley commented on JIBX-416:
-
Venn,
I'm stumped. I've always wondered why there are eclipse dependencies in the
maven plugin. I've always been reluctant to remove them and break something.
Does anyone have any ideas why these dependencies are here? I rewrote the
jibx-maven-plugin and there were never any eclipse calls in the code.
I'll check with our eclipse plugin author and if he agrees, and no one objects,
I'm going to remove this dependency altogether. If it tests out okay for me,
I'll deploy a snapshot for everyone to try.
Thanks,
Don
> Plugin dependency resolving fails
> -
>
> Key: JIBX-416
> URL: http://jira.codehaus.org/browse/JIBX-416
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2
>Reporter: Antti Koivisto
>Assignee: Don Corley
> Fix For: JiBX 1.2.3
>
> Attachments: maven-jibx-plugin-problematic-build-log-cleaned.txt.txt
>
>
> I'm having a really hard time using the maven jibx plugin. Initially I got
> this same build failure in W7 with Maven 3, but it went away.
> In our Bamboo environment that uses Maven 2, the problem persists:
> {code}
> Missing:
> --
> 1) org.eclipse.equinox:registry:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.equinox:registry:jar:3.3.1
> 2) org.eclipse.core:resources:jar:3.4.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:resources:jar:3.4.0
> 3) org.eclipse.core:jobs:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.core:jobs:jar:3.3.1
> 4) org.eclipse.core:commands:jar:3.3.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=commands -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=commands
> -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse:text:jar:3.3.0-v20070606-0010
> 4) org.eclipse.core:commands:jar:3.3.0
> 5) org.eclipse:osgi:jar:3.3.2
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse -Dart
[jibx-devs] [jira] Commented: (JIBX-440) Multi-module build does not use bindings from referenced modules
[ http://jira.codehaus.org/browse/JIBX-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267065#action_267065 ] Don Corley commented on JIBX-440: - Alexandros, First, thank you very much for spending the time to include an example. Since you are getting an error on the command line, you probably have an error in your binding file. I looked through the JiBX examples and the documentation and I can't seem to find a sample with a pre-compiled base class. Sorry, but I'm not an expert on JiBX bindings, I maintain the maven plugin. I was assigned your bug since the description seemed like the problem was with the maven plug-in. Can you repost your question in the JiBX user list. You can ask for the correct binding file syntax to include a pre-compiled jibx binding class. Include the example that you posted for me. I'm sure somebody here can help you. Don > Multi-module build does not use bindings from referenced modules > > > Key: JIBX-440 > URL: http://jira.codehaus.org/browse/JIBX-440 > Project: JiBX > Issue Type: Bug > Components: BindGen, maven plugin >Affects Versions: JiBX 1.2.3 >Reporter: Alexandros Karypidis >Assignee: Don Corley > Attachments: prj.zip > > > A maven project contains two modules (module1 and module2). Module1 contains > some bindings. Module2 contains some extra bindings, that build upon those of > module1. > In a multi-module build, one should only reference the bindings of module1. > However, it appears as if one must repeat them. > To reproduce, run "mvn process-classes" for the attached sample project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-440) Multi-module build does not use bindings from referenced modules
[ http://jira.codehaus.org/browse/JIBX-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266956#action_266956 ] Don Corley commented on JIBX-440: - Alexandros, Does this project work when you execute from the command line? (ie., java -jar jibx-bind.jar ...) Don > Multi-module build does not use bindings from referenced modules > > > Key: JIBX-440 > URL: http://jira.codehaus.org/browse/JIBX-440 > Project: JiBX > Issue Type: Bug > Components: BindGen, maven plugin >Affects Versions: JiBX 1.2.3 >Reporter: Alexandros Karypidis >Assignee: Don Corley > Attachments: prj.zip > > > A maven project contains two modules (module1 and module2). Module1 contains > some bindings. Module2 contains some extra bindings, that build upon those of > module1. > In a multi-module build, one should only reference the bindings of module1. > However, it appears as if one must repeat them. > To reproduce, run "mvn process-classes" for the attached sample project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Assigned: (JIBX-440) Multi-module build does not use bindings from referenced modules
[ http://jira.codehaus.org/browse/JIBX-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Corley reassigned JIBX-440: --- Assignee: Don Corley > Multi-module build does not use bindings from referenced modules > > > Key: JIBX-440 > URL: http://jira.codehaus.org/browse/JIBX-440 > Project: JiBX > Issue Type: Bug > Components: BindGen, maven plugin >Affects Versions: JiBX 1.2.3 >Reporter: Alexandros Karypidis >Assignee: Don Corley > Attachments: prj.zip > > > A maven project contains two modules (module1 and module2). Module1 contains > some bindings. Module2 contains some extra bindings, that build upon those of > module1. > In a multi-module build, one should only reference the bindings of module1. > However, it appears as if one must repeat them. > To reproduce, run "mvn process-classes" for the attached sample project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-439) Jibx bindings not compiling separately in a Maven Multi Module project
[ http://jira.codehaus.org/browse/JIBX-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266921#action_266921 ] Don Corley commented on JIBX-439: - Umang, There was a multi-module bug (JIBX-431) that was filed and fixed recently. Can you try your code with the latest version of JiBX: svn co https://jibx.svn.sourceforge.net/svnroot/jibx/trunk/plugins/maven-plugin/jibx-maven-plugin cd jibx-maven-plugin mvn install Remember to change your plugin name to jibx-maven-plugin (from maven-jibx-plugin) and update the revision number to 1.2.4-SNAPSHOT. jibx-maven-plugin is the new plugin name. Remember to build multi-module project from the parent project. You may also want to take a look at: http://jibx.sourceforge.net/jibx-maven-plugin/modular-codegen.html In 1.2.3 a new (easier) multi-module build procedure was introduced. If you can't get this to work, email me back and I'll release a bugfix (1.2.3.1) version. Don > Jibx bindings not compiling separately in a Maven Multi Module project > -- > > Key: JIBX-439 > URL: http://jira.codehaus.org/browse/JIBX-439 > Project: JiBX > Issue Type: Bug >Reporter: Umang Singh >Assignee: Don Corley >Priority: Blocker > > I have a project which is split in service & web module. So there are three > poms. Now when we package the poms the TestNG test cases run fine but when we > try to individually run the test cases it gives binding exception as below : > Caused by: org.jibx.runtime.JiBXException: Unable to access binding > information for class com.hilton.search.ws.response.GeocodeResponse > Make sure the binding has been compiled > at > org.jibx.runtime.BindingDirectory.getBindingList(BindingDirectory.java:75) > at > org.jibx.runtime.BindingDirectory.getFactory(BindingDirectory.java:211) > at > com.hilton.search.ws.rest.JibxHttpMessageConverter.afterPropertiesSet(JibxHttpMessageConverter.java:106) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1469) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1409) > ... 83 more > Caused by: java.lang.NoSuchFieldException: JiBX_bindingList > at java.lang.Class.getDeclaredField(Unknown Source) > at > org.jibx.runtime.BindingDirectory.getBindingList(BindingDirectory.java:68) > The Binding compiler plugin & its configuration is in service pom & the class > is also in the service module so this should not be an issue. > Could somebody help me on this as early as possible -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Assigned: (JIBX-439) Jibx bindings not compiling separately in a Maven Multi Module project
[ http://jira.codehaus.org/browse/JIBX-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Corley reassigned JIBX-439: --- Assignee: Don Corley > Jibx bindings not compiling separately in a Maven Multi Module project > -- > > Key: JIBX-439 > URL: http://jira.codehaus.org/browse/JIBX-439 > Project: JiBX > Issue Type: Bug >Reporter: Umang Singh >Assignee: Don Corley >Priority: Blocker > > I have a project which is split in service & web module. So there are three > poms. Now when we package the poms the TestNG test cases run fine but when we > try to individually run the test cases it gives binding exception as below : > Caused by: org.jibx.runtime.JiBXException: Unable to access binding > information for class com.hilton.search.ws.response.GeocodeResponse > Make sure the binding has been compiled > at > org.jibx.runtime.BindingDirectory.getBindingList(BindingDirectory.java:75) > at > org.jibx.runtime.BindingDirectory.getFactory(BindingDirectory.java:211) > at > com.hilton.search.ws.rest.JibxHttpMessageConverter.afterPropertiesSet(JibxHttpMessageConverter.java:106) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1469) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1409) > ... 83 more > Caused by: java.lang.NoSuchFieldException: JiBX_bindingList > at java.lang.Class.getDeclaredField(Unknown Source) > at > org.jibx.runtime.BindingDirectory.getBindingList(BindingDirectory.java:68) > The Binding compiler plugin & its configuration is in service pom & the class > is also in the service module so this should not be an issue. > Could somebody help me on this as early as possible -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-416) Plugin dependency resolving fails
[
http://jira.codehaus.org/browse/JIBX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-416.
-
Resolution: Fixed
Fix Version/s: JiBX 1.2.3
Upgrading to 1.2.3 will fix this.
> Plugin dependency resolving fails
> -
>
> Key: JIBX-416
> URL: http://jira.codehaus.org/browse/JIBX-416
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2
>Reporter: Antti Koivisto
>Assignee: Don Corley
> Fix For: JiBX 1.2.3
>
> Attachments: maven-jibx-plugin-problematic-build-log-cleaned.txt.txt
>
>
> I'm having a really hard time using the maven jibx plugin. Initially I got
> this same build failure in W7 with Maven 3, but it went away.
> In our Bamboo environment that uses Maven 2, the problem persists:
> {code}
> Missing:
> --
> 1) org.eclipse.equinox:registry:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.equinox:registry:jar:3.3.1
> 2) org.eclipse.core:resources:jar:3.4.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:resources:jar:3.4.0
> 3) org.eclipse.core:jobs:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.core:jobs:jar:3.3.1
> 4) org.eclipse.core:commands:jar:3.3.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=commands -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=commands
> -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse:text:jar:3.3.0-v20070606-0010
> 4) org.eclipse.core:commands:jar:3.3.0
> 5) org.eclipse:osgi:jar:3.3.2
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse:osgi:jar:3.3.2
> --
> 5 required artifacts are missing.
> for artifact:
> org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> from the specified rem
[jibx-devs] [jira] Resolved: (JIBX-415) schema-codegen does not work if module is built in an "also-make" way or from a multimodule parent
[
http://jira.codehaus.org/browse/JIBX-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-415.
-
Resolution: Fixed
Fix Version/s: JiBX 1.2.3
1.2.3 has fixed this issue.
> schema-codegen does not work if module is built in an "also-make" way or from
> a multimodule parent
> --
>
> Key: JIBX-415
> URL: http://jira.codehaus.org/browse/JIBX-415
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.1
> Environment: Windows 7, Maven 3.0.2
>Reporter: Antti Koivisto
>Assignee: Don Corley
> Fix For: JiBX 1.2.3
>
>
> I have a multi module project like this:
> * A
> ** A.I
> *** A.I.OXM
> *** A.I.COMMON
> The A.I.OXM module contains the following:
> {code}
>
>
>
> org.jibx
> maven-jibx-plugin
>
>
> generate-java-code-from-schema
>
> schema-codegen
>
>
>
>
> src/main/resources/jibx
> foo.bar
>
>
>
>
> compile-binding
>
> bind
>
>
> target/generated-sources
> true
> true
> true
> true
>
>
>
>
>
>
> {code}
> If I build the A.I.OXM module by going into it and issuing "mvn clean
> install", the codes are generated correctly and the jar file installed to
> local maven repo contains the generated sources.
> But if I go into module A and do a "mvn clean install
> --projects=A.I/A.I.COMMON --also-make" the A.I.OXM module is not built
> properly. The xsd schema file available in the specified directory is not
> picked up.
> Also doing a "mvn clean install" in the A module has the same effect.
> A solution to this problem seems to be to remove the option and
> use the default location.
> When I did this, all three ways of building the module were successful.
> The problem might be mostly with documentation that used
> src/something as an example. Should it have some maven
> property references too?
> My environment is:
> Apache Maven 3.0.2 (r1056850; 2011-01-09 02:58:10+0200)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> Java home: C:\java\jdk6u23\jre
> Default locale: fi_FI, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Closed: (JIBX-431) multi-module builds - jibx maven plugin breaks between version 1.2.2 and 1.2.3
[
http://jira.codehaus.org/browse/JIBX-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley closed JIBX-431.
---
Resolution: Fixed
Fix Version/s: JiBX 1.2.3
Fixed.
> multi-module builds - jibx maven plugin breaks between version 1.2.2 and 1.2.3
> --
>
> Key: JIBX-431
> URL: http://jira.codehaus.org/browse/JIBX-431
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Don Corley
>Assignee: Don Corley
> Fix For: JiBX 1.2.3
>
>
> Date: Tue, 15 Mar 2011 17:13:15 -0700
> From: Frank Mena
> Subject: [jibx-users] jibx maven plugin breaks between version 1.2.2
>and 1.2.3
> To: jibx-us...@lists.sourceforge.net
> Message-ID:
>
> Content-Type: text/plain; charset="iso-8859-1"
> Hi Dennis, long time no speak. I was the original author of the plugin
> collaborating with Andreas back in 2005.
> Here is my setup:
> project common:some bindings
> project dbmodel:some bindings
> project service: some bindings
> project web: no bindings, jibx plugin
> Here is the plugin in the web pom:
>
> org.jibx
> maven-jibx-plugin
> ${jibx.version}
>
>
> process-classes
>
>bind
>
>
>
>
>true
>src/main/config
>
> *.jibx.xml
>
>
>
> This works perfectly with version 1.2.2, but version 1.2.3 says:
> Not running JiBX binding compiler (multi-module mode) - no binding files
> I have tried every combination of changing to restricted mode:
>
> com.noledgy.appryse:common
> com.noledgy.appryse:dbmodel
> com.noledgy.appryse:service
>
> and the new syntax:
>
>com.example:example1
>com.example:example2
>
> but nothing works. What's wrong?
> Frank Mena
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-431) multi-module builds - jibx maven plugin breaks between version 1.2.2 and 1.2.3
[
http://jira.codehaus.org/browse/JIBX-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260765#action_260765
]
Don Corley commented on JIBX-431:
-
Frank,
Fixed legacy multi-module build.
git commit: 0ef1fd9ab4429815ecfd0bdb02518d434c531239
Close this bug if this works now.
Thanks,
Don
> multi-module builds - jibx maven plugin breaks between version 1.2.2 and 1.2.3
> --
>
> Key: JIBX-431
> URL: http://jira.codehaus.org/browse/JIBX-431
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Don Corley
>Assignee: Don Corley
>
> Date: Tue, 15 Mar 2011 17:13:15 -0700
> From: Frank Mena
> Subject: [jibx-users] jibx maven plugin breaks between version 1.2.2
>and 1.2.3
> To: jibx-us...@lists.sourceforge.net
> Message-ID:
>
> Content-Type: text/plain; charset="iso-8859-1"
> Hi Dennis, long time no speak. I was the original author of the plugin
> collaborating with Andreas back in 2005.
> Here is my setup:
> project common:some bindings
> project dbmodel:some bindings
> project service: some bindings
> project web: no bindings, jibx plugin
> Here is the plugin in the web pom:
>
> org.jibx
> maven-jibx-plugin
> ${jibx.version}
>
>
> process-classes
>
>bind
>
>
>
>
>true
>src/main/config
>
> *.jibx.xml
>
>
>
> This works perfectly with version 1.2.2, but version 1.2.3 says:
> Not running JiBX binding compiler (multi-module mode) - no binding files
> I have tried every combination of changing to restricted mode:
>
> com.noledgy.appryse:common
> com.noledgy.appryse:dbmodel
> com.noledgy.appryse:service
>
> and the new syntax:
>
>com.example:example1
>com.example:example2
>
> but nothing works. What's wrong?
> Frank Mena
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-431) multi-module builds - jibx maven plugin breaks between version 1.2.2 and 1.2.3
[
http://jira.codehaus.org/browse/JIBX-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260639#action_260639
]
Don Corley commented on JIBX-431:
-
Yep, I broke it.
I changed the file scanner from apache oro to plexus, since oro was retired by
Apache. In the process I broke multi-module mode.
I should be able to fix this.
Note: I did add a new multi-module capability in 1.2.3 that does not require a
build to be run on the shared parent.
> multi-module builds - jibx maven plugin breaks between version 1.2.2 and 1.2.3
> --
>
> Key: JIBX-431
> URL: http://jira.codehaus.org/browse/JIBX-431
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
>Reporter: Don Corley
>Assignee: Don Corley
>
> Date: Tue, 15 Mar 2011 17:13:15 -0700
> From: Frank Mena
> Subject: [jibx-users] jibx maven plugin breaks between version 1.2.2
>and 1.2.3
> To: jibx-us...@lists.sourceforge.net
> Message-ID:
>
> Content-Type: text/plain; charset="iso-8859-1"
> Hi Dennis, long time no speak. I was the original author of the plugin
> collaborating with Andreas back in 2005.
> Here is my setup:
> project common:some bindings
> project dbmodel:some bindings
> project service: some bindings
> project web: no bindings, jibx plugin
> Here is the plugin in the web pom:
>
> org.jibx
> maven-jibx-plugin
> ${jibx.version}
>
>
> process-classes
>
>bind
>
>
>
>
>true
>src/main/config
>
> *.jibx.xml
>
>
>
> This works perfectly with version 1.2.2, but version 1.2.3 says:
> Not running JiBX binding compiler (multi-module mode) - no binding files
> I have tried every combination of changing to restricted mode:
>
> com.noledgy.appryse:common
> com.noledgy.appryse:dbmodel
> com.noledgy.appryse:service
>
> and the new syntax:
>
>com.example:example1
>com.example:example2
>
> but nothing works. What's wrong?
> Frank Mena
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Created: (JIBX-431) multi-module builds - jibx maven plugin breaks between version 1.2.2 and 1.2.3
multi-module builds - jibx maven plugin breaks between version 1.2.2 and 1.2.3
--
Key: JIBX-431
URL: http://jira.codehaus.org/browse/JIBX-431
Project: JiBX
Issue Type: Bug
Components: maven plugin
Affects Versions: JiBX 1.2.3
Reporter: Don Corley
Assignee: Don Corley
Date: Tue, 15 Mar 2011 17:13:15 -0700
From: Frank Mena
Subject: [jibx-users] jibx maven plugin breaks between version 1.2.2
and 1.2.3
To: jibx-us...@lists.sourceforge.net
Message-ID:
Content-Type: text/plain; charset="iso-8859-1"
Hi Dennis, long time no speak. I was the original author of the plugin
collaborating with Andreas back in 2005.
Here is my setup:
project common:some bindings
project dbmodel:some bindings
project service: some bindings
project web: no bindings, jibx plugin
Here is the plugin in the web pom:
org.jibx
maven-jibx-plugin
${jibx.version}
process-classes
bind
true
src/main/config
*.jibx.xml
This works perfectly with version 1.2.2, but version 1.2.3 says:
Not running JiBX binding compiler (multi-module mode) - no binding files
I have tried every combination of changing to restricted mode:
com.noledgy.appryse:common
com.noledgy.appryse:dbmodel
com.noledgy.appryse:service
and the new syntax:
com.example:example1
com.example:example2
but nothing works. What's wrong?
Frank Mena
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-429) Directory issue when configuring the plugin using ${project.basedir}... in a windows environment
[
http://jira.codehaus.org/browse/JIBX-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-429.
-
Resolution: Fixed
Fix Version/s: JiBX 1.2.3
Dave,
I found a nice method that should fix this bug for any platform.
Give it a try and close this bug if this fixes your problem.
The bugfix is in this commit:
git commit: 193ba70710d71133813fe59656e28bc82cd809ae
I have deployed the new code to the sonatype snapshop repository.
If you don't know how to use the snapshot repo, just download the jar file
directly:
https://oss.sonatype.org/content/repositories/snapshots/org/jibx/
The actual file that you need is here:
https://oss.sonatype.org/content/repositories/snapshots/org/jibx/jibx-maven-plugin/1.2.4-SNAPSHOT/jibx-maven-plugin-1.2.4-20110317.142136-1.jar
Just rename this file to jibx-maven-plugin-1.2.3 and replace this file with the
one in your local maven repository... someplace like:
C:\Documents and
Settings\[yourusername]\.m2\repository\org\jibx\jibx-maven-plugin\1.2.3\jibx-maven-plugin-1.2.3
Remember to use the new maven plugin name:
jibx-maven-plugin
not
maven-jibx-plugin
Also, use the new parameter names:
${project.basedir}/src/test/resources/org/jibx/test/jibx
binding.xml
not
Thanks,
Don
> Directory issue when configuring the plugin using ${project.basedir}... in a
> windows environment
>
>
> Key: JIBX-429
> URL: http://jira.codehaus.org/browse/JIBX-429
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
> Environment: Windows 7, Java JDK 1.6.0_24, Maven 3.0.3
>Reporter: David Wolff
>Assignee: Don Corley
>Priority: Minor
> Fix For: JiBX 1.2.3
>
>
> I had a booger of a time getting the plugin to work because I was specifying
> an absolute path (by putting ${project.basedir} on the front of my relative
> path) in the element. The code in
> AbstractJibxMojo.getFullPath(String dir)... looks to see if the path
> specified is absolute by checking for a file separator at the beginning.
> This works great for linux style file systems but bombs for windows
> : type entries.
> Example:
> ---
> My config was as follows:
> ${project.basedir}/src/main/resources/schema
> The directory that the JiBX maven plugin ended up searching for my binding
> files was
> "D:/dev/java/myprojectD:/dev/java/myproject/src/main/resources/schema", which
> is obviously an invalid directory, because the mojo was presuming the path
> was relative and prepended another project base directory to the front. This
> naturally resulted in zero binding files found and no JiBX bytecode
> enhancement.
> ---
> The mojo works great when I specify a relative path (e.g.
> src/main/resources/schema) however, I
> think it should work when I have {$project.basedir} on the front as well. I
> wasted a tremendous amount of time trying to determine what the problem was
> when my configuration was more or less correct.
> Many thanks in advance for a fix for this :)
> Dave Wolff
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Assigned: (JIBX-429) Directory issue when configuring the plugin using ${project.basedir}... in a windows environment
[
http://jira.codehaus.org/browse/JIBX-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley reassigned JIBX-429:
---
Assignee: Don Corley
> Directory issue when configuring the plugin using ${project.basedir}... in a
> windows environment
>
>
> Key: JIBX-429
> URL: http://jira.codehaus.org/browse/JIBX-429
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.3
> Environment: Windows 7, Java JDK 1.6.0_24, Maven 3.0.3
>Reporter: David Wolff
>Assignee: Don Corley
>Priority: Minor
>
> I had a booger of a time getting the plugin to work because I was specifying
> an absolute path (by putting ${project.basedir} on the front of my relative
> path) in the element. The code in
> AbstractJibxMojo.getFullPath(String dir)... looks to see if the path
> specified is absolute by checking for a file separator at the beginning.
> This works great for linux style file systems but bombs for windows
> : type entries.
> Example:
> ---
> My config was as follows:
> ${project.basedir}/src/main/resources/schema
> The directory that the JiBX maven plugin ended up searching for my binding
> files was
> "D:/dev/java/myprojectD:/dev/java/myproject/src/main/resources/schema", which
> is obviously an invalid directory, because the mojo was presuming the path
> was relative and prepended another project base directory to the front. This
> naturally resulted in zero binding files found and no JiBX bytecode
> enhancement.
> ---
> The mojo works great when I specify a relative path (e.g.
> src/main/resources/schema) however, I
> think it should work when I have {$project.basedir} on the front as well. I
> wasted a tremendous amount of time trying to determine what the problem was
> when my configuration was more or less correct.
> Many thanks in advance for a fix for this :)
> Dave Wolff
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Resolved: (JIBX-422) NullPointerExceptions and wrong paths when using the JiBX Maven plugin
[
http://jira.codehaus.org/browse/JIBX-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-422.
-
Resolution: Cannot Reproduce
Assignee: Dennis Sosnoski (was: Don Corley)
Johann,
I'm going to reassign this bug to Dennis for now.
He is the JiBX core project owner and your patches are in his project.
Perhaps he will be able to recognize the bug that you describe without a test
case and apply your patches.
Sorry,
Don
> NullPointerExceptions and wrong paths when using the JiBX Maven plugin
> --
>
> Key: JIBX-422
> URL: http://jira.codehaus.org/browse/JIBX-422
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2, JiBX 1.2.3
> Environment: Ubuntu Linux, Maven 3 something
>Reporter: Johann Burkard
>Assignee: Dennis Sosnoski
>
> I have been trying to get the Maven-JiBX plugin to work on a project I work
> on. The binding files are in src/main/binding
> With maven-jibx-plugin 1.2.3, jibx-run 1.2.2 and jibx-extras 1.2.2 in the
> dependencies, I get:
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.jibx.binding.classes.MungedClass.checkDirectory(MungedClass.java:238)
> at org.jibx.binding.classes.BoundClass.getInstance(BoundClass.java:405)
> at org.jibx.binding.classes.BoundClass.getInstance(BoundClass.java:443)
> at org.jibx.binding.def.ObjectBinding.(ObjectBinding.java:294)
> {code}
> With maven-jibx-plugin 1.2.2, jibx-run 1.2.2 and jibx-extras 1.2.2 in the
> dependencies, I get:
> {code}
> Caused by: java.io.FileNotFoundException:
> .../.hudson/jobs//workspace//target/classes/config//bindings//JiBX_binding__request_commonFactory.class
> (No such file or directory)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at org.jibx.binding.classes.ClassFile.writeFile(ClassFile.java:1999)
> at
> org.jibx.binding.classes.MungedClass.writeChanges(MungedClass.java:424)
> {code}
> Note that /target/classes/config? Shouldn't that be /target/classes?
> Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-422) NullPointerExceptions and wrong paths when using the JiBX Maven plugin
[
http://jira.codehaus.org/browse/JIBX-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258137#action_258137
]
Don Corley commented on JIBX-422:
-
Johann,
I really need an example of this failure before I can apply your patch.
I don't need your employer's code, just make a small sample project that only
contains this failure.
To give you an example, here are two bug reports that I filed with another
contributor on JiBX:
http://jira.codehaus.org/browse/JIBX-419
http://jira.codehaus.org/browse/JIBX-420
You will notice that the examples that I included in these bug reports are tiny
projects with instructions on creating the failure. The actual project that
failed is way too complicated to submit as a example.
I know it takes more time, but I need to be able to replicate the problem
before I can fix it.
Thanks,
Don
> NullPointerExceptions and wrong paths when using the JiBX Maven plugin
> --
>
> Key: JIBX-422
> URL: http://jira.codehaus.org/browse/JIBX-422
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2, JiBX 1.2.3
> Environment: Ubuntu Linux, Maven 3 something
>Reporter: Johann Burkard
>Assignee: Don Corley
>
> I have been trying to get the Maven-JiBX plugin to work on a project I work
> on. The binding files are in src/main/binding
> With maven-jibx-plugin 1.2.3, jibx-run 1.2.2 and jibx-extras 1.2.2 in the
> dependencies, I get:
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.jibx.binding.classes.MungedClass.checkDirectory(MungedClass.java:238)
> at org.jibx.binding.classes.BoundClass.getInstance(BoundClass.java:405)
> at org.jibx.binding.classes.BoundClass.getInstance(BoundClass.java:443)
> at org.jibx.binding.def.ObjectBinding.(ObjectBinding.java:294)
> {code}
> With maven-jibx-plugin 1.2.2, jibx-run 1.2.2 and jibx-extras 1.2.2 in the
> dependencies, I get:
> {code}
> Caused by: java.io.FileNotFoundException:
> .../.hudson/jobs//workspace//target/classes/config//bindings//JiBX_binding__request_commonFactory.class
> (No such file or directory)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at org.jibx.binding.classes.ClassFile.writeFile(ClassFile.java:1999)
> at
> org.jibx.binding.classes.MungedClass.writeChanges(MungedClass.java:424)
> {code}
> Note that /target/classes/config? Shouldn't that be /target/classes?
> Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Updated: (JIBX-419) Inconsistent classpaths when using a base binding file in CodeGen
[ http://jira.codehaus.org/browse/JIBX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Corley updated JIBX-419: Attachment: codegen.patch This patch should fix the problem. The first two lines are optional, they say if the binding location is relative, make it relative to the target dir. The second two lines fix this bug. If the binding file location is at or below the target directory, don't include the target directory name. Dennis... nice code; easy to understand. Better than my code. Don > Inconsistent classpaths when using a base binding file in CodeGen > - > > Key: JIBX-419 > URL: http://jira.codehaus.org/browse/JIBX-419 > Project: JiBX > Issue Type: Bug > Components: CodeGen >Affects Versions: JiBX 1.2.2 > Environment: Java 1.6 >Reporter: Don Corley >Assignee: Dennis Sosnoski > Attachments: codegen.patch, test.zip > > > Dennis, > I'm having a problem using codegen with based binding (which I need for the > schema-library). > Since I'm calling codegen from java, I can't change the classpath or my > current directory and I can only specify relative paths. > I have to use -t (target dir) which specifies the source and binding file > location. -i requires a path from my working location, but the generated > binding file ends up specifying the this link to the base binding file as > relative to the compile root. > Just unzip this file, change line 1 to point to your core/lib and run it... > it fails on the third codegen. > Take a look at the in person-binding.xml > Thanks, > Don > My test schema looks like this > person.xsd <- address.xsd <- company.xsd -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-422) NullPointerExceptions and wrong paths when using the JiBX Maven plugin
[
http://jira.codehaus.org/browse/JIBX-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257152#action_257152
]
Don Corley commented on JIBX-422:
-
Johann,
Can you try this with maven-jibx-plugin 1.2.3, jibx-run 1.2.3 and jibx-extras
1.2.3 in the dependencies.
If you could attach a sample project, it would be very helpful.
Thanks,
Don
> NullPointerExceptions and wrong paths when using the JiBX Maven plugin
> --
>
> Key: JIBX-422
> URL: http://jira.codehaus.org/browse/JIBX-422
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2, JiBX 1.2.3
> Environment: Ubuntu Linux, Maven 3 something
>Reporter: Johann Burkard
>Assignee: Don Corley
>
> I have been trying to get the Maven-JiBX plugin to work on a project I work
> on. The binding files are in src/main/binding
> With maven-jibx-plugin 1.2.3, jibx-run 1.2.2 and jibx-extras 1.2.2 in the
> dependencies, I get:
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.jibx.binding.classes.MungedClass.checkDirectory(MungedClass.java:238)
> at org.jibx.binding.classes.BoundClass.getInstance(BoundClass.java:405)
> at org.jibx.binding.classes.BoundClass.getInstance(BoundClass.java:443)
> at org.jibx.binding.def.ObjectBinding.(ObjectBinding.java:294)
> {code}
> With maven-jibx-plugin 1.2.2, jibx-run 1.2.2 and jibx-extras 1.2.2 in the
> dependencies, I get:
> {code}
> Caused by: java.io.FileNotFoundException:
> .../.hudson/jobs//workspace//target/classes/config//bindings//JiBX_binding__request_commonFactory.class
> (No such file or directory)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at org.jibx.binding.classes.ClassFile.writeFile(ClassFile.java:1999)
> at
> org.jibx.binding.classes.MungedClass.writeChanges(MungedClass.java:424)
> {code}
> Note that /target/classes/config? Shouldn't that be /target/classes?
> Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Index, Search & Analyze Logs and other IT data in Real-Time with Splunk
Collect, index and harness all the fast moving IT data generated by your
applications, servers and devices whether physical, virtual or in the cloud.
Deliver compliance at lower cost and gain new business insights.
Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Assigned: (JIBX-422) NullPointerExceptions and wrong paths when using the JiBX Maven plugin
[
http://jira.codehaus.org/browse/JIBX-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley reassigned JIBX-422:
---
Assignee: Don Corley
> NullPointerExceptions and wrong paths when using the JiBX Maven plugin
> --
>
> Key: JIBX-422
> URL: http://jira.codehaus.org/browse/JIBX-422
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2, JiBX 1.2.3
> Environment: Ubuntu Linux, Maven 3 something
>Reporter: Johann Burkard
>Assignee: Don Corley
>
> I have been trying to get the Maven-JiBX plugin to work on a project I work
> on. The binding files are in src/main/binding
> With maven-jibx-plugin 1.2.3, jibx-run 1.2.2 and jibx-extras 1.2.2 in the
> dependencies, I get:
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.jibx.binding.classes.MungedClass.checkDirectory(MungedClass.java:238)
> at org.jibx.binding.classes.BoundClass.getInstance(BoundClass.java:405)
> at org.jibx.binding.classes.BoundClass.getInstance(BoundClass.java:443)
> at org.jibx.binding.def.ObjectBinding.(ObjectBinding.java:294)
> {code}
> With maven-jibx-plugin 1.2.2, jibx-run 1.2.2 and jibx-extras 1.2.2 in the
> dependencies, I get:
> {code}
> Caused by: java.io.FileNotFoundException:
> .../.hudson/jobs//workspace//target/classes/config//bindings//JiBX_binding__request_commonFactory.class
> (No such file or directory)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at org.jibx.binding.classes.ClassFile.writeFile(ClassFile.java:1999)
> at
> org.jibx.binding.classes.MungedClass.writeChanges(MungedClass.java:424)
> {code}
> Note that /target/classes/config? Shouldn't that be /target/classes?
> Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Index, Search & Analyze Logs and other IT data in Real-Time with Splunk
Collect, index and harness all the fast moving IT data generated by your
applications, servers and devices whether physical, virtual or in the cloud.
Deliver compliance at lower cost and gain new business insights.
Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-415) schema-codegen does not work if module is built in an "also-make" way or from a multimodule parent
[
http://jira.codehaus.org/browse/JIBX-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257060#action_257060
]
Don Corley commented on JIBX-415:
-
Antti,
Release 1.2.3 is in the maven repo.
Please try your build again.
Make sure all your jibx versions are 1.2.3.
You should not have to change your dependencies section.
Don
> schema-codegen does not work if module is built in an "also-make" way or from
> a multimodule parent
> --
>
> Key: JIBX-415
> URL: http://jira.codehaus.org/browse/JIBX-415
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.1
> Environment: Windows 7, Maven 3.0.2
>Reporter: Antti Koivisto
>Assignee: Don Corley
>
> I have a multi module project like this:
> * A
> ** A.I
> *** A.I.OXM
> *** A.I.COMMON
> The A.I.OXM module contains the following:
> {code}
>
>
>
> org.jibx
> maven-jibx-plugin
>
>
> generate-java-code-from-schema
>
> schema-codegen
>
>
>
>
> src/main/resources/jibx
> foo.bar
>
>
>
>
> compile-binding
>
> bind
>
>
> target/generated-sources
> true
> true
> true
> true
>
>
>
>
>
>
> {code}
> If I build the A.I.OXM module by going into it and issuing "mvn clean
> install", the codes are generated correctly and the jar file installed to
> local maven repo contains the generated sources.
> But if I go into module A and do a "mvn clean install
> --projects=A.I/A.I.COMMON --also-make" the A.I.OXM module is not built
> properly. The xsd schema file available in the specified directory is not
> picked up.
> Also doing a "mvn clean install" in the A module has the same effect.
> A solution to this problem seems to be to remove the option and
> use the default location.
> When I did this, all three ways of building the module were successful.
> The problem might be mostly with documentation that used
> src/something as an example. Should it have some maven
> property references too?
> My environment is:
> Apache Maven 3.0.2 (r1056850; 2011-01-09 02:58:10+0200)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> Java home: C:\java\jdk6u23\jre
> Default locale: fi_FI, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Commented: (JIBX-416) Plugin dependency resolving fails
[
http://jira.codehaus.org/browse/JIBX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257059#action_257059
]
Don Corley commented on JIBX-416:
-
Release 1.2.3 is in the maven repo.
Please try your build again.
Make sure all your jibx versions are 1.2.3.
You should not have to change your dependencies section.
Note: Tomek, you might try removing the clause from your org.osgi
dependency to make your test work.
Don
> Plugin dependency resolving fails
> -
>
> Key: JIBX-416
> URL: http://jira.codehaus.org/browse/JIBX-416
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2
>Reporter: Antti Koivisto
>Assignee: Don Corley
> Attachments: maven-jibx-plugin-problematic-build-log-cleaned.txt.txt
>
>
> I'm having a really hard time using the maven jibx plugin. Initially I got
> this same build failure in W7 with Maven 3, but it went away.
> In our Bamboo environment that uses Maven 2, the problem persists:
> {code}
> Missing:
> --
> 1) org.eclipse.equinox:registry:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.equinox:registry:jar:3.3.1
> 2) org.eclipse.core:resources:jar:3.4.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:resources:jar:3.4.0
> 3) org.eclipse.core:jobs:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.core:jobs:jar:3.3.1
> 4) org.eclipse.core:commands:jar:3.3.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=commands -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=commands
> -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse:text:jar:3.3.0-v20070606-0010
> 4) org.eclipse.core:commands:jar:3.3.0
> 5) org.eclipse:osgi:jar:3.3.2
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3
[jibx-devs] [jira] Commented: (JIBX-416) Plugin dependency resolving fails
[
http://jira.codehaus.org/browse/JIBX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256878#action_256878
]
Don Corley commented on JIBX-416:
-
Hang on a bit longer.
I'm still waiting for 1.2.3 to sync to maven central (we just changed to nexus,
so we are waiting for approval on our first sync).
As soon as we sync, I'll get this fixed.
Thanks,
Don
> Plugin dependency resolving fails
> -
>
> Key: JIBX-416
> URL: http://jira.codehaus.org/browse/JIBX-416
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
>Affects Versions: JiBX 1.2.2
>Reporter: Antti Koivisto
>Assignee: Don Corley
> Attachments: maven-jibx-plugin-problematic-build-log-cleaned.txt.txt
>
>
> I'm having a really hard time using the maven jibx plugin. Initially I got
> this same build failure in W7 with Maven 3, but it went away.
> In our Bamboo environment that uses Maven 2, the problem persists:
> {code}
> Missing:
> --
> 1) org.eclipse.equinox:registry:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.equinox
> -DartifactId=registry -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.equinox:registry:jar:3.3.1
> 2) org.eclipse.core:resources:jar:3.4.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core
> -DartifactId=resources -Dversion=3.4.0 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:resources:jar:3.4.0
> 3) org.eclipse.core:jobs:jar:3.3.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=jobs
> -Dversion=3.3.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse.core:jobs:jar:3.3.1
> 4) org.eclipse.core:commands:jar:3.3.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse.core
> -DartifactId=commands -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse.core -DartifactId=commands
> -Dversion=3.3.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse:text:jar:3.3.0-v20070606-0010
> 4) org.eclipse.core:commands:jar:3.3.0
> 5) org.eclipse:osgi:jar:3.3.2
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.eclipse -DartifactId=osgi
> -Dversion=3.3.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.jibx:maven-jibx-plugin:maven-plugin:1.2.2
> 2) org.eclipse.jdt:core:jar:3.3.0-v_771
> 3) org.eclipse.core:runtime:jar:3.3.100-v20070530
> 4) org.eclipse:osgi:jar:3.3.2
> ---
[jibx-devs] [jira] Commented: (JIBX-419) Inconsistent classpaths when using a base binding file in CodeGen
[ http://jira.codehaus.org/browse/JIBX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256438#action_256438 ] Don Corley commented on JIBX-419: - When I say change line 1, I mean in the run.sh script in this zip file. > Inconsistent classpaths when using a base binding file in CodeGen > - > > Key: JIBX-419 > URL: http://jira.codehaus.org/browse/JIBX-419 > Project: JiBX > Issue Type: Bug > Components: CodeGen >Affects Versions: JiBX 1.2.2 > Environment: Java 1.6 >Reporter: Don Corley >Assignee: Dennis Sosnoski > Attachments: test.zip > > > Dennis, > I'm having a problem using codegen with based binding (which I need for the > schema-library). > Since I'm calling codegen from java, I can't change the classpath or my > current directory and I can only specify relative paths. > I have to use -t (target dir) which specifies the source and binding file > location. -i requires a path from my working location, but the generated > binding file ends up specifying the this link to the base binding file as > relative to the compile root. > Just unzip this file, change line 1 to point to your core/lib and run it... > it fails on the third codegen. > Take a look at the in person-binding.xml > Thanks, > Don > My test schema looks like this > person.xsd <- address.xsd <- company.xsd -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
[jibx-devs] [jira] Created: (JIBX-420) OSGi illegal access error when accessing a base binding of a base binding
OSGi illegal access error when accessing a base binding of a base binding - Key: JIBX-420 URL: http://jira.codehaus.org/browse/JIBX-420 Project: JiBX Issue Type: Bug Components: core Affects Versions: JiBX 1.2.3 Environment: Felix 3.0.7 Reporter: Don Corley Assignee: Dennis Sosnoski Attachments: jibx-osgi-test.zip Dennis, I have this schema structure: company.xsd (imports)==> address.xsd (imports)==> person.xsd When I marshal and unmarshal person, no problem. When I marshal and unmarshal address (imports person), no problem. When I marshal and unmarshal company (imports address which imports person), I get an OSGi access error: org.jibx.runtime.JiBXException: Unable to load precompiled base binding 'binding' used by binding 'binding' at org.jibx.runtime.impl.BindingFactoryBase.verifyBaseBindings(BindingFactoryBase.java:447) at org.jibx.runtime.BindingDirectory.getFactoryFromName(BindingDirectory.java:132) at org.jibx.runtime.BindingDirectory.getFactory(BindingDirectory.java:215) at org.jibx.schema.test.company.CompanyTest.marshalObject(CompanyTest.java:109) To recreate this test, unzip the attached projects in your /tmp directory (since I include an obr index). > cd /tmp/jibx-osgi-test > mvn install Now download apache Felix Framework Distribution from: http://felix.apache.org/site/downloads.cgi untar it somewhere: > tar zxvf org.apache.felix.main.distribution-3.0.8.tar.gz > cd felix-framework-3.0.8/ > java -jar bin/felix.jar(Add the java debugger if you want) g! repos add file:/tmp/jibx-osgi-test/repository.xml (The obr index of these test bundles) g! repos add http://jibx.org/repository.xml (obr index to jibx bundles - cool, huh) g! list (will show you the available OSGi bundles) g! deploy 'test-person' (Adds this test and all it's dependencies to runtime) g! lb (list the loaded bundles) g! start 6 (runs the person marshal/unmarshal test) g! deploy 'test-address' (Doesn't have to load person-schema since it's already up) g! lb (list the loaded bundles) g! start 9 g! deploy 'test-company' g! lb (list the loaded bundles) g! start 11 You should see this error. Thanks! Don P.S. Wait for the 1.2.3 sync -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ jibx-devs mailing list jibx-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-devs
