-
It seems like development with Xpages randomly, but very frequently (say 80% of the time), requires a full clean and build. Since I’m learning Xpages, and I have a lot of controls with complex interaction of facets with multiple layers of controls, I make a small change, I save it, then I look at it in the browser. Make another small change and look at it in the browser. It’s slower than molasses in January, but given the absolute dearth of usable documentation on Xpages there’s little recourse.
-
With increasing frequency the small changes I make fail to appear in the browser. The browser is configured to always reload the page from the server, because I use it for development all the time. When the small changes fail to appear, I can do a full clean and build in DDE, and then the small change appears, every single time.
-
A full clean and build takes a very long time compared to a simple save operation, so today in particular I’ve literally spent more time waiting for builds than actually coding anything. For instance, right now I’m trying to figure out why my page gets a stack trace on edit. No message, nothing of use, just a “uh oh” indication and a stack trace. It’s a nightmare. I commented out all my changes, added deleted elements back so it loads again, The only way I can think of to tell what’s happening is to comment out one restored element, uncomment the change for that one element, save it, and load it to see if it crashes. When I hit the stack trace I’ll know I’ve found the real problem. Currently this dog and pony show is to replace about two dozen input text with combo box.
-
Each and every time I make the slightest change to this control I must do a full clean & build, or the combo box never appears, the input text still does. There are no errors on the build, nothing what-so-ever to indicate anything is amiss. It simply refuses to update whatever automagic makes the Xpage work, so it continues to work using stale code.
-
Document-based combo boxes are like pulling eye teeth to start with. This is just salt in the wound.
-
I’ve done development in Eclipse for years and years, and it does every occasionally need a full rebuild. Maybe once per week during intensive development. I’ve never known why, but it doesn’t bother me if it’s once a week. It bothers me a lot when it essentially has to be done every single build, because significantly more often than not it doesn’t work without it. It’s just one more in the near-infinite list of little issues with DDE and Xpages, which collectively amount to a serious mountain of frustration.
Subject: Sounds like you’ve got a reproducible case… can you submit a PMR?
If you can submit it and it’s as reproducible as you say it’ll probably get fixed.
Subject: Actually it’s not doing it today…
-
I set it to build automatically and the issue went away. (knocks on wooden head) I figured if I had to rebuild all the time, I’d just have it do that for me to save the mouse clicks.
-
When I wasn’t building automatically, it wasn’t reproducible in that some set sequence would always cause it to require a clean & build. I noticed no particular correlation between changes made and clean/build requirement.
-
If you’d like a PMR even with intermittent reproducibility, I can set it back to build manually and see what I can come up with. Otherwise I consider the issue “resolved” as I don’t have to clean & build all the time any longer. (happy smile)
Thanks for your time…
Subject: The problem with automagic build…
- Every time I load DDE it forces a full build, even if the binaries are not stale. This triples the amount of time before DDE is useable. Since I’ve loaded DDE four times today that’s becoming an annoyance, exacerbated by the fact that every single time I load DDE it reverts back to Java 1.5 compile. So I get to wait for it to do a full build of a version I’m not interested in, set it to v1.6, then do a clean and build again, each every time I’ve loaded DDE. This is not developer friendly.