[jbosstools-dev] BIRT and Seam facet (JBoss BIRT Integration)
Snjezana Peco
snjezana.peco at redhat.com
Sun Jun 1 19:56:26 EDT 2008
Hi,
I have tried to create a project to integrate BIRT, JSF and Seam.
The JSF facet is created correctly, but BIRT and Seam have problems when
they are used with other facets.
1) BIRT
The BIRT facet works correctly with J2EE 1.4, but doesn't work with Java
EE 5.
The problem is that BIRT's install delegate uses the old API
(WebArtifactEdit) instead of the new model provider.
For more info see:
http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg05306.html
Steps to reproduce:
Try to create a dynamic web project, choose module version 2.5 and add
the BIRT and JSF 1.2 facet.
web.xml will contain only those artifacts created with the dynamic web
and JSF facet.
I have solved this issue by creating a new facet (JBoss BIRT Reporting
Runtime Component facet).
We probably need to enter a bug against BIRT.
2) Seam
Seam doesn't use WTP API to handle web.xml, but copy web.xml created by
seam-gen.
It isn't compatble with any facet that updates web.xml (Seam's web.xml
includes the JSF servlet and mapping, but overwrites the setting added
by the dynamic web and JSF facet )
If the Seam facet is the last executed facet, Seam will overwrite
artifacts added to the web.xml file by other facets (I get this issue
when adding the new correct BIRT facet that doesn't depend on the Seam
facet).
If some facet is executed after executing the Seam facet, it will
overwrite Seam setting (I get this issue when adding the new BIRT facet
that depends on the Seam facet).
You can test this by adding the Axis2 Web Service facet when creating a
Seam project. AxisServlet, AxisAdminServlet and servlet mappings for
these servlets won't be created
(the Seam facet overwrites Axis2 setting).
I propose to update web.xml using the WTP API (the model provider) in
order to solve this issue.
Snjeza
More information about the jbosstools-dev
mailing list