01-13-2010 06:07 AM
I started using browser.field2 as i need ajax support.
My understanding is, The classes in browser.field package are used to render the screens in the browser and handle all the request and response events manually by our own code.
But the browser.field2.BrowserField class is used directly to embed a browser and just giving the url of the website will render the screen and it itself will manage the navigation options.
But my problem is, when i use browser.field2.BrowserField class, i am not able to navigate after the login screen? When i press on login button, the same login page is loaded again and again. I am not able to figure out the problem.
Can anyone have a clue on this issue?
Is there any sample application using browser.field2 package?
01-14-2010 01:48 PM
Thanks for your post, that is a really great question. One of the items on my quarterly content plan is to cover this subject in as greater detail as I understand there is a lot of confusion out there about this.
To help explain this, let me start by clarifying that there are two separate browser rendering engines included in the BlackBerry handheld software:
BlackBerry Widgets applications, introduced in 5.0, use an embedded browser.field2.BrowserField object for rendering content.
For the login problems you are describing, what is the URL you are accessing? Can you capture any HTTP request/response information that is being transmitted between your application and the server? In my experience, whenever a login page reloads after a signin attempt (without displaying an error message), it usually suggests the secure site redirected flow back to the login page for some reason (usually represents an expired session state). Could this be a possibility in this situation? I believe further investigation is necessary.
04-23-2010 10:22 AM
According to API documentation net.rim.device.api.browser.field2 is available since 5.0.0 and
net_rim_api.jar included in the simulator doesn't have this class.
Seems that 4.7.0 doesn't have also.
Can you confirm that third party applications can use this field since 4.6.0 ?
05-01-2010 10:34 AM
BrowserField2 is only available on OS version 5.0 and higher. No other previous version has this control.
10-26-2011 08:05 PM
I also encountered the same problem re: can't pass the login screen.
After inspecting the request / response. It seems that the cookie was not working on a real device. It worked fine from the simulator.
I also tried set the cookie enabled explicitly, although cookie should be enabled by default in field2.BrowserFieldConfig