Hi Isomorphic,
Since some people have had problems using the tag libs, I went ahead and did a prototype with the TLD file bundled in a Jar.
I posted in the past with this thread.
http://forums.smartclient.com/showthread.php?t=18326
Seeing that J2EE1.3 Servlet 2.3 is very old, I made the prototype so that it should work for J2EE1.4 Servlet 2.4 and newer. This means I changed the DTD to XSD and had to change a few element names in the TLD/XML as well as some values of the top level elements.
The code is based off of this build.
Isomorphic SmartClient/SmartGWT Framework (v9.1p_2014-04-09/Enterprise Deployment 2014-04-09) - Initialization Complete
I found that I needed to put the classes and TLD in their own jar so I could put the JAR into WEB-INF/lib so the server would scan the JAR - then the Eclipse tools also could see the TLD and provide hints etc. This is because we use a EAR structure including isomorphic_core_rpc.jar at the EAR level so all the WARS can use that code. So I guess each WAR might need to include the isomorphic_tags.jar in the proposal.
I used this documentation as a usage guide. http://www.smartclient.com/docs/9.1/a/b/c/go.html#group..loadDSTag
In the myDataSources.jsp file you would put the following:
<%@ taglib uri="http://isomorphic.com/jsp/tags" prefix="isomorphic" %>
<isomorphic:loadDS ID="supplyItem" />
No entry in web.xml is required and the taglib does not have to be added to the web project.
I can't upload a jar file so what I did was unjar the isomorphic_core_rpc and remove the properties and xml files from the root level and the remove all the classes except the taglib package. I put the isomorphic.tld file in the META-INF file and re-jarred as isomorphic_tags.jar. TLD file is attached as xml but I believe only tld files are scanned so it would need to be renamed.
The taglib uri could change in the TLD file to your liking. Also the prefix is up to the user but could be <isc:loadDS /> if desired.
Eric R
Since some people have had problems using the tag libs, I went ahead and did a prototype with the TLD file bundled in a Jar.
I posted in the past with this thread.
http://forums.smartclient.com/showthread.php?t=18326
Seeing that J2EE1.3 Servlet 2.3 is very old, I made the prototype so that it should work for J2EE1.4 Servlet 2.4 and newer. This means I changed the DTD to XSD and had to change a few element names in the TLD/XML as well as some values of the top level elements.
The code is based off of this build.
Isomorphic SmartClient/SmartGWT Framework (v9.1p_2014-04-09/Enterprise Deployment 2014-04-09) - Initialization Complete
I found that I needed to put the classes and TLD in their own jar so I could put the JAR into WEB-INF/lib so the server would scan the JAR - then the Eclipse tools also could see the TLD and provide hints etc. This is because we use a EAR structure including isomorphic_core_rpc.jar at the EAR level so all the WARS can use that code. So I guess each WAR might need to include the isomorphic_tags.jar in the proposal.
I used this documentation as a usage guide. http://www.smartclient.com/docs/9.1/a/b/c/go.html#group..loadDSTag
In the myDataSources.jsp file you would put the following:
<%@ taglib uri="http://isomorphic.com/jsp/tags" prefix="isomorphic" %>
<isomorphic:loadDS ID="supplyItem" />
No entry in web.xml is required and the taglib does not have to be added to the web project.
I can't upload a jar file so what I did was unjar the isomorphic_core_rpc and remove the properties and xml files from the root level and the remove all the classes except the taglib package. I put the isomorphic.tld file in the META-INF file and re-jarred as isomorphic_tags.jar. TLD file is attached as xml but I believe only tld files are scanned so it would need to be renamed.
The taglib uri could change in the TLD file to your liking. Also the prefix is up to the user but could be <isc:loadDS /> if desired.
Eric R