[jira] Closed: (GERONIMO-5602) SPNEGO support in Geronimo failed.
[ https://issues.apache.org/jira/browse/GERONIMO-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang closed GERONIMO-5602. --- Resolution: Invalid Close this JIRA based on janel's posting. SPNEGO support in Geronimo failed. -- Key: GERONIMO-5602 URL: https://issues.apache.org/jira/browse/GERONIMO-5602 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 3.0 Environment: OS:Windows 7 Server:Geronimo 3.0 Build 2010.09.08-09:38:48.805+0800 JVM:IBM 1.6.0 Reporter: janel Zhang Assignee: Han Hong Fang Fix For: 3.0 Attachments: file-realm-demo-2.1.0.0(updated).war, file-realm-demo-2.1.0.0.war, spnego_properties_realm_tester1.xml 1.Deploy SPENGO realm spnego_properties_realm_tester1.xml, work correctly. 2.Deploy war file-realm-demo-2.1.0.0.war,fail.The error is as following: Unable to resolve reference ConfigurationFactory in gbean com.ibm.wasce.samples/security-demo/2.1.0.0/war?J2EEApplication=nul l,j2eeType=WebModule,name=com.ibm.wasce.samples/security-demo/2.1.0.0/war to a gbean matching the pattern [?name=SpnegoTest#org.apache.geronimo.securi ty.jaas.ConfigurationFactory] due to: No matches for referencePatterns: [?name=SpnegoTest#org.apache.geron imo.security.jaas.ConfigurationFactory] org.apache.geronimo.common.DeploymentException: Unable to resolve reference Con figurationFactory in gbean com.ibm.wasce.samples/security-demo/2.1.0.0/war?J2EEApplication=nul l,j2eeType=WebModule,name=com.ibm.wasce.samples/security-demo/2.1.0.0/war to a gbean matching the pattern [?name=SpnegoTest#org.apache.geronimo.securi ty.jaas.ConfigurationFactory] due to: No matches for referencePatterns: [?name=SpnegoTest#org.apache.geron imo.security.jaas.ConfigurationFactory] at org.apache.geronimo.deployment.DeploymentContext.getConfigurationData (DeploymentContext.java:534) at org.apache.geronimo.deployment.Deployer.install(Deployer.java:342) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:265) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(Refl ectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio n.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java: 245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doD eploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(Dis tributeCommand.java:61) at java.lang.Thread.run(Thread.java:736) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-673) Don't download TPTP runtime since maven-eclipsepde-plugin 1.1 can handle optional bundle now
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai updated GERONIMODEVTOOLS-673: --- Description: From 2.1.6, building GEP will download TPTP runtime from eclipse site. In fact, it's not necessary now, since maven-eclipsepde-plugin 1.1 has been updated and we don't have to download optional bundle such as plugins in TPTP runtime. was: From 2.2.x, building GEP will download TPTP runtime from eclipse site. In fact, it's not necessary now, since maven-eclipsepde-plugin 1.1 has been updated and we don't have to download optional bundle such as plugins in TPTP runtime. Don't download TPTP runtime since maven-eclipsepde-plugin 1.1 can handle optional bundle now Key: GERONIMODEVTOOLS-673 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-673 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 3.0 From 2.1.6, building GEP will download TPTP runtime from eclipse site. In fact, it's not necessary now, since maven-eclipsepde-plugin 1.1 has been updated and we don't have to download optional bundle such as plugins in TPTP runtime. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-673) Don't download TPTP runtime since maven-eclipsepde-plugin 1.1 can handle optional bundle now
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang updated GERONIMODEVTOOLS-673: --- Attachment: GERONIMODEVTOOLS-673 .patch Please check the patch. Thanks! Don't download TPTP runtime since maven-eclipsepde-plugin 1.1 can handle optional bundle now Key: GERONIMODEVTOOLS-673 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-673 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 3.0 Attachments: GERONIMODEVTOOLS-673 .patch From 2.1.6, building GEP will download TPTP runtime from eclipse site. In fact, it's not necessary now, since maven-eclipsepde-plugin 1.1 has been updated and we don't have to download optional bundle such as plugins in TPTP runtime. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
How to package the standalone ejb file ?
Hi,
In the past, while deploying a standalone ejb module, we renamed it with
ejb.jar and packaged in in the car package, and we use the same way now in
OSGI, which means ejb.jar is added to the bundle-classpath.
This causes some failures, while scanning the annotations, it uses the codes
below, while the zipFileDiscroveryRequired is called, the parameter s is
ejb.jar, which leads to all the classes are ignored. I am wondering why we
wrapper the initial ejb jar file, why not directly use it ?
---
final String location = module.getModuleId();
boolean useLocation = location != null
!location.isEmpty()
!module.getJarLocation().endsWith(.war);
if (useLocation) {
ResourceDiscoveryFilter filter = new
ResourceDiscoveryFilter() {
@Override
public boolean rangeDiscoveryRequired(DiscoveryRange
discoveryRange) {
return discoveryRange ==
DiscoveryRange.BUNDLE_CLASSPATH || discoveryRange ==
DiscoveryRange.FRAGMENT_BUNDLES;
}
@Override
public boolean zipFileDiscoveryRequired(String s) {
return s.equals(location);
}
@Override
public boolean directoryDiscoveryRequired(String s) {
return s.equals(location);
}
};
return new BundleAnnotationFinder(packageAdmin, bundle,
filter);
} else {
ResourceDiscoveryFilter filter = new
ResourceDiscoveryFilter() {
@Override
public boolean rangeDiscoveryRequired(DiscoveryRange
discoveryRange) {
return discoveryRange ==
DiscoveryRange.BUNDLE_CLASSPATH || discoveryRange ==
DiscoveryRange.FRAGMENT_BUNDLES;
}
@Override
public boolean zipFileDiscoveryRequired(String s) {
return true;
}
@Override
public boolean directoryDiscoveryRequired(String s) {
return true;
}
};
return new BundleAnnotationFinder(packageAdmin, bundle,
filter);
}
}
---
--
Ivan
Re: How to package the standalone ejb file ?
On Sep 28, 2010, at 12:16 AM, Ivan wrote:
Hi,
In the past, while deploying a standalone ejb module, we renamed it with
ejb.jar and packaged in in the car package, and we use the same way now in
OSGI, which means ejb.jar is added to the bundle-classpath.
This causes some failures, while scanning the annotations, it uses the codes
below, while the zipFileDiscroveryRequired is called, the parameter s is
ejb.jar, which leads to all the classes are ignored. I am wondering why we
wrapper the initial ejb jar file, why not directly use it ?
We'll have to add stuff to it (currently the serialized gbean state) but I
think that would be fine.
thanks
david jencks
---
final String location = module.getModuleId();
boolean useLocation = location != null
!location.isEmpty()
!module.getJarLocation().endsWith(.war);
if (useLocation) {
ResourceDiscoveryFilter filter = new
ResourceDiscoveryFilter() {
@Override
public boolean rangeDiscoveryRequired(DiscoveryRange
discoveryRange) {
return discoveryRange ==
DiscoveryRange.BUNDLE_CLASSPATH || discoveryRange ==
DiscoveryRange.FRAGMENT_BUNDLES;
}
@Override
public boolean zipFileDiscoveryRequired(String s) {
return s.equals(location);
}
@Override
public boolean directoryDiscoveryRequired(String s) {
return s.equals(location);
}
};
return new BundleAnnotationFinder(packageAdmin, bundle,
filter);
} else {
ResourceDiscoveryFilter filter = new
ResourceDiscoveryFilter() {
@Override
public boolean rangeDiscoveryRequired(DiscoveryRange
discoveryRange) {
return discoveryRange ==
DiscoveryRange.BUNDLE_CLASSPATH || discoveryRange ==
DiscoveryRange.FRAGMENT_BUNDLES;
}
@Override
public boolean zipFileDiscoveryRequired(String s) {
return true;
}
@Override
public boolean directoryDiscoveryRequired(String s) {
return true;
}
};
return new BundleAnnotationFinder(packageAdmin, bundle,
filter);
}
}
---
--
Ivan
[BUILD] trunk: Failed for Revision: 1002039
Geronimo Revision: 1002039 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/build-0300.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 42 minutes 8 seconds [INFO] Finished at: Tue Sep 28 03:47:31 EDT 2010 [INFO] Final Memory: 457M/1005M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/logs-0300-tomcat/ Running TestSuite Tests run: 22, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 1.832 sec FAILURE! -- Running TestSuite Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 9.908 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/logs-0300-jetty/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.232 sec FAILURE! -- Running TestSuite Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 7.859 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/samples-0300.log Build status: OK
Re: How to package the standalone ejb file ?
Hmm, seems that it should be OK if the ejb jar is used directly, it looks
like more nature. One disadvantage is that we need to extract the jar and
repackage it, but I think that it should not an issue. I will try it.
Thanks.
2010/9/28 David Jencks david_jen...@yahoo.com
On Sep 28, 2010, at 12:16 AM, Ivan wrote:
Hi,
In the past, while deploying a standalone ejb module, we renamed it
with ejb.jar and packaged in in the car package, and we use the same way now
in OSGI, which means ejb.jar is added to the bundle-classpath.
This causes some failures, while scanning the annotations, it uses the
codes below, while the zipFileDiscroveryRequired is called, the parameter s
is ejb.jar, which leads to all the classes are ignored. I am wondering why
we wrapper the initial ejb jar file, why not directly use it ?
We'll have to add stuff to it (currently the serialized gbean state) but I
think that would be fine.
thanks
david jencks
---
final String location = module.getModuleId();
boolean useLocation = location != null
!location.isEmpty()
!module.getJarLocation().endsWith(.war);
if (useLocation) {
ResourceDiscoveryFilter filter = new
ResourceDiscoveryFilter() {
@Override
public boolean rangeDiscoveryRequired(DiscoveryRange
discoveryRange) {
return discoveryRange ==
DiscoveryRange.BUNDLE_CLASSPATH || discoveryRange ==
DiscoveryRange.FRAGMENT_BUNDLES;
}
@Override
public boolean zipFileDiscoveryRequired(String s) {
return s.equals(location);
}
@Override
public boolean directoryDiscoveryRequired(String s) {
return s.equals(location);
}
};
return new BundleAnnotationFinder(packageAdmin, bundle,
filter);
} else {
ResourceDiscoveryFilter filter = new
ResourceDiscoveryFilter() {
@Override
public boolean rangeDiscoveryRequired(DiscoveryRange
discoveryRange) {
return discoveryRange ==
DiscoveryRange.BUNDLE_CLASSPATH || discoveryRange ==
DiscoveryRange.FRAGMENT_BUNDLES;
}
@Override
public boolean zipFileDiscoveryRequired(String s) {
return true;
}
@Override
public boolean directoryDiscoveryRequired(String s) {
return true;
}
};
return new BundleAnnotationFinder(packageAdmin, bundle,
filter);
}
}
---
--
Ivan
--
Ivan
[BUILD] trunk: Failed for Revision: 1002153
Geronimo Revision: 1002153 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/build-0900.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 38 minutes 10 seconds [INFO] Finished at: Tue Sep 28 09:43:44 EDT 2010 [INFO] Final Memory: 458M/1001M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/logs-0900-tomcat/ Running TestSuite Tests run: 22, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 1.834 sec FAILURE! -- Running TestSuite Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 7.808 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/logs-0900-jetty/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.257 sec FAILURE! -- Running TestSuite Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 7.807 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/samples-0900.log Build status: OK
[jira] Commented: (GERONIMO-5222) Add support for application validation descriptor support for deployed applications.
[ https://issues.apache.org/jira/browse/GERONIMO-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915789#action_12915789 ] Vamsavardhana Reddy commented on GERONIMO-5222: --- At revision: 100 o Throw deployment exception for errors in parsing validation and constraint mapping xml Add support for application validation descriptor support for deployed applications. - Key: GERONIMO-5222 URL: https://issues.apache.org/jira/browse/GERONIMO-5222 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6, naming Reporter: Rick McGuire Assignee: Vamsavardhana Reddy -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: http://localhost:8080/console/ is showing directory listing instead of login page
On Sep 27, 2010, at 7:15 AM, Ivan wrote: Currently, the default servlet is merged in the deployment time, and I am thinking that we might need to have a better way for merging the default web.xml file. It seems that we could not easily modify those parameters if we want to enable/disable some functions in the default servlet and jasper servlet after the application is deplooyed. I'm not quite sure what you mean, but I can see overriding the default servlets could be a good idea, I'll think about how to do that. We could also do stuff like using config admin to change init params on servlets but this might conflict with servlet lifecycle requirements. This particular problem is caused by the default welcome files being missing, adding index.jsp explicitly to the portal driver web.xml fixes it. Should be an easy fix to make sure the default welcome files are getting added thanks david jencks 2010/9/27 Vamsavardhana Reddy c1vams...@gmail.com Hi, I built the server from latest trunk (Revision: 1001591. Wow! a million commits to the subversion repo!!) and ran the server from geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT assembly. When I access the URL http://localhost:8080/console/ , I am getting a directory listing instead of the login page!! Anyone else seeing this? Anybody knows what is broken? -- Vamsi -- Ivan
[BUILD] trunk: Failed for Revision: 1002327
Geronimo Revision: 1002327 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/build-1500.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 64 minutes 46 seconds [INFO] Finished at: Tue Sep 28 16:10:41 EDT 2010 [INFO] Final Memory: 447M/998M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/logs-1500-tomcat/ Running TestSuite Tests run: 22, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 1.767 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/logs-1500-jetty/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.484 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/samples-1500.log Build status: OK
Re: http://localhost:8080/console/ is showing directory listing instead of login page
2010/9/29 David Jencks david_jen...@yahoo.com On Sep 27, 2010, at 7:15 AM, Ivan wrote: Currently, the default servlet is merged in the deployment time, and I am thinking that we might need to have a better way for merging the default web.xml file. It seems that we could not easily modify those parameters if we want to enable/disable some functions in the default servlet and jasper servlet after the application is deplooyed. I'm not quite sure what you mean, but I can see overriding the default servlets could be a good idea, I'll think about how to do that. We could also do stuff like using config admin to change init params on servlets but this might conflict with servlet lifecycle requirements. Yes, that is what I mean. we do need a way to change the init parameters for those servlets, also, I remember that some default mime-mapping in the default web.xml, it should be added, too. Thanks. This particular problem is caused by the default welcome files being missing, adding index.jsp explicitly to the portal driver web.xml fixes it. Should be an easy fix to make sure the default welcome files are getting added thanks david jencks 2010/9/27 Vamsavardhana Reddy c1vams...@gmail.com Hi, I built the server from latest trunk (Revision: 1001591. Wow! a million commits to the subversion repo!!) and ran the server from geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT assembly. When I access the URL http://localhost:8080/console/ , I am getting a directory listing instead of the login page!! Anyone else seeing this? Anybody knows what is broken? -- Vamsi -- Ivan -- Ivan
[BUILD] trunk: Failed for Revision: 1002439
Geronimo Revision: 1002439 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/build-2100.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 37 minutes 59 seconds [INFO] Finished at: Tue Sep 28 21:43:23 EDT 2010 [INFO] Final Memory: 458M/1003M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/logs-2100-tomcat/ Running TestSuite Tests run: 22, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 1.895 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/logs-2100-jetty/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.292 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20100928/samples-2100.log Build status: OK
[jira] Resolved: (GERONIMODEVTOOLS-673) Don't download TPTP runtime since maven-eclipsepde-plugin 1.1 can handle optional bundle now
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-673. Resolution: Fixed Commit the patch in revision 1002477 for 2.2.1 branch, 1002478 for 2.1.6 branch, 1001147 for trunk. Thanks Janet for the patch! Don't download TPTP runtime since maven-eclipsepde-plugin 1.1 can handle optional bundle now Key: GERONIMODEVTOOLS-673 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-673 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 3.0 Attachments: GERONIMODEVTOOLS-673 .patch From 2.1.6, building GEP will download TPTP runtime from eclipse site. In fact, it's not necessary now, since maven-eclipsepde-plugin 1.1 has been updated and we don't have to download optional bundle such as plugins in TPTP runtime. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
