CodeStore.net comments on "Mystery Of the Missing Java Agents"

Reply from Jake Howlett

Jake Howlett — Fri, 19 Feb 2010 02:33:03 -0600

Hi Frank,

It's not happened to me again since I wrote this blog entry almost 3 weeks ago even though I've been using Java agents just as much. The only thing I can put this down to is that I took the advice given above that you don't copy/paste an existing Java agent when you need a new one (which is what I normally always do).

Since I stopped copying existing Java agents it's stopped happening. Perhaps coincidence, perhaps not?

Jake

Reply from Frank Dröge

Frank Dröge — Thu, 18 Feb 2010 13:58:49 -0600

I'm also experiencing this issue. Everything in my app is fine, except for Java agents. I have spent quite some time reimplementing all my Java Code recently, because everything was broken when I opened the ntf in 8.5.1, and now this. After 15 years of Notes/Domino, I'm really wondering if it's time to quit...

But still, the app needs to run. Does anybody have new info on this?

Reply from Jake Howlett

Jake Howlett — Tue, 02 Feb 2010 03:19:25 -0600

Hi Fredrik,

More than likely, yes I did copy/rename the agents. That's how I tend to work.

Although the agents I've since added to fix the "not found" problem are created from scratch, so let's hope you're right and it doesn't happen to them too....

Jake

Reply from Fredrik Stöckel

Fredrik Stöckel — Mon, 01 Feb 2010 17:07:32 -0600

I have seen that problem a few times before. Did you copy/rename the agent from the list of agent-designelements? (not sure this is related) but i have encountered some wierd behavior by copy/and or renaming agents directly from the agent list (clicking on the agent name).

Fredrik

Reply from Bjørn Cintra

Bjørn Cintra — Mon, 01 Feb 2010 02:43:36 -0600

This is about where to put code that you want to reference from your SSJ code. (For the interested, I am using Freemarker as a templating language for our CMS, instead of JSF components). As far as I know, the "traditional" Java libraries, and xPages don't talk together, as the xPages cannot reference the code in those libraries (correct me if I'm wrong anyone). I suspect that with a proper Java editor for Java agents, and Java libraries, they will do so in the future.

The missing agents are still an issue. You could most likelly store your classes in src, but you would still have to reference it from an agent, and it's the agent code that disappears, it seems.

quote:"How do I add to the classpath for the NSF? You do mean the NSF I take it, and not the machine itself?"

He is talking about classpath references in the Java/eclipse view.

Reply from Bjørn Cintra

Bjørn Cintra — Mon, 01 Feb 2010 02:35:09 -0600

Looks like you learn something every day :)

Now, if class.getResource() would actually understand how to read from an nsf, I could drop external jars form my code...

Reply from Jake Howlett

Jake Howlett — Sun, 31 Jan 2010 16:24:40 -0600

Hi Stephan,

Just to clarify my understanding of what you're saying -- are you saying I shouldn't use Java Script Libraries for my Java classes? Instead I should create them in a new "src" folder, which I'd create by switching to the Java perspective?

How do I add to the classpath for the NSF? You do mean the NSF I take it, and not the machine itself?

Do you think this would help prevent future "missing agents"?

Thanks,

Jake

Reply from Stephan H. Wissel

Stephan H. Wissel — Sun, 31 Jan 2010 10:23:53 -0600

Bjørn,

The intended - and safe - place for your Java files inside the NSF is /WebContent/WEB-INF/src (you need to create the src folder and add it to the classpath). The default location "local" in the classpath is for generated files only and all other stuff will be overwritten / removed.

Stick to the /WebContent/WEB-INF/src location.

Hth

:-) stw

Reply from Jake Howlett

Jake Howlett — Sat, 30 Jan 2010 02:32:43 -0600

Hi Bjørn,

Do you know when it's likely to happens? Does it just happen at any point - for no reason - or does it get triggered by a save in designer? What worries me is the idea that I could test my work, deliver it to customer, get it up and running only for it then to break for no reason. Could that happen? If so I need to consider reverting back to Lotuscript.

Jake

Reply from Bjørn Cintra

Bjørn Cintra — Fri, 29 Jan 2010 13:55:23 -0600

There are lots of problems related to 8.5.1 and code disappearing, I have at least 3 different situations identified:

1.) Java source code disappears from agents and script libraries, and have to be copied back in (this is your issue I believe)

2.) If you open Java perspective, and create a java package and som java files to go with it, the designer will usually delete them on exit (or is it restart). I know IBM is aware of at least this issue. I get around this by creating a jarfile in eclipse instead, and putting this on the server.

3.) I think I identified another issue yesterday, when one of our clients website suddenly threw an error, complaining that a Server Side Javascript library was missing, and my xPage could not call it. A resave of the xpage fixed that issue. This is actually the second time I see this, so it's not a "fluke". I suspect the compiled class file somehow disappeared....

I bet most of these are related to the virtual filesystem that IBM has created on top of notes to get eclipse to talk to the nsf.

I know IBM are aware of some of these issues, and hopefully they are fixed in 8.5.2 (now in beta), but I have not yet had the opportunity to try it out.

Reply from Sandra Noronha

Sandra Noronha — Fri, 29 Jan 2010 09:26:09 -0600

Jake,

This is not directly related to your post (or to the browser client you mostly develop for), but still I thought it would be better to warn you.

Using an eclipse based notes designer to develop an application, will produce a *.nsf with "special" objects within it, that may crash older Notes Clients.

See this post for more details: http://lekkimworld.com/2009/07/09/why_you_should_develop_with_the_same_version_as_your_users_use.html

(my experience in the comment: http://lekkimworld.com/2009/07/09/why_you_should_develop_with_the_same_version_as_your_users_use.html#comment1247142925468).

You never know what other side effects the Eclipse Designer development may have...

Reply from Jake Howlett

Jake Howlett — Fri, 29 Jan 2010 08:37:06 -0600

In an odd way I'm glad to hear I'm not alone and that there's no point hassling the customer to upgrade their server.

But, then, if there's no solution...

Reply from Paul T. Calhoun

Paul T. Calhoun — Fri, 29 Jan 2010 08:21:03 -0600

I have experienced this EXACT same behavior. As I'm developing locally and deploying on an 8.5.1 server it is not a server issue.

As it is not easily duplicated I haven't submitted an SPR, but it is very frustrating.

Only work around I have found is to recreate the agent with the same name as you described.

Reply from mdmadph

mdmadph — Fri, 29 Jan 2010 08:00:10 -0600

Have I seen this before? I have seen so many wonky things happen in the Domino Designer over the years -- man, where do I begin.

Reply from Jerry Carter

Jerry Carter — Fri, 29 Jan 2010 07:57:32 -0600

I think the answer to that is "very likely". I though to mention that the other day but figured you knew what you were doing. ;-)

Reply from Jake Howlett

Jake Howlett — Fri, 29 Jan 2010 06:24:20 -0600

Hi Stephan. Could the client/server mismatch explain the problems I'm getting?

Reply from Stephan H. Wissel

Stephan H. Wissel — Fri, 29 Jan 2010 06:10:46 -0600

The Domino Designer 8.5.1 handles Agents completely different (as checking them out as temp Java projects). So you might want to go and upgrade that server. Anyway: Domino 6.5 is JVM 1.3 and Domino 8.5 is 6.0.... you can expect quite some speed improvements.

:-) stw

Reply from Nick

Nick — Fri, 29 Jan 2010 05:41:36 -0600

I have run into issues with Java agents when I'm using a higher version of the designer client than the server version, so have had to save the agents on another pc that has a version of designer that is the same as the server.