Hi,

We created table structure in the database, we created maps
using CocoBase admin tool and generated BMPs using admin tool
and got the source code in Visual Age for Java through
integration. Then we added some business methods in the BMP.
After sometime, we decided to add an attribute. So we altered
the database table and created the map again. But now if I
have to create my BMP again and overwrite the existing one
then I?ll lose all my business methods. Please suggest a
solution for this problem. This kind of scenarios will occur
at our end multiple times, so please treat this issue as a
very high priority one.

You don't have to regenerate, but you can if you'd like
and merge the two versions. Visual Age may have some
merge facility that you like, but often our customers use
a windows based merge facility from www.araxis.com called
Araxis Merge. It's a really nice graphical tool that lets
you do side by side comparison and merge, and it's very
fast to do the task you're describing...

Now if you don't want to regenerate, just add the public
get/set methods on the bean, and stateObject and the
method signature on the remote interface for any new
attributes in the same way that you would for your own
code. The only caveat to this is that you'll notice in
the methods we already have created in your EntityBean,
that we also have a modified flag in the set attribute.
You should also copy this line of code from one of the
other generated method.

That's all you need to ensure you have your existing
code preserved while you add new persistent attributes...

THOUGHT Support

Hi,

Thanks for the response. But i'll really appreciate if
you guys can give me an example on this, clearly highlighting
the changes and the place where we have to make these.

We're not sure what we could/should provide. As we said
before this depends on how you're working as to what you
should do, but here are some general guidelines.

If you want to use CocoBase and regenerate, then you can
use source code control, and then you can easily merge any
changes between the two version with a merge tool such as
the Araxis merge tool.

Otherwise if you just want to add an attribute, you can
just add your own get/set methods by copying the get and
set methods of another attribute as you would with any
java class...

Are these instructions confusing in some way?

THOUGHT Support