One option is to check the usage with https://docs.oracle.com/javase/8/docs/api/java/io/FilenameFilter.html

https://wso2.org/jira/projects/CDEPLOY/issues/CDEPLOY-2

For the following invalid authorization header values CXF returns Java exceptions along with stack trace to the client side.

1. multiple empty spaces after "Basic" string with/without client credentials (this is a valid case according to the specification) [1]
2. Using client credentials with spaces in between
3. Using invalid encoded JSON data as client credentials

[1] curl -k -d "grant_type=password&username=Username&password=Password" -H "Authorization: Basic something" http://localhost:8280/token

Need to update carbon-kernel version to 5.2.0-m3 and carbon-feature-plugin version to 3.0.0 with the changes introduced in the directory structure, osgi tests and the global configuration model.

Description:
Even though the latest release is v5.1.8, package export version in org.wso2.carbon.deployment.engine and org.wso2.carbon.deployment.notifier components is still v5.0.0 because of carbon.deployment.pkg.export.version property in the parent pom.xml.

Affected Product Version:
v5.1.8

Description:

The following jars need to be upgraded.

cxf-xjc-dv-3.0.2.jar
httpasyncclient-4.0-beta3.jar
httpclient-4.2.5.jar
spring-core-3.0.7.RELEASE.jar

Suggested Labels:

Suggested Assignees:

Affected Product Version:
APIM 2.1.0
OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

We added surefire plugin to downgrade the version to 2.18.1 as temporary fix(#265) to fixed the issue #264.
Remove this fix once we merge wso2/carbon-parent#36 and upgrade the carbon-parent version

For PR #262 We would need to create two folders, i.e.,

• one for the Server - where custerm can deploy artifacts
• one for the Runtime - for WSO2 specific artifacts.

https://wso2.org/jira/projects/CDEPLOY/issues/CDEPLOY-4

A large file (> 50MB) may take more time to get copied to deployment directory. This may result in corrupt file behavior when repository scanner starts to scan with schedule. Properly handle this behavior.

https://wso2.org/jira/projects/CDEPLOY/issues/CDEPLOY-8

Currently, we don't have OSGi tests for deployments. We need to have some tests

Handle hot update of artifacts (handle gracefully) - undeploy/deploy will not work since server will be on an inconsistent state.

• put deployer on maintenance mode (reject or queue the income requests)
• if there are available request first serve all that req’s and then deploy the new artifact. This has to be coordinated with deployer and runtime.

https://wso2.org/jira/projects/CDEPLOY/issues/CDEPLOY-7

When building MB-4 in the EI 7 profile the following error was thrown:

ERROR {org.wso2.carbon.deployment.engine.internal.DeploymentEngineListenerComponent} - Could not initialize carbon deployment engine org.wso2.carbon.deployment.engine.exception.DeploymentEngineException: Cannot find repository : /home/riyafa/Documents/Workspace/product-mb/product/target/wso2mb-4.0.0-SNAPSHOT/deployment
    at org.wso2.carbon.deployment.engine.internal.DeploymentEngine.start(DeploymentEngine.java:103)
    at org.wso2.carbon.deployment.engine.internal.DeploymentEngineListenerComponent.onAllRequiredCapabilitiesAvailable(DeploymentEngineListenerComponent.java:212)
    at org.wso2.carbon.kernel.internal.startupresolver.StartupComponentManager.lambda$notifySatisfiableComponents$51(StartupComponentManager.java:238)
    at java.util.ArrayList.forEach(ArrayList.java:1249)
    at org.wso2.carbon.kernel.internal.startupresolver.StartupComponentManager.notifySatisfiableComponents(StartupComponentManager.java:224)
    at org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver$1.run(StartupOrderResolver.java:204)
    at java.util.TimerThread.mainLoop(Timer.java:555)
    at java.util.TimerThread.run(Timer.java:505)

Currently MB-4 uses carbon-deployment feature and the reason for the issue is because the deployment folder is not present in the product. Manual fix is to create a folder named deployment in the product.
This issue has been noticed to occur in other products using this feature. The fix would be to create the deployment folder when the product is built rather than having to create it manually.

Enterprise Integrator 6.0 requires a change in directory structure. Hence current "$CARBON_HOME/repository/conf" moves in to "$CARBON_HOME/conf". This is fixed with carbon-kernel 4.4.12 within CarbonUtils to read the System parameter.

Within carbon-deployment there are certain places which refers to older format with coded parameters. These needs to be fixed in order to use the current CarbonConfigDir.

In triggered deployment, we need to provide an API which takes in a Callback. This call back will be notified with the status of the deployment. This is use-full to let the callers know about the status of the deployment.

https://wso2.org/jira/projects/CDEPLOY/issues/CDEPLOY-6

Description:
It is not possible to change the session manager used by updating the configs in context.xml as the manager is always dynamically set to an instance of CarbonTomcatSessionManager in the deployer.

For WSO2 Identity Server, there are no use cases which require webapps to be accessed in the same tenant context which deployed the app. Webapps should be accessible across tenants.

In the current implementation shown above, the CarbonTomcatSessionManager is explicitly set for webapps in the Super Tenant realm during deployment. Therefore, those webapps become accessible only from within Super Tenant context.

https://wso2.org/jira/projects/CDEPLOY/issues/CDEPLOY-5

• Add new changes in carbon-config, carbon-utils

Throwing below error,
Waiting for Jenkins to finish collecting data[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project osgi-tests: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ERROR] Command was /bin/sh -c cd /build/jenkins-home/workspace/platform-builds/carbon-deployment/tests/osgi-tests && /build/jenkins-home/software/java/jdk1.8.0_45/jre/bin/java '-javaagent:/build/jenkins-home/workspace/platform-builds/carbon-deployment/.repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/build/jenkins-home/workspace/platform-builds/carbon-deployment/tests/osgi-tests/target/jacoco.exec,includes=org.wso2.carbon*' -jar /build/jenkins-home/workspace/platform-builds/carbon-deployment/tests/osgi-tests/target/surefire/surefirebooter5152829544684532020.jar /build/jenkins-home/workspace/platform-builds/carbon-deployment/tests/osgi-tests/target/surefire/surefire8592043572268409080tmp /build/jenkins-home/workspace/platform-builds/carbon-deployment/tests/osgi-tests/target/surefire/surefire_24347295732707164145tmp