]
Norman Richards closed JBSEAM-2775.
-----------------------------------
Resolution: Done
Closing this off, but don't consider this set in stone yet. We've got plenty of
time to refine this if we aren't happy with something or think of better ways.
package-info.java should be optional:"convention over
configuration"
--------------------------------------------------------------------
Key: JBSEAM-2775
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2775
Project: Seam
Issue Type: Feature Request
Reporter: Eric Jung
Assigned To: Norman Richards
Fix For: 2.1.0.BETA1
Attachments: JBSEAM-2775-v3.diff, JBSEAM-2775.diff, JBSEAM-2775.diff
Currently, package-info.java is required when referring to custom Seam components in
components.xml. However, to further align Seam with the "convention over
configuration" philosophy, this file can be optional by making some assumptions:
1. In the absence of package-info.java , the XML namespace in components.xml for custom
components has a well-defined mapping to a Java package
2. This mapping can be defined as:
a. The XML namespace must be parsable by java.net.URI otherwise automatic mapping is
aborted
a. Protocol (scheme), the www/ subdomain, port, query parameters, anchors (references),
and userInfo are ignored, if present.
b. The top-level domain becomes the root Java package
c. Subdomains become Java packages under the root package, applied in right-to-left
order as specified in the URI.
d. The path, as returned by URI.getPath(), is mapped to further Java packages such that
each path element becomes another Java package appended in left-to-right order
Examples:
http://www.company.com/department/product ==> com.company.department.product
https://company.com/department/product ==> com.company.department.product
ftp://www.company.org/department/product ==> org.company.department.product
abc://company.org/department/product ==> org.company.department.product
company.net/foo/bar/baz ==> net.company.foo.bar.baz
JIRA isn't displaying my last example correctly. See
http://pastebin.mozilla.org/375878 for the last example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: