We'd like to hear about anything you'd like to tell us. If you're
short on ideas, here are some:
- Anything you found difficult or inconvenient about using TomEE
I've spend a few days trying to figure out and find documentation about
how to customize (enable and handle jaxws schema validation events) when
using tomee and I've found the documentation to be non-existing /
scattered all over the net in various incomplete and out dated bits. I
can now, enable schema validation, but I've yet to be allowed to handle
them. (The same bit took about 30 mins with Tomcat + Metro, thus I'm a
tad frustrated).
Figuring out where to place openejb.xml in a warfile was a mystery at
first, not to mention the many futile attempts to place cxf.xml and
cxf-servlet.xml files where ever one could guess it would be read from
and in the end realizing it wasn't read at all in TomEE.
- Documentation you would like to see
A clearly seperated documentation, so that when you're using TomEE, the
you do not get a mix of TomEE (Tomcat) and OpenEJB standalone
documnetation thrown at you. Do TomEE if you have a TomEE project and
ditch the OpenEJB standalone from this project.
Documentation about how to configure CXF in TomEE and I would like this
documentation to be at TomEE's site, correlated to each released version
and not on some blog somewhere out on the internet.
Simple layout examples with locations of configuration that actually
gets read and works for (in my case) a war file.
- Features you would like to have
Ability to use and hook standard Jaxws schema validation events:
Ability to fully configure CXF endpoints in TomEE.
A complete list of cxf.jaxws. properties supported !? Again not on
some blog, but on TomEE's documentation and correlated to a TomEE
release,- so you can see: "that in 1.7.2 we support this set of
attributes,..."
Not have the SchemaValidation annotation read from the interface class
but the implementing class (so that its up to the implementing class to
determin whether schema validation should be enabled or not, this could
be a CXF issue tho).
Not having to supply the WSDL and XSDs as cxf.jaxws properties when you
enable schema validation through properties, but having the WebService
annotation's wsdlLocation attribute being used (this may be a CXF issue
too tho).
Regards,
Thomas Larsen
