The NAS class-loader doesn't handle loading classes with native methods.
You need to make sure that the java class is loaded by the primordial
class-loader. This is a registry setting and should be doc'd in the
manual somewhere.
-Dave
Oliver Pereira wrote:
>
> Hi All,
>
> We r calling native me
"Kallur, Padmaja (GEL, MSX)" wrote:
> Iam using NAB 4.0 . Iam having a onChange="validate" for a text item, where
> validate is a java script function.
...and you're trying to do JSP inside of a client-side script tag? I think
you're probably out of luck until 4.0SP1. The NAB team discovered th
"Kallur, Padmaja (GEL, MSX)" wrote:
> Hello everybody,
> Is any one using Netscape Application Builder 4.0
Well, I'm the project lead (at least for the next couple of weeks).
I'd be happy to answer any questions.
Conversely, I'd be happy to hold my tongue whilst you complain about
non-standard t
Michael Hu wrote:
> > > Implicitly, the JSP engine will allocate resources in the pageContext. Although
>not
> > > explictly demanded by the specs, it should be safe to assume that
>releasePageContext()
> > > will be called in service's finally block for JSP 1.1 compliant implementations
>(ref
Michael Hu wrote:
> There are three places where a JSP page author can allocate limited resources:
>
> 1) _jspInit() which is cleaned up by _jspDestroy(), both of which are guaranteed to
>be
> called at the appropriate times in 1.1 spec.
Once -- during engine/application start and stop -- not on
In the process of executing a page with a multitude of tag extensions, one
tends to create objects which need to be release()d, close()d, dispose()d,
or otherwise free some resources back to the system. [Aside: wouldn't it be
nice if we agreed on the name of this method across all java apis!]
It
Sandy Tiu wrote:
> I found out that I have to parse the above string and replace all spaces
> with a "%20" before appending it to the url. It worked after
> I did this. Is there a better way?
Take a peek at java.net.URLEncoder.encode().
-Dave
Eoin Curran wrote:
> The cookies used to track sessions disappear once the browser is closed (For
> Jrun, anyway). So If you need to use a cookie to recognize a user returning
> to your site, this solution will not work.
>
> It is a nice way to work things though. Maybe the way that the session
>
Eduardo Pelegri-Llopart wrote:
> doEndTag() returns an indication of whether you are done with this page
> (e.g. because you just forwarded the request elsewhere, or whatever), or
> not. (EVAL_PAGE and SKIP_PAGE). It should also release all local
> resources.
Err, did this change recently? The
Foster Bob wrote:
> Michael Hu wrote:
>
> >Connection attributes don't belong in the query tag, definitely. I would
> >argue connections (and query select statements) also don't belong in JSP
> >pages. Sorta orthogonal.
>
> Then how do you propose to implement commit and rollback in JSP pages?
A
Just fyi -- I think that was fairly clear, its just that the
implementation I was using lost content and I wanted to make sure I was
doing things correctly. :)
By the way, I'm not sure what the doEndTag() exists for. Are there places
where it should be called and release() should/might not?
-D
Michael Hu wrote:
> Tags which encapsulate database functionality:
>
> 1) : allows for connection pooling, and multiple queries to
> reuse a common database connection.
>
> 2) : allows for execution of arbitrary SQL statements over a
> . Some may agrue that this tag should be as
> implies SELEC
12 matches
Mail list logo
