Open source Tag Library

Hi,
i wish to use the tag library (http://displaytag.sf.net) within a portlet. I have the successfully created this but when i select the Next / Prev links, the table is displayed outside off the portlet.
Has anyone successfully implemented this or any other 3rd party tag library into portlal ?
I cannot use the netui-data:pager or netui-data:grid tags as they only support the datasource javax.sql.RowSet. I need to use java.util.List.
Thanks
Mark

"Mark Gilleece" <[email protected]> wrote in message
news:16491524.1092761567367.JavaMail.root@jserv5...
i wish to use the tag library (http://displaytag.sf.net) within a portlet.
I have the
successfully created this but when i select the Next / Prev links, thetable is displayed
outside off the portlet.The problem here is that tag libraries and third party code need to work
with the portal APIs in order to have request parameters, etc prefixed with
portlet instance identifiers. If they don't do this and you used the same
tags in multiple portlets the request parameters would collide.
I cannot use the netui-data:pager or netui-data:grid tags as they onlysupport the datasource javax.sql.RowSet. I need to use java.util.List.
Why not create a simple RowSet implementation around the List and feed that
to the pager and grid tags. Alternatively, use the repeater tag and handle
paging yourself as it is a pretty trivial operation.
Cheers,
Gerald

Similar Messages

  • OT: Yahoo open sources Javascript library

    Scott had a interesting link on his blog recently.
    http://developer.yahoo.net/yui/index.html
    http://yuiblog.com/
    http://developer.yahoo.net/ypatterns/
    Interesting development. Wonder what their business rationale for doing this is.
    It is kinda sad to see whole new Javascript toolkits being built from scratch over and over again. There are so many awesome toolkits out there today (Dojo, Prototype, script.aculo.us, the list goes on), wonder why the communities don't just collaborate and concentrate on 1 or 2 toolkits. I guess that is the open source model at work :-(

    Hallo,
    ... and ApEx is doing their own also. How about integration of e.g. http://www.dojotoolkit.org/ and collaborate with that framework?
    dojo has a real good basic structure and stable foundation of their libraries to write high level browser independent JavaScript Code (including an Aspect Oriented Event System in JavaScript, that is very powerful).
    What about wrapping the libaries
    htmldb_html_elements.js over dojo.html.* and
    htmldb_get.js over dojo.hostenv / dojo.rpc
    For further info on dojo see:
    http://www.ajaxian.com/articles/dojo-in-practice/DojoToolkitInPractice.pdf
    http://www.javapassion.com/j2ee/DojoToolkit_speakernoted.pdf
    For comparison of different toolkits see:
    http://forums.theajaxworkshop.com/viewtopic.php?t=237&sid=0a6781a1deec72ba3f7e851e3d4746ed
    Thx, Willi

  • Open Source j2me Library

    hi to all.
    i am working in Netbeans 5.5 with j2me WTK 2.5. As all know there is no special GUI controls. Now my questions is
    1. is there any j2me GUI library that integrate in Netbeans environment (5.5 or 6.0)..
    Can anybody help me in this regards. Bcoz there are alot of applications build in j2me having special GUI controls. I need it urgently.
    best regards
    Hassan Mushtaq

    1. how can i integrate this library into netbeans 5.5 or Netbeans 6.0Tools ---> Library Manager ---> Add Jar
    And you simply add the jar file of the library , in the classpath tab.
    After that to use the library you have to add it, in your project properties
    2. Which Netbeans IDE u recommend to use this library. currently i m using 5.5.Either stay with 5.5 or upgrade to 6 , it doesn't matter the library works on both.
    3. Can i integrate its control in Netbeans visual editor? if Yes How?No , till this point i think could be wrong though
    1. Is j2me Polish is free? i don't think so. J2ME Polish is free , http://www.j2mepolish.org/ (url tag still doesn't work)
    With Polish you can use the visual editor, since polish uses the same GUI components and enhances them with CSS.
    I strongly recommend the J2ME Polish tool , i have been using it a while and it has great potentials especially for creating bundles of the application for different mobiles , as well for the interface enhancements. There is also a book i bought on J2ME Polish called Pro J2ME Polish if you are interested
    Regards
    Andreas Michaelides

  • Windows not showing. Page source and library windows open but not showing.

    I select View --> Page Source and no window appears. Under the Window menu, the item Source: . . . shows but no window. If I close the main window then the item is ticked but still no actual window.
    I have disable all extensions and plugins, safe mode, revert all preferences.
    the same happens with Show all Bookmarks. This is why I posted this under bookmarks problems originally - see below.
    I now find the same happens to downloads and Error console windows. No problems in Safari or MS Word (usually the worst performer)
    Bookmarks are all present, but show all bookmarks produces no window, even though the window menu shows an item and I can select it.
    Mac OS 10.6.8 FF 5.01 Show all bookmarks shows no window, even if I close the main window. Under window menu the 'Library' item is ticked but still nothing. I have restarted, and renamed places database. recently installed some of these addons

    The one that solved it was my own last post, which does not have a Solved it.
    I copied the FF profile folder from another login and started with that.
    However. . . the problem is back. I installed extensions, NoScript and MyBookmarks and it seemed OK after that.
    Then I installed Download Youtube videos + 3.3.51, then DownThemAll! 2.0.7, Google Shortcuts 2.1..6, ImTranslator, QuickWiki and Read It later. No Plugins ennabled.
    when I disable all extensions then the windows for downloads, error console and 'open link in new window appear OK, but not the source or Library windows.
    As before they are on the window menu but no way to make them visible.

  • Announce: JSTL (Standard Tags) + Struts (MVC) live web Demo (open source)

    If you are starting a Java Web, you should use MVC and Standard tags,
              this "kit" is a sample of "best" (at least good) practices.
              It is MVC (Struts/Tiles)+JSTL XSLT DAO (Open Source Data Access Object
              w/ SQL) + DB CRUD (Create update delete and SQL DLL scripts)+ J2EE
              Security ( to make Tomcat run like Apache )
              It is KISS (you'll see how simple and how very standard) , good
              practices Free Open Source Framework to develop any web app, with the
              aim of being 80% of any app, but done as simple as possible and easy to
              teach. Again, everything is standard and simple. And it is the fastest,
              most efficient way to develop maintainable code I know of.
              Samples include CMS (Authorize content, XSLT, CMS Comments, sinkable,
              single sign on, etc.), Issue tracking, + more coming.
              Please download and install and see if you want to attend. Details:
              http://basicportal.sourceforge.net
              I use it to teach Struts + JSTL public and private classes. I epically
              teach WHY you should want to do something in a certain way, not just how.
              To attend and see "best practices"
              http://www.basebeans.com/webEx.jsp
              The seminar requires you know servlets, jsp, SQL, JDBC, and at least
              some MVC. (a plus is if you have already deployed and MVC web app in the
              past) Oh...it is $10.00 ( but free to baseBeans clients and/or apache.org
              committers.)
              To keep in touch on this join "MVC-Programmers" mail list at
              http://www.netbean.net/mailman/listinfo/mvc-programmers
              To keep in touch with open source projects go to
              http://news.netbean.net/cgi-bin/webnews.cgi
              Future plans include more docs, Dream weaver support, mail client, RSS
              feeds, BLOG, Shopping Cart Store, etc. etc.
              Did I say everything is standard and as simple as possible?
              Vic
              "Always code to the least amount of astonishment"
              Elements of Java Style
              

    Hi Devlin.
    > And changing the TLD is not
    > something I think should be done. 
    -> http://help.sap.com/saphelp_nw04/helpdata/en/e7/1f1e405d21c442e10000000a1550b0/frameset.htm
    > I see the portal-inf/lib  Is this the
    > same as web-inf/lib and gets picked up by the
    > webserver?
    -> yes. http://help.sap.com/saphelp_nw04/helpdata/en/f9/561140d72dc442e10000000a1550b0/frameset.htm
    Regards, Karsten

  • Do I need to pay anything to Adobe if I inject java script using some open source library?

    Hello,
    I want to restrict PDF reader to achieve Digital Rights Management (DRM).
    Do I need to pay anything to Adobe if I inject java script to achieve so using some open source library?
    Basically I want my PDF documents to be restricted such that I can: 
    Limit printing
    Prevent screenshots
    Restrict access by license expiry date
    Restrict distribution of downloaded PDF (i.e. the document should run on specific machine only)
    Restrict copy and paste within PDF document
    I came across below links from which I suspect Adobe expects one to pay if he/she attempts to restrict reader functionality in some way?
    http://www.adobe.com/devnet/reader/topic_drm.html
    http://www.adobe.com/devnet/acrobat/overview.html
    Am I correct in my assumption?

    I think it is a vain hope to imagine you could implement DRM via JavaScript. Remember it can be turned off.
    Printing is either enabled or disabled according to document security.
    Working with PDFs does not require permission from Adobe but
    * adding functionality to Adobe Reader definitely does; a DRM development license is a major investment.
    * if the file is Reader-enabled, all third party tools will disable that.

  • Connection Pooling and JSP Custom Tag Library - is code (inside) the best way/correc?

    Hi, can anyone advise as to whether my tag library code (based
    on Apache Jakarta Project) will actually achieve connection
    pooling functionality across my entire JSP based application? I
    am slightly concerned that my OracleConnectionCacheImpl object
    may exist multiple times, hence rendering my conection pooling
    attempt useless.
    package com.solved.tag.dbtags.connection;
    import java.io.IOException;
    import java.sql.Connection;
    import java.sql.SQLException;
    import javax.servlet.jsp.tagext.TagSupport;
    import javax.servlet.jsp.JspTagException;
    import javax.sql.DataSource;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    import oracle.jdbc.pool.OracleConnectionCacheImpl;
    * <p>JSP tag connection, used to get a
    * java.sql.Connection object.</p>
    * <p>JSP Tag Lib Descriptor
    * <pre>
    * &lt;name>connection&lt;/name>
    &lt;tagclass>com.solved.tag.dbtags.connection.ConnectionTag&lt;/t
    agclass>
    * &lt;bodycontent>JSP&lt;/bodycontent>
    &lt;teiclass>com.solved.tag.dbtags.connection.ConnectionTEI&lt;/t
    eiclass>
    * &lt;info>Opens a connection based on a jndiName.&lt;/info>
    * &lt;attribute>
    * &lt;name>id&lt;/name>
    * &lt;required>true&lt;/required>
    * &lt;rtexprvalue>false&lt;/rtexprvalue>
    * &lt;/attribute>
    * </pre>
    * @author Matt Shannon
    public class ConnectionTag extends TagSupport {
    static private OracleConnectionCacheImpl cache = null;
    public int doStartTag() throws JspTagException {
    try {
    Connection conn = null;
    if (cache == null) {
    try {
    InitialContext ic = new InitialContext();
    DataSource ds = (DataSource) ic.lookup
    ("jdbc/pool/OracleCache");
    cache = (OracleConnectionCacheImpl)ds;
    catch (NamingException ne) {
    throw new JspTagException(ne.toString());
    conn = cache.getConnection();
    pageContext.setAttribute(getId(),conn);
    catch (SQLException e) {
    throw new JspTagException(e.toString());
    return EVAL_BODY_INCLUDE;
    package com.solved.tag.dbtags.connection;
    import java.sql.Connection;
    import java.sql.SQLException;
    import javax.servlet.jsp.tagext.TagSupport;
    * <p>JSP tag closeconnection, used to close the
    * specified java.sql.Connection.<p>
    * <p>JSP Tag Lib Descriptor
    * <pre>
    * &lt;name>closeConnection&lt;/name>
    &lt;tagclass>com.solved.tag.dbtags.connection.CloseConnectionTag&
    lt;/tagclass>
    * &lt;bodycontent>empty&lt;/bodycontent>
    * &lt;info>Close the specified connection. The "conn"
    attribute is the name of a
    * connection object in the page context.&lt;/info>
    * &lt;attribute>
    * &lt;name>conn&lt;/name>
    * &lt;required>true&lt;/required>
    * &lt;rtexprvalue>false&lt;/rtexprvalue>
    * &lt;/attribute>
    * </pre>
    * @author Matt Shannon
    * @see ConnectionTag
    public class CloseConnectionTag extends TagSupport {
    private String _connId = null;
    * The "conn" attribute is the name of a
    * page context object containing a
    * java.sql.Connection.
    * @param connectionId
    * attribute name of the java.sql.Connection to
    close.
    * @see ConnectionTag
    public void setConn(String connectionId) {
    _connId = connectionId;
    public int doStartTag() {
    try {
    Connection conn = (Connection)pageContext.getAttribute
    (_connId);
    conn.close();
    } catch (SQLException e) {
    // failing to close a connection is not fatal
    e.printStackTrace();
    return EVAL_BODY_INCLUDE;
    public void release() {
    _connId = null;
    package com.solved.tag.dbtags.connection;
    import javax.servlet.jsp.tagext.TagData;
    import javax.servlet.jsp.tagext.TagExtraInfo;
    import javax.servlet.jsp.tagext.VariableInfo;
    * TagExtraInfo for the connection tag. This
    * TagExtraInfo specifies that the ConnectionTag
    * assigns a java.sql.Connection object to the
    * "id" attribute at the end tag.
    * @author Matt Shannon
    * @see ConnectionTag
    public class ConnectionTEI extends TagExtraInfo {
    public final VariableInfo[] getVariableInfo(TagData data)
    return new VariableInfo[]
    new VariableInfo(
    data.getAttributeString("id"),
    "java.sql.Connection",
    true,
    VariableInfo.AT_END
    data-sources.xml:
    <?xml version="1.0"?>
    <!DOCTYPE data-sources PUBLIC "Orion data-
    sources" "http://xmlns.oracle.com/ias/dtds/data-sources.dtd">
    <data-sources>
    <data-source
    class="oracle.jdbc.pool.OracleConnectionCacheImpl"
    name="jdbc/pool/OracleCache"
    location="jdbc/pool/OracleCache"
    url="jdbc:oracle:thin:@oracle1:1521:pdev"
    >
    <property name="maxLimit" value="15" />
    <property name="cacheScheme" value="2" />
    <property name="user" value="console" />
    <property name="password" value="console" />
    <description>
    This DataSource is using an Oracle-native DataSource Class so as
    to allow Oracle Specific extensions.
    A getConnection() call on this DataSource will return
    oracle.jdbc.driver.OracleConnection.
    The connection returned is a logical connection.
    The caching scheme in place is Fixed Wait. Refer below to
    possible values.
    Dynamic 1
    Fixed Wait 2
    Fixed Return Null 3
    </description>
    </data-source>
    </data-sources>
    many thanks,
    Matt.

    Hi. Show me your pool definition.
    Joe
    Ramamurthy wrote:
    I am using the jsp custom tag library from BEA called sqltags.tld which came with Weblogic 5.1. Currently I am using Weblogic6.1 sp2 on Solaris.
    I have created a Connection Pool for Sybase database using the driver com.sybase.jdbc.SybDriver.
    When I created jsp page to connect to the connection pool using sqltags custom tag library, I am getting the error
    "javax.servlet.jsp.JspException: Failed to write body content
    at weblogic.taglib.sql.ConnectionTag.doAfterBody(ConnectionTag.java:43)
    at jsp_servlet.__hubwcdata._jspService(__sampletest.java:1014)"
    After this message, whenever I try to access the same jsp page I am getting the message
    "javax.servlet.jsp.JspException: Failed to load JDBC driver: weblogic.jdbc.pool.D
    river
    at weblogic.taglib.sql.ConnectionTag.doStartTag(ConnectionTag.java:34)
    at jsp_servlet.__hubwcdata._jspService(__sampletest.java:205)".
    Can you please help me the reason why this problem is happening and how to fix this ?
    This problem doexn't happen consistently. This occurs once in a while.
    I tried to increase Login delay Seconds parameter in the Connection Pool to 15 sec. It didn't help me much.
    Thanks for your help !!!
    Ram

  • Definitive Word On ID3 Tags, Library Files & Which Data Is Stored Where...

    I have spent a few hours just now (and have read the discussions a lot previously) on various iTunes issues, namely ones pertaining to organization and storage of data & info. I still have quite a few questions I would like the definitive answers for. If anyone knows for sure, thanks in advance for your response!
    1) Is there any difference between how and where iTunes stores data for audio (mp3, m4a, aif, etc.) files vs. movie (mpg, mp4, mov) files, and if so, what are they?
    2) In the info tabs/panes of tracks in iTunes, is the entered data stored in separate places? i.e., the info under the INFO pane stored in the individual media file itself while that in the OPTIONS pane stored in the main library file? Also, did I read correctly that Convert ID3 Tags causes more of the library file data to be embedded in the media file itself? (Not desirable of course, because each play would in effect "modify" the file as if it had changed and needed to be resynched, since play count is part of the data).
    3) Is there a difference between where editable data (artist, title, equalizer setting, genre, rating, etc.) is stored vs uneditable data such as play count, date added, last played, etc.?
    4) Is there a list somewhere online that shows what data is stored in the library file (settings unique to the iTunes) and what is universally in the standard ID3 tag in the media file itself?
    5) Is it safe to assume that rating, equalizer, volume, remember position and start/stop time settings for each individual track are not in the ID3 tag but only in the library file? If so, one can then assume that merely copying the library file will preserve these settings?
    6) Are ID3 tags applied and applicable to movie and audio files similarly, and do they further differ how & if they are used among each file type (mp3, m4a, aif, wav, mpg, mp4, mov, etc.)? I know with movies you cannot set or change the poster frame in mpg (muxed) files, for example.
    7) I do all my iTunes importing, editing, managment, etc. on my PowerMac desktop, with the prefs, library and xml files stored in my home folder on the PowerMac's OS drive and the large media files store on an attached ext. 500 GB FW drive. If I use a synching program to continuously keep the library/xml files the same on my iBook laptop's home folder and the media files the same on another ext. 160 GB FW drive, then when I use the iBook with the 160 GB at different events it should operate exactly the same a when using my PowerMac at home with the 500 GB? The only thing I should have to change is the location of the iTunes folder in the Prefs on the iBook to point to the 160 GB, right?
    8) Finally, now that iTunes 7 allows you to indicate sort order ("The Beatles" can now appear under "B" without writing "Beatles, The" as I have been) would it retain that sort when importing the song list into other database programs or even an iPod, or would it default back to "T"? (AppleWorks database has a similar feature where you can specify an ARTIST field which sorts by first letter of last word, but won't stay that way in other programs).
    PHEW! ...long post I know, but I spent a lot of time reading and hopefully over time I can get the answers to most (or even all) of these questions. Thanks!!!
    PowerMac G4/500 MHz (1 GB); iBook G4/1.33 GHz (1.5 GB)   Mac OS X (10.4.9)   (still using 10.3.9 Panther on PowerMac)

    I read this on the ID3 site:
    ID3 tags were designed with the MP3 file format in mind. ID3v2 tags will break formats which are container-based such as Ogg Vorbis and WMA. Here is some information on specific formats:
    ID3 tags work in MP3 and MP3pro files
    WAV has no tags
    WMA has its own tagging format, which is specified in the wma spec, available in the MSDN (which unfortunately, basically does not allow Open Source implementations)
    Ogg Vorbis uses "Xiph Comments" (same as later versions of FLAC and Speex), which are embedded into the Ogg container. You can find information on these in the comment and container specs on www.xiph.org
    AAC uses yet another tagging format, which does not at present have a published spec as of 3/1/2006.
    So since I rip in AAC, does that mean the tags work differently, are stored differently or offer different editable info? Also, I found nothing regarding tags for video files as I mentioned in my question. Within iTunes I am assuming all the information you may edit or view when you Get Info for each file is not all stored together: some is in the file's ID3 tag and others in the iTunes Library file. I guess you are always safe if you keep back-ups of your media files and library files, even if you don't always know which info resides where.
    I found a complete list of frames (fields) that are available in ID3v2 at the following link, many not available in iTunes, but the site lists other apps that allow you to edit tags for both Mac & Windows.
    http://www.id3.org/Frames
    I am curious, if you use another app to edit the tag with a frame not offered in iTunes, will it still work in iTunes (like if you use the frame for synchronized lyrics; since it is part of the tag itself will they show up when played in iTunes even though not editable in iTunes)?

  • Tag library 'div' hook

    Well, 'div' is not corrupt, but the application programming related to customization of Tag libraries is corrupt.
    What is happening:
    When Dreamweaver CC is installed, and when it opens fresh html files, it makes a mess of line breaks and indents in the text layout of the code. Using the menu item Commands / Apply source formatting also makes a mess, This menu command mess is a slight improvement over the horrendous mess that Dreamweaver CC makes of code when it opens and when it periodically 'refreshes' the files that it trashes. However, the code is not usable, as with more advanced css and html technique, the code becomes unreadable for Chrome, Internet Explorer, Safari, and presumably all browsers.
    DW's mess described:
    All indents are as spaces, making manual clean-up repetitive, necessary and extremely tedious.
    The head and body tags are indented far inside their content, and that content is also erratically indented.
    The use of Tag library editor would seem the expected user path, in seeking a user resolution, and perhaps in defining a programmatic intervention.
    All tags are trashed, put going to the heart of the html cascade, we start with the p tag: e.g., p tag in Tag libraries defaults as
    Line breaks: before and after tag
    Contents: formatted and indented
    Case: default
    We try numerous combinations of p tag settings in the noted dialog interface.
    The p tag settings do not appear to effect the mess. Dreamweaver, ignores default and manual settings, sometimes shuffling the mess a little, but minor shuffling only occurring twice, and without any tag block line break changes.
    Perhaps, for a given instance of Dreamweaver installation, within a given simple document's system interface, Dreamweaver settings may reveal something called a 'performance hook' by application programmers. Perhaps we can isolate a hook that is useful for the Adobe support; support that lacking professional attention has maintained Dreamweaver as a failed application for over a year (since October 2012) on my Windows desktop. We move next to the div tag.
    Manual intervention 'exposes bad behavior of div tag' hook:
    Our simple document layout is... simple. Deploying doctypes for both html5 and xhtml transitional and deploying internal and external style methods, with the same code trashing result, we correctly layout tags as HEAD, BODY, DIV and P. Beginning with the p tag, various tag library settings are applied to determine effect on Apply source formatting command. Various p tag settings have no effect, and p is returned to its DW default setting, as noted above. The following div tag settings disable Apply source formatting command's code trashing specifically of line indents.
    Line breaks: before and after tag
    Contents: formatted but not indented
    Case: default
    Unfortunately, with this setting, line breaks between only some tags are maintained during Dreamweaver's auto code trashing (e.g., between closing head and opening body tag): sometimes when Dreamweaver does it's auto (or manual) trashing, these specific line breaks, between block tags, are not preserved. However, with this Tag library setting for the div tag using the noted basic cascade, all tag indents are ignored. But only when code is manually kept against left margin, without any indentation. And, ONLY WITH DIV TAG HOLDING THESE PARTICULAR SETTINGS, FOR THIS PARTICULAR DOCUMENT!
    FLAT CODE is preferable to the bigger mess that Dreamweaver routinely imposes as it auto trashes code. Also, allowing any left margin indentation worsens Dreamweaver's code trashing... so, given Dreamweaver's chaotic destructiveness, I don't know if it is correct to imply any significance to my manual Tag library settings management, but it is clear that Dreamweaver is unable to correct the mess it makes, using the manual Apply source formatting command. And this is the first 'performance hook' that has been defined for my desktop in over 400 days. But setting div tag in this way is the only way to stop Dreamweaver trashing code layout line indents (trashing that occurs both during Dreamweaver automatic actions and with user menu action, for the specific noted html layout - a layout that is far too basic to be useful for 99.9% of design work). But only for a given instance of Dreamweaver installation for a given OS installation, and not across OS installations, or with any other file than the file (or files, in relational assessment) targeted for our 'hook' presentation analysis.
    Conclusion:
    Dreamweaver trashes code layout every time the application applies code formatting (e.g., opening new documents from other sources, applying menu commands, etc.). That is, all user code layout will be trashed by Dreamweaver. However, a specific div tag setting in Tag library editor may maintain a single instance for manual correction of Dreamweaver code trashing, when basic page layout is used with div in the noted cascade, and with div settings manually corrected as noted. This is a hopelessly unacceptable condition that the Dreamweaver application imposes on design work for my Windows 8.1 operating system. Professional designers of global significance and stature using many variants of Mac and PC systems have warned me not to use Dreamweaver, recommending numerous alternatives. I am taking the position that Adobe retains a shred of marketplace survivability, and therefore will promptly fix minor problems when I bring them to Adobe's attention.
    IMPORTANT:
    Obviously, this is not acceptable application performance. Is support available to Adobe that will now, immediately repair the Dreamweaver application that I use as a paid subscription to eliminate systematic code trashing?

    I figured it out. Under the Configuration/TagLibraries,
    create a CrossTagAttr folder and stick a .vtm file in it. In the
    .vtm file, use the <crosstag_attributes> tag and its
    children. See Configuration/TagLibraries/CrossTagAttr/Spry/Spry.vtm
    for an example.

  • How to make Open Source work on Solaris 10, x86 ?

    I'm trying to make this Open Source code for MDBTools work on my
    Solaris 10, x86.
    What this tool does is to read in a Microsoft Access MDB file, and
    outputs the contents of that database file, into an ASCII text file.
    I unzipped these files already, but how do I make "mdbtools" work on
    Solaris x86, version 10?
    http://sourceforge.net/search/?type_of_search=soft&words=mdbtools
    http://sourceforge.net/projects/mdbtools/files/mdbtools/mdbtools-0.6pre1.tar.gz/download

    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking dlfcn.h usability... yes
    checking dlfcn.h presence... yes
    checking for dlfcn.h... yes
    checking for g++... no
    checking for c++... no
    checking for gpp... no
    checking for aCC... no
    checking for CC... no
    checking for cxx... no
    checking for cc++... no
    checking for cl... no
    checking for FCC... no
    checking for KCC... no
    checking for RCC... no
    checking for xlC_r... no
    checking for xlC... no
    checking whether we are using the GNU C++ compiler... no
    checking whether g++ accepts -g... no
    checking dependency style of g++... none
    checking how to run the C++ preprocessor... /lib/cpp
    checking for g77... no
    checking for f77... no
    checking for xlf... no
    checking for frt... no
    checking for pgf77... no
    checking for fl32... no
    checking for af77... no
    checking for fort77... no
    checking for f90... no
    checking for xlf90... no
    checking for pgf90... no
    checking for epcf90... no
    checking for f95... no
    checking for fort... no
    checking for xlf95... no
    checking for lf95... no
    checking for g95... no
    checking whether we are using the GNU Fortran 77 compiler... no
    checking whether accepts -g... no
    checking the maximum length of command line arguments... 262144
    checking command to parse /usr/ccs/bin/nm -p output from gcc object... ok
    checking for objdir... .libs
    checking for ar... false
    checking for ranlib... :
    checking for strip... :
    checking if gcc static flag works... yes
    checking if gcc supports -fno-rtti -fno-exceptions... no
    checking for gcc option to produce PIC... -fPIC
    checking if gcc PIC flag -fPIC works... yes
    checking if gcc supports -c -o file.o... yes
    checking whether the gcc linker (/usr/ccs/bin/ld) supports shared libraries... yes
    checking whether -lc should be explicitly linked in... yes
    checking dynamic linker characteristics... solaris2.10 ld.so
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... no
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    configure: creating libtool
    appending configuration tag "CXX" to libtool
    checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes
    libtool.m4: error: problem compiling CXX test program
    checking for g++ option to produce PIC...
    checking if g++ supports -c -o file.o... no
    checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes
    checking dynamic linker characteristics... solaris2.10 ld.so
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... no
    appending configuration tag "F77" to libtool
    checking for flex... no
    checking for lex... no
    checking for yywrap in -lfl... no
    checking for yywrap in -ll... yes
    checking for bison... no
    checking for byacc... no
    checking for ANSI C header files... (cached) yes
    checking fcntl.h usability... yes
    checking fcntl.h presence... yes
    checking for fcntl.h... yes
    checking limits.h usability... yes
    checking limits.h presence... yes
    checking for limits.h... yes
    checking for unistd.h... (cached) yes
    checking wordexp.h usability... yes
    checking wordexp.h presence... yes
    checking for wordexp.h... yes
    checking for an ANSI C-conforming const... yes
    checking for size_t... yes
    checking whether byte ordering is bigendian... no
    checking Are we using flex ... yes
    checking for SQLGetPrivateProfileString in -lodbcinst... no
    checking for pkg-config... /usr/bin/pkg-config
    checking for GLIB - version >= 2.0.0... yes (version 2.4.1)
    checking for libglade-2.0 libgnomeui-2.0... yes
    checking GNOME_CFLAGS... -DORBIT2=1 -mt -I/usr/include/libglade-2.0 -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/openwin/include -I/usr/sfw/include -I/usr/sfw/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libgnomeui-2.0 -I/usr/include/libgnome-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -I/usr/include/libbonoboui-2.0 -I/usr/include/orbit-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/bonobo-activation-2.0
    checking GNOME_LIBS... -mt -lglade-2.0 -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lxml2 -lpthread -lz -lgnomecanvas-2 -lgnome-2 -lpopt -lart_lgpl_2 -lpangoft2-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lmlib -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lbonobo-2 -lgconf-2 -lgnomevfs-2 -lbonobo-activation -lORBit-2 -lgobject-2.0 -lresolv -lnsl -lsocket -lm -lgmodule-2.0 -lgthread-2.0 -lglib-2.0
    checking gtk-doc version >= 1.0... yes
    checking for initscr in -lncurses... no
    checking for add_history in -lreadline... no
    configure: creating ./config.status
    config.status: creating src/Makefile
    config.status: creating libmdb.pc
    config.status: creating libmdbsql.pc
    config.status: creating src/util/Makefile
    config.status: creating src/extras/Makefile
    config.status: creating Makefile
    config.status: creating include/Makefile
    config.status: creating src/libmdb/Makefile
    config.status: creating src/sql/Makefile
    config.status: creating src/odbc/Makefile
    config.status: creating doc/Makefile
    config.status: creating src/gmdb2/Makefile
    config.status: creating src/gmdb2/gladefiles/Makefile
    config.status: creating src/gmdb2/pixmaps/Makefile
    config.status: creating src/gmdb2/help/Makefile
    config.status: creating src/gmdb2/help/C/Makefile
    config.status: creating mdbtools.spec
    config.status: creating include/mdbver.h
    config.status: creating include/config.h
    config.status: include/config.h is unchanged
    config.status: executing depfiles commands
    @

  • Open Source releasing best practices?

    Hello,
    When creating open source software, I don't really know what the best way to release it (what kind of makefile, versioning system, etc...) is. It's also hard to find this info online, is there any good online info or book about this?
    Here are some of my questions...
    -How many operating systems should your makefile support? Should I make special cases for every single Linux distro and other OS in the makefile, or can I just  put a generic "g++ *.cpp" in the makefile, and let each OS and distro's own package managers take care of tailoring it to their OS?
    -For makefile complexity, I guess there is a scale ranging from a hack like just typing "g++ *.cpp" in it, through having nice sections, groups of files and definitions like "CFLAGS", all the way up to projects which have 20 different makefiles in them like "Makefile.in", "Makefile.pandora", etc.... Where on that scale should you ideally be?
    -Makefiles of many projects look incredibly complex, why?
    -What versioning system to use? When to make a 1.0.0? When to append "rc" at the end?
    -When to tag stable versions? And when you change something in head, do you need to change version number every single time?
    -When creating a dynamic library, and you tagged a stable version, and you then change something in head. Should in the makefile the version number of the library name be changed to something? If so, should it be changed to a next minor version, or to something with "-rc" at the end?
    -What names should be used for tags of versions?
    -Does there need to be both a zipped version of the source code and one under VCS, and if so why is that zipped version needed?
    -Are there any naming conventions for output binaries and libraries?
    -Are you supposed to let your makefile clean up .o files after compilation or not?
    -Are there any conventions for makefiles for names of sections and variables in it? E.g. is it a good idea to have a "clean:" in your makefile to remove everything?
    -When depending on another library which is hosted somewhere else, how to handle that? What when statically depending on it?
    -Any other things I should know?
    Thanks!
    Last edited by aardwolf (2013-05-07 12:32:57)

    aardwolf wrote:Hello,
    Many of your questions have no single correct response. I'll reply with my own opinions and experiences, based on my release of two open source projects (GPT fdisk and rEFInd).
    -How many operating systems should your makefile support? Should I make special cases for every single Linux distro and other OS in the makefile, or can I just  put a generic "g++ *.cpp" in the makefile, and let each OS and distro's own package managers take care of tailoring it to their OS?
    Ideally, a Makefile should build a package under every OS on the planet. In practice, this isn't always practical. Many developers use programs like Autotools to create Makefiles that are suited to a particular build environment. Other developers (myself included) create a handful of Makefiles for different environments -- for instance, my GPT fdisk has Makefiles for Linux, FreeBSD, OS X, and Windows. My rEFInd officially supports building only under Linux, although it supports two EFI toolkits (GNU-EFI and TianoCore EDK II) via a cascading set of Makefiles. Any of these Makefiles can require changes depending on the distribution and development environment in use, but that's not really my concern.
    If a distribution requires changes, that type of change is generally best left to a build system like Autotools or to the person who builds or packages the program. IMHO, it's unreasonable to ask a developer to make minor tweaks to a static Makefile to support every minor Linux variant on the planet.
    -For makefile complexity, I guess there is a scale ranging from a hack like just typing "g++ *.cpp" in it, through having nice sections, groups of files and definitions like "CFLAGS", all the way up to projects which have 20 different makefiles in them like "Makefile.in", "Makefile.pandora", etc.... Where on that scale should you ideally be?
    This is very much a matter of personal preference and project complexity. Autotools or something similar will make it easy for users and distribution maintainers, but can be tricky to use for the developer. If your program is a simple single-file C program, you might forego a Makefile completely; but for something on the scale of the Linux kernel, a Makefile (or something equivalent) is absolutely required.
    -Makefiles of many projects look incredibly complex, why?
    Some projects are very complex, as in the Linux kernel itself. Other times, the Makefiles generated by automated systems like Autotools can be more complex than they might be if they were hand-crafted. In still other cases the developers like complexity or are barely competent at creating Makefiles and so create something that's more complex than it needs to be.
    -What versioning system to use? When to make a 1.0.0? When to append "rc" at the end?
    AFAIK, there are no standards on this. A 1.0 release denotes that something has moved beyond "beta test" status -- in other words, you think it's stable and usable for the masses. Open source software authors tend to be conservative in making that judgment, so pre-1.0 releases in the open source world are often as good as post-1.0 releases of commercial software. The bottom line, though, is that it is a judgment call -- what I consider "1.0" software you might consider well beyond that point and something else might consider pre-beta.
    As to release candidate (RC), not all projects use that designation at all. It seems to me to be more common among large projects as they approach major release milestones, to denote something that is close to being finalized, but not quite -- essentially a sort of very late beta stage, even if the initial 1.0 release was made some time before.
    -When to tag stable versions? And when you change something in head, do you need to change version number every single time?
    If the code changes, you should definitely change the version number. Most developers accumulate several changes before making a new official release, though. Personally, I make full releases with three-digit numbers (like 0.8.6 or 0.6.10), and I upload minor changes to my project's git repository with four-digit numbers (like 0.8.6.1 or 0.6.10.2), but don't do full releases with tarballs and RPMs and whatnot for these, except in a limited way if I want specific people to test a recent change because they filed a bug report. Others have other systems.
    -When creating a dynamic library, and you tagged a stable version, and you then change something in head. Should in the makefile the version number of the library name be changed to something? If so, should it be changed to a next minor version, or to something with "-rc" at the end?
    The key difference with dynamic libraries is that the interfaces should not change with minor changes. IIRC, the second digit (like "2" in 1.2.3) is the cutoff point. In other words, a program that uses library version 1.2.3 should continue to work without changes or recompilation with library 1.2.4 or 1.2.2 (assuming no bugs). This enables users to upgrade the library (from 1.2.3 to 1.2.4 or the like) without upgrading every binary that relies on it. With version 1.3.0, though, the interface to the library might change in a way that would require recompilation of the program or even changes to the source code. Thus, changing the library from 1.2.4 to 1.3.0 will require the user to upgrade all the programs that use that dynamic library (or keep the old version around along with the new one). Note that I've never created a publicly-released library, and it's been a while since I've read up on this, so I might be a little off on these details.
    -What names should be used for tags of versions?
    I'm not sure what you mean by this.
    -Does there need to be both a zipped version of the source code and one under VCS, and if so why is that zipped version needed?
    You can do it any way you want; but as a general rule, you should provide source code in a tarball or .zip file because that's easier to download. Some package systems, such as RPM, require that a source package filename be specified, and so not providing source in such a package just complicates matters for packagers and therefore makes it less likely that they'll bother packaging your program at all. This in turn makes it harder for your users to use the program.
    Note that most Linux programs' source code is provided as tarballs rather than as .zip files. Some cross-platform programs can be exceptions to this rule. For instance, I used .zip for rEFInd (a boot loader) because .zip is a little more common in Windows -- although I'm sure either would have worked fine, in practice.
    You should probably provide binary builds of your software -- although in some cases this can be tricky because a binary built for Distribution A may not work on Distribution B because of library differences. The OpenSUSE Build Service (OBS) can help with this, although it's a bit of a pain to use.
    -Are there any naming conventions for output binaries and libraries?
    Not AFAIK, except of course for filename extensions like .so and .a.
    -Are you supposed to let your makefile clean up .o files after compilation or not?
    No, except for the "clean" target and anything else that's supposed to do this.
    -Are there any conventions for makefiles for names of sections and variables in it? E.g. is it a good idea to have a "clean:" in your makefile to remove everything?
    The "all" target builds everything, "clean" cleans up, "install" installs everything, and "uninstall" uninstalls everything. There's no law that says you have to have all of these, but they're common, particularly with big projects.
    -When depending on another library which is hosted somewhere else, how to handle that? What when statically depending on it?
    This type of thing is generally handled by packaging programs (pacman, rpm, dpkg, etc.), not by developers' Makefiles. That said, Makefile builders like Autotools should check for the relevant development libraries and stop if they aren't present. That will handle the static linking issue, as well as other problems. On another level, when using RPM, a source RPM will include dependencies on the relevant development libraries, and Debian source files have a similar feature. Putting these files together is the responsibility of distribution maintainers, not of program authors.
    -Any other things I should know?
    There's a huge range of acceptable practices on these issues. As a general rule, though, the smaller the package the more likely you are to find a simple Makefile that builds the whole project. Bigger projects are more likely to rely on multiple Makefiles, Autotools, or other complex pre-build software. More standardization emerges at the distribution level, in the form of source and binary RPMs, Debian packages, etc. You shouldn't need to worry too much about that. So long as your package builds with few or no changes on a variety of distributions, the distribution packagers can handle the rest. Build systems always support patches so that minor changes to Makefiles or whatnot can be incorporated. This frees you up to worry about other things rather than trying to support every minor variant distribution in existence.

  • Template tag library

    I am building a tag library to take care of templating. However, I have some questions.
    right now, here is how they work.
    <it:Template>
    <it:TemplateSet varName='test' value='Here is an example'/>
    <%@include uri='test.tpl' %>
    </it:Template>
    where test.tpl would have
    <it:TemplateGet varName='test'>
    What I want to do is to integrate the template file, test.tpl, into the top level template tag. like this: <it:Template file='test.tpl'>
    then include whatever is in the tpl file into the body of the Template tag.
    any suggestions.

    I did something similar.
    http://ostermiller.org/bte/
    But instead of including full files, I include the content of the file in another file.
    This means that you can have a file with
    <html>
    Welcome to my site
    include content-
    </html>
    and then two content files:
    content
    page 1
    content
    page 2
    Both pages get built with the appropriate header.
    It gets a bit more complicated than that because you can have more than just one variable (such as the content variable). I use it with servlets rather than JSP. I don't know how hard it would be to integrate into JSP. (Its open source if you want to try.)
    Stephen

  • New free/open-source tool to encapsulate the OCI interface

    Hello,
    Here is a short presentation and a link to a new free tool available on soureceforge.net.
    This tool is a powerful "wrapper" to encapsulate the OCI interface:
    Introduction
    OCILIB is a free, open source and platform independant library, written in C, that access Oracle Databases.
    The OCILIB library :
    * Encapsulates OCI (Oracle Call Interface which is powerful but complex)
    * Hides OCI complexity
    * Proposes instead a simple, readable and reusable API
    * Offers up to 310 simple and straightforward APIs.
    Introduction
    Current version : 2.3.0 (2008-03-30)
    Main features
    * Data binding
    * Integrated smart define and fetch mecanisms
    * Full Unicode support on all platorms
    * Multi row fetching
    * Binding array Interface for fast and massive bulk operations
    * Reusable Statements
    * Connection Pooling
    * Global Transactions
    * Returning DML feature support
    * ROWIDs support
    * Named Types (Object types) support (User or Builtin)
    * Cursors
    * PL/SQL blocks
    * PL/SQL Ref cursors and Nested tables
    * LOB (BLOBs/ FILEs)
    * Supports lobs > 4Go
    * Long datatype (piecewise operations)
    * Provides "All in one" Formatted functions (printf's like)
    * Smallest possible memory usage
    * Date/time management
    * Timestamps and Intervals support
    * Error handling
    * Describe database schema objects
    * Access columns by index or name
    * Hash tables API
    * Portable Threads and mutexes API
    * Supports static / shared oracle linkage
    * Support runtime loading (no OCI libs required at compile / time)
    * Great performances (straight OCI encapsulation)
    Download
    Get OCILIB from OCILIB Project page at Sourceforge Website:
    http://orclib.sourceforge.net/
    Hope this would help some of you ;D
    Francois

    Don't give up just because there are other options out there.
    Adobe is only giving up the free tool for education purposes, or unemployed developer.  You didn't say if you were one of those.
    I believe over time there will be plenty of room for alternate IDE approaches that support the Flex Framework; and in fact there are quite a few options already out there.

  • "No tag library could be found with this URI" error while compiling jsp

    I am using WebLogic Server 9.2 MP1, JDK 1.5.0_09, Struts 1.3.5
              I am pre-compiling jsp pages with wlappc ant task. However, I got following errors when a jsp page contains ant taglib:
              No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
              The jsp page looks like:
              <%@ taglib uri="http://struts.apache.org/tags-html" prefix="html" %>
              wlappc complains taglib could not be retrieved from this uri. Actually, since Struts 1.3.5, those ".tld" files are contained in strust-taglib-1.3.5.jar, folder META-INF/tld/. And I don't need to set anything in web.xml <tag-lib> tab anymore.
              All the jsp pages can be successfully compiled while being deployed to Server. So what am I missing? My build.xml file looks like:
                   <target name="compile-jsp">
                        <wlappc source="${src.dir}" output="${out.dir}"
                             keepgenerated="true" optimize="true" classpathref="wl_classpath"/>
                   </target>
              where "wl_classpath" contains all the struts related jar files, e.g. struts-core-1.3.5.jar, struts-taglib-1.3.5.jar, ...., and weblogic related jars, e.g. weblogic.jar.....
              I checked "beehive" samples coming with weblogic92, and found it pretty much did the same thing regarding build script and jsp files. So I am totally lost!
              Please help me out. Many thanks.
              Edited by jqian at 02/02/2007 10:24 AM

    Yes sorry, you're correct. The uri I mentioned is just 1.0.
    Do you have the "Oracle WebLogic Web App Extension" Facet for your web project? If not, try adding that and making sure that there is a weblogic.xml file created in the WEB-INF dir. The weblogic.xml file allows you to deploy usig a shared lib for JSTL. It should contain a library-ref element something like the following, with a version of 1.1.
    <wls:library-ref>
    <wls:library-name>jstl</wls:library-name>
    <wls:specification-version>1.1</wls:specification-version>
    <wls:exact-match>true</wls:exact-match>
    </wls:library-ref>

  • My app can't see the tag library

    Hi everybody,
    I am developing an application in JSP which accesses an Oracle database and display the results to the user.
    I am using the tag "exceltag.jar" taken from "http://www.servletsuite.com/servlets/exceltag.htm" to convert an html table to an excel sheet. This works fine on my computer but it fails after we installed the application to our web server, running Tomcat 4.1.12.
    The "exceltag.jar" file has been placed under 'WEB-INF\lib' and the classpath has been set to point to that location. However when I attempt to convert the html table to an excel sheet by clicking a button, I get the following error:
    java.lang.NoClassDefFoundError:
    javax/servlet/jsp/tagext/BodyTagSupport at java.lang.ClassLoader.defineClass0(Native Method) at
    java.lang.ClassLoader.defineClass(ClassLoader.java:509)
    It seems like the application can't see the "exceltag.jar" file.
    What do I need to do to overcome this problem?
    Thank you very much.

    The servlet.jar is in TOMCAT_HOME/common/lib. Since all the JARs in that directory are automatically added to the CLASSPATH and are visible to all applications running under Tomcat, you don't have to do anything for the class loader to find it.
    Your app's WEB-INF/lib directory JARs are also automatically added to to the CLASSPATH. That's the correct place to put that exceltag.jar, by the way, not the TOMCAT_HOME/common/lib.
    As a matter of fact, if you have a system CLASSPATH, be sure that Tomcat ignores it completely. You shouldn't even have one, IMO. (I don't.)
    When I open up the servlet.jar in my TOMCAT_H0ME/common/lib, I can see a class named BodyTagSupport with path javax.servlet.jsp.tagext. You should, too.
    In your exceltag.jar, you should find a TLD for the library. Open that with a text editor and make sure that the text under the <uri> tag matches that in your JSP. For example, I use the JSTL tag library. The c.tld has this <uri> tag:
      <uri>http://java.sun.com/jstl/core</uri>My JSPs that want to use the core tag library have this near the top of the page:
    <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>Notice how the URIs match. That's what yours should do, too.
    If you don't find a TLD inside the exceltag.jar, that means they didn't package it properly. - MOD

Maybe you are looking for