JSefa is a simple library for stream-based serialization of java objects to XML, CSV, or FLR and back again using an iterator-style interface independent of the serialization format. There is a standard and an android edition available.

Project Activity

See All Activity >

Categories

Data Formats

Follow JSefa

JSefa Web Site

Other Useful Business Software

Reduce Support Costs with TeamSupport’s B2B helpdesk Reduce Support Costs with TeamSupport’s B2B helpdesk Icon
Reduce Support Costs with TeamSupport’s B2B helpdesk Icon

Improve customer satisfaction with powerful and easy to use helpdesk software built specifically for business to business customer support.

We do what you do – business software – so we get it. Customer support is critical to any business and as a B2B provider you not only need to manage contacts and tickets, you need to understand your business relationships at a customer level. TeamSupport is the only helpdesk software built for B2B and made to scale with you as you grow.
  • Easy to Use and Fully Customizable to Your Business
  • Relational Customer Database and Best in Class SLAs

Rate This Project

Login To Rate This Project

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

User Reviews

  • 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 ...

  • 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 :)

Read more reviews >

Additional Project Details

Intended Audience

Developers

Programming Language

Java

Registered

2007-03-02