JSefa Icon

User Ratings

★★★★★
★★★★
★★★
★★
2
0
0
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
Write a Review

User Reviews

  • 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    Jsefa is not bad, but they some bug, 0.9.3 or 1.0.0, you need to fixe it, not perfect 1) you cant add several constraints on cvsfield/flrfield with a validator, you can set only one constraint because you get an error on annotation, feature say we can but in reality it is not possible constraint="maxLength=15" that run, constraint="minLength=5', "maxLength=15"doesnt run and give error 2) When you make validator for your application, you need add jsefa class for get accessor in the package of your validator, or you cant access because not visible. This one : class ConstraintsAccessor { is only visible from current package, we must copy it in package of application validator. 3) you can use for serialization/deserialization a prefix cascade object like object Departement with prefix DEP with subrecord Employee with prefix EMP, The big problem, you must set the same size prefix, if we dont do we get an exception length prefix error, not funny, when you write several blocs record with different structure, it is logic to have a prefix of different size. in case, this mecanizem is totaly useless because we must manage with loop and close/open with several serializer for write several blocs with different size prefix and it is not possible to set padding.. HEADER:.......... CUSTOMER:........ CUSTOMER:........ CUSTOMER:........ CONTRACTORS:.... CONTRACTORS:.... SUBSDIARIES:........... SUBSDIARIES:........... SUBSDIARIES:........... SUBSDIARIES:........... SUBSDIARIES:........... SUBSDIARIES:........... FOOTER ...

    Posted 02/26/2013
  • 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    I am using JSEFA in 2 different projects, where we have to create textual export files. The implementation is really stable and comfortable. Simply annotate what you need, and there you go. I am using FLR and CSV Variants - never tried XML, yet. For FLR i am using compositions of a base class with head-data and specialized classes which extend the base-class for specific data. This works pretty good. I use gaps in the annotation pos = x where i use x in *10 Steps. So I start with pos = 10, pos = 20 and so on. For later inserts of new Data between 2 i take 5 and so on... so this makes it easy to extend the data-lines. Thanks for this piece of code :)

    Posted 11/28/2012

Thanks for helping keep SourceForge clean.

Screenshot instructions:
Windows
Mac
Red Hat Linux   Ubuntu

Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies
X

Briefly describe the problem (required):

Upload screenshot of ad (required):
Select a file, or drag & drop file here.

Please provide the ad click URL, if possible:

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks