[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2297) standard-jaxws-endpoint-config.xml filename in webservice chapter has a dash too much
Shane Bryzak (JIRA)
jira-events at lists.jboss.org
Mon Nov 26 04:08:18 EST 2007
[ http://jira.jboss.com/jira/browse/JBSEAM-2297?page=all ]
Shane Bryzak closed JBSEAM-2297.
--------------------------------
Fix Version/s: 2.0.1.GA
Resolution: Done
Assignee: Shane Bryzak
Ugh, that's no good. Because I don't know how to make it not wrap, I've gone with the grammar-hack solution and created a new paragraph with the filename closer to the beginning of the sentence.
> standard-jaxws-endpoint-config.xml filename in webservice chapter has a dash too much
> -------------------------------------------------------------------------------------
>
> Key: JBSEAM-2297
> URL: http://jira.jboss.com/jira/browse/JBSEAM-2297
> Project: JBoss Seam
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 2.0.0.GA
> Reporter: Paul Bakker
> Assigned To: Shane Bryzak
> Priority: Minor
> Fix For: 2.0.1.GA
>
>
> In the PDF reference documentation, in the webservice chapter, the standard-jaxws-endpoint-config.xml is described. Because of a line-wrap however, there is a dash added between jaxws, which makes the the filename like this: standard-jax-ws-endpoint-config.xml. Because this does not look wrong it's easy to think that the line-wrap dash is part of the filename.
> If the file is named like that, the webservice will throw "no application context available" exeptions when accessing a Seam component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list