[jira] [Updated] (GERONIMO-6488) Use GEronimoClassLoader for classloader injection for GBeans
[ https://issues.apache.org/jira/browse/GERONIMO-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-6488: --- Attachment: geronimo-kernel-3.0.1.jar GERONIMO-6488.patch > Use GEronimoClassLoader for classloader injection for GBeans > > > Key: GERONIMO-6488 > URL: https://issues.apache.org/jira/browse/GERONIMO-6488 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core >Affects Versions: 3.0.1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0.2 > > Attachments: GERONIMO-6488.patch, geronimo-kernel-3.0.1.jar > > > To support jar url classloader, originally, we had EquonixClassLoader from > xbean, later, we use Equonix hook to create a GeronimoClassLoader on Geronimo > side. So, for a web application, its context classloader will use > EquonixClassLoader and GeronimoClassLoader is used for loading web > application classes. This would bring issues in some special scenarios. > http://apache-geronimo.328035.n3.nabble.com/Classes-generated-on-runtime-javassist-classloader-issue-td3987081.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6488) Use GEronimoClassLoader for classloader injection for GBeans
[ https://issues.apache.org/jira/browse/GERONIMO-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747448#comment-13747448 ] Ivan commented on GERONIMO-6488: I attached a patched jar file, you may replace that in Geronimo server, the directory is repository\org\apache\geronimo\framework\geronimo-kernel\3.0.1 > Use GEronimoClassLoader for classloader injection for GBeans > > > Key: GERONIMO-6488 > URL: https://issues.apache.org/jira/browse/GERONIMO-6488 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core >Affects Versions: 3.0.1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0.2 > > Attachments: GERONIMO-6488.patch, geronimo-kernel-3.0.1.jar > > > To support jar url classloader, originally, we had EquonixClassLoader from > xbean, later, we use Equonix hook to create a GeronimoClassLoader on Geronimo > side. So, for a web application, its context classloader will use > EquonixClassLoader and GeronimoClassLoader is used for loading web > application classes. This would bring issues in some special scenarios. > http://apache-geronimo.328035.n3.nabble.com/Classes-generated-on-runtime-javassist-classloader-issue-td3987081.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6488) Use GEronimoClassLoader for classloader injection for GBeans
[ https://issues.apache.org/jira/browse/GERONIMO-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-6488: --- Component/s: core Description: To support jar url classloader, originally, we had EquonixClassLoader from xbean, later, we use Equonix hook to create a GeronimoClassLoader on Geronimo side. So, for a web application, its context classloader will use EquonixClassLoader and GeronimoClassLoader is used for loading web application classes. This would bring issues in some special scenarios. http://apache-geronimo.328035.n3.nabble.com/Classes-generated-on-runtime-javassist-classloader-issue-td3987081.html was:To support jar url classloader, originally, we had EquonixClassLoader from xbean, later, we use Equonix hook to create a GeronimoClassLoader on Geronimo side. So, for a web application, its context classloader will use EquonixClassLoader and GeronimoClassLoader is used for loading web application classes. This would bring issues in some special scenarios. Affects Version/s: 3.0.1 Fix Version/s: 3.0.2 Assignee: Ivan > Use GEronimoClassLoader for classloader injection for GBeans > > > Key: GERONIMO-6488 > URL: https://issues.apache.org/jira/browse/GERONIMO-6488 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core >Affects Versions: 3.0.1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0.2 > > > To support jar url classloader, originally, we had EquonixClassLoader from > xbean, later, we use Equonix hook to create a GeronimoClassLoader on Geronimo > side. So, for a web application, its context classloader will use > EquonixClassLoader and GeronimoClassLoader is used for loading web > application classes. This would bring issues in some special scenarios. > http://apache-geronimo.328035.n3.nabble.com/Classes-generated-on-runtime-javassist-classloader-issue-td3987081.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6488) Use GEronimoClassLoader for classloader injection for GBeans
Ivan created GERONIMO-6488: -- Summary: Use GEronimoClassLoader for classloader injection for GBeans Key: GERONIMO-6488 URL: https://issues.apache.org/jira/browse/GERONIMO-6488 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Ivan To support jar url classloader, originally, we had EquonixClassLoader from xbean, later, we use Equonix hook to create a GeronimoClassLoader on Geronimo side. So, for a web application, its context classloader will use EquonixClassLoader and GeronimoClassLoader is used for loading web application classes. This would bring issues in some special scenarios. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6486) @Resource SessionContext is not working
[ https://issues.apache.org/jira/browse/GERONIMO-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6486. Resolution: Not A Problem JIRA system is mostly for defects only, not asking questions. If you found that it does not work, you may need to show us the steps to reproducing the issues. Thanks. > @Resource SessionContext is not working > --- > > Key: GERONIMO-6486 > URL: https://issues.apache.org/jira/browse/GERONIMO-6486 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Environment: Geronimo 3.0.0 >Reporter: Nayela Manzoor > > I think, I am missing some geronimo 3.0 dependencies. Can you please tell me > what geronimo jars I need to make @Resource SessionContext work? > Thanks, > Nayela -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6486) @Resource SessionContext is not working
[ https://issues.apache.org/jira/browse/GERONIMO-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742931#comment-13742931 ] Ivan commented on GERONIMO-6486: I did not see any jar files are required to support SessionContext injections with Resource annotation. > @Resource SessionContext is not working > --- > > Key: GERONIMO-6486 > URL: https://issues.apache.org/jira/browse/GERONIMO-6486 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Environment: Geronimo 3.0.0 >Reporter: Nayela Manzoor > > I think, I am missing some geronimo 3.0 dependencies. Can you please tell me > what geronimo jars I need to make @Resource SessionContext work? > Thanks, > Nayela -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6487) @Resource SessionContext is not working in Geronimo 3.0.0
[ https://issues.apache.org/jira/browse/GERONIMO-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6487. Resolution: Cannot Reproduce JIRA system is mostly for defects only, not asking questions. If you found that it does not work for you, you may need to show us the steps to reproducing the issues. Thanks. > @Resource SessionContext is not working in Geronimo 3.0.0 > - > > Key: GERONIMO-6487 > URL: https://issues.apache.org/jira/browse/GERONIMO-6487 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Environment: Both Windows and Unix >Reporter: Nayela Manzoor > > Can I please get the jar needed in geronimo 3.0 to make @Resource > SessionContext work? > Thanks, > Nayela -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6473) el_2.2 spec pass index of vararg not the real params
[ https://issues.apache.org/jira/browse/GERONIMO-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696866#comment-13696866 ] Ivan commented on GERONIMO-6473: Seems that this has been fixed in GERONIMO-6476. > el_2.2 spec pass index of vararg not the real params > > > Key: GERONIMO-6473 > URL: https://issues.apache.org/jira/browse/GERONIMO-6473 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Reporter: chunlinyao > Fix For: 1.x > > > The line no 442 > Array.set(targetArray, i, expressionFactory.coerceToType(iCurrentIndex + i, > componentClassType)); > Should be: > Array.set(targetArray, i, expressionFactory.coerceToType(params[iCurrentIndex > + i], componentClassType)); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6473) el_2.2 spec pass index of vararg not the real params
[ https://issues.apache.org/jira/browse/GERONIMO-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6473. Resolution: Duplicate Fix Version/s: 1.x > el_2.2 spec pass index of vararg not the real params > > > Key: GERONIMO-6473 > URL: https://issues.apache.org/jira/browse/GERONIMO-6473 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Reporter: chunlinyao > Fix For: 1.x > > > The line no 442 > Array.set(targetArray, i, expressionFactory.coerceToType(iCurrentIndex + i, > componentClassType)); > Should be: > Array.set(targetArray, i, expressionFactory.coerceToType(params[iCurrentIndex > + i], componentClassType)); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6475) Legacy JNDI context usage support
Ivan created GERONIMO-6475: -- Summary: Legacy JNDI context usage support Key: GERONIMO-6475 URL: https://issues.apache.org/jira/browse/GERONIMO-6475 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: naming Affects Versions: 3.0.1 Reporter: Ivan Assignee: Ivan Fix For: 3.0.2 One tradition usage for JNDI API is that, the users could configure a factory class while creating the Context instance, and the jar file contains the context factory is shipped in the user application. Hashtable env = new Hashtable(); env.put(Context.INITIAL_CONTEXT_FACTORY, "org.apache.myContextFactory"); InitialContext ctx = new InitialContext(env); While moving to OSGi, the typical scenario above will not work, as the current JNDI lookup follows the JNDI OSGi spec, except that the configured factory could be loaded from JRE, we will always return the default XBean context. I could saw two solutions for this, a. Enable the leagacy JNDI support from Aries http://svn.apache.org/repos/asf/aries/tags/jndi-0.3/jndi-legacy-support/src/main/java/org/apache/aries/jndi/legacy/support/LegacyInitialContextFinder.java b. Add the similar logic in our DefaultInitialContextFactoryBuilder. I would prefer the option b, considering the logic is so simple, and there is no need to import another jar file, also, we may not suffer the potential ordering issue, since the current DefaultInitialContextFactoryBuilder will always return one context instance. Another reason is that, in my opinion, once the users have specified the context factory and we failed to create the jndi context, there is no need to for the next step trying, also, the log should be print to notify the users for the errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6469) EJB annotations are not working in Geronimo 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6469. Resolution: Cannot Reproduce Assignee: Ivan Nayela, I went ahead to change this as could not reproduce, you may reopen this if have a sample to reproduce that. Thanks. > EJB annotations are not working in Geronimo 3.0 > --- > > Key: GERONIMO-6469 > URL: https://issues.apache.org/jira/browse/GERONIMO-6469 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Nayela Manzoor >Assignee: Ivan > > EJB annotations, for exampe, EJB, Stateless, aroundinvoke are not working in > Geronimo 3.0. I have current application running well in Geronimo 2.0.1. I > deployed it on Geronimo 3.0 and got many issues due to EJB annotation > failures. I had to replace EJB annotations with descriptors in ejb-jar file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6471) IllegalStateException : Cause already initialized is thrown while mail provider failed to connect or sent the messages
[ https://issues.apache.org/jira/browse/GERONIMO-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6471. Resolution: Fixed > IllegalStateException : Cause already initialized is thrown while mail > provider failed to connect or sent the messages > -- > > Key: GERONIMO-6471 > URL: https://issues.apache.org/jira/browse/GERONIMO-6471 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail >Affects Versions: 3.0.1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0.2 > > > If the Geronimo mail failed to connect or send the messages, it would thrown > the exception below. The most issue here is that, MessagingException uses a > legacy chain throwable, and a next exception is maintained in the codes, > while our codes would call initCause to configure the root cause for the > first time, this may bring issue if the original MessagingException is > initialized with null root cause. > java.lang.IllegalStateException: Cause already initialized > at java.lang.Throwable.initCause(Throwable.java:275) > at > javax.mail.MessagingException.setNextException(MessagingException.java:51) > at javax.mail.Transport.send(Transport.java:109) > at javax.mail.Transport.send(Transport.java:48) > at > com.mybankersbank.gateway.email.GatewayEmailBean.sendEmail(GatewayEmailBean.java:297) > at sun.reflect.GeneratedMethodAccessor1221.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:600) > at > org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6471) IllegalStateException : Cause already initialized is thrown while mail provider failed to connect or sent the messages
[ https://issues.apache.org/jira/browse/GERONIMO-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675527#comment-13675527 ] Ivan commented on GERONIMO-6471: Commit the changes to trunk at rev. 1489683 > IllegalStateException : Cause already initialized is thrown while mail > provider failed to connect or sent the messages > -- > > Key: GERONIMO-6471 > URL: https://issues.apache.org/jira/browse/GERONIMO-6471 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail >Affects Versions: 3.0.1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0.2 > > > If the Geronimo mail failed to connect or send the messages, it would thrown > the exception below. The most issue here is that, MessagingException uses a > legacy chain throwable, and a next exception is maintained in the codes, > while our codes would call initCause to configure the root cause for the > first time, this may bring issue if the original MessagingException is > initialized with null root cause. > java.lang.IllegalStateException: Cause already initialized > at java.lang.Throwable.initCause(Throwable.java:275) > at > javax.mail.MessagingException.setNextException(MessagingException.java:51) > at javax.mail.Transport.send(Transport.java:109) > at javax.mail.Transport.send(Transport.java:48) > at > com.mybankersbank.gateway.email.GatewayEmailBean.sendEmail(GatewayEmailBean.java:297) > at sun.reflect.GeneratedMethodAccessor1221.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:600) > at > org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6471) IllegalStateException : Cause already initialized is thrown while mail provider failed to connect or sent the messages
[ https://issues.apache.org/jira/browse/GERONIMO-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-6471: --- Affects Version/s: (was: 3.0.2) Fix Version/s: 3.0.2 > IllegalStateException : Cause already initialized is thrown while mail > provider failed to connect or sent the messages > -- > > Key: GERONIMO-6471 > URL: https://issues.apache.org/jira/browse/GERONIMO-6471 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail >Affects Versions: 3.0.1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0.2 > > > If the Geronimo mail failed to connect or send the messages, it would thrown > the exception below. The most issue here is that, MessagingException uses a > legacy chain throwable, and a next exception is maintained in the codes, > while our codes would call initCause to configure the root cause for the > first time, this may bring issue if the original MessagingException is > initialized with null root cause. > java.lang.IllegalStateException: Cause already initialized > at java.lang.Throwable.initCause(Throwable.java:275) > at > javax.mail.MessagingException.setNextException(MessagingException.java:51) > at javax.mail.Transport.send(Transport.java:109) > at javax.mail.Transport.send(Transport.java:48) > at > com.mybankersbank.gateway.email.GatewayEmailBean.sendEmail(GatewayEmailBean.java:297) > at sun.reflect.GeneratedMethodAccessor1221.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:600) > at > org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6471) IllegalStateException : Cause already initialized is thrown while mail provider failed to connect or sent the messages
Ivan created GERONIMO-6471: -- Summary: IllegalStateException : Cause already initialized is thrown while mail provider failed to connect or sent the messages Key: GERONIMO-6471 URL: https://issues.apache.org/jira/browse/GERONIMO-6471 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: mail Affects Versions: 3.0.1, 3.0.2 Reporter: Ivan Assignee: Ivan If the Geronimo mail failed to connect or send the messages, it would thrown the exception below. The most issue here is that, MessagingException uses a legacy chain throwable, and a next exception is maintained in the codes, while our codes would call initCause to configure the root cause for the first time, this may bring issue if the original MessagingException is initialized with null root cause. java.lang.IllegalStateException: Cause already initialized at java.lang.Throwable.initCause(Throwable.java:275) at javax.mail.MessagingException.setNextException(MessagingException.java:51) at javax.mail.Transport.send(Transport.java:109) at javax.mail.Transport.send(Transport.java:48) at com.mybankersbank.gateway.email.GatewayEmailBean.sendEmail(GatewayEmailBean.java:297) at sun.reflect.GeneratedMethodAccessor1221.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6469) EJB annotations are not working in Geronimo 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669345#comment-13669345 ] Ivan commented on GERONIMO-6469: ok, you may help to provide a sample to reproduce this, so that I could have a look at it in my local environment. > EJB annotations are not working in Geronimo 3.0 > --- > > Key: GERONIMO-6469 > URL: https://issues.apache.org/jira/browse/GERONIMO-6469 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Nayela Manzoor > > EJB annotations, for exampe, EJB, Stateless, aroundinvoke are not working in > Geronimo 3.0. I have current application running well in Geronimo 2.0.1. I > deployed it on Geronimo 3.0 and got many issues due to EJB annotation > failures. I had to replace EJB annotations with descriptors in ejb-jar file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6469) EJB annotations are not working in Geronimo 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668967#comment-13668967 ] Ivan commented on GERONIMO-6469: Hmm, is that seprate jar file kind of library (e.g. in the lib directory)? If not, did you configure it as an ejb in the application.xml file ? As for annotation scanning, the library files will not be considered. > EJB annotations are not working in Geronimo 3.0 > --- > > Key: GERONIMO-6469 > URL: https://issues.apache.org/jira/browse/GERONIMO-6469 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Nayela Manzoor > > EJB annotations, for exampe, EJB, Stateless, aroundinvoke are not working in > Geronimo 3.0. I have current application running well in Geronimo 2.0.1. I > deployed it on Geronimo 3.0 and got many issues due to EJB annotation > failures. I had to replace EJB annotations with descriptors in ejb-jar file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6469) EJB annotations are not working in Geronimo 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668319#comment-13668319 ] Ivan commented on GERONIMO-6469: The code fragment looks fine to me, where did you place the class CRAEETimerBMO ? In a jar file or in the war ? Is there any output in the log file ? > EJB annotations are not working in Geronimo 3.0 > --- > > Key: GERONIMO-6469 > URL: https://issues.apache.org/jira/browse/GERONIMO-6469 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Nayela Manzoor > > EJB annotations, for exampe, EJB, Stateless, aroundinvoke are not working in > Geronimo 3.0. I have current application running well in Geronimo 2.0.1. I > deployed it on Geronimo 3.0 and got many issues due to EJB annotation > failures. I had to replace EJB annotations with descriptors in ejb-jar file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6469) EJB annotations are not working in Geronimo 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668003#comment-13668003 ] Ivan commented on GERONIMO-6469: You may want to provide the sample for reproducing this issue, or is there any output in the log ? With the current description, it is hard to know what happened. > EJB annotations are not working in Geronimo 3.0 > --- > > Key: GERONIMO-6469 > URL: https://issues.apache.org/jira/browse/GERONIMO-6469 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Nayela Manzoor > > EJB annotations, for exampe, EJB, Stateless, aroundinvoke are not working in > Geronimo 3.0. I have current application running well in Geronimo 2.0.1. I > deployed it on Geronimo 3.0 and got many issues due to EJB annotation > failures. I had to replace EJB annotations with descriptors in ejb-jar file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6422) Enable usehttponly feature of tomcat in geronimo 2.1.x
[ https://issues.apache.org/jira/browse/GERONIMO-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6422. Resolution: Fixed Fix Version/s: 2.1.9 Commit the changes to 2.1-branch at rev.1459120 based on the patch from XieZhi, thanks. > Enable usehttponly feature of tomcat in geronimo 2.1.x > -- > > Key: GERONIMO-6422 > URL: https://issues.apache.org/jira/browse/GERONIMO-6422 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.1 >Reporter: xiezhi >Assignee: Ivan > Labels: patch, tomcat, usehttponly > Fix For: 2.1.9 > > Attachments: usehttponlyforgeronimo.patch > > > Geronimo 2.1.x don't have the usehttponly feature of tomcat. > In geronimo 3.0 there is a same patch for this issue. > https://issues.apache.org/jira/browse/GERONIMO-5557 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6422) Enable usehttponly feature of tomcat in geronimo 2.1.x
[ https://issues.apache.org/jira/browse/GERONIMO-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reassigned GERONIMO-6422: -- Assignee: Ivan > Enable usehttponly feature of tomcat in geronimo 2.1.x > -- > > Key: GERONIMO-6422 > URL: https://issues.apache.org/jira/browse/GERONIMO-6422 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.1 >Reporter: xiezhi >Assignee: Ivan > Labels: patch, tomcat, usehttponly > Attachments: usehttponlyforgeronimo.patch > > > Geronimo 2.1.x don't have the usehttponly feature of tomcat. > In geronimo 3.0 there is a same patch for this issue. > https://issues.apache.org/jira/browse/GERONIMO-5557 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6389) Obscuring Passwords Feature couldn't work
[ https://issues.apache.org/jira/browse/GERONIMO-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6389. Resolution: Fixed Fix Version/s: 4.0.0 3.0-beta-2 Commit the changes to 3.0 branch at rev.1459106 and trunk at rev.1459107 Thanks, Xie Zhi ! > Obscuring Passwords Feature couldn't work > - > > Key: GERONIMO-6389 > URL: https://issues.apache.org/jira/browse/GERONIMO-6389 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: crypto >Affects Versions: 3.0-beta-1 >Reporter: xiezhi >Assignee: Ivan > Fix For: 3.0-beta-2, 4.0.0 > > Attachments: ConfiguredEncryption.java.patch > > > Follow geronimo doc https://cwiki.apache.org/GMOxDEV/obscuring-passwords.html > and Geronimo jira 6309 to use the Obscuring Passwords feature. Met the > exception below when start the server. > [] 21% 5s Loading tomcat7 > 2012-09-14 16:17:49,061 ERROR [Http11Pro > tocol] Failed to initialize end point associated with ProtocolHandler > ["http-bio-0.0.0.0-8443"] > java.io.IOException: Keystore was tampered with, or password was incorrect > at com.ibm.crypto.provider.JavaKeyStore.engineLoad(Unknown Source) > at java.security.KeyStore.load(KeyStore.java:414) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getStore(JSSESocketFactory.java:407) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeystore(JSSESocketFactory.java:306) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:565) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:505) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:449) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:169) > at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:383) > at > org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:566) > at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:417) > at > org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119) > at > org.apache.catalina.connector.Connector.initInternal(Connector.java:956) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.catalina.core.StandardService.initInternal(StandardService.java:559) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.geronimo.tomcat.TomcatServerGBean.doStart(TomcatServerGBean.java:159) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:1000) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:569) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:466) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:225) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:710) > at > org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:239) > at > org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:99) > at > org.apache.geronimo.system.osgi.BootActivator$1.execute(BootActivator.java:107) > at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:68) > at > org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65) > at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:32) > Caused by: java.security.UnrecoverableKeyException: Password verification > failed > ... 34 more > 2012-09-14 16:17:49,122 ERROR [StandardService] Failed to initialize > connector [Connector[HTTP/1.1-8443]] > org.apache.catalina.LifecycleException
[jira] [Assigned] (GERONIMO-6389) Obscuring Passwords Feature couldn't work
[ https://issues.apache.org/jira/browse/GERONIMO-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reassigned GERONIMO-6389: -- Assignee: Ivan (was: xiezhi) > Obscuring Passwords Feature couldn't work > - > > Key: GERONIMO-6389 > URL: https://issues.apache.org/jira/browse/GERONIMO-6389 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: crypto >Affects Versions: 3.0-beta-1 >Reporter: xiezhi >Assignee: Ivan > Attachments: ConfiguredEncryption.java.patch > > > Follow geronimo doc https://cwiki.apache.org/GMOxDEV/obscuring-passwords.html > and Geronimo jira 6309 to use the Obscuring Passwords feature. Met the > exception below when start the server. > [] 21% 5s Loading tomcat7 > 2012-09-14 16:17:49,061 ERROR [Http11Pro > tocol] Failed to initialize end point associated with ProtocolHandler > ["http-bio-0.0.0.0-8443"] > java.io.IOException: Keystore was tampered with, or password was incorrect > at com.ibm.crypto.provider.JavaKeyStore.engineLoad(Unknown Source) > at java.security.KeyStore.load(KeyStore.java:414) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getStore(JSSESocketFactory.java:407) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeystore(JSSESocketFactory.java:306) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:565) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:505) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:449) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:169) > at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:383) > at > org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:566) > at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:417) > at > org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119) > at > org.apache.catalina.connector.Connector.initInternal(Connector.java:956) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.catalina.core.StandardService.initInternal(StandardService.java:559) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.geronimo.tomcat.TomcatServerGBean.doStart(TomcatServerGBean.java:159) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:1000) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:569) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:466) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:225) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:710) > at > org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:239) > at > org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:99) > at > org.apache.geronimo.system.osgi.BootActivator$1.execute(BootActivator.java:107) > at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:68) > at > org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65) > at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:32) > Caused by: java.security.UnrecoverableKeyException: Password verification > failed > ... 34 more > 2012-09-14 16:17:49,122 ERROR [StandardService] Failed to initialize > connector [Connector[HTTP/1.1-8443]] > org.apache.catalina.LifecycleException: Failed to initialize component > [Connector[HTTP/1.1-8443]] > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106) > at > org.apache.catalina.core.Stan
[jira] [Closed] (GERONIMO-6420) test
[ https://issues.apache.org/jira/browse/GERONIMO-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan closed GERONIMO-6420. -- Resolution: Invalid > test > > > Key: GERONIMO-6420 > URL: https://issues.apache.org/jira/browse/GERONIMO-6420 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: srikanth > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6419) java.lang.NoClassDefFoundError: org/apache/log4j/CategoryKey
[ https://issues.apache.org/jira/browse/GERONIMO-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508294#comment-13508294 ] Ivan commented on GERONIMO-6419: Could you try to configure the hidden-classes in geronimo-application.xml ? With this, it should prevent loading log4j classes from server runtime. > java.lang.NoClassDefFoundError: org/apache/log4j/CategoryKey > > > Key: GERONIMO-6419 > URL: https://issues.apache.org/jira/browse/GERONIMO-6419 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Logging >Affects Versions: 3.0.0 > Environment: Windows xp professional,eclipse3.6, jdk1.6.0_21, > Geronimo 3.0.0, log4j-1.2.15.jar >Reporter: Aaron Qian > > My EAR contains a Web project and a EJB project, I put a log4j-1.2.15.jar in > the EAR/EarContent/lib directoty, and use the org.apache.log4j.Logger in the > Web project,it works ok,but if i refer org.apache.log4j.Logger in the EJB > project,i could not deploy the EAR project to the Geronimo3.0 > log message is as follows: > java.lang.NoClassDefFoundError: org/apache/log4j/CategoryKey > at org.apache.log4j.Hierarchy.getLogger(Hierarchy.java:262) > at org.apache.log4j.Hierarchy.getLogger(Hierarchy.java:243) > at org.apache.log4j.LogManager.getLogger(LogManager.java:199) > at org.apache.log4j.Logger.getLogger(Logger.java:118) > at > sampleear.MyStatelessSessionBean.(MyStatelessSessionBean.java:19) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:247) > at org.apache.openejb.util.Classes.forName(Classes.java:62) > at > org.apache.openejb.config.rules.ValidationBase.loadClass(ValidationBase.java:139) > at > org.apache.openejb.config.rules.CheckMethods.check_unusedCreateMethods(CheckMethods.java:305) > at > org.apache.openejb.config.rules.CheckMethods.validate(CheckMethods.java:52) > at > org.apache.openejb.config.rules.ValidationBase.validate(ValidationBase.java:45) > at org.apache.openejb.config.AppValidator.validate(AppValidator.java:88) > at > org.apache.openejb.config.ValidateModules.deploy(ValidateModules.java:29) > at > org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:263) > at > org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:692) > at > org.apache.geronimo.openejb.deployment.EjbModuleBuilder.configureApplication(EjbModuleBuilder.java:966) > at > org.apache.geronimo.openejb.deployment.EjbModuleBuilder.getAppInfo(EjbModuleBuilder.java:886) > at > org.apache.geronimo.openejb.deployment.EjbModuleBuilder.doInitContext(EjbModuleBuilder.java:796) > at > org.apache.geronimo.openejb.deployment.EjbModuleBuilder.initContext(EjbModuleBuilder.java:775) > at > org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:686) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:256) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) > at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) > at > org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) > at > com.sun.jmx.interceptor.Def
[jira] [Resolved] (GERONIMO-6401) Download MYSQL drivers attempts to retrieve old jar file
[ https://issues.apache.org/jira/browse/GERONIMO-6401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6401. Resolution: Fixed Fix Version/s: 3.0.1 Assignee: Ivan I did some changes on the properties file at r1405540, that is why it works now ;-) > Download MYSQL drivers attempts to retrieve old jar file > > > Key: GERONIMO-6401 > URL: https://issues.apache.org/jira/browse/GERONIMO-6401 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: databases >Affects Versions: 3.0.0 > Environment: Full profile >Reporter: Michael Bayls >Assignee: Ivan >Priority: Minor > Fix For: 3.0.1 > > > I am attempting to create a new datasource with MYSQL. I don't have the > mysql driver installed so I asked the console to do it. It attempts to > download:- > http://mysql.mirrors.pair.com/Downloads/Connector-J/mysql-connector-java-5.1.12.zip > which no longer exists. > The routine should be modified to down a current version of the driver -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6323) Shared library is not available while reading the ConfigurationData
[ https://issues.apache.org/jira/browse/GERONIMO-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490425#comment-13490425 ] Ivan commented on GERONIMO-6323: One possible workaround is to deploy the library as an artifact in the Geronimo server, and declare the dependency for that artifact in the application deployment plan. > Shared library is not available while reading the ConfigurationData > --- > > Key: GERONIMO-6323 > URL: https://issues.apache.org/jira/browse/GERONIMO-6323 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: dependencies >Affects Versions: 3.0-beta-1 >Reporter: Ivan > Fix For: 3.0-beta-2 > > > Now, SharedLibExtender will install the dependent shared libraries while the > target application bundle is started, while if the application users some > classes from the shared library while reading ConfigurationData from the > config.ser, CNF will be thrown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5868) ClassNotFoundException when using commons-fileupload
[ https://issues.apache.org/jira/browse/GERONIMO-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396357#comment-13396357 ] Ivan commented on GERONIMO-5868: As stated by Martin, adding the configurations below to the deployment plan and places those two libraries will solve this issue. org.apache.commons.io org.apache.commons.fileupload Axis2 does need fileupload to parse the MIME headers. The most problem here is that, if the target application did not use web service, Axis2 classloader should not be in the parent classloader list. There is a jira opened for this, https://issues.apache.org/jira/browse/GERONIMO-6203 > ClassNotFoundException when using commons-fileupload > > > Key: GERONIMO-5868 > URL: https://issues.apache.org/jira/browse/GERONIMO-5868 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: general >Affects Versions: 2.2.1 >Reporter: Martin Hejl > Attachments: geronimo_postfile.zip > > > Using a vanilla geronimo 2.2.1 server from > http://www.apache.org/dyn/closer.cgi/geronimo/2.2.1/geronimo-tomcat6-javaee5-2.2.1-bin.zip > > and GEP 2.2.1 I created a simple dynamic web project (one jsp and one > servlet, with commons-fileupload and commons-io in WEB-INF/lib/ - see > attachment) > When the form in hello.jsp (http://localhost:8080/HelloWorld/) is postet to > the servlet (http://localhost:8080/HelloWorld/postFile), I get the following > exception: > java.lang.ClassNotFoundException: > org.apache.commons.io.output.DeferredFileOutputStream in classloader > org.apache.geronimo.configs/axis2/2.2.1/car > at > org.apache.geronimo.kernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.java:407) > at > org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:257) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > at > org.apache.commons.fileupload.disk.DiskFileItemFactory.createItem(DiskFileItemFactory.java:179) > at > org.apache.commons.fileupload.FileUploadBase.createItem(FileUploadBase.java:500) > at > org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:367) > at > org.apache.commons.fileupload.servlet.ServletFileUpload.parseRequest(ServletFileUpload.java:116) > at de.guhsoft.test.PostServlet.doPost(PostServlet.java:38) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:713) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:420) > at > org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) > at > org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:396) > at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214) > at > org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > As suggestet by Kevan at > http://article.gmane.org/gmane.comp.java.geronimo.user/15126 adding > > org.apache.commons.io > org.apache.commons.fileupload > > to the deployment plan fixes the issue. > Kevan suggested at > http://article.gmane.org/gmane.comp.java.geronimo.user/15127 that I should > open a Jira anyway, fileupload probably > shouldn't be in the axis2 classloader -- This message
[jira] [Commented] (GERONIMO-6364) jaxws-catalog-tests test failed for UnknownHostException
[ https://issues.apache.org/jira/browse/GERONIMO-6364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294274#comment-13294274 ] Ivan commented on GERONIMO-6364: Commit changes to trunk at rev.1349684 > jaxws-catalog-tests test failed for UnknownHostException > > > Key: GERONIMO-6364 > URL: https://issues.apache.org/jira/browse/GERONIMO-6364 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0-beta-1 >Reporter: Forrest Xia >Assignee: Ivan >Priority: Minor > Fix For: 3.0 > > > If running jaxws-catalog-tests, these exceptions happen: > Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: > Configuration > org.apache.geronimo.testsuite/catalog-ear/3.0-beta-2-SNAPSHOT/ear failed to > start due to the following reasons: > The service > EJBModule=catalog-ejb-3.0-beta-2-SNAPSHOT.jar,J2EEApplication=org.apache.geronimo.testsuite/catalog-ear/3.0-beta-2-SNAPSHOT/ear,StatelessSessionBean=GreeterBean,j2eeType=WSLink,name=GreeterBean > did not start because WSDLException: faultCode=WSDL4JWrapper : : > javax.xml.ws.WebServiceException: javax.wsdl.WSDLException: WSDLException (at > /wsdl:definitions/wsdl:import): faultCode=OTHER_ERROR: Unable to resolve > imported document at 'http://foo1/greeter_binding.wsdl', relative to > 'bundleresource://515.fwk1130907398/META-INF/wsdl/greeter_service.wsdl': > java.net.UnknownHostException: foo1 > javax.wsdl.WSDLException: WSDLException: faultCode=WSDL4JWrapper : : > javax.xml.ws.WebServiceException: javax.wsdl.WSDLException: WSDLException (at > /wsdl:definitions/wsdl:import): faultCode=OTHER_ERROR: Unable to resolve > imported document at 'http://foo1/greeter_binding.wsdl', relative to > 'bundleresource://515.fwk1130907398/META-INF/wsdl/greeter_service.wsdl': > java.net.UnknownHostException: foo1 > at > org.apache.axis2.jaxws.util.WSDL4JWrapper.commonPartsURLConstructor(WSDL4JWrapper.java:234) > at > org.apache.axis2.jaxws.util.WSDL4JWrapper.(WSDL4JWrapper.java:156) > at > org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java:160) > at > org.apache.geronimo.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java:172) > at > org.apache.geronimo.axis2.ejb.EJBWebServiceContainer.init(EJBWebServiceContainer.java:62) > at > org.apache.geronimo.axis2.ejb.EJBWebServiceGBean.(EJBWebServiceGBean.java:82) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:958) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:569) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:466) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:225) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:710) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:689) > at sun.reflect.GeneratedMethodAccessor135.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperat
[jira] [Commented] (GERONIMO-6314) Add monitor role to protect the JMX access
[ https://issues.apache.org/jira/browse/GERONIMO-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294188#comment-13294188 ] Ivan commented on GERONIMO-6314: Commit more changes to 3.0 beta branch at rev.1349652 > Add monitor role to protect the JMX access > > > Key: GERONIMO-6314 > URL: https://issues.apache.org/jira/browse/GERONIMO-6314 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: connector, JVM-compatibility >Affects Versions: 3.0-beta-1 > Environment: linux,windows >Reporter: Tina Li >Assignee: Tina Li > Fix For: 3.0 > > Attachments: GERONIMO-6314_formatUpdated.patch > > > Currently, only the admin user can connect to JMX and the admin user has > read/write access to MBeans. Now find a method to let "monitor" role also can > access JMX but only has read-only access. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6363) jaxrpc-jaxws-tests failed for IllegalAnnotationsException when doing wsgen
[ https://issues.apache.org/jira/browse/GERONIMO-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6363. Resolution: Fixed Fix Version/s: 3.0-beta-2 > jaxrpc-jaxws-tests failed for IllegalAnnotationsException when doing wsgen > -- > > Key: GERONIMO-6363 > URL: https://issues.apache.org/jira/browse/GERONIMO-6363 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0-beta-1 >Reporter: Forrest Xia >Assignee: Ivan >Priority: Minor > Fix For: 3.0, 3.0-beta-2 > > > When running jaxrpc-jaxws-tests testsuite, these exception happened when > deployment: > org.apache.geronimo.common.DeploymentException: Unable to generate the wsdl > file using wsgen. > at > org.apache.geronimo.jaxws.sun.tools.WsdlGenerator.generateWsdl(WsdlGenerator.java:182) > at > org.apache.geronimo.jaxws.sun.tools.SunWsdlGenerator.generateWsdl(SunWsdlGenerator.java:34) > at > org.apache.geronimo.axis2.builder.Axis2Builder.initialize(Axis2Builder.java:153) > at > org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.configurePOJO(JAXWSServiceBuilder.java:337) > at > org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:630) > at > org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:174) > at > org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:764) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:256) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) > at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) > at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344) > at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) > at > org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) > at > com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) > at > javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427) > at > javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) > at > javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367) > at > javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) > at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303) > at sun.rmi.transport.Transport$1.run(Transport.java:159) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:155) > at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) > at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) > at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadP
[jira] [Commented] (GERONIMO-6363) jaxrpc-jaxws-tests failed for IllegalAnnotationsException when doing wsgen
[ https://issues.apache.org/jira/browse/GERONIMO-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294185#comment-13294185 ] Ivan commented on GERONIMO-6363: Commit changes to 3.0-beta at rev.1349649, and trunk at rev.1349650 > jaxrpc-jaxws-tests failed for IllegalAnnotationsException when doing wsgen > -- > > Key: GERONIMO-6363 > URL: https://issues.apache.org/jira/browse/GERONIMO-6363 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0-beta-1 >Reporter: Forrest Xia >Assignee: Ivan >Priority: Minor > Fix For: 3.0 > > > When running jaxrpc-jaxws-tests testsuite, these exception happened when > deployment: > org.apache.geronimo.common.DeploymentException: Unable to generate the wsdl > file using wsgen. > at > org.apache.geronimo.jaxws.sun.tools.WsdlGenerator.generateWsdl(WsdlGenerator.java:182) > at > org.apache.geronimo.jaxws.sun.tools.SunWsdlGenerator.generateWsdl(SunWsdlGenerator.java:34) > at > org.apache.geronimo.axis2.builder.Axis2Builder.initialize(Axis2Builder.java:153) > at > org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.configurePOJO(JAXWSServiceBuilder.java:337) > at > org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:630) > at > org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:174) > at > org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:764) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:256) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) > at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) > at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344) > at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) > at > org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) > at > com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) > at > javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427) > at > javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) > at > javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367) > at > javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) > at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303) > at sun.rmi.transport.Transport$1.run(Transport.java:159) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:155) > at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) > at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) > at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) >
[jira] [Commented] (GERONIMO-6364) jaxws-catalog-tests test failed for UnknownHostException
[ https://issues.apache.org/jira/browse/GERONIMO-6364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293750#comment-13293750 ] Ivan commented on GERONIMO-6364: Commit more changes to 3.0-beta at rev.1349427. Now we should be able to read WSDL/catalog file correctly. > jaxws-catalog-tests test failed for UnknownHostException > > > Key: GERONIMO-6364 > URL: https://issues.apache.org/jira/browse/GERONIMO-6364 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0-beta-1 >Reporter: Forrest Xia >Assignee: Ivan >Priority: Minor > > If running jaxws-catalog-tests, these exceptions happen: > Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: > Configuration > org.apache.geronimo.testsuite/catalog-ear/3.0-beta-2-SNAPSHOT/ear failed to > start due to the following reasons: > The service > EJBModule=catalog-ejb-3.0-beta-2-SNAPSHOT.jar,J2EEApplication=org.apache.geronimo.testsuite/catalog-ear/3.0-beta-2-SNAPSHOT/ear,StatelessSessionBean=GreeterBean,j2eeType=WSLink,name=GreeterBean > did not start because WSDLException: faultCode=WSDL4JWrapper : : > javax.xml.ws.WebServiceException: javax.wsdl.WSDLException: WSDLException (at > /wsdl:definitions/wsdl:import): faultCode=OTHER_ERROR: Unable to resolve > imported document at 'http://foo1/greeter_binding.wsdl', relative to > 'bundleresource://515.fwk1130907398/META-INF/wsdl/greeter_service.wsdl': > java.net.UnknownHostException: foo1 > javax.wsdl.WSDLException: WSDLException: faultCode=WSDL4JWrapper : : > javax.xml.ws.WebServiceException: javax.wsdl.WSDLException: WSDLException (at > /wsdl:definitions/wsdl:import): faultCode=OTHER_ERROR: Unable to resolve > imported document at 'http://foo1/greeter_binding.wsdl', relative to > 'bundleresource://515.fwk1130907398/META-INF/wsdl/greeter_service.wsdl': > java.net.UnknownHostException: foo1 > at > org.apache.axis2.jaxws.util.WSDL4JWrapper.commonPartsURLConstructor(WSDL4JWrapper.java:234) > at > org.apache.axis2.jaxws.util.WSDL4JWrapper.(WSDL4JWrapper.java:156) > at > org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java:160) > at > org.apache.geronimo.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java:172) > at > org.apache.geronimo.axis2.ejb.EJBWebServiceContainer.init(EJBWebServiceContainer.java:62) > at > org.apache.geronimo.axis2.ejb.EJBWebServiceGBean.(EJBWebServiceGBean.java:82) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:958) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:569) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:466) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:225) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:710) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:689) > at sun.reflect.GeneratedMethodAccessor135.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.a
[jira] [Commented] (GERONIMO-6364) jaxws-catalog-tests test failed for UnknownHostException
[ https://issues.apache.org/jira/browse/GERONIMO-6364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293294#comment-13293294 ] Ivan commented on GERONIMO-6364: Commit changes to trunk at rev.1349097 > jaxws-catalog-tests test failed for UnknownHostException > > > Key: GERONIMO-6364 > URL: https://issues.apache.org/jira/browse/GERONIMO-6364 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0-beta-1 >Reporter: Forrest Xia >Assignee: Ivan >Priority: Minor > > If running jaxws-catalog-tests, these exceptions happen: > Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: > Configuration > org.apache.geronimo.testsuite/catalog-ear/3.0-beta-2-SNAPSHOT/ear failed to > start due to the following reasons: > The service > EJBModule=catalog-ejb-3.0-beta-2-SNAPSHOT.jar,J2EEApplication=org.apache.geronimo.testsuite/catalog-ear/3.0-beta-2-SNAPSHOT/ear,StatelessSessionBean=GreeterBean,j2eeType=WSLink,name=GreeterBean > did not start because WSDLException: faultCode=WSDL4JWrapper : : > javax.xml.ws.WebServiceException: javax.wsdl.WSDLException: WSDLException (at > /wsdl:definitions/wsdl:import): faultCode=OTHER_ERROR: Unable to resolve > imported document at 'http://foo1/greeter_binding.wsdl', relative to > 'bundleresource://515.fwk1130907398/META-INF/wsdl/greeter_service.wsdl': > java.net.UnknownHostException: foo1 > javax.wsdl.WSDLException: WSDLException: faultCode=WSDL4JWrapper : : > javax.xml.ws.WebServiceException: javax.wsdl.WSDLException: WSDLException (at > /wsdl:definitions/wsdl:import): faultCode=OTHER_ERROR: Unable to resolve > imported document at 'http://foo1/greeter_binding.wsdl', relative to > 'bundleresource://515.fwk1130907398/META-INF/wsdl/greeter_service.wsdl': > java.net.UnknownHostException: foo1 > at > org.apache.axis2.jaxws.util.WSDL4JWrapper.commonPartsURLConstructor(WSDL4JWrapper.java:234) > at > org.apache.axis2.jaxws.util.WSDL4JWrapper.(WSDL4JWrapper.java:156) > at > org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java:160) > at > org.apache.geronimo.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java:172) > at > org.apache.geronimo.axis2.ejb.EJBWebServiceContainer.init(EJBWebServiceContainer.java:62) > at > org.apache.geronimo.axis2.ejb.EJBWebServiceGBean.(EJBWebServiceGBean.java:82) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:958) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:569) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:466) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:225) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:710) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:689) > at sun.reflect.GeneratedMethodAccessor135.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.jav
[jira] [Commented] (GERONIMO-6364) jaxws-catalog-tests test failed for UnknownHostException
[ https://issues.apache.org/jira/browse/GERONIMO-6364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293291#comment-13293291 ] Ivan commented on GERONIMO-6364: Commit changes to 3.0-beta at rev.1349095 > jaxws-catalog-tests test failed for UnknownHostException > > > Key: GERONIMO-6364 > URL: https://issues.apache.org/jira/browse/GERONIMO-6364 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0-beta-1 >Reporter: Forrest Xia >Assignee: Ivan >Priority: Minor > > If running jaxws-catalog-tests, these exceptions happen: > Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: > Configuration > org.apache.geronimo.testsuite/catalog-ear/3.0-beta-2-SNAPSHOT/ear failed to > start due to the following reasons: > The service > EJBModule=catalog-ejb-3.0-beta-2-SNAPSHOT.jar,J2EEApplication=org.apache.geronimo.testsuite/catalog-ear/3.0-beta-2-SNAPSHOT/ear,StatelessSessionBean=GreeterBean,j2eeType=WSLink,name=GreeterBean > did not start because WSDLException: faultCode=WSDL4JWrapper : : > javax.xml.ws.WebServiceException: javax.wsdl.WSDLException: WSDLException (at > /wsdl:definitions/wsdl:import): faultCode=OTHER_ERROR: Unable to resolve > imported document at 'http://foo1/greeter_binding.wsdl', relative to > 'bundleresource://515.fwk1130907398/META-INF/wsdl/greeter_service.wsdl': > java.net.UnknownHostException: foo1 > javax.wsdl.WSDLException: WSDLException: faultCode=WSDL4JWrapper : : > javax.xml.ws.WebServiceException: javax.wsdl.WSDLException: WSDLException (at > /wsdl:definitions/wsdl:import): faultCode=OTHER_ERROR: Unable to resolve > imported document at 'http://foo1/greeter_binding.wsdl', relative to > 'bundleresource://515.fwk1130907398/META-INF/wsdl/greeter_service.wsdl': > java.net.UnknownHostException: foo1 > at > org.apache.axis2.jaxws.util.WSDL4JWrapper.commonPartsURLConstructor(WSDL4JWrapper.java:234) > at > org.apache.axis2.jaxws.util.WSDL4JWrapper.(WSDL4JWrapper.java:156) > at > org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java:160) > at > org.apache.geronimo.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java:172) > at > org.apache.geronimo.axis2.ejb.EJBWebServiceContainer.init(EJBWebServiceContainer.java:62) > at > org.apache.geronimo.axis2.ejb.EJBWebServiceGBean.(EJBWebServiceGBean.java:82) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:958) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:569) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:466) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:225) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:710) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:689) > at sun.reflect.GeneratedMethodAccessor135.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.
[jira] [Assigned] (GERONIMO-6364) jaxws-catalog-tests test failed for UnknownHostException
[ https://issues.apache.org/jira/browse/GERONIMO-6364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reassigned GERONIMO-6364: -- Assignee: Ivan > jaxws-catalog-tests test failed for UnknownHostException > > > Key: GERONIMO-6364 > URL: https://issues.apache.org/jira/browse/GERONIMO-6364 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0-beta-1 >Reporter: Forrest Xia >Assignee: Ivan >Priority: Minor > > If running jaxws-catalog-tests, these exceptions happen: > Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: > Configuration > org.apache.geronimo.testsuite/catalog-ear/3.0-beta-2-SNAPSHOT/ear failed to > start due to the following reasons: > The service > EJBModule=catalog-ejb-3.0-beta-2-SNAPSHOT.jar,J2EEApplication=org.apache.geronimo.testsuite/catalog-ear/3.0-beta-2-SNAPSHOT/ear,StatelessSessionBean=GreeterBean,j2eeType=WSLink,name=GreeterBean > did not start because WSDLException: faultCode=WSDL4JWrapper : : > javax.xml.ws.WebServiceException: javax.wsdl.WSDLException: WSDLException (at > /wsdl:definitions/wsdl:import): faultCode=OTHER_ERROR: Unable to resolve > imported document at 'http://foo1/greeter_binding.wsdl', relative to > 'bundleresource://515.fwk1130907398/META-INF/wsdl/greeter_service.wsdl': > java.net.UnknownHostException: foo1 > javax.wsdl.WSDLException: WSDLException: faultCode=WSDL4JWrapper : : > javax.xml.ws.WebServiceException: javax.wsdl.WSDLException: WSDLException (at > /wsdl:definitions/wsdl:import): faultCode=OTHER_ERROR: Unable to resolve > imported document at 'http://foo1/greeter_binding.wsdl', relative to > 'bundleresource://515.fwk1130907398/META-INF/wsdl/greeter_service.wsdl': > java.net.UnknownHostException: foo1 > at > org.apache.axis2.jaxws.util.WSDL4JWrapper.commonPartsURLConstructor(WSDL4JWrapper.java:234) > at > org.apache.axis2.jaxws.util.WSDL4JWrapper.(WSDL4JWrapper.java:156) > at > org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java:160) > at > org.apache.geronimo.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java:172) > at > org.apache.geronimo.axis2.ejb.EJBWebServiceContainer.init(EJBWebServiceContainer.java:62) > at > org.apache.geronimo.axis2.ejb.EJBWebServiceGBean.(EJBWebServiceGBean.java:82) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:958) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:569) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:466) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:225) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:710) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:689) > at sun.reflect.GeneratedMethodAccessor135.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanIn
[jira] [Commented] (GERONIMO-4784) Problem with ActiveMQ, two connections/sessions, and UserTransaction
[ https://issues.apache.org/jira/browse/GERONIMO-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290745#comment-13290745 ] Ivan commented on GERONIMO-4784: If the transaction is rollback, those consumed messages should be recovered, that is why it is expected to receive the sample message twice. I am not sure whether it is an issue of test case, if not, that means that the transaction did not work as expected. > Problem with ActiveMQ, two connections/sessions, and UserTransaction > > > Key: GERONIMO-4784 > URL: https://issues.apache.org/jira/browse/GERONIMO-4784 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 2.2, 3.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 2.2 > > Attachments: GERONIMO-4784-pom.patch, GERONIMO-4784-testng.patch, > GERONIMO-4784-workaround.patch > > > This is probably a problem in activemq with dealing with multiple connection > handles to the same managed connection and XA transactions controlled by > UserTransaction. It may be causing intermittent tck failures. In any case I > think the test ought to work. > Not sure how to reproduce this in AMQ standalone yet, so I'm adding a > testsuite test to demonstrate the problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6352) session configuration info is not serialized correctly
[ https://issues.apache.org/jira/browse/GERONIMO-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281021#comment-13281021 ] Ivan commented on GERONIMO-6352: Commit changes to trunk at rev.1341512 > session configuration info is not serialized correctly > -- > > Key: GERONIMO-6352 > URL: https://issues.apache.org/jira/browse/GERONIMO-6352 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: web >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0, 3.0-beta-2 > > > While creating the WebAppInfo, those information from session config in the > web.xml is not serialized correctly, so those configurations will never take > effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6352) session configuration info is not serialized correctly
[ https://issues.apache.org/jira/browse/GERONIMO-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280850#comment-13280850 ] Ivan commented on GERONIMO-6352: commit changes to 3.0-beta at rev.1341377. > session configuration info is not serialized correctly > -- > > Key: GERONIMO-6352 > URL: https://issues.apache.org/jira/browse/GERONIMO-6352 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: web >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0, 3.0-beta-2 > > > While creating the WebAppInfo, those information from session config in the > web.xml is not serialized correctly, so those configurations will never take > effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (GERONIMO-6352) session configuration info is not serialized correctly
[ https://issues.apache.org/jira/browse/GERONIMO-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reopened GERONIMO-6352: Seems that we did not handle those session configuration properly, as the codes always configures those values even no explicitly configured in web.xml file. > session configuration info is not serialized correctly > -- > > Key: GERONIMO-6352 > URL: https://issues.apache.org/jira/browse/GERONIMO-6352 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: web >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0, 3.0-beta-2 > > > While creating the WebAppInfo, those information from session config in the > web.xml is not serialized correctly, so those configurations will never take > effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6349) Follow Axis2 version convention in Geronimo Axis2 bundle
[ https://issues.apache.org/jira/browse/GERONIMO-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6349. Resolution: Fixed Fix Version/s: 3.0-beta-2 Assignee: Ivan Commit changes to axis2 bundle at rev.1339960 > Follow Axis2 version convention in Geronimo Axis2 bundle > > > Key: GERONIMO-6349 > URL: https://issues.apache.org/jira/browse/GERONIMO-6349 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan >Priority: Minor > Fix For: 3.0-beta-2 > > > 2012-05-14 21:17:24,651 ERROR [ModuleDeployer] The axis2-1.6.1_1.jar module, > which is not valid, caused For input string: "1_1" > org.apache.axis2.deployment.DeploymentException: For input string: "1_1" > at > org.apache.axis2.deployment.repository.util.ArchiveReader.readModuleArchive(ArchiveReader.java:527) > at > org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:77) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) > at > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:813) > at > org.apache.axis2.deployment.RepositoryListener.loadClassPathModules(RepositoryListener.java:222) > at > org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:71) > at > org.apache.axis2.deployment.RepositoryListener.(RepositoryListener.java:64) > at > org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:175) > at > org.apache.geronimo.axis2.GeronimoConfigurator.getAxisConfiguration(GeronimoConfigurator.java:47) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) > at > org.apache.geronimo.axis2.client.Axis2ClientConfigurationFactory.createConfigurationContext(Axis2ClientConfigurationFactory.java:104) > at > org.apache.geronimo.axis2.client.Axis2ClientConfigurationFactory.getConfigurationContext(Axis2ClientConfigurationFactory.java:64) > at > org.apache.geronimo.axis2.client.Axis2ClientConfigurationFactory.getClientConfigurationContext(Axis2ClientConfigurationFactory.java:57) > at > org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(DescriptionFactoryImpl.java:92) > at > org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(DescriptionFactoryImpl.java:79) > at > org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescription(DescriptionFactory.java:78) > at org.apache.axis2.jaxws.spi.ServiceDelegate.(ServiceDelegate.java:218) > at > org.apache.axis2.jaxws.spi.Provider.createServiceDelegate(Provider.java:83) > at > org.apache.axis2.jaxws.spi.Provider.createServiceDelegate(Provider.java:79) > at javax.xml.ws.Service.(Service.java:35) > at > *** > at > net.sf.cglib.reflect.FastConstructor.newInstance(FastConstructor.java:40) > at > org.apache.geronimo.jaxws.client.JAXWSServiceReference.createServiceProxy(JAXWSServiceReference.java:218) > at > org.apache.geronimo.jaxws.client.JAXWSServiceReference.getContent(JAXWSServiceReference.java:153) > at > org.apache.geronimo.axis2.client.Axis2ServiceReference.getContent(Axis2ServiceReference.java:74) > at > org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:116) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:605) > at > org.apache.geronimo.client.AppClientContainer.main(AppClientContainer.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) > at > org.apache.geronimo.system.main.CommandLine.doInvokeMainGBean(CommandLine.java:112) > at > org.apache.ger
[jira] [Resolved] (GERONIMO-6352) session configuration info is not serialized correctly
[ https://issues.apache.org/jira/browse/GERONIMO-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6352. Resolution: Fixed Fix Version/s: 3.0 > session configuration info is not serialized correctly > -- > > Key: GERONIMO-6352 > URL: https://issues.apache.org/jira/browse/GERONIMO-6352 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: web >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0, 3.0-beta-2 > > > While creating the WebAppInfo, those information from session config in the > web.xml is not serialized correctly, so those configurations will never take > effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6352) session configuration info is not serialized correctly
[ https://issues.apache.org/jira/browse/GERONIMO-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277656#comment-13277656 ] Ivan commented on GERONIMO-6352: Commit changes to trunk at rev.1339513 > session configuration info is not serialized correctly > -- > > Key: GERONIMO-6352 > URL: https://issues.apache.org/jira/browse/GERONIMO-6352 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: web >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0, 3.0-beta-2 > > > While creating the WebAppInfo, those information from session config in the > web.xml is not serialized correctly, so those configurations will never take > effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6352) session configuration info is not serialized correctly
[ https://issues.apache.org/jira/browse/GERONIMO-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277607#comment-13277607 ] Ivan commented on GERONIMO-6352: Commit changes to 3.0-beta at rev.1339497 > session configuration info is not serialized correctly > -- > > Key: GERONIMO-6352 > URL: https://issues.apache.org/jira/browse/GERONIMO-6352 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: web >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0-beta-2 > > > While creating the WebAppInfo, those information from session config in the > web.xml is not serialized correctly, so those configurations will never take > effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6352) session configuration info is not serialized correctly
Ivan created GERONIMO-6352: -- Summary: session configuration info is not serialized correctly Key: GERONIMO-6352 URL: https://issues.apache.org/jira/browse/GERONIMO-6352 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: web Affects Versions: 3.0-beta-1 Reporter: Ivan Assignee: Ivan Fix For: 3.0-beta-2 While creating the WebAppInfo, those information from session config in the web.xml is not serialized correctly, so those configurations will never take effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6349) Follow Axis2 version convention in Geronimo Axis2 bundle
Ivan created GERONIMO-6349: -- Summary: Follow Axis2 version convention in Geronimo Axis2 bundle Key: GERONIMO-6349 URL: https://issues.apache.org/jira/browse/GERONIMO-6349 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: webservices Affects Versions: 3.0-beta-1 Reporter: Ivan Priority: Minor 2012-05-14 21:17:24,651 ERROR [ModuleDeployer] The axis2-1.6.1_1.jar module, which is not valid, caused For input string: "1_1" org.apache.axis2.deployment.DeploymentException: For input string: "1_1" at org.apache.axis2.deployment.repository.util.ArchiveReader.readModuleArchive(ArchiveReader.java:527) at org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:77) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:813) at org.apache.axis2.deployment.RepositoryListener.loadClassPathModules(RepositoryListener.java:222) at org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:71) at org.apache.axis2.deployment.RepositoryListener.(RepositoryListener.java:64) at org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:175) at org.apache.geronimo.axis2.GeronimoConfigurator.getAxisConfiguration(GeronimoConfigurator.java:47) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) at org.apache.geronimo.axis2.client.Axis2ClientConfigurationFactory.createConfigurationContext(Axis2ClientConfigurationFactory.java:104) at org.apache.geronimo.axis2.client.Axis2ClientConfigurationFactory.getConfigurationContext(Axis2ClientConfigurationFactory.java:64) at org.apache.geronimo.axis2.client.Axis2ClientConfigurationFactory.getClientConfigurationContext(Axis2ClientConfigurationFactory.java:57) at org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(DescriptionFactoryImpl.java:92) at org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(DescriptionFactoryImpl.java:79) at org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescription(DescriptionFactory.java:78) at org.apache.axis2.jaxws.spi.ServiceDelegate.(ServiceDelegate.java:218) at org.apache.axis2.jaxws.spi.Provider.createServiceDelegate(Provider.java:83) at org.apache.axis2.jaxws.spi.Provider.createServiceDelegate(Provider.java:79) at javax.xml.ws.Service.(Service.java:35) at *** at net.sf.cglib.reflect.FastConstructor.newInstance(FastConstructor.java:40) at org.apache.geronimo.jaxws.client.JAXWSServiceReference.createServiceProxy(JAXWSServiceReference.java:218) at org.apache.geronimo.jaxws.client.JAXWSServiceReference.getContent(JAXWSServiceReference.java:153) at org.apache.geronimo.axis2.client.Axis2ServiceReference.getContent(Axis2ServiceReference.java:74) at org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:116) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:605) at org.apache.geronimo.client.AppClientContainer.main(AppClientContainer.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.system.main.CommandLine.doInvokeMainGBean(CommandLine.java:112) at org.apache.geronimo.system.main.CommandLine.invokeMainGBean(CommandLine.java:92) at org.apache.geronimo.system.main.ClientCommandLine.startClient(ClientCommandLine.java:84) at org.apache.geronimo.system.main.ClientCommandLine.execute(ClientCommandLine.java:66) at org.apache.geronimo.system.main.EmbeddedClientCommandLine.execute(EmbeddedClientCommandLine.java:46) at org.apache.geronimo.system.osgi.BootActivator$1.execute(BootActivator.jav
[jira] [Commented] (GERONIMO-5778) Exclude jars from annotation scanning and/or bundle classpath
[ https://issues.apache.org/jira/browse/GERONIMO-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266485#comment-13266485 ] Ivan commented on GERONIMO-5778: This jira is based on the GERONIMO-5813, not sure I could include this in the 3.0-beta-2, may move to next version. > Exclude jars from annotation scanning and/or bundle classpath > - > > Key: GERONIMO-5778 > URL: https://issues.apache.org/jira/browse/GERONIMO-5778 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Ivan > Fix For: 3.0-beta-2 > > > In most cases large web applications with a number of embedded dependencies > contain jars that do not need to be scanned for annotations and/or included > on bundle class path. So it would be nice to have a way to specify in a > deployment descriptor 1) a list of jars that shouldn't be scanned for > annotations, and 2) a list of jars that do not need to be included in the > bundle class path. > #2 is probably a bit less useful as the web application archive can always be > recreated but #1 might be very useful. It would help to speed up the > (re)deployment process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-6254) Shared library does not work in the deployment process
[ https://issues.apache.org/jira/browse/GERONIMO-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan closed GERONIMO-6254. -- > Shared library does not work in the deployment process > -- > > Key: GERONIMO-6254 > URL: https://issues.apache.org/jira/browse/GERONIMO-6254 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0, 3.0-beta-2 > > > In the deployment process, as the temp configuration is kept in the > DeploymentConfigurationManager, SharedLibExtender will not find its parents. > Will use DependencyManager to look up the dependent bundles instead. There > maybe issue in the trunk codes, too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6254) Shared library does not work in the deployment process
[ https://issues.apache.org/jira/browse/GERONIMO-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6254. Resolution: Fixed > Shared library does not work in the deployment process > -- > > Key: GERONIMO-6254 > URL: https://issues.apache.org/jira/browse/GERONIMO-6254 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0, 3.0-beta-2 > > > In the deployment process, as the temp configuration is kept in the > DeploymentConfigurationManager, SharedLibExtender will not find its parents. > Will use DependencyManager to look up the dependent bundles instead. There > maybe issue in the trunk codes, too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6169) Recursive lookup while the default comp entry is configured
[ https://issues.apache.org/jira/browse/GERONIMO-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112396#comment-13112396 ] Ivan commented on GERONIMO-6169: Commit first step changes to trunk at r1173982. It looks to me that the name should be first checked, if it is the default comp name, we should not create a JndiReference, and leave other modules processed it. > Recursive lookup while the default comp entry is configured > --- > > Key: GERONIMO-6169 > URL: https://issues.apache.org/jira/browse/GERONIMO-6169 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0-M1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > If there is an resource entry like java:comp/EJBContext configured in the DD > or added by other modules, and the responsible module has not processed it, > AdminObjectRefBuilder will add a JndiReference in the binding map, which will > cause the infinite lookup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6169) Recursive lookup while the default comp entry is configured
Recursive lookup while the default comp entry is configured --- Key: GERONIMO-6169 URL: https://issues.apache.org/jira/browse/GERONIMO-6169 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 3.0-M1 Reporter: Ivan Assignee: Ivan Fix For: 3.0 If there is an resource entry like java:comp/EJBContext configured in the DD or added by other modules, and the responsible module has not processed it, AdminObjectRefBuilder will add a JndiReference in the binding map, which will cause the infinite lookup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5265) Modify the redeploy behavior to start all the running childs along with the parent
[ https://issues.apache.org/jira/browse/GERONIMO-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-5265. Resolution: Fixed Fix Version/s: 2.1.8 Assignee: Ivan (was: Ashish Jain) > Modify the redeploy behavior to start all the running childs along with the > parent > -- > > Key: GERONIMO-5265 > URL: https://issues.apache.org/jira/browse/GERONIMO-5265 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.1.5, 2.2.1, 3.0 > Environment: geronimo tomcat assembly >Reporter: Ashish Jain >Assignee: Ivan > Fix For: 2.1.8, 2.2.2, 3.0 > > Attachments: 5265_21.patch > > > Kindly refer the discussion thread > http://n3.nabble.com/Modify-the-redeploy-behaviour-td739706.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5265) Modify the redeploy behavior to start all the running childs along with the parent
[ https://issues.apache.org/jira/browse/GERONIMO-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108410#comment-13108410 ] Ivan commented on GERONIMO-5265: Commit changes based on the patch to 2.1 at rev.1173000, 2.2 at rev.1173001 and trunk at rev.1173002, it looks to me that there is no need to add methods on the ConfigurationManager. Thanks, Ashish Jain ! > Modify the redeploy behavior to start all the running childs along with the > parent > -- > > Key: GERONIMO-5265 > URL: https://issues.apache.org/jira/browse/GERONIMO-5265 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.1.5, 2.2.1, 3.0 > Environment: geronimo tomcat assembly >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.1.8, 2.2.2, 3.0 > > Attachments: 5265_21.patch > > > Kindly refer the discussion thread > http://n3.nabble.com/Modify-the-redeploy-behaviour-td739706.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5265) Modify the redeploy behavior to start all the running childs along with the parent
[ https://issues.apache.org/jira/browse/GERONIMO-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-5265: --- Comment: was deleted (was: Commit changes based on the patch to 2.1 at rev.1173000, 2.2 at rev.1173001 and trunk at rev.1173002, it looks to me that there is no need to add methods on the ConfigurationManager. Thanks, Ashish Jain ! ) > Modify the redeploy behavior to start all the running childs along with the > parent > -- > > Key: GERONIMO-5265 > URL: https://issues.apache.org/jira/browse/GERONIMO-5265 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.1.5, 2.2.1, 3.0 > Environment: geronimo tomcat assembly >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.1.8, 2.2.2, 3.0 > > Attachments: 5265_21.patch > > > Kindly refer the discussion thread > http://n3.nabble.com/Modify-the-redeploy-behaviour-td739706.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5265) Modify the redeploy behavior to start all the running childs along with the parent
[ https://issues.apache.org/jira/browse/GERONIMO-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108409#comment-13108409 ] Ivan commented on GERONIMO-5265: Commit changes based on the patch to 2.1 at rev.1173000, 2.2 at rev.1173001 and trunk at rev.1173002, it looks to me that there is no need to add methods on the ConfigurationManager. Thanks, Ashish Jain ! > Modify the redeploy behavior to start all the running childs along with the > parent > -- > > Key: GERONIMO-5265 > URL: https://issues.apache.org/jira/browse/GERONIMO-5265 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.1.5, 2.2.1, 3.0 > Environment: geronimo tomcat assembly >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.2.2, 3.0 > > Attachments: 5265_21.patch > > > Kindly refer the discussion thread > http://n3.nabble.com/Modify-the-redeploy-behaviour-td739706.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5432) Encrypt password values in server.xml for geronimo 2.2 onwards
[ https://issues.apache.org/jira/browse/GERONIMO-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-5432. Resolution: Fixed Assignee: Ivan (was: Ashish Jain) > Encrypt password values in server.xml for geronimo 2.2 onwards > -- > > Key: GERONIMO-5432 > URL: https://issues.apache.org/jira/browse/GERONIMO-5432 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.2 > Environment: geronimo tomcat assembly >Reporter: Ashish Jain >Assignee: Ivan > Fix For: 2.2.2, 3.0 > > Attachments: EncryptPasswordInServerXMLFor2.2.2_5432.patch, > EncryptPasswordInServerXML_5432.patch, > EncryptPasswordInServerXML_5432_optimize2.patch, > EncryptPasswordInServerXML_5432_optimize3.patch, > EncryptPasswordInServerXML_5432_optmize.patch > > > Password fields in plain text in server.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5432) Encrypt password values in server.xml for geronimo 2.2 onwards
[ https://issues.apache.org/jira/browse/GERONIMO-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107696#comment-13107696 ] Ivan commented on GERONIMO-5432: Commit the changes based on the patch from Xiao Yi to 2.2 at rev.1172511 and trunk at rev.1172518 Thanks, Xiao Yi ! > Encrypt password values in server.xml for geronimo 2.2 onwards > -- > > Key: GERONIMO-5432 > URL: https://issues.apache.org/jira/browse/GERONIMO-5432 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.2 > Environment: geronimo tomcat assembly >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.2.2, 3.0 > > Attachments: EncryptPasswordInServerXMLFor2.2.2_5432.patch, > EncryptPasswordInServerXML_5432.patch, > EncryptPasswordInServerXML_5432_optimize2.patch, > EncryptPasswordInServerXML_5432_optimize3.patch, > EncryptPasswordInServerXML_5432_optmize.patch > > > Password fields in plain text in server.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5704) Track: Farming module provision of utilizing encrypted password instead of plain text
[ https://issues.apache.org/jira/browse/GERONIMO-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107613#comment-13107613 ] Ivan commented on GERONIMO-5704: Commit changes to 2.2 at r1172420 and trunk at r1172421 Thanks, Xiao Yi > Track: Farming module provision of utilizing encrypted password instead of > plain text > - > > Key: GERONIMO-5704 > URL: https://issues.apache.org/jira/browse/GERONIMO-5704 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.2.2, 3.0 > > Attachments: armingModuleEncryptedPasswordFor2.2.2_5704.patch, > farmingModuleEncryptedPassword_5704.patch > > > Track for GERONIMO-5691 for 2,2 and 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5704) Track: Farming module provision of utilizing encrypted password instead of plain text
[ https://issues.apache.org/jira/browse/GERONIMO-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-5704. Resolution: Fixed > Track: Farming module provision of utilizing encrypted password instead of > plain text > - > > Key: GERONIMO-5704 > URL: https://issues.apache.org/jira/browse/GERONIMO-5704 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.2.2, 3.0 > > Attachments: armingModuleEncryptedPasswordFor2.2.2_5704.patch, > farmingModuleEncryptedPassword_5704.patch > > > Track for GERONIMO-5691 for 2,2 and 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6145) Factory info should not be shared among those web jsf applications in one EAR package
[ https://issues.apache.org/jira/browse/GERONIMO-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6145. Resolution: Fixed > Factory info should not be shared among those web jsf applications in one EAR > package > - > > Key: GERONIMO-6145 > URL: https://issues.apache.org/jira/browse/GERONIMO-6145 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: myfaces >Affects Versions: 3.0-M1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > In the FactoryFinder, a map below is used for keep the factory information, > but it should not be shared by different web application in the EAR package. > Now, due to one bundle is used for all the web applications, there will be an > issue > private static Map>> > _registeredFactoryNames = new HashMap List>>(); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6145) Factory info should not be shared among those web jsf applications in one EAR package
[ https://issues.apache.org/jira/browse/GERONIMO-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105953#comment-13105953 ] Ivan commented on GERONIMO-6145: Commit changes to trunk at rev.1171450. Now the abstract name is used for the web application identity. We might not need this function if we turn to multiple bundles strategy per EAR in the future. > Factory info should not be shared among those web jsf applications in one EAR > package > - > > Key: GERONIMO-6145 > URL: https://issues.apache.org/jira/browse/GERONIMO-6145 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: myfaces >Affects Versions: 3.0-M1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > In the FactoryFinder, a map below is used for keep the factory information, > but it should not be shared by different web application in the EAR package. > Now, due to one bundle is used for all the web applications, there will be an > issue > private static Map>> > _registeredFactoryNames = new HashMap List>>(); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-4540) Improve windows startup batch scripts to redirect stdout and stderr messages to GERONIMO_HOME/var/log/geronimo.out
[ https://issues.apache.org/jira/browse/GERONIMO-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105874#comment-13105874 ] Ivan commented on GERONIMO-4540: Agree that we should keep the same behavior between Linux and windows. While it seems that there is no way to control the file output with this way, I am thinking that we should not use this by default. By the way, current changes seem not redirect the error messages to the same output file, guess something like 2>&1 on linux platform is required. > Improve windows startup batch scripts to redirect stdout and stderr messages > to GERONIMO_HOME/var/log/geronimo.out > -- > > Key: GERONIMO-4540 > URL: https://issues.apache.org/jira/browse/GERONIMO-4540 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: commands >Affects Versions: 2.1.4, 2.2 > Environment: Any windows platform >Reporter: Forrest Xia >Assignee: viola.lu >Priority: Minor > Fix For: 2.1.8, 2.2, 3.0 > > > Now the windows startup batch scripts print the stdout and stderr in a > Command Prompt window, sometimes it is not user-friendly to check error or > stdout message for analysis purpose. > Do we need to improve it, so that the stdout and stderr are redirected to a > file, as did on linux platform? > Please comment. thanks! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-4540) Improve windows startup batch scripts to redirect stdout and stderr messages to GERONIMO_HOME/var/log/geronimo.out
[ https://issues.apache.org/jira/browse/GERONIMO-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105150#comment-13105150 ] Ivan commented on GERONIMO-4540: I have some concern for this change, one side, for the windows users, at least from my side, I get used to see a pop windows while using geronimo start or startup.bat to start the server, and I could check the windows whether the server is ready, but now, it seems that I need to check the out put file. Another side, I think that redirect all the output to a file might not a good choice, it means that the file will increase continuously, for a long running server, it might be a problem. If for tracking the messages purpose, all the logger outputs should be also found in the log files, except for the system.out, and actually we could turn off the console appender to disable the outputs on the console, which is a recommended configuration in the product environment. Thoughts ? > Improve windows startup batch scripts to redirect stdout and stderr messages > to GERONIMO_HOME/var/log/geronimo.out > -- > > Key: GERONIMO-4540 > URL: https://issues.apache.org/jira/browse/GERONIMO-4540 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: commands >Affects Versions: 2.1.4, 2.2 > Environment: Any windows platform >Reporter: Forrest Xia >Assignee: viola.lu >Priority: Minor > Fix For: 2.1.8, 2.2, 3.0 > > > Now the windows startup batch scripts print the stdout and stderr in a > Command Prompt window, sometimes it is not user-friendly to check error or > stdout message for analysis purpose. > Do we need to improve it, so that the stdout and stderr are redirected to a > file, as did on linux platform? > Please comment. thanks! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5432) Encrypt password values in server.xml for geronimo 2.2 onwards
[ https://issues.apache.org/jira/browse/GERONIMO-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104547#comment-13104547 ] Ivan commented on GERONIMO-5432: One better location to decrypt the password should be in the connector jaxb class, so there is no need to create a temp servre.xml file while starting up the server. > Encrypt password values in server.xml for geronimo 2.2 onwards > -- > > Key: GERONIMO-5432 > URL: https://issues.apache.org/jira/browse/GERONIMO-5432 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.2 > Environment: geronimo tomcat assembly >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.2.2, 3.0 > > Attachments: EncryptPasswordInServerXML_5432.patch > > > Password fields in plain text in server.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5734) Enable sharelib in osgi based geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-5734. Resolution: Fixed > Enable sharelib in osgi based geronimo > --- > > Key: GERONIMO-5734 > URL: https://issues.apache.org/jira/browse/GERONIMO-5734 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0 > Environment: geronimo 3.0 >Reporter: Ashish Jain >Assignee: Ivan > Fix For: 3.0 > > Attachments: > 0003-GERONIMO-5734-Enable-sharelib-in-osgi-based-geronimo.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6104) @HandlerChain
[ https://issues.apache.org/jira/browse/GERONIMO-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6104. Resolution: Fixed Commit changes to support absolute URL form in the HandlerChain annotation. > @HandlerChain > - > > Key: GERONIMO-6104 > URL: https://issues.apache.org/jira/browse/GERONIMO-6104 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.2.1 >Reporter: vu.nguyen >Assignee: Ivan > Labels: patch > Fix For: 2.2.2, 3.0 > > Attachments: patch.txt > > > Got NPE when using the @HandlerChain annotation in WebService -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6104) @HandlerChain
[ https://issues.apache.org/jira/browse/GERONIMO-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-6104: --- Fix Version/s: 3.0 2.2.2 > @HandlerChain > - > > Key: GERONIMO-6104 > URL: https://issues.apache.org/jira/browse/GERONIMO-6104 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.2.1 >Reporter: vu.nguyen >Assignee: Ivan > Labels: patch > Fix For: 2.2.2, 3.0 > > Attachments: patch.txt > > > Got NPE when using the @HandlerChain annotation in WebService -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6104) @HandlerChain
[ https://issues.apache.org/jira/browse/GERONIMO-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104164#comment-13104164 ] Ivan commented on GERONIMO-6104: Commit changes to 2.2.1 branch at rev1170411, and trunk r1170413. > @HandlerChain > - > > Key: GERONIMO-6104 > URL: https://issues.apache.org/jira/browse/GERONIMO-6104 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.2.1 >Reporter: vu.nguyen >Assignee: Ivan > Labels: patch > Fix For: 2.2.2, 3.0 > > Attachments: patch.txt > > > Got NPE when using the @HandlerChain annotation in WebService -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6157) Generate fixed version number for the import packages
[ https://issues.apache.org/jira/browse/GERONIMO-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6157. Resolution: Fixed > Generate fixed version number for the import packages > - > > Key: GERONIMO-6157 > URL: https://issues.apache.org/jira/browse/GERONIMO-6157 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0-M1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > Provide an option that, the deployer will generate the fixed version number > for the import package, e.g. org.apache.geronimo;version="[3.0,3.0]", so that > make sure the specified version is used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6157) Generate fixed version number for the import packages
[ https://issues.apache.org/jira/browse/GERONIMO-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100893#comment-13100893 ] Ivan commented on GERONIMO-6157: Commit changes to trunk at r1166971. a. Provide an option to decide whether the fixed version number is used to generate b. Do not generate import packages with mandatory directive. > Generate fixed version number for the import packages > - > > Key: GERONIMO-6157 > URL: https://issues.apache.org/jira/browse/GERONIMO-6157 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0-M1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > Provide an option that, the deployer will generate the fixed version number > for the import package, e.g. org.apache.geronimo;version="[3.0,3.0]", so that > make sure the specified version is used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6157) Generate fixed version number for the import packages
Generate fixed version number for the import packages - Key: GERONIMO-6157 URL: https://issues.apache.org/jira/browse/GERONIMO-6157 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: deployment Affects Versions: 3.0-M1 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Provide an option that, the deployer will generate the fixed version number for the import package, e.g. org.apache.geronimo;version="[3.0,3.0]", so that make sure the specified version is used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6132) Not search wired bundles in bundle classloader by default
[ https://issues.apache.org/jira/browse/GERONIMO-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6132. Resolution: Fixed Now the option is added in the startup script at rev.1163516 > Not search wired bundles in bundle classloader by default > - > > Key: GERONIMO-6132 > URL: https://issues.apache.org/jira/browse/GERONIMO-6132 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > From the testing result, it seems that all the functions works well without > searching wired bundles. Also, considering that all kinds of Java EE > applications are installed as one bundle, including EAR package, it should > not an issue for user application to finding the resources in the same > application. > I am thinking to change the codes in xbean and geronimo-hook, by default, > wired bundles will not be searched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6133) The name of NamedXAResourceFactory is not configured while working with DataSource
[ https://issues.apache.org/jira/browse/GERONIMO-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6133. Resolution: Fixed > The name of NamedXAResourceFactory is not configured while working with > DataSource > -- > > Key: GERONIMO-6133 > URL: https://issues.apache.org/jira/browse/GERONIMO-6133 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: connector >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > The exception could be reproduced with the > testsuite\javaee6-testsuite\jta1.1-test sample. > 2011-08-30 14:28:52,421 INFO [Holder] Could not look up > comp/env/org.apache.geronimo.sample.servlet.SHAcc/dataSourcenTx > javax.naming.NamingException: SHAccTx [Root exception is > java.lang.NullPointerException] > at > org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:78) > at > org.apache.xbean.naming.context.ContextUtil$ReadOnlyBinding.getObject(ContextUtil.java:199) > at > org.apache.xbean.naming.context.ContextFederation.getFederatedBindings(ContextFederation.java:119) > at > org.apache.xbean.naming.context.AbstractFederatedContext.getBindings(AbstractFederatedContext.java:99) > at > org.apache.xbean.naming.context.AbstractFederatedContext.getBinding(AbstractFederatedContext.java:86) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:133) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:605) > at > org.apache.geronimo.naming.java.RootContext.lookup(RootContext.java:63) > at > org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161) > at javax.naming.InitialContext.lookup(InitialContext.java:392) > at > org.apache.geronimo.naming.reference.JndiReference.getContent(JndiReference.java:53) > at > org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:116) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:619) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:156) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:619) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:156) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:605) > at > org.apache.geronimo.j2ee.annotation.Holder.addInjections(Holder.java:207) > at > org.apache.geronimo.j2ee.annotation.Holder.newInstance(Holder.java:170) > at > org.apache.geronimo.tomcat.TomcatInstanceManager.newInstance(TomcatInstanceManager.java:74) > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1087) > at > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:824) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:135) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:818) > at > org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:48) > at > org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:851) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:405) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:278) > at > org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:515) > at > org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:300) > at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:243) > at > org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:373) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.lang.NullPoint
[jira] [Resolved] (GERONIMO-6143) Create a fragment context for each sub modules in the EAR package
[ https://issues.apache.org/jira/browse/GERONIMO-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6143. Resolution: Fixed > Create a fragment context for each sub modules in the EAR package > - > > Key: GERONIMO-6143 > URL: https://issues.apache.org/jira/browse/GERONIMO-6143 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0-M1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > Currently, all the sub modules share the same EARContext in one EAR package, > it brings issues for general data, which should be kept for each module > itself. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6143) Create a fragment context for each sub modules in the EAR package
[ https://issues.apache.org/jira/browse/GERONIMO-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099010#comment-13099010 ] Ivan commented on GERONIMO-6143: Commit changes to trunk at rev.1166214. Will trigger a full round TCK to validate the changes. > Create a fragment context for each sub modules in the EAR package > - > > Key: GERONIMO-6143 > URL: https://issues.apache.org/jira/browse/GERONIMO-6143 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0-M1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > Currently, all the sub modules share the same EARContext in one EAR package, > it brings issues for general data, which should be kept for each module > itself. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6126) deploy of the Spring petclinic.war sample app fails
[
https://issues.apache.org/jira/browse/GERONIMO-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098807#comment-13098807
]
Ivan commented on GERONIMO-6126:
There is no default value for the servlet name , the name "default" is from the
Tomcat server configuration, which is for accessing static resources in the web
application, you might check the file in the var/catalina/conf/web.xml file. I
think that the problem here is that, whether it is allowed users to override
the default configurations for the 'default' and 'jsp' servlet from the web
application's web.xml file.
> deploy of the Spring petclinic.war sample app fails
> ---
>
> Key: GERONIMO-6126
> URL: https://issues.apache.org/jira/browse/GERONIMO-6126
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
>Affects Versions: 3.0
>Reporter: Kevan Miller
> Fix For: 3.0
>
>
> Deploying the petclinic.war app on Geroimo 3.0 fails as follows:
> {code}
> $ ./deploy deploy
> ~/spring/spring-samples/petclinic/trunk/target/petclinic.war
> Using GERONIMO_HOME:
> /Users/kevan/geronimo/server/trunk/assemblies/geronimo-tomcat7-javaee6/target/geronimo-tomcat7-javaee6-3.0-SNAPSHOT
> Using GERONIMO_TMPDIR: var/temp
> Using JRE_HOME:
> /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home
> 2011-08-25 11:37:05,880 ERROR [DeployTool] Error:
> org.apache.geronimo.common.DeploymentException: Unable to deploy
> petclinic.war: Problems encountered parsing web.xml: [
> No servlet matching servlet mappings for default]
> at
> org.apache.geronimo.deployment.cli.CommandDeploy.runCommand(CommandDeploy.java:43)
> at
> org.apache.geronimo.deployment.cli.CommandDistribute.executeOnline(CommandDistribute.java:148)
> at
> org.apache.geronimo.deployment.cli.CommandDistribute.execute(CommandDistribute.java:124)
> at
> org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:171)
> at
> org.apache.geronimo.system.main.MainBridge.execute(MainBridge.java:64)
> at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:65)
> at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
> at
> org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:32)
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6126) deploy of the Spring petclinic.war sample app fails
[
https://issues.apache.org/jira/browse/GERONIMO-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098774#comment-13098774
]
Ivan commented on GERONIMO-6126:
It will be better that Geronimo could support to override default servlet in
the parent configuration, I opened a JIRA in the past
https://issues.apache.org/jira/browse/GERONIMO-5882
> deploy of the Spring petclinic.war sample app fails
> ---
>
> Key: GERONIMO-6126
> URL: https://issues.apache.org/jira/browse/GERONIMO-6126
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
>Affects Versions: 3.0
>Reporter: Kevan Miller
> Fix For: 3.0
>
>
> Deploying the petclinic.war app on Geroimo 3.0 fails as follows:
> {code}
> $ ./deploy deploy
> ~/spring/spring-samples/petclinic/trunk/target/petclinic.war
> Using GERONIMO_HOME:
> /Users/kevan/geronimo/server/trunk/assemblies/geronimo-tomcat7-javaee6/target/geronimo-tomcat7-javaee6-3.0-SNAPSHOT
> Using GERONIMO_TMPDIR: var/temp
> Using JRE_HOME:
> /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home
> 2011-08-25 11:37:05,880 ERROR [DeployTool] Error:
> org.apache.geronimo.common.DeploymentException: Unable to deploy
> petclinic.war: Problems encountered parsing web.xml: [
> No servlet matching servlet mappings for default]
> at
> org.apache.geronimo.deployment.cli.CommandDeploy.runCommand(CommandDeploy.java:43)
> at
> org.apache.geronimo.deployment.cli.CommandDistribute.executeOnline(CommandDistribute.java:148)
> at
> org.apache.geronimo.deployment.cli.CommandDistribute.execute(CommandDistribute.java:124)
> at
> org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:171)
> at
> org.apache.geronimo.system.main.MainBridge.execute(MainBridge.java:64)
> at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:65)
> at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
> at
> org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:32)
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6147) Cache the jaxb classes searching result in Axis2 BundleClassFinder
[ https://issues.apache.org/jira/browse/GERONIMO-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097786#comment-13097786 ] Ivan commented on GERONIMO-6147: Commit changes to trunk at r1165547. > Cache the jaxb classes searching result in Axis2 BundleClassFinder > -- > > Key: GERONIMO-6147 > URL: https://issues.apache.org/jira/browse/GERONIMO-6147 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0-M1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > Cache the jaxb classes searching result in Axis2 BundleClassFinder, and use > bundle listener to clear the cache when the bundle is uninstalled. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6147) Cache the jaxb classes searching result in Axis2 BundleClassFinder
[ https://issues.apache.org/jira/browse/GERONIMO-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6147. Resolution: Fixed > Cache the jaxb classes searching result in Axis2 BundleClassFinder > -- > > Key: GERONIMO-6147 > URL: https://issues.apache.org/jira/browse/GERONIMO-6147 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0-M1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > Cache the jaxb classes searching result in Axis2 BundleClassFinder, and use > bundle listener to clear the cache when the bundle is uninstalled. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6147) Cache the jaxb classes searching result in Axis2 BundleClassFinder
Cache the jaxb classes searching result in Axis2 BundleClassFinder -- Key: GERONIMO-6147 URL: https://issues.apache.org/jira/browse/GERONIMO-6147 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: webservices Affects Versions: 3.0-M1 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Cache the jaxb classes searching result in Axis2 BundleClassFinder, and use bundle listener to clear the cache when the bundle is uninstalled. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6145) Factory info should not be shared among those web jsf applications in one EAR package
Factory info should not be shared among those web jsf applications in one EAR package - Key: GERONIMO-6145 URL: https://issues.apache.org/jira/browse/GERONIMO-6145 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: myfaces Affects Versions: 3.0-M1 Reporter: Ivan Assignee: Ivan Fix For: 3.0 In the FactoryFinder, a map below is used for keep the factory information, but it should not be shared by different web application in the EAR package. Now, due to one bundle is used for all the web applications, there will be an issue private static Map>> _registeredFactoryNames = new HashMap>>(); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6143) Create a fragment context for each sub modules in the EAR package
Create a fragment context for each sub modules in the EAR package - Key: GERONIMO-6143 URL: https://issues.apache.org/jira/browse/GERONIMO-6143 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 3.0-M1 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Currently, all the sub modules share the same EARContext in one EAR package, it brings issues for general data, which should be kept for each module itself. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6009) Add a JDBC driver leak prevention bundle listener
[ https://issues.apache.org/jira/browse/GERONIMO-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095876#comment-13095876 ] Ivan commented on GERONIMO-6009: Commit the changes to trunk at 1164418. The idea of listener does not work as I thought in the OSGi environment, it only could help to unregister the Delegating Driver from geronimo-jdbc driver. > Add a JDBC driver leak prevention bundle listener > - > > Key: GERONIMO-6009 > URL: https://issues.apache.org/jira/browse/GERONIMO-6009 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: databases >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: Wish List > > > I like the function of JdbcLeakPrevention function in Tomcat, > https://svn.apache.org/repos/asf/tomcat/trunk/java/org/apache/catalina/loader/JdbcLeakPrevention.java > I am thinking to add a similar function as a bundle listener in Geronimo OSGi > environment, and actually we are suffering the classloader leaking issue now > while building the server. DelegatingDriver loaded by different classloaders > will be registered in the DriverManager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6009) Add a JDBC driver leak prevention bundle listener
[ https://issues.apache.org/jira/browse/GERONIMO-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-6009: --- Fix Version/s: (was: 3.0) Wish List > Add a JDBC driver leak prevention bundle listener > - > > Key: GERONIMO-6009 > URL: https://issues.apache.org/jira/browse/GERONIMO-6009 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: databases >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: Wish List > > > I like the function of JdbcLeakPrevention function in Tomcat, > https://svn.apache.org/repos/asf/tomcat/trunk/java/org/apache/catalina/loader/JdbcLeakPrevention.java > I am thinking to add a similar function as a bundle listener in Geronimo OSGi > environment, and actually we are suffering the classloader leaking issue now > while building the server. DelegatingDriver loaded by different classloaders > will be registered in the DriverManager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (GERONIMO-6009) Add a JDBC driver leak prevention bundle listener
[ https://issues.apache.org/jira/browse/GERONIMO-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reopened GERONIMO-6009: > Add a JDBC driver leak prevention bundle listener > - > > Key: GERONIMO-6009 > URL: https://issues.apache.org/jira/browse/GERONIMO-6009 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: databases >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: Wish List > > > I like the function of JdbcLeakPrevention function in Tomcat, > https://svn.apache.org/repos/asf/tomcat/trunk/java/org/apache/catalina/loader/JdbcLeakPrevention.java > I am thinking to add a similar function as a bundle listener in Geronimo OSGi > environment, and actually we are suffering the classloader leaking issue now > while building the server. DelegatingDriver loaded by different classloaders > will be registered in the DriverManager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6139) Support Java 1.7 Runtime
Support Java 1.7 Runtime Key: GERONIMO-6139 URL: https://issues.apache.org/jira/browse/GERONIMO-6139 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: osgi Affects Versions: 3.0-M1 Reporter: Ivan Assignee: Ivan Seems that the time of 1.7 is coming, it is better that Geronimo could run against 1.7 The initial step is to add the 1.7 profile in the OSGi configuration file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5743) ServletContext.getRealPath() returns null
[ https://issues.apache.org/jira/browse/GERONIMO-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095796#comment-13095796 ] Ivan commented on GERONIMO-5743: Commit changes to trunk at r1164356, a deployment watcher is added to delete the temporary directories while undeploying the applications. > ServletContext.getRealPath() returns null > - > > Key: GERONIMO-5743 > URL: https://issues.apache.org/jira/browse/GERONIMO-5743 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: web >Affects Versions: 3.0-M1 >Reporter: Jarek Gawor >Assignee: Ivan > Fix For: 3.0 > > > In 3.0 M1 and trunk, ServletContext.getRealPath() returns null. In previous > versions of Geronimo a real path was returned. Returning null is ok from > specification point of view but it breaks compatibility for applications. It > also looks like there are a number of web applications that rely on the > getRealPath() to return a non-null value. One such application is Nexus web > app. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6137) Support to deploy web applications with other JSF vendors
Support to deploy web applications with other JSF vendors - Key: GERONIMO-6137 URL: https://issues.apache.org/jira/browse/GERONIMO-6137 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: myfaces Affects Versions: 3.0-M1 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Although Geronimo ships the MyFaces implementation, while still some users would like to use other JSF providers. In the past, users have to configure some classloading options and disable the myfaces deployer. The initial idea for it is to detect whether there is another jsf implementation in the web application by trying to load some vendor class, and once detect, skip the MyFaces builder. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6133) The name of NamedXAResourceFactory is not configured while working with DataSource
[ https://issues.apache.org/jira/browse/GERONIMO-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093552#comment-13093552 ] Ivan commented on GERONIMO-6133: Commit changes to trunk at rev.1163135 > The name of NamedXAResourceFactory is not configured while working with > DataSource > -- > > Key: GERONIMO-6133 > URL: https://issues.apache.org/jira/browse/GERONIMO-6133 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: connector >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > The exception could be reproduced with the > testsuite\javaee6-testsuite\jta1.1-test sample. > 2011-08-30 14:28:52,421 INFO [Holder] Could not look up > comp/env/org.apache.geronimo.sample.servlet.SHAcc/dataSourcenTx > javax.naming.NamingException: SHAccTx [Root exception is > java.lang.NullPointerException] > at > org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:78) > at > org.apache.xbean.naming.context.ContextUtil$ReadOnlyBinding.getObject(ContextUtil.java:199) > at > org.apache.xbean.naming.context.ContextFederation.getFederatedBindings(ContextFederation.java:119) > at > org.apache.xbean.naming.context.AbstractFederatedContext.getBindings(AbstractFederatedContext.java:99) > at > org.apache.xbean.naming.context.AbstractFederatedContext.getBinding(AbstractFederatedContext.java:86) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:133) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:605) > at > org.apache.geronimo.naming.java.RootContext.lookup(RootContext.java:63) > at > org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161) > at javax.naming.InitialContext.lookup(InitialContext.java:392) > at > org.apache.geronimo.naming.reference.JndiReference.getContent(JndiReference.java:53) > at > org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:116) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:619) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:156) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:619) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:156) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:605) > at > org.apache.geronimo.j2ee.annotation.Holder.addInjections(Holder.java:207) > at > org.apache.geronimo.j2ee.annotation.Holder.newInstance(Holder.java:170) > at > org.apache.geronimo.tomcat.TomcatInstanceManager.newInstance(TomcatInstanceManager.java:74) > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1087) > at > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:824) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:135) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:818) > at > org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:48) > at > org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:851) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:405) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:278) > at > org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:515) > at > org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:300) > at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:243) > at > org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:373) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > a
[jira] [Created] (GERONIMO-6133) The name of NamedXAResourceFactory is not configured while working with DataSource
The name of NamedXAResourceFactory is not configured while working with DataSource -- Key: GERONIMO-6133 URL: https://issues.apache.org/jira/browse/GERONIMO-6133 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: connector Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 The exception could be reproduced with the testsuite\javaee6-testsuite\jta1.1-test sample. 2011-08-30 14:28:52,421 INFO [Holder] Could not look up comp/env/org.apache.geronimo.sample.servlet.SHAcc/dataSourcenTx javax.naming.NamingException: SHAccTx [Root exception is java.lang.NullPointerException] at org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:78) at org.apache.xbean.naming.context.ContextUtil$ReadOnlyBinding.getObject(ContextUtil.java:199) at org.apache.xbean.naming.context.ContextFederation.getFederatedBindings(ContextFederation.java:119) at org.apache.xbean.naming.context.AbstractFederatedContext.getBindings(AbstractFederatedContext.java:99) at org.apache.xbean.naming.context.AbstractFederatedContext.getBinding(AbstractFederatedContext.java:86) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:133) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:605) at org.apache.geronimo.naming.java.RootContext.lookup(RootContext.java:63) at org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.apache.geronimo.naming.reference.JndiReference.getContent(JndiReference.java:53) at org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:116) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:619) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:156) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:619) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:156) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:605) at org.apache.geronimo.j2ee.annotation.Holder.addInjections(Holder.java:207) at org.apache.geronimo.j2ee.annotation.Holder.newInstance(Holder.java:170) at org.apache.geronimo.tomcat.TomcatInstanceManager.newInstance(TomcatInstanceManager.java:74) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1087) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:824) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:135) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:818) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:48) at org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:851) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:405) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:278) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:515) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:300) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:243) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:373) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:882) at org.apache.geronimo.transaction.manager.TransactionManagerImpl.registerNamedXAResourceFactory(TransactionManagerImpl.java:352) at org.apache.geronimo.connector.outbound.AbstractConnectionManager.doRecovery
[jira] [Commented] (GERONIMO-6132) Not search wired bundles in bundle classloader by default
[ https://issues.apache.org/jira/browse/GERONIMO-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093462#comment-13093462 ] Ivan commented on GERONIMO-6132: Commit changes to trunk at r1163094 > Not search wired bundles in bundle classloader by default > - > > Key: GERONIMO-6132 > URL: https://issues.apache.org/jira/browse/GERONIMO-6132 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > From the testing result, it seems that all the functions works well without > searching wired bundles. Also, considering that all kinds of Java EE > applications are installed as one bundle, including EAR package, it should > not an issue for user application to finding the resources in the same > application. > I am thinking to change the codes in xbean and geronimo-hook, by default, > wired bundles will not be searched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6132) Not search wired bundles in bundle classloader by default
[ https://issues.apache.org/jira/browse/GERONIMO-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093461#comment-13093461 ] Ivan commented on GERONIMO-6132: Open a JIRA on xbean https://issues.apache.org/jira/browse/XBEAN-183, and commit the changes to trunk. > Not search wired bundles in bundle classloader by default > - > > Key: GERONIMO-6132 > URL: https://issues.apache.org/jira/browse/GERONIMO-6132 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > From the testing result, it seems that all the functions works well without > searching wired bundles. Also, considering that all kinds of Java EE > applications are installed as one bundle, including EAR package, it should > not an issue for user application to finding the resources in the same > application. > I am thinking to change the codes in xbean and geronimo-hook, by default, > wired bundles will not be searched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5734) Enable sharelib in osgi based geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093457#comment-13093457 ] Ivan commented on GERONIMO-5734: Commit changes to trunk at rev.1163089, might need to print some warning messages if felix runtime is used. > Enable sharelib in osgi based geronimo > --- > > Key: GERONIMO-5734 > URL: https://issues.apache.org/jira/browse/GERONIMO-5734 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0 > Environment: geronimo 3.0 >Reporter: Ashish Jain >Assignee: Ivan > Fix For: 3.0 > > Attachments: > 0003-GERONIMO-5734-Enable-sharelib-in-osgi-based-geronimo.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6132) Not search wired bundles in bundle classloader by default
Not search wired bundles in bundle classloader by default - Key: GERONIMO-6132 URL: https://issues.apache.org/jira/browse/GERONIMO-6132 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 >From the testing result, it seems that all the functions works well without >searching wired bundles. Also, considering that all kinds of Java EE >applications are installed as one bundle, including EAR package, it should not >an issue for user application to finding the resources in the same application. I am thinking to change the codes in xbean and geronimo-hook, by default, wired bundles will not be searched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6129) Improvements for Admin Console navigation
[ https://issues.apache.org/jira/browse/GERONIMO-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091802#comment-13091802 ] Ivan commented on GERONIMO-6129: Without the central pages.xml file, it is still able to use the page name in the user-page.xml file, might just need some codes to get the page name from the full name. Or we might add separate attributes (e.g. category, order etc.) in the GBean. For the system user, I mean it is not required to configure the access right in the configuration file, we might treat them as the root users in the system. Or after installing a new portlet plugin, users still need to manually edit the users-page.xml even for system users ? > Improvements for Admin Console navigation > - > > Key: GERONIMO-6129 > URL: https://issues.apache.org/jira/browse/GERONIMO-6129 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 3.0 >Reporter: Shenghao Fang >Assignee: Shenghao Fang >Priority: Minor > Attachments: navigation.patch, pages.xml, user-pages.xml > > > Make 2 improvements for Admin Console navigation: > 1) Centralized configuration file for portlet category >The portlet category is hard-coded in the gbean attribute 'pageTitle' in > 'plan.xml' of each portlet in current implementation. It makes the category > configuration distributed in multiple files which are hard to maintain. >This improvement targets to keep only title in 'pageTitle' and provide a > centralized configuration file for portlet category. It also enables runtime > configuration. > 2) User based navigation tree >This improvement is a part of > [GERONIMO-5675|https://issues.apache.org/jira/browse/GERONIMO-5675]. But it > provides more flexible configuration which makes the basic tree and the > advanced tree can be customized independently. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6129) Improvements for Admin Console navigation
[ https://issues.apache.org/jira/browse/GERONIMO-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091680#comment-13091680 ] Ivan commented on GERONIMO-6129: Personally, I did not find a must reason to keep all the categories in one single one, and it might not a good idea to require an extra action after installing the plugin. If it is for portal authentication, for users of role system, by default, all the portlets could be viewed, for other roles, using the configuration file in the patch should be fine. > Improvements for Admin Console navigation > - > > Key: GERONIMO-6129 > URL: https://issues.apache.org/jira/browse/GERONIMO-6129 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 3.0 >Reporter: Shenghao Fang >Assignee: Shenghao Fang >Priority: Minor > Attachments: navigation.patch, pages.xml, user-pages.xml > > > Make 2 improvements for Admin Console navigation: > 1) Centralized configuration file for portlet category >The portlet category is hard-coded in the gbean attribute 'pageTitle' in > 'plan.xml' of each portlet in current implementation. It makes the category > configuration distributed in multiple files which are hard to maintain. >This improvement targets to keep only title in 'pageTitle' and provide a > centralized configuration file for portlet category. It also enables runtime > configuration. > 2) User based navigation tree >This improvement is a part of > [GERONIMO-5675|https://issues.apache.org/jira/browse/GERONIMO-5675]. But it > provides more flexible configuration which makes the basic tree and the > advanced tree can be customized independently. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6129) Improvements for Admin Console navigation
[ https://issues.apache.org/jira/browse/GERONIMO-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091623#comment-13091623 ] Ivan commented on GERONIMO-6129: I guess that one of the reasons for keeping the category in the title is that, once a console-plugin is installed, it will be automatically added in the admin console. If a centralized configuration file is provided, is it possible to do this ? I mean, users could install the console plugin on an existing server, it will automatically included in the admin console, and a new category will be added in the centralized configuration file if required. > Improvements for Admin Console navigation > - > > Key: GERONIMO-6129 > URL: https://issues.apache.org/jira/browse/GERONIMO-6129 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 3.0 >Reporter: Shenghao Fang >Assignee: Shenghao Fang >Priority: Minor > > Make 2 improvements for Admin Console navigation: > 1) Centralized configuration file for portlet category >The portlet category is hard-coded in the gbean attribute 'pageTitle' in > 'plan.xml' of each portlet in current implementation. It makes the category > configuration distributed in multiple files which are hard to maintain. >This improvement targets to keep only title in 'pageTitle' and provide a > centralized configuration file for portlet category. It also enables runtime > configuration. > 2) User based navigation tree >This improvement is a part of > [GERONIMO-5675|https://issues.apache.org/jira/browse/GERONIMO-5675]. But it > provides more flexible configuration which makes the basic tree and the > advanced tree can be customized independently. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5734) Enable sharelib in osgi based geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090867#comment-13090867 ] Ivan commented on GERONIMO-5734: I made a mistake in the patch, so far, seems that if we would make the share library work, one ways is to generate the export packages and use require-bundle. Another possible way might be check the eclipse buddy policy. > Enable sharelib in osgi based geronimo > --- > > Key: GERONIMO-5734 > URL: https://issues.apache.org/jira/browse/GERONIMO-5734 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0 > Environment: geronimo 3.0 >Reporter: Ashish Jain >Assignee: Ivan > Fix For: 3.0 > > Attachments: > 0003-GERONIMO-5734-Enable-sharelib-in-osgi-based-geronimo.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6122) Support Stateless and Statefull EJB as JAX-RS root resource classes, providers and Application subclasses
[ https://issues.apache.org/jira/browse/GERONIMO-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-6122: --- Fix Version/s: (was: 3.0) > Support Stateless and Statefull EJB as JAX-RS root resource classes, > providers and Application subclasses > - > > Key: GERONIMO-6122 > URL: https://issues.apache.org/jira/browse/GERONIMO-6122 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: viola.lu >Assignee: Ivan >Priority: Minor > Fix For: 3.0.1 > > > From JAX-RS spec 1.1 > In a product that also supports EJB, an implementation MUST support use of > stateless and singleton > session beans as root resource classes, providers and Application subclasses. > JAX-RS annotations > MAY be applied to a bean's local interface or directly to a no-interface > bean. If an Exception- > Mapper for a EJBException or subclass is not included with an application > then exceptions thrown > by an EJB resource class or provider method MUST be treated as EJB > application exceptions: the > embedded cause of the EJBException MUST be unwrapped and processed as > described in section > 3.3.4. > Now geronimo recognize javax.ws.rs.URIinfo as EJB resource in a stateless > EJB, so failed to get Uriinfo > Run Restfulorder samples can give more details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5096) Integrate Wink JAX-RS implementation into Geronimo.
[ https://issues.apache.org/jira/browse/GERONIMO-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan closed GERONIMO-5096. -- The initial wink integration should be OK now, track those optional functions in other JIRAs > Integrate Wink JAX-RS implementation into Geronimo. > > > Key: GERONIMO-5096 > URL: https://issues.apache.org/jira/browse/GERONIMO-5096 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, webservices >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: Shawn Jiang > Fix For: 3.0 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
