[switchyard-issues] [JBoss JIRA] (SWITCHYARD-486) Application projects should build without warning

[Keith Babo (Created) (JIRA)]

Application projects should build without warning
-------------------------------------------------

                 Key: SWITCHYARD-486
                 URL: https://issues.jboss.org/browse/SWITCHYARD-486
             Project: SwitchYard
          Issue Type: Sub-task
          Components: build, tooling
            Reporter: Keith Babo


When building a SwitchYard application project, the user sees several WARNING messages in the test output.  We need to investigate these and address them.  I suggest walking through the quickstarts and building them one at a time while viewing the build output.  For each ERROR/WARNING in the output, do the following:

o If it's an issue with the application, fix it.
o If it's an issue with SwitchYard core or a component, file an issue.
o If it's spurious log output, filter it with log4j.  This applies to the quickstart and possibly to the forge/eclipse tooling when creating a new project.

Here are some examples from the bean-service quickstart:

Why are we looking up commons-cli?  Where is this dependency creeping in?  Possibly forge-related.
{noformat}
[WARNING] Could not transfer metadata org.apache.commons:commons-cli:2.0-SNAPSHOT/maven-metadata.xml from/to apache.m1 (http://people.apache.org/repo/m1-snapshot-repository/): No connector available to access repository apache.m1 (http://people.apache.org/repo/m1-snapshot-repository/) of type legacy using the available factories WagonRepositoryConnectorFactory
{noformat}

This could be chunked encoding returned to the SOAP component.  We see this issue in JBESB as well.  For now, we can simply file a JIRA against SOAP component and investigate it separately.
{noformat}
10:43:25,500 WARN  [httpclient.HttpMethodBase] Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
{noformat}

This needs to be address with a log4j filter.  Note that the log4j filter should *only* go in the src/test/resources directory so that it's not packaged with the application.
{noformat}
404 [main] WARN org.jboss.interceptor.util.InterceptionTypeRegistry - Class 'javax.ejb.PostActivate' not found, interception based on it is not enabled
404 [main] WARN org.jboss.interceptor.util.InterceptionTypeRegistry - Class 'javax.ejb.PrePassivate' not found, interception based on it is not enabled
{noformat}



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira