I am working on a program for this website using the Java module HtmlUnit. I need to select options from the select fields, but when I do so, it doesn't trigger any events. I have tried a few solutions on forums for this same question (fireEvent method, injecting a JS script to trigger the event), but none have worked so far.
I would really appreciate some help with this one
If you like to get some help you have to provide more details; the version of HtmlUnit you use and your code (as simple as possible). Including a description where your expectation differs from the real results. And of course more details why you think the event is not triggered.
If you think this is a HtmlUnit issue please open a issue in the HtmlUnit issue tracker.
Have written a Wetator (www.wetator.org) test for the web site. Was able to work with all the select boxes and got the appropriate changes on the web site. Based on this i'm really sure this is not a problem with HtmlUnit. Post your code and i will have a look.
Related
I've spent few hours trying to get my deep links to work. The only issue that I still have is that it won't work if the link is opened from the domain that is supposed to be handled by the app but it works fine if the link that is clicked from any other website.
For example:
The link which should open the app: https://example34.com/test.
If I click on a link on Github it'll work.
If I open https://example34.com/ and then click on the link from there it will open this in the browser instead of the app...
What am I doing wrong?
Short answer: This is the expected behavior.
When using Applinks, Chrome will always defer to directing users on the same domain to the web instead of deep linking to the native app. The only way to open the application is to trigger a URI scheme when the user is routing within the same domain. I suggest using Branch to guarantee that your links work in all of these cases.
I'm looking in to trying to build an application that will allow me to interact with specific elements of a web site, without going through a browser.
This is more a matter of general interest but for my prototype I am using the Guardian web site.
I want to log in, crawl through the content to find articles that can be commented on, and then display and allow the logged in user to comment on the articles.
I am a professional java developer but I've never really gone in to http development, and my search for resources that will help me with this project has not turned up much.
Firstly, I suppose I should ask, is this possible?
Secondly if so how would you for instance log in and post a comment to This Article
Have a look at Selenium Webdriver: http://docs.seleniumhq.org/projects/webdriver/
But please be good. Don't make a comment spam robot.
I read the nebeans tutorial for RESTfull service (http://netbeans.org/kb/docs/websvc/rest.html) and tried to implement it. But when i'm run the test I'm not getting the screen what they say. I found that some say it is a bug on netbeans whilst some say it is bug on browser.I read some related question on this site but could not get much help
Suppose to appear as previous one
but appear as following one....
Note that navigation is not appears.
I'm unable to get the test it further.
I'm using netbeans 7.1 bundle
Can any one help me out. Thank you.
p.s : This page opens as reading a file( file:///home/xxx/xxx )
In that link you can notice the caution
Caution: For later versions of Firefox, you need to generate the test client in another Java web application than the service project.
I got the same error in firefox and chrome, then I tried test-resbeans.html in IE and its working fine as mentioned.
That tutorial dose't work on that way. When we test the restfull test we need to brows and give that restfull service. Then it will work on any browser.(I guess to test it need a service).
I need to display any web page as a browser field,not browser session.I am building the app in 4.7 OS.Can anyone help me with sample code?
On 4.7 you are stuck with the old browser field. Also known as Browser Field 1. It renders HTML pretty close to how it was on 4.5 devices. There is no way to take advantage of the newer browser that you invoke via browser session. So, you can forget about CSS2 or or JavaScript on the pages you want to render as a browser field. But for the fairly basic stuff it is good enough.
For the sample code - you really should check out and understand all the examples there are in the development package before starting writing the code. It will really save more time than take for learning. Look at components\samples\com\rim\samples\device\blackberry\browser\BrowserFieldDemo.java
I doubt that the problem lies with the browser field per se. Rather with communications.
The people in the post that you refer to were probably suggesting ";deviceside=true" as this gets around the "BES effect" in a simulator.
You may wish to experiment with running the MDS emulator alongside the simulator session as well. There are a number of posts that discuss the impact of deviceside and simulation. You can test in code to see if you are running a simulator so that you can programmatically influence the "BES effect".
I have a JSF/ICEFaces application that was working fine but all of the sudden it started taking sinfully long time in rendering response phase! I can tell from the console that the java part completes fine but it takes like 10 minutes to display the web page!
I'm using JBoss as my application server.
Could you please tell me how to go about debugging this problem? I don't even know where to start. Please tell me also if putting some code here will help in knowing the root of the problem. To start with, do you think it's a JBoss problem or application problem?
Thanks,
Tam
Have a read of BalusC: Debug JSF lifecycle
Is your page particularly complex? For example if you have a large dataTable where each row contains logic then the render phase may take ages.
You could try to use tools like Firebug to see if there is some Ajax functionality that blocks the render process. IceFaces as I know it relies heavily on doing everything on the serverside of the application and then send the results to the browser for displaying.
Maybe your use of the components generates a lot of communication to the server or the component can not be updated.
I would look into IceFaces it has proven as unstable and problem prone all the times I worked with it. They have a own forum where you often find an answer to your problems. I think it is on Icefaces.org. But without knowing more I can't really tell where the problem is.