Where can the Content Type Bean class be found when it is generated automatically?

Hi there,

When a new Content Type ctd is created, a light-weight java bean class will be generated automatically to map this new content type ctd, the default package name is com.cust.contentbean as it is set in Global Settings. But I can't find any jar file that includes this auto-generated java bean, does anybody know?

Thanks a lot!

-Peter

Find more posts tagged with

Comments

They’re generated in memory and loaded from memory; thereis no persisted jar file.

You can generate a jar with the vgnbeangen command-line tool ifyou really want one. Just realize that if you do so, and you put it in your classpathsomewhere, any content bean classes in there will prevent the auto-generationof those same classes, which means that subsequent CTD changes won’t bereflected in those classes until you update the jar file.

More details available here: https://knowledge.opentext.com/knowledge/llisapi.dll/wiki/17781594/ContentBeans vgnbeangen

Mark

From: eLink Entry:Vignette V7 and V8 Web Content Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, January 26, 2011 2:41 PM
To: eLink Recipient
Subject: Where can the Content Type Bean class be found when it isgenerated automatically?

Where can the Content Type Bean class be found when it is generated automatically?

Posted by rcao@toronto.ca (Johns, Peter) On 2011/01/26 15:39

Hi there,

When a new Content Type ctd is created, a light-weight java bean class will be generated automatically to map this new content type ctd, the default package name is com.cust.contentbean as it is set in Global Settings. But I can't find any jar file that includes this auto-generated java bean, does anybody know?

Thanks a lot!

-Peter

[To post a comment, use the normal reply function]
Forum:	Vignette V7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01

Not sure why you want it. But you can generate a jar on demend using the genBean command in the in directory. Keep in mind this will only generate the jar for the current state of the CTDs'

John

Many thanks for the reply. even though I use Managed Object directly, I still have to change the jsp or jsp helper code if the CTD got changed such as xml name, adding/dropping attribute(s). The reason that I wanna use a pojo, is to keep a view jsp page decouping with Vignette API.

After get the generated content bean jar, I realize it's not a pojo bean, it still depends on Vignette API, can't fit the target of decoupling with Vignette API in jsp view page. I have to create my own pojo classes and mappers to handle this issue.

Didn't understand the reason for this can you elaborate. I understand the generated JavaBeans are read only, but they and still follow pojo conbvention for all getters.

If you are seeing any issue please share.

Best Regards

Qutub

From: eLink Entry: Vignette V7 and V8 Web Content Management [v7webcontentmanagement@elinkkc.opentext.com]
Sent: Friday, January 28, 2011 1:50 PM
To: eLink Recipient
Subject: Where can the Content Type Bean class be found when it is generated automatically?

Where can the Content Type Bean class be found when it is generated automatically?

Posted by rcao@toronto.ca (Johns, Peter) On 2011/01/28 13:47

After get the generated content bean jar, I realize it's not a pojo bean, it still depends on Vignette API, can't fit the target of decoupling with Vignette API in jsp view page. I have to create my own pojo classes and mappers to handle this issue.

[To post a comment, use the normal reply function]
Topic:	Where can the Content Type Bean class be found when it is generated automatically?
Forum:	Vignette V7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01

In the current implementation, the generated beans delegate to the underlying ManagedObject instances that are retrieved from the ContentUtil cache. Peter apparently wants something that goes straight to the database (or some other cache) without using any Vignette APIs whatsoever. It's unlikely that we'll be building such a thing, because whatever improvements we pursue in the future will be intended to benefit both the ManagedObject and the ContentBean layers.Mark________________________________________From: eLink Entry: Vignette V7 and V8 Web Content Management [v7webcontentmanagement@elinkkc.opentext.com]Sent: Friday, January 28, 2011 5:58 PMTo: eLink RecipientSubject: RE Where can the Content Type Bean class be found when it is generated automatically?RE Where can the Content Type Bean class be found when it is generated automatically? Posted by qsaifudd (Saifuddin, Qutubuddin) On 2011/01/28 18:58Didn't understand the reason for this can you elaborate. I understand the generated JavaBeans are read only, but they and still follow pojo conbvention for all getters.If you are seeing any issue please share.Best RegardsQutub________________________________From: eLink Entry: Vignette V7 and V8 Web Content Management [v7webcontentmanagement@elinkkc.opentext.com]Sent: Friday, January 28, 2011 1:50 PMTo: eLink RecipientSubject: Where can the Content Type Bean class be found when it is generated automatically?Where can the Content Type Bean class be found when it is generated automatically? Posted by rcao@toronto.ca (Johns, Peter) On 2011/01/28 13:47After get the generated content bean jar, I realize it's not a pojo bean, it still depends on Vignette API, can't fit the target of decoupling with Vignette API in jsp view page. I have to create my own pojo classes and mappers to handle this issue.________________________________[To post a comment, use the normal reply function]Topic: Where can the Content Type Bean class be found when it is generated automatically?Forum: Vignette V7 and V8 Web Content ManagementLivelink Server: knowledge-wlweb01________________________________[To post a comment, use the normal reply function]Topic: Where can the Content Type Bean class be found when it is generated automatically?Forum: Vignette V7 and V8 Web Content ManagementLivelink Server: knowledge-wlweb01

Thanks for the discussion. I try to design a multi-tier architecture as a JEE application best practice, There is an adapter tier to interact with the legacy system-VCM, I use the VCM API to access VCM, when I get data by VCM API, while I would like to use a pojo to save data, so a mapper class will be needed to convert data into a pojo. and this pojo instead of ManagedObject will be used in presentation tier, so the presentation tier doen't need to know any Vignette related stuff, even though you changed content management system vender to IBM, Open Text, or EMC, it still doesn't affect the presentation tier.