Yes, I can... however, not all jsftemplating users will necessarily use
GlassFish. And dataprovider.jar is part of our web application, not
part of the libraries GlassFish provides. So if dataprovider.jar
changes such that jsftemplating requires a different version in the
future, we'd like to be able to provide a different version. So I think
we should leave it as is. That's for the suggestion, though!!
Thanks,
Ken
Senthil Chidambaram wrote:
> Ken,
> Can't you pick dataprovider.jar from
> <glassfish_home>/lib/install/applications/admingui/adminGUI_war/WEB-INF/lib
> directory, instead of checking it in under jsftemplating.
>
> If you want I can go ahead, and make this change in jsftemplating
> build files.
>
> thx
> Senthil
>
> Ken Paulsen wrote:
>
>>
>> Hi Everyone,
>>
>> dataprovider.jar is now required for building jsftemplating. It is
>> not required at runtime unless you are using Woodstock (then
>> Woodstock requires it). I added this so that I could provide a
>> custom DataProvider implementation for simple Woodstock tables that
>> works w/o needing to write any Java code.
>>
>> What does this mean for you? The build.properties.example file has
>> changed. You will need to make sure your build.properties file has
>> this change. The change is:
>>
>> dataprovider.jar=lib/external/woodstock/dataprovider.jar
>>
>> I hope to modularize JSFTemplating's build so different component
>> library support can be built, or skipped. If anyone is interested in
>> helping out with that, let me know!
>>
>> Thanks,
>>
>> Ken Paulsen
>> https://jsftemplating.dev.java.net
>>