Hi Sven,
Sounds interesting and like something we could also use.
I unfortunately don't know the best way to start however two things I think we would need are:
1) A "Rhino Library" we can add in the project settings. This would give us some of the base objects we need to reference java code like "Package" and "java"
2) Java "Project" support in project settings that automates (and likely hides behind the scenes) Java stub creation
I'd open bugs for those two issues to start things rolling.
-Simon
Sven Asp ---04/21/2010 10:24:36 AM---Hi Chris, Thanks for your rapid response.
From: |
Sven Asp <asp.sven@xxxxxxxxx> |
To: |
"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx> |
Date: |
04/21/2010 10:24 AM |
Subject: |
Re: [wtp-dev] JSDT Libraries and Java classes |
Sent by: |
wtp-dev-bounces@xxxxxxxxxxx |
Hi Chris,
Thanks for your rapid response.
My problem is that I'm using a web-server (Cocoon) that makes a lot of jars available for _javascript_ server side evaluation. A lot of the logic is written in _javascript_ that imports packages from those jars. The jars in turn, are also part of the application.
Ideally, I'd like to be able to alter the name of a method a Java file, compile it, and get error in a _javascript_ file that references the old method name.
The situation (_javascript_ calling on custom java) can't be that uncommon, so perhaps some support for that would be worth considering?
Regards,
Sven
On 04/21/2010 03:38 PM, Christopher Jaun wrote:
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
|