07-15-2008 06:30 AM
SAXParserFactory factory = SAXParserFactory.newInstance();
SAXParser saxParser = factory.newSAXParser();
saxParser.parse(con._in, new XMLParserHandler());
In simulators it work fine...but when I try to install the app in a BB...
"This application requires the following module, which is not installed:
net_rim_xml_org".
I try with:
Blackberry 8320 - v4.2.2.171 (Platform 2.5.0.24)
Blackberry 8310 - v4.2.2.94 (Platform 2.5.0.10)
I don't find a solution in any forum L
Is ther any way to download and install that module?
Regards.
There are 2 packages with those classes:
Which one are you using? Remember that the JDE is only forwards-compatible with handheld software, so if you are using any classes from JDE v4.3, then the handheld must be running minimum handheld software v4.3.
Tariq
09-13-2008 12:41 PM
Has there been any clarity on the cause of this error? I see lots of posts across the internet on the topic, but no clear solution. If it is a versioning problem, it isn't obvious.
I have had an application developed... originally on JDE 4.0, but we upped to 4.2. We use the net.rim.device.api.xml.parsers.SAXParser library. I have users on 4.2 get the net_rim_xml_org not found (or not installed) error. Shouldn't be a version compatibility problem.
I'm pretty sure it is something specific to the users device, but not sure what advice to give... I certainly can't advise them to wipe out their OS and reinstall!
09-15-2008 09:42 AM
There are 2 possible causes to this error.
1. Building the application in a version of the BlackBerry JDE that is not compatible with the version of BlackBerry handheld software.
What Is - Appropriate version of the BlackBerry JDE
Article Number: DB-00537
2. The user does not have the BlackBerry Browser installed. This can be added and removed by using the Application Loader wizard of Desktop Manager.
09-15-2008 08:17 PM
Are there any other possibilities?
My app was done in the 4.2 JDE
I have at least one user with an 8820 running 4.2.2.169 who used the built-in blackberry browser (not a 3rd party) to install the app via OTA at mobihand... At least 3 failures with the net_rim_xml_org problem... Hundreds of other successful installs...
09-16-2008 11:11 AM
Please verify that they have also installed JavaScript support in the BlackBerry Browser. This is an optional element in older versions of BlackBerry handheld software (including 4.2).
09-19-2008 05:13 PM
So I have some more troubleshooting on this... and starting to see a trend.
I've spoken to 4 folks with this issue. 3 were on T-Mobile, one on Telus. All had OS 4.2 or greater, using BB browser with javascript enabled. I'm thinking it is something the carriers removed or such for "security" purposes (like the way Verizon sold me a GPS that I can't use).
I dont see why an XML class would be a risk - but it certainly does seem coincidental that 3 of the problems came from TMO which probably doesn't have the largest network share versus VZW, ATT, etc...
Does anyone have an idea where to confirm? A web search didn't yield anything concrete.
09-22-2008 10:53 AM
09-22-2008 09:12 PM
4.2.1.107 (T-Mo)
4.2.2.176 (Telus)
4.2.2.169 (T-Mo)
As for the code, I'm not sure what you need. I haven't written the code (although do know a little bit of programming - just not what is necessary for my project)... There are 22 .java files in the latest version. I'll confirm with my coder the xml parsing library, but last I knew we were using net.rim.device.api.xml.parsers.SAXParser.
We can drop the topic for now... I was just thinking there was an easy answer to this even though there are a number of references around the web of a similar error with no clear explanation.
Thanks for all the help...
Matt Lochansky
Cognitive Powers, Inc.
10-14-2008 11:04 AM
I see the same problem as well, without no clear pattern. I just tested on a Tmo Blackberry 8820 v4.2.2.193 and the net_rim_xml_org module is missing, however when I test the same build on an At&T 8310 v4.2.2.170 it works. It seems, I'm going to stop wasting time chasing this module around. I'll probably just go with a bundled kxml parser.
Any other person worked out a better solution for this?
Thanks.
10-14-2008 02:47 PM