Limit on tags or bytes in JDeveloper?

I've been working with Java and JDeveloper 3.2.2 with JDK 1.2.2 and OJVM for only a few weeks but the last 2 weeks I haven't been able to solve a problem:
When I run an application after our login page I will receive:
Request URI:/reports/gen_app_by_job_stat_report.jsp
Exception:
java.lang.VerifyError: reports.gen_app_by_job_stat_report
There is no other exception messages so I don't know where the problem is coming from.
Does JDeveloper limit the size of each JSP page or how many tags/custom tags you can put on it? All the code seems to have correct form.
Any help/suggestions would be greatly appreciated.
Thanks!
Karl

Hi Brian, thanks for you reply!
I think we solved it, but i'm not sure if it's because of a limitation with Java.
I think the JVM seems to have a bytecode limit on our JSP. Thus when we take some lines of code out on short pages the page would load properly...and when we took a whole include out of a long page it would work too. We have 4 includes in each report page (one for header, one for navbar, one for search bar, and one for our SQL statement).
We now have this:
<%objref.Service.include"/header.jsp",request, response);%>
instead of this:

The former compiles the include as it's own separate JSP rather than the latter which compiles the includes into the main JSP and thus produces a huge page. That seems to have reduced the amount of bytes in the java file by half and works properly now.
I think we're using the Oracle Servlet Engine.
null

Similar Messages

A SWF Tag of type 75 contains 10 bytes of unread data at the end of the tag at byte offset 1762

When building with Flash builder 4.7 I get two warnings I can't seem to track down.
Those are
"A SWF Tag of type 75 contains 10 bytes of unread data at the end of the tag at byte offset 1762" The other
"A SWF Tag of type 75 contains 5464 bytes of unread data at the end of the tag at byte offset 797163"
No file is pointed out or anything else to help.
Any ideas what to look for, why this is a warning, possible implications & what to do?

This is one output after running a variation of the script, but I get this    on all of the libraries
Here is a link to the swc for further inspection https://dl.dropbox.com/u/154782/GoCoUtil.swc
<?xml version="1.0" encoding="UTF-8"?>

<swf xmlns="http://macromedia/2003/swfx" version="14" framerate="24.0" size="10000x7500" compressed="true" >

<FileAttributes useDirectBlit="false" useGPU="false" hasMetadata="true" actionScript3="true" suppressCrossDomainCaching="false" swfRelativeUrls="false" useNetwork="true"/>
<Metadata>
        <![CDATA[<rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'><rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1'><dc:format>application/x-shockwave-flash</dc:format><dc:title>Adobe Flex 4 Application</dc:title><dc:description>http://www.adobe.com/products/flex</dc:description><dc:publisher>unknown</dc:publisher><dc:creator>unknown</dc:creator><dc:l anguage>EN</dc:language><dc:date>Sep 20, 2012</dc:date></rdf:Description></rdf:RDF>
]]>
</Metadata>
<EnableDebugger2 password="NO-PASSWORD" reserved="0x1975"/>

<ScriptLimits scriptRecursionLimit="1000" scriptTimeLimit="60"/>
<SetBackgroundColor color="#FFFFFF"/>
<ProductInfo product="FLEX" edition="NONE" version="4.6" build="23201" compileDate="9/20/12 12:41 PM"/>
<DoABC name="com/gogogic/common/util/interfaces/IParsableList"/>
<DoABC name="_5655ee2c6f5749799717c751ad05c55879a42026a02d38e5e206aab452dbcc6f_flash_display_Spr ite"/>
<DoABC name="com/gogogic/common/util/ShallowCloner"/>
<DoABC name="com/gogogic/common/util/GoCoDataUtil"/>
<DoABC name="com/gogogic/common/util/PropertyParseError"/>
<DoABC name="com/gogogic/common/util/interfaces/IDataChange"/>
<DoABC name="com/gogogic/common/util/vo/DataChangeVO"/>
<DoABC name="com/gogogic/common/util/GoCoUtilVersion"/>
<DoABC name="com/gogogic/common/util/event/DataChangeEvent"/>
<DoABC name="com/gogogic/common/util/PropertyParser"/>
<SymbolClass>
    <Symbol idref="0" className="_5655ee2c6f5749799717c751ad05c55879a42026a02d38e5e206aab452dbcc6f_flash_displa y_Sprite" />
</SymbolClass>
<ShowFrame/>
</swf>

Import Tag library problem in JDeveloper 10.1.3.3.0

I want to have an FCKEditor on a JHeadstart generated page, so I downloaded the FCKFaces jar with the tag library in it.
When I try to add the FCKFaces tag library to my project, doing just that and not modifying any code, when I run my application after that I get an empty page... No data in the project. This is very confusing because everything works well, no code errors, the fck library is found and auto completion works with the library.
So when I have the empty page, to view the JHeadstart page again I just have to shut down JDeveloper, go to the project/web-inf/lib directory and delete the FCKFaces jar. When I do that and start up again, the page loads successfully.
Thanks for the help in advance..

Thanks for your reply.
I tried your solution but still the same problem remains.. I don't have a clue what's wrong with the project, everything works well except for that the page's aren't rendered on execution.

Some JSF 2.0 Tag not found in JDeveloper

Dear All,
I am now using JDeveloper 11.1.2 to develop an ADF application. I found that some JSF 2.0 features cannot be implement.
The tag f:metadata and f:viewParam cannot not be found in JDeveloper.
What I want to do is to implement a page Load event as the following:
<f:metadata>
<f:viewParam id="id" name="id" value="#{backingBean.id}"/>
<f:event type="preRenderView" listener="#{backingBean.pageLoad}"/>
</f:metadata>
However, the JDeveloper shows up the message "Element f:metadata not supported".
Is it a known issue in JDeveloper? Does JSF 2.0 fully supported in JDeveloper 11.1.2?
Thanks and Regards,
Boris

Hi All,
I finally solve my problem.
(1) The first problem is that "f:metadata" tag is not allowed to place under "f:view"
(2) The second problem is that "f:event" tag is not allowed to place within "f:metadata". I just place it within "af:document"
<af:document title="main2.jsf" id="d1">
<f:event type="preRenderView" listener="#{backing.pageLoad}"/>
Thank you.
Boris

Tag libraries added to Jdeveloper using Manage Libs option

I have done this many times and every time I do it there is a different result.
I create a new Tag with name and the attribute values in my tld file.
The web.xml have the location of the .tld.
In the jsp I try to use the most recently added tag and I cannot see it BUT I can use it!
this is the error::: 'tg:dateField' is not a registered tag in namespace '/WEB-INF/tags.tld'.
All my other tags are in the same .tld and I can see them as context sensitive menu BUT not the one that I just added.
I tried....
Restarting Jdev (worked once)
ReBuilding my project
but isn't Jdev being inconsistant?? or am I doing something wrong here? Are there any other solutions
please share.
regards,
raj

repost

Oracle 8.1.7 driver limit causes problems with CMP

The information below is from Oracle's site and has been noted by a few
people on various message groups. We had upgraded to 8.1.7 but hadn't put
the latest classes12.zip (June 2001) in our classpath. When we do, we get
the following error from the driver/generated code. We believe this is
because we are hitting the limit cited below. I don't know why the Oracle
driver has this limit, but since WL generates this code for the EB, I don't
see an easy way for us to avoid it.
Anyone have any comments on this? Is my interpretation of the stacktrace
correct? If we go back to the old classes12.zip (June 2000) then we don't
have this problem. But in addition to wanting to run the matching zip file
with the version of the DB, we also want to use some of the functionality in
the 8.1.7 zip. Does BEA have a workaround for CMP?
java.rmi.UnexpectedException: Unexpected exception in
sync.server.system.SystemSessionDataBean.setSessionData():
java.sql.SQLException: ORA-01483: invalid length for DATE or NUMBER bind
variable
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:169)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:822)
at
oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1610
at
oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1535)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
:2053)
at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedState
ment.java:398)
at
weblogic.jdbc20.pool.PreparedStatement.executeUpdate(PreparedStatement.java:
47)
at
sync.server.system.SystemSessionDataPSWebLogic_CMP_RDBMS.update(SystemSessio
nDataPSWebLogic_CMP_RDBMS.java:318)
at
sync.server.system.SystemSessionDataPSWebLogic_CMP_RDBMS.store(SystemSession
DataPSWebLogic_CMP_RDBMS.java:284)
at weblogic.ejb.internal.EntityEJBContext.store(EntityEJBContext.java:192)
at
weblogic.ejb.internal.EntityEJBContext.beforeCompletion(EntityEJBContext.jav
a:227)
at
weblogic.ejb.internal.StatefulEJBObject.postInvokeNoTx(StatefulEJBObject.jav
a:355)
at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:865)
Using Streams to Avoid Limits on setBytes() and setString()
There is a limit on the maximum size of the array which can be bound using
the PreparedStatement class setBytes() method, and on the size of the string
which can be bound using the setString() method.
Above the limits, which depend on the version of the server you use, you
should use setBinaryStream() or setCharacterStream() instead.
When connecting to an Oracle8 database, the limit for setBytes() is 2000
bytes (the maximum size of a RAW in Oracle8) and the limit for setString()
is 4000 bytes (the maximum size of a VARCHAR2 in Oracle8).
When connecting to an Oracle7 database, the limit for setBytes() is 255
bytes (the maximum size of a RAW in Oracle7) and the limit for setString()
is 2000 bytes (the maximum size of a VARCHAR2 in Oracle7).
The 8.1.6 Oracle JDBC drivers may not raise an error if you exceed the limit
when using setBytes() or setString(), but you may receive the following
error:
ORA-17070: Data size bigger than max size for this type
Future versions of the Oracle drivers will raise an error if the length
exceeds these limits.

Joe Herbers wrote:
>
I added some debug output to verify that this problem is definitely caused
by the WL generated code/Oracle driver. To do this, I used
the -keepgenerated code on ejbc. Then I modified the generated code to
print the length of the byte array before calling setBytes. I compiled the
class and put an updated version in my bean jar.
When I run our test suite, I see hundreds of calls to setBytes with sizes
such as 315, 368, 1988, 2020. And then occasionally there are sizes of
41932 or 19409. These larger sizes are always followed by the ORA-01483
exceptions.
This appears to be certain confirmation that the problem is caused by the
8.1.7 driver's enforcement of the 4k limit on the methods that the
WL-generated code is using to map our Java byte[] to our Long Raw/BLOB field
in Oracle. Any suggestions for workarounds?Actually, it indicates the driver's being caught by the limitation that
Oracle itself imposes with setBytes(). This is a known issue I believe, and
you should ask support for a patch to ejbc that generates calls to setBinaryStream()
rather than setBytes().
Joe Weinstein
>
"Joe Herbers" <[email protected]> wrote in message
news:[email protected]...
We use WL 5.1, SP10. I've noticed that sp11 is now out, but it doesn'tseem
to have any fixes for this problem (it mentions Oracle 8.1.6, but not8.1.7,
which seems to be the release in which Oracle started enforcing thislimit).
We're kind of stuck at the moment, I'm surprised no one else hasencountered
this problem with WebLogic (I have seen postings elsewhere about it with
other AppServers)
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]...
Hi Joe,
From your CMP DD it's clear that you use WL 5.1. Which service pack
do you use?
AFAIR this problem was fixed in WL 6.1, though I'm not sure about
5.1. Could you use ejbc with -keepgenerated option and look at
SystemSessionDataPSWebLogic_CMP_RDBMS.java, particularly
how bind variable related to you LONG RAW? Is setBytes used? Or
it's something like setBinaryStream?
Regards,
Slava Imeshev
"Joe Herbers" <[email protected]> wrote in message
news:[email protected]...
The table has only three fields: two IDs (Number(18)) and a Long Raw
that
we
are storing a Hashtable in. The field seems to be filled fine most of
the
time. With the old driver, it always works. As soon as we switch thenew
driver in, certain operations fail consistently. I haven't verifiedthat
the size is indeed > 4k in these cases, but our error matches whatothers
have seen. Here's the CMP DD but I doubt that helps...
<weblogic-rdbms-bean>
<pool-name>oracle</pool-name>
<table-name>scc_sm_sys_sess_data</table-name>
<attribute-map>
<object-link>
<bean-field>mlSystemSessionDataID</bean-field>
<dbms-column>sys_sess_data_id</dbms-column>
</object-link>
<object-link>
<bean-field>mlSystemSessionID</bean-field>
<dbms-column>sys_sess_id</dbms-column>
</object-link>
<object-link>
<bean-field>mBSessionData</bean-field>
<dbms-column>sys_sess_data</dbms-column>
</object-link>
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]...
Hi Joe,
This limit defines limit written to oracle strings, raws, blobs and
clobs
when setBytes is used. It has nothing to do with the exception
you're
getting.
Could you show us your CMP deployment descriptor(s)?
Regards,
Slava Imeshev
"Joe Herbers" <[email protected]> wrote in message
news:[email protected]...
The information below is from Oracle's site and has been noted by
a
few
people on various message groups. We had upgraded to 8.1.7 but
hadn't
put
the latest classes12.zip (June 2001) in our classpath. When we
do,
we
get
the following error from the driver/generated code. We believe th
is
is
because we are hitting the limit cited below. I don't know why
the
Oracle
driver has this limit, but since WL generates this code for the
EB,
I
don't
see an easy way for us to avoid it.
Anyone have any comments on this? Is my interpretation of the
stacktrace
correct? If we go back to the old classes12.zip (June 2000) then
we
don't
have this problem. But in addition to wanting to run the matching
zip
file
with the version of the DB, we also want to use some of the
functionality
in
the 8.1.7 zip. Does BEA have a workaround for CMP?
java.rmi.UnexpectedException: Unexpected exception in
sync.server.system.SystemSessionDataBean.setSessionData():
java.sql.SQLException: ORA-01483: invalid length for DATE or
NUMBER
bind
variable
at
oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:169)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
atoracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:822)
at
oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1610
at
oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1535)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
:2053)
at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedState
ment.java:398)
at
weblogic.jdbc20.pool.PreparedStatement.executeUpdate(PreparedStatement.java:
47)
at
sync.server.system.SystemSessionDataPSWebLogic_CMP_RDBMS.update(SystemSessio
nDataPSWebLogic_CMP_RDBMS.java:318)
at
sync.server.system.SystemSessionDataPSWebLogic_CMP_RDBMS.store(SystemSession
DataPSWebLogic_CMP_RDBMS.java:284)
atweblogic.ejb.internal.EntityEJBContext.store(EntityEJBContext.java:192)
at
weblogic.ejb.internal.EntityEJBContext.beforeCompletion(EntityEJBContext.jav
a:227)
at
weblogic.ejb.internal.StatefulEJBObject.postInvokeNoTx(StatefulEJBObject.jav
a:355)
atweblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:865)
Using Streams to Avoid Limits on setBytes() and setString()
There is a limit on the maximum size of the array which can be
bound
using
the PreparedStatement class setBytes() method, and on the size of
the
string
which can be bound using the setString() method.
Above the limits, which depend on the version of the server you
use,
you
should use setBinaryStream() or setCharacterStream() instead.
When connecting to an Oracle8 database, the limit for setBytes()
is
2000
bytes (the maximum size of a RAW in Oracle8) and the limit forsetString()
is 4000 bytes (the maximum size of a VARCHAR2 in Oracle8).
When connecting to an Oracle7 database, the limit for setBytes()
is
255
bytes (the maximum size of a RAW in Oracle7) and the limit forsetString()
is 2000 bytes (the maximum size of a VARCHAR2 in Oracle7).
The 8.1.6 Oracle JDBC drivers may not raise an error if you exceed
the
limit
when using setBytes() or setString(), but you may receive the
following
error:
ORA-17070: Data size bigger than max size for this type
Future versions of the Oracle drivers will raise an error if thelength
exceeds these limits.
B.E.A. is now hiring! (12/14/01) If interested send a resume to [email protected]
DIRECTOR OF PRODUCT PLANS AND STRATEGY San Francisco, CA
E-SALES BUSINESS DEVELOPMENT REPRESENTATIVE Dallas, TX
SOFTWARE ENGINEER (DBA) Liberty Corner, NJ
SENIOR WEB DEVELOPER San Jose, CA
SOFTWARE ENGINEER (ALL LEVELS), CARY, NORTH CAROLINA San Jose, CA
SR. PRODUCT MANAGER Bellevue, WA
SR. WEB DESIGNER San Jose, CA
Channel Marketing Manager - EMEA Region London, GBR
DIRECTOR OF MARKETING STRATEGY, APPLICATION SERVERS San Jose, CA
SENIOR SOFTWARE ENGINEER (PLATFORM) San Jose, CA
E-COMMERCE INTEGRATION ARCHITECT San Jose, CA
QUALITY ASSURANCE ENGINEER Redmond, WA
Services Development Manager (Business Development Manager - Services) Paris, FRA; Munich, DEU
SENIOR SOFTWARE ENGINEER (PLATFORM) Redmond, WA
E-Marketing Programs Specialist EMEA London, GBR
BUSINESS DEVELOPMENT DIRECTOR - E COMMERCE INTEGRATION San Jose, CA
MANAGER, E-SALES Plano, TX

Regular Expressions and Double Byte Characters ?

Is it possible to use Java Regular Expressions to parse
a file that will contain double byte characters ?
For example, I want a regular expression to match the following line
tag="double byte stuff" id="double byte stuff"

The comments on the bytes/strings were helpful. Thanks.
But I'm still confused as to what matching pattern could be used.
For example a pattern like:
[A-Za-z]
I assume would not match any double byte characters.
I also assume the following won't work either:
[\\p{Alpah}]
because it is posix - US-ASCII only.
So how do you say "match the tag, then take any characters,
double byte, ascii, whatever, then match the text tag - per the
original example ?

Problem with JSP Tag class

Hi,
          After some time of work, WLS ends up with the following error message:
          weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
          'cm': There is no setter method for property 'limit', for Tag
          class 'com.hp.module.cm.tag.GetDocumentsTag'
          at
          weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
          at
          weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:272)
          at
          weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
          at
          weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
          at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
          at
          weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3811)
          at
          weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3561)
          at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3422)
          at
          weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1760)
          at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1601)
          at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1491)
          at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:880)
          at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
          at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
          at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
          at
          weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
          at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:302)
          at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:217)
          at
          weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:164)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:101)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
          at
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
          at
          weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
          at
          weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
          The class does contain the setter, so we don't know why the message pops
          up. After rebooting the server, the page works properly (!) Does anyone
          know how to get rid of it ? We're running out of ideas, and rebooting
          the server every 2-3 days is not acceptable.
          The configuration consists of BEA WebLogic 5.1.0 SP8 + JDK 1.2.2_07 +
          HPUX 11.0.
          Any help is greatly appreciated.
          Jacek Laskowski


so doesn you bean have a
          void setLimit(String) {}
          String getLimit() {}
          or does it have mismatched getter and setter?
          like
          setLimit(String) {}
          int getLimit() {}
          take a look at :
          http://developer.java.sun.com/developer/bugParade/bugs/4407050.html
          -Nagesh
          Jacek Laskowski wrote:
          > Hi Mike,
          >
          > Thanks for the response. Unfortunatelly, it's happening on a production
          > server and nobody's changing anything. The error message pops up every
          > 2-3 days and the only way to get rid of that is to reboot the server.
          > Hmmm...I could even say it's hitting us quite regularly.
          >
          > The first time I've seen this I thought that there might be somewhere a
          > class which does not really have the necessary setter. It might've been
          > a case, but it's not. Even though we assume it might happen, what's
          > going on with the WLS classloaders that they pick up the right class at
          > the startup and after some time they change their mind and pick up the
          > wrong one. That would be a bug, shouldn't it ?
          >
          > What's more annoying is the fact that we're not able to open a case in
          > the support as there is nothing to be shown. There is merely the error
          > message which anybody can clearly explain that it relates to a wrong
          > class - no setter in it.
          >
          > The only way I can think of would be to enable remote debugging and as
          > soon as it's happend, connect to the WLS JVM and see what's wrong. We
          > don't have the WLS sources, though.
          >
          > -Jacek
          >
          > Mike Reiche wrote:
          > >
          > > Is it possible that the tag was changed - an attribute was added in the .tld and
          > > to the class?
          > >
          > > The new .tld is seen immediately. The new class is not - not until you restart
          > > WL.
          > >
          > > Mike
          > >
          > > Jacek Laskowski <[email protected]> wrote:
          > > >Hi,
          > > >
          > > >After some time of work, WLS ends up with the following error message:
          > > >
          > > >weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
          > > >'cm': There is no setter method for property 'limit', for Tag
          > > > class 'com.hp.module.cm.tag.GetDocumentsTag'
          > > > at
          > > >weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
          > > > at
          > > >weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:272)
          > > > at
          > > >weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
          > > > at
          > > >weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
          > > > at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
          > > > at
          > > >weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3811)
          > > > at
          > > >weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3561)
          > > > at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3422)
          > > > at
          > > >weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1760)
          > > > at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1601)
          > > > at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1491)
          > > > at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:880)
          > > > at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
          > > > at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
          > > > at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
          > > > at
          > > >weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
          > > > at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:302)
          > > > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:217)
          > > > at
          > > >weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:164)
          > > > at
          > > >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:101)
          > > > at
          > > >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
          > > > at
          > > >weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
          > > > at
          > > >weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
          > > > at
          > > >weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
          > > > at
          > > >weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
          > > > at
          > > >weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
          > > >
          > > >The class does contain the setter, so we don't know why the message pops
          > > >up. After rebooting the server, the page works properly (!) Does anyone
          > > >know how to get rid of it ? We're running out of ideas, and rebooting
          > > >the server every 2-3 days is not acceptable.
          > > >
          > > >The configuration consists of BEA WebLogic 5.1.0 SP8 + JDK 1.2.2_07 +
          > > >HPUX 11.0.
          > > >
          > > >Any help is greatly appreciated.
          > > >
          > > >Jacek Laskowski

How can I limit the size of a file upload?

I am uploading a file using a file reference using the code below. I want to limit the file size (bytes) of the uploaded file to 100k, so that a huge file won't crash the browser or my SWF.
What's the best place in the following process to test this, and actually prevent the large file from being loaded? Is that even possible?
private function uploadImageBtn_clickHandler() : void {
     var arr:Array = [];
     arr.push(new FileFilter("Images", "*.gif;*.jpeg;*.jpg;*.png"));
     fileRef.browse(arr);
private function fileReference_select(evt:Event):void {
     fileRef.load();
private function fileReference_complete(event:Event):void {
     var loader:Loader = new Loader();
     loader.contentLoaderInfo.addEventListener(Event.COMPLETE, loader_complete);
     loader.loadBytes(fileRef.data);
public function loader_complete (event:Event) : void {
     trace("Loader info = "+event.currentTarget.bytesLoaded); // file size in bytes
     var sourceBMP:Bitmap = event.currentTarget.loader.content as Bitmap;
     bgImage.source = sourceBMP;

Thank you. I just needed to be pointed in the right direction. After looking over this stuff, including FilePermission, I think this may give me what I was looking for. It will be a while before I get to implementing it or testing something like this, I'm just trying to get a grasp on all of the things I need to do and how to approach it.
By doing this I can control how much filespace it can use.
I can control CPU usage by monitoring for extra threads that don't belong and killing or settings the priority on it.
Now I just need to think of something to monitor how much memory the plugin uses. I suppose I could gc, then store the current memory usage, then execute the plugin, gc again, and measure the size again. Does that sound like a reasonable way to estimate it's memory usage? I'm not looking for tiny changes, I just want to see large, substantial increases.

Oracle Text contain query limit with 9i

The Oracle Text contain query is defined as this:
CONTAINS(
[schema.]column,
text_query VARCHAR2
[,label NUMBER])
RETURN NUMBER;
Is the size limit of text_query 4000 bytes with 9i? Is it increased with 10g or is it accepting CLOB in 10g?
I always got the error: "ORA-01460: unimplemented or unreasonable conversion requested" when I do the following where p_var was dynamically passed with size of more than 4000 bytes:
p_statement varchar2(20000);
p_var varchar2(8000);
p_statement := select count(*) from dewey_table where contains(concat, :x)>0;
open m_cursor for p_statement using p_var;
Thanks very much,
Kevin

The limit is definitely 4000 characters in 9i and the 10g documentation shows no change in the calling spec for that parameter.

JSTL in JDeveloper

I'm having trouble getting the jstl tags to work in JDeveloper 9.0.3.
I've downloaded JSTL 1.1.0-B1, extracted it and copied the files under lib/ to (J2EE_HOME)/default-web-app/WEB-INF/lib. The folder didn't exist so I created it.
I still get the following error when I compile:
Error(1): "http://java.sun.com/jstl/core" is not a registered TLD namespace.
Error(1): Unable to load taghandler class: http://java.sun.com/jstl/core
What am I doing wrong?

Hi Lars,
Did you register the taglibs in web.xml? The entries there have to be just right for the libraries to load in the jsp.
Good luck,
Conrad

Simple java archive type deployment is invalid in Jdeveloper 9031

Hi All,
If I choose a Simple Java archive type of deployment of a jsp tag lib project in Jdeveloper the archive does not include the directory layout recursively. Ex. I get this.
c:\> jar tvf test.jar
64 Sat Jan 01 23:53:48 PST 2000 META-INF/MANIFEST.MF
1300 Sat Jan 01 23:53:48 PST 2000 META-INF/autodate.tld
5772 Sat Jan 01 23:53:48 PST 2000 test/autodate.class
Where if I do it the archiving from the comman line. i.e
c:\> jar cvf test.jar META-INF test
I get
0 Wed Feb 26 20:52:42 PST 2003 META-INF/
68 Wed Feb 26 20:52:42 PST 2003 META-INF/MANIFEST.MF
1300 Wed Feb 26 20:12:42 PST 2003 META-INF/autodate.tld
0 Wed Feb 26 20:12:42 PST 2003 test/
5772 Wed Feb 26 20:12:42 PST 2003 test/autodate.class
The latter is a valid archive that I can use for taglib deployment. The former, i.e the Jdev deployed archive does not work. The jsp does not find the tag library.
What is the archiving tool that jdeveloper uses??
Why is it different from doing a command line archive??
Is there anyway I can instruct the deployment tool to include the directory tree in the archive??
- Manish

Hi Lynn,
The Archive looks exactly the same and the jsp fails to find the tld from the classpath.
64 Fri Apr 04 13:53:48 PST 2000 META-INF/MANIFEST.MF
1300 Fri Apr 04 13:36:48 PST 2000 META-INF/autodate.tld
5772 Fri Apr 04 13:42:48 PST 2000 test/autodate.class
Note, this is a problem only when using the Tag lib autodiscovery mechanism of JSP 1.2 where the tld can exist anywhere in the classpath under META-INF and the path is not explicitly specified in the jsp.
- Manish
- Manish

WSImport - Jdeveloper and WSImport generating different code

Hi,
I am using ANT to generate the stubs of a WSDL via WSImport. I m finding that for certain WSDLs the port code is not getting generated and its giving me warnings as
[WARNING] SOAP port "XYZDetailsPort": uses a non-standard SOAP 1.2 binding.
[clientgen] line 33 of file:./XYZIHIDetailsWS.wsdl
[clientgen]
[clientgen] [WARNING] ignoring operation "XYZIHIDetails": message part does not refer to a schema element declaration
[clientgen] line 15 of file:XYZIHIDetailsWS.wsdl
[clientgen]
[clientgen] [WARNING] Port "XYZIHIDetailsPort" does not contain any usable operations
[clientgen] line 33 of file:XYZIHIDetailsWS.wsdl
but its generating fine when I use the Jdeveloper wizard for generating web service proxy.
What codegen tool does Jdev use? I used Weblogic Server's clientgen tool but the I found out that internally it uses wsimport. Any suggestions?
I m using Jdeveloepr 11.1.1.5 OSX, OpenJDK.
Regards,
Ansuman
Edited by: AnsumanRoy on Jan 5, 2012 2:02 PM

Then the DB Schema is changed and the code needs to be modified in order to take advantage of the new schema.You should be able to use "Synchronize features" in Bc4J wizards (Rightmouse on Package node and select Sychronize... or edit individual entity and select "Synchronize" on the attributes panel).
You may also want to see JDev online help - search for Synchronize
Is it possible to use the Jdeveloper to modify the code to use the new schema without overwriting the customized code?Yes, designtime wizards do try to "preserve" your code. Let us know more on what kind of synchronized changes are leading to "removal" of custom code.
Are there for example some special tags to add that Jdeveloper recognizes? no.

Is there any limit for VISA allocate DMA memory ?

Hi,
I have get an error: -1073807300, when I allocate memory for DMA larger than 4M Bytes.
Is there any limit for allocate memory for DMA ?
I have run the attach vi on win7 32bit or 64bit, It seems there is a limit at about 4M Bytes.
However I can allocate memory more than 20M Bytes on WinXP system.
Is there any solution for win7 to allocate memory more than 4M Bytes ?

I altered the VI to loop from 1M in increments of 1M until it errored (as fast as it could) and then output the farthest it got without an error. Here is what the plot of those highest allocations looks like and attached is the VI.

Java.lang.UnsatisfiedLinkError in JDeveloper standalone CMSDK application

When I try to run my standalone Content Management application on my development PC against a Content Management SDK deployed on another server (using jvm runtime parameters as in CM WebStarterApp II -DIFS.DOMAIN.Name=ifs://xtorc1:1521:test:CMSDK -DIFS.STANDALONE.Mode=true -DIFS.SCHEMA.PASSWORD=welcome), I got " IFS-20103: Unable to get sessions". When I debug the code, I notice the actual error as following:(I've tested it using JDeveloper versions 10.1.2 and 9.0.4)
(in JDeveloper 10.1.2):
java.lang.UnsatisfiedLinkError: int oracle.jdbc.driver.T2CConnection.t2cCreateState(byte[], int, byte[], int, byte[], int, short, int, short[], byte[], byte[])
(in JDeveloper 9.0.4):
java.lang.UnsatisfiedLinkError: int oracle.jdbc.oci8.OCIDBAccess.make_c_state(boolean)
I've checked the metalink and the forums, however nothing helped me solve the problem so far. It seems like the JDeveloper is confusing the oci driver (the dll's) somehow, however I checked my PATH in my environment, everything seems OK.
I was trying to run a standalone IFS (CM SDK) web application in development machine,
in JDeveloper's embedded OC4J server, against the CM SDK domain on another
server where the Application Server resides. The logon page appears and after
submitting the form the following piece of code returns the error:
String schemaPassword = System.getProperty("IFS.SCHEMA.PASSWORD");
String domainName = System.getProperty("IFS.DOMAIN.Name");
try
//the exception is caused by the following line
m_LibraryService = LibraryService.startService(serviceName, schemaPassword,
null, domainName);
catch (Throwable e)
// the exception is caught here
Any ideas??
ÃzgÃ¼r

I see that you're doing your conection using oci8; I had the same problem and my solution was changed to thin
For example: jdbc:oracle:thin:@IP_ADDRESS:PORT:SID
I hope it can help to you

Limit on tags or bytes in JDeveloper?

Similar Messages

Maybe you are looking for