[Design of Messaging on JBoss (Messaging/JBoss)] - Re: User documentation for 2.0.0.beta1
by jmesnil
I evaluated Docbook support for OpenOffice and the results are mixed.
* Multiple chapters is not supported. Our doc is split into separate chapters that are included in the master.xml "book".
When I edit one of the individual chapter, OOo does not recognize it as a docbook subset and display the source text (with xml tags)
=> We'd have to aggregate all our document in a single file to be able to use OOo (this means more svn merge operations)
* OpenOffice Docbook support is not complete. If I add a toc tag to the file outside OOo (to generate the table of contents in the output formats), OOo removes it when I save the file.
=> Table of contents would have to be generated from OOo. This means the document generation will no longer be automated
* Section ID. I've some issues to create permalink to sections. Either I have a duplicated title (only 1 having the permalink ID) or none. I'm still figuring out how it works
To sum up, using OOo and saving in docbook:
* does not allow to edit manually the file (changes will be lost next time the file is saved by Ooo)
* prevents automatic generation of HTML/PDF (missing TOC)
I'm not an OOo expert and there may be ways to circumvent these limitations but I haven't found them.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228676#4228676
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228676
15 years, 1 month
[Design of EJB 3.0] - Re: javax.ejb.EJB Annotations Outside EJB3 Components
by jaikiran
<bean name="WSInjectionMetaDataDeploymentAspect" class="org.jboss.wsf.container.jboss50.deployment.metadata.InjectionMetaDataDeploymentAspect">
| <property name="requires">WebMetaData</property>
| <property name="provides">InjectionMetaData</property>
| <property name="ejbReferenceResolver"><inject bean="org.jboss.ejb3.EjbReferenceResolver"/></property>
| </bean>
I did not find the definition for the org.jboss.ejb3.EjbReferenceResolver bean within that jbossws-deployer-jboss-beans.xml. Does this mean that JBossWS will rely on EJB3 deployer jboss-beans.xml to deploy an EjbReferenceResolver? :)
I would recommend that you define your own EjbReferenceResolver (with a unique MC bean name) within JBossWS to ensure that any changes to the EJB3 deployer will not affect JBossWS. Something like:
<bean name="WSInjectionMetaDataDeploymentAspect" class="org.jboss.wsf.container.jboss50.deployment.metadata.InjectionMetaDataDeploymentAspect">
| <property name="requires">WebMetaData</property>
| <property name="provides">InjectionMetaData</property>
| <property name="ejbReferenceResolver"><inject bean="EJBReferenceResolverForWS"/></property>
| </bean>
|
| <bean name="EJBReferenceResolverForWS" class="org.jboss.ejb3.common.resolvers.spi.EjbReferenceResolver">
| <constructor factoryClass="org.jboss.ejb3.common.resolvers.spi.EjbReferenceResolverFactory"
| factoryMethod="newInstance">
| <parameter>org.jboss.ejb3.common.resolvers.plugins.FirstMatchEjbReferenceResolver</parameter>
| </constructor>
| </bean>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228657#4228657
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228657
15 years, 1 month