Be the first to post a text review of SPWrapper. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Code committed

  bricconi committed patchset 82 of module distribution to the SPWrapper CVS repository, changing 1 files

  posted by bricconi 367 days ago

• Code committed

  bricconi committed patchset 21 of module NBSPWrapperPlugin to the SPWrapper CVS repository, changing 1 files

  posted by bricconi 373 days ago

• Tracker artifact added

  bricconi created the artifact

  posted by bricconi 399 days ago

• nbspwplugin 2.0.3 file released: NBSPWrapperPlugin-2.0.3.zip

  this release fixes a bug with netbeans 6.1, due to a log library incomatibility. It also introduces DYNTABLES, very useful with oracle stored procedures with refcursors. Data in ref cursor gets loaded into a list of hash tables. The list preseves rows sorting and the has table make data access available through column names.

  posted 447 days ago

• spwrapper 0.9.2 file released: SPWrapper-0.9.2.zip

  Added dyntable support for oracle result set in stored procedures

  posted 447 days ago

• Oracle RefCursor News

  Hello, the new release increases the support for ref cursor with stored procedures introducing dyntable datatype. DYNTABLE make it easyer to deal with these result set. You simply have to provide an overry rule in the ant makefile to turn a result set output into a dyntable output. For each dyntable parameter this snippet is added to the generated source code java.sql.ResultSet r_X_RIGHE_CONTAB=(narrowedStatement).getCursor(8); if (r_X_RIGHE_CONTAB != null) { ResultSetMetaData meta = r_X_RIGHE_CONTAB.getMetaData(); while (r_X_RIGHE_CONTAB.next()) { HashMap<String, Object> row = new HashMap<String, Object>(); int colNo = meta.getColumnCount(); for (int i = 1; i <= colNo; i++) { String name = meta.getColumnName(i); row.put(name, r_X_RIGHE_CONTAB.getObject(i)); } X_RIGHE_CONTAB.add(row); } } X_RIGHE_CONTAB is the output parameter name, the result set. The result set is iterated and a new hashmap is created for each row, then each column object is read out with getObject, and pushed into the hashmap. Notice that the Oracle JDBC driver returns column names all uppercase, so the Hash key are all uppercase strings. The actual hashmap value is always the object returned by the jdbc driver, so some surprise can occour. For instance Number types are converted to BigDecimals! If you are using the code inside Tomcat you have one furter step to do before using this code. You have to make the underlying connection directly available to SPWrapper. In fact Tomcat hides the native connection inside its pooling object, but we need the proprietary getCursor method to retrive the data. Open you context file and add change the Resource tag as follows <Resource auth="Container" driverClassName="oracle.jdbc.OracleDriver" name="jdbc/xxxx" password="xxxx" type="javax.sql.DataSource" url="jdbc:oracle:thin:@10.10.10.10:1521:ORCL" username="yyyyy" accessToUnderlyingConnectionAllowed='true' /> The key is to add the accessToUnderlyingConnectionAllowed='true' attribute to the resource. Now you are ready to use DYNTABLEs inside your web pages.

  posted by bricconi 447 days ago

• File released: /nbspwplugin/2.0.3/NBSPWrapperPlugin-2.0.3.zip

  posted 447 days ago

• Code committed

  bricconi committed patchset 20 of module NBSPWrapperPlugin to the SPWrapper CVS repository, changing 8 files

  posted by bricconi 447 days ago

• File released: /spwrapper/0.9.2/SPWrapper-0.9.2.zip

  posted 447 days ago

• Code committed

  bricconi committed patchset 81 of module distribution to the SPWrapper CVS repository, changing 2 files

  posted by bricconi 447 days ago