Ahhh... now you're starting to paint a picture someone can help with.
So the jnlp file is the return data and it's composed on the fly from
repository data. That's certainly a cool way to leverage the repository
for updates.
To the web server there really is no difference -- a request is a
request whether it be from IE, Firefox, or javaws. What you really want
to do is construct a GET request so all the form params are encoded in
the URL, then have magnolia serve up a jnlp file based on the request
parameters. A servlet that acts as a page template serving up jnlp
files would be the way I would go.
Maybe others on the list have done work with servlets as templates, but
I haven't. Sorry. You could also try taking a look at the servlet that
responds to requests for binary requests (.jpg, .png, .tif, .pdf, etc.,
...). Might be a good thing to base your own work on.
--David
Boris Ioffe wrote:
Hello David,
My links are accessed via browser only for the first
time. Java WebStart installs an icon for the app on a
client's desktop After javaws.exe will check if there
is a change in the structure of the installed jnlp or
updated jar files. So, essentially we have java
webstart framework as a client in this case. They rely
on muffins(webstart cookies), but they can be purged
at any moment, so we have to incorporate some params
right into the URI itself.
Here is what i am trying to accomplish here:
1) acess jnlp file at
/MyWebapp/jnlpserver/username/productname/version/xvz.jnlp
2) parse out params from URI such as username,
productname,version, etc...
3) Query jcr for proper sets of jar files and java
properties
4) Assemble jnlp file with all resources from DMS
5) Ship back to the client jnlp and proper jars
As a result we have a powerful release management
system, that can maintain an array of java trading
applications.
If (success){
workflows and LDAP user management is the next step;
magnolians will get mucho dineros &
myself.getsPatOnTheBack(bosses);
}
I think the solution is easy, however it beats me at
this point. I did this:
1) In server/filters/cms/config/bypass added
,/templates/jnlp/
2) In modules/adminInterface/virtualURIMapping/ added
jnlpHandler with
fromURI=*.jnlp,toURI=forward:/templates/jnlp/JNLPTemplate.jsp
it works, but i get this
ERROR info.magnolia.context.MgnlContext
MgnlContext.java(getInstance:289) 20.05.2007 20:38:18
MgnlContext is not initialized, This could happen if
the request does not go through magnolia default
filters
Thank you very much,
-B
--- David Smith <[email protected]> wrote:
I have to say the message you cite at the bottom is
really not
answerable. There isn't enough context or detail to
provide any sort of
intelligent answer.
As to your problem specifically, could you provide
more details on what
your are setting up? Why can't these links be
accessed via the browser
more than once?
--David
Boris Ioffe wrote:
Hello Magnolians,
I'd like to say few nice words to developers of
this
really neat project. Good job. This CMS is simply
amazing. However I must draw your attention to one
very unfortunate deficiency of this tool. It is
very
poorly documented.
I am prototyping a webstart distribution system
for
huge interbrokerage firm. They are capable of
buying
ent. license, but I will need to convince them
with
the pilot and some other tangible results.
So far I had to learn from the source code
(documentation website doesn't really have
development
guidelines and the wiki is useless in that
regard).
Thus the learning curve is unpleasantly difficult.
Here is my problem:
I have few hundred users, each has homepage with
webstart links available based on user's groups
and
roles. Each link points to
/MyWebapp/jnlpserver/username/productname/version/xvz.jnlp
these links can be accessed via browser only for
the
first time and later are being called directly by
javaws. Since we can not really on
muffins,cookies,
bagels,etc... whatever they use to track a session
in
Java WebStart, we have to create dynamic links to
*.jnlp template and read params info from URI.
I can't figure it out with magnolia.
I need the answer for the question below that was
floating on this mailing list, since 6 month ago,
unanswered.
Thanks in advance,
-B
------------------------------
Do we have to edit all the filters? Or just the
CMS
one?
Also, can you give an example on how to write it
up?
Does it also
work for all extensions? (like, for instance,
*.jsp,
*.dwr, *.do).
If I'm on the wrong track, can someone explain to
me
how to set up the
project, so that struts actions coexists with
pages
rendered by
Magnolia?
Thank you.
JS.
____________________________________________________________________________________Got
a little couch potato?
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
____________________________________________________________________________________Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more.
http://mobile.yahoo.com/go?refer=1GNXIC
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
