Experimental maven plugin
I have just committed an experimental maven plugin that can be used to build Configurations using the local Maven repo as a source for dependencies and parent Configurations. The plugin produces a packaged configuration as its output artifact which can be used for subsequent deployments. There is also a goal for installing such an artifact in a running server. Currently only GBean configurations are supported; I plan to add support for other configurations (including J2EE) over the next few days. This is experimental; the normal build process is unaffected. -- Jeremy
[jira] Closed: (GERONIMO-553) Security Timeout Test failures
[ http://issues.apache.org/jira/browse/GERONIMO-553?page=history ] Alan Cabrera closed GERONIMO-553: - Resolution: Fixed Thanks Sandip. > Security Timeout Test failures > -- > > Key: GERONIMO-553 > URL: http://issues.apache.org/jira/browse/GERONIMO-553 > Project: Geronimo > Type: Improvement > Components: security > Environment: Windows XP > Reporter: Sandip Ghayal > Priority: Minor > Attachments: security_Timout_fix.patch, security_Timout_fix.patch > > When during Geronimo Build I found the Security test failures for Timeout > Test. > During investigation what I found was my login context was being dropped > during running of the test. When investigating further I found that the > timeout was set to one second. Where as the next request came after 1.2 secs > (though the sleep in the test was for 300 ms). > I think that the time out values and machine speed is too critical for this > test to work with such precisions. So I propose to increase the timeout value > to 10 secs and increase the sleep times within the test to 3 secs and 17 > secs. (just multiplied all times by 10). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-604) Gbean error starting configuration org/apache/geronimo/Secure
[ http://issues.apache.org/jira/browse/GERONIMO-604?page=comments#action_61315 ] Alan Cabrera commented on GERONIMO-604: --- How do I reproduce this error? > Gbean error starting configuration org/apache/geronimo/Secure > - > > Key: GERONIMO-604 > URL: http://issues.apache.org/jira/browse/GERONIMO-604 > Project: Geronimo > Type: Bug > Components: security > Environment: svn revision 156721 > Reporter: John Sisson > Assignee: Alan Cabrera > Priority: Blocker > > 22:20:02,888 INFO [Configuration] Started configuration > org/apache/geronimo/Secure > 22:20:02,982 ERROR [GBeanInstanceState] Error while starting; GBean is not in > the FAILED state: > objectName="geronimo.security:type=SecurityRealm,name=demo-properties-realm" > java.lang.IllegalArgumentException: Could not get GBeanInfo for target > object: geronimo.server:j2eeType=LoginModule,J2EEServer=geron > imo,J2EEApplication=null,J2EEModule=org/apache/geronimo/Secure,name=demo-properties-login > at > org.apache.geronimo.kernel.proxy.ProxyMethodInterceptor.createKernelGBeanInvokers(ProxyMethodInterceptor.java:185) > at > org.apache.geronimo.kernel.proxy.ProxyMethodInterceptor.createGBeanInvokers(ProxyMethodInterceptor.java:101) > at > org.apache.geronimo.kernel.proxy.ProxyMethodInterceptor.(ProxyMethodInterceptor.java:66) > at > org.apache.geronimo.kernel.proxy.ProxyManager$ManagedProxyFactory.createProxy(ProxyManager.java:90) > at > org.apache.geronimo.kernel.proxy.ProxyManager.createProxy(ProxyManager.java:49) > at > org.apache.geronimo.security.realm.GenericSecurityRealm.processConfiguration(GenericSecurityRealm.java:178) > at > org.apache.geronimo.security.realm.GenericSecurityRealm.(GenericSecurityRealm.java:107) > 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:274) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:806) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:331) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:111) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:133) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:494) > at > org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:339) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:141) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:494) > at > org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:339) > at org.apache.geronimo.system.main.Daemon.main(Daemon.java:185) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-613) Numerous enhancements / fixes to interop
[ http://issues.apache.org/jira/browse/GERONIMO-613?page=history ] Mark DeLaFranier updated GERONIMO-613: -- Attachment: main.patch This is a patch of my code. > Numerous enhancements / fixes to interop > > > Key: GERONIMO-613 > URL: http://issues.apache.org/jira/browse/GERONIMO-613 > Project: Geronimo > Type: Improvement > Components: CORBA > Versions: 1.0-M3 > Reporter: Mark DeLaFranier > Priority: Minor > Attachments: main.patch > > - Numerious changes have been made to the code to make it more Geronimo code > friendly. > - Cleaned up the stub / skel generator > - Add java method overloading > - Removed some un-necessary files (iiop name stubs, repository, standalone > server startup) > - Fixeda bunch of IIOP marshalling errors that showed up while running the > rmi.iiop code against the J2EE CS 1.3 test harness. > - Not all the rmi.iiop variable names and code style was changed. This > wasn't done to make the previous point easier. > - Made a number of GBeans to support various elements of the server > - Started to use the existing NetworkServices idea of the EJBContainer and > WebServiceContainer. > - More things that I can not remember doing... > Still todo: > - Add interceptor support to plug in security and transactions > - Add code for inserting custom data into the object ref to store references > to statefull objects on the server side. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-613) Numerous enhancements / fixes to interop
Numerous enhancements / fixes to interop Key: GERONIMO-613 URL: http://issues.apache.org/jira/browse/GERONIMO-613 Project: Geronimo Type: Improvement Components: CORBA Versions: 1.0-M3 Reporter: Mark DeLaFranier Priority: Minor Attachments: main.patch - Numerious changes have been made to the code to make it more Geronimo code friendly. - Cleaned up the stub / skel generator - Add java method overloading - Removed some un-necessary files (iiop name stubs, repository, standalone server startup) - Fixeda bunch of IIOP marshalling errors that showed up while running the rmi.iiop code against the J2EE CS 1.3 test harness. - Not all the rmi.iiop variable names and code style was changed. This wasn't done to make the previous point easier. - Made a number of GBeans to support various elements of the server - Started to use the existing NetworkServices idea of the EJBContainer and WebServiceContainer. - More things that I can not remember doing... Still todo: - Add interceptor support to plug in security and transactions - Add code for inserting custom data into the object ref to store references to statefull objects on the server side. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-613) Numerous enhancements / fixes to interop
[ http://issues.apache.org/jira/browse/GERONIMO-613?page=history ] Alan Cabrera reassigned GERONIMO-613: - Assign To: Alan Cabrera > Numerous enhancements / fixes to interop > > > Key: GERONIMO-613 > URL: http://issues.apache.org/jira/browse/GERONIMO-613 > Project: Geronimo > Type: Improvement > Components: CORBA > Versions: 1.0-M3 > Reporter: Mark DeLaFranier > Assignee: Alan Cabrera > Priority: Minor > Attachments: main.patch > > - Numerious changes have been made to the code to make it more Geronimo code > friendly. > - Cleaned up the stub / skel generator > - Add java method overloading > - Removed some un-necessary files (iiop name stubs, repository, standalone > server startup) > - Fixeda bunch of IIOP marshalling errors that showed up while running the > rmi.iiop code against the J2EE CS 1.3 test harness. > - Not all the rmi.iiop variable names and code style was changed. This > wasn't done to make the previous point easier. > - Made a number of GBeans to support various elements of the server > - Started to use the existing NetworkServices idea of the EJBContainer and > WebServiceContainer. > - More things that I can not remember doing... > Still todo: > - Add interceptor support to plug in security and transactions > - Add code for inserting custom data into the object ref to store references > to statefull objects on the server side. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-613) Numerous enhancements / fixes to interop
[ http://issues.apache.org/jira/browse/GERONIMO-613?page=comments#action_61327 ] Alan Cabrera commented on GERONIMO-613: --- nm > Numerous enhancements / fixes to interop > > > Key: GERONIMO-613 > URL: http://issues.apache.org/jira/browse/GERONIMO-613 > Project: Geronimo > Type: Improvement > Components: CORBA > Versions: 1.0-M3 > Reporter: Mark DeLaFranier > Assignee: Alan Cabrera > Priority: Minor > Attachments: main.patch > > - Numerious changes have been made to the code to make it more Geronimo code > friendly. > - Cleaned up the stub / skel generator > - Add java method overloading > - Removed some un-necessary files (iiop name stubs, repository, standalone > server startup) > - Fixeda bunch of IIOP marshalling errors that showed up while running the > rmi.iiop code against the J2EE CS 1.3 test harness. > - Not all the rmi.iiop variable names and code style was changed. This > wasn't done to make the previous point easier. > - Made a number of GBeans to support various elements of the server > - Started to use the existing NetworkServices idea of the EJBContainer and > WebServiceContainer. > - More things that I can not remember doing... > Still todo: > - Add interceptor support to plug in security and transactions > - Add code for inserting custom data into the object ref to store references > to statefull objects on the server side. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-613) Numerous enhancements / fixes to interop
[ http://issues.apache.org/jira/browse/GERONIMO-613?page=comments#action_61326 ] Alan Cabrera commented on GERONIMO-613: --- Mark, is this a cat of several patches? The paths don't seem to line up. > Numerous enhancements / fixes to interop > > > Key: GERONIMO-613 > URL: http://issues.apache.org/jira/browse/GERONIMO-613 > Project: Geronimo > Type: Improvement > Components: CORBA > Versions: 1.0-M3 > Reporter: Mark DeLaFranier > Assignee: Alan Cabrera > Priority: Minor > Attachments: main.patch > > - Numerious changes have been made to the code to make it more Geronimo code > friendly. > - Cleaned up the stub / skel generator > - Add java method overloading > - Removed some un-necessary files (iiop name stubs, repository, standalone > server startup) > - Fixeda bunch of IIOP marshalling errors that showed up while running the > rmi.iiop code against the J2EE CS 1.3 test harness. > - Not all the rmi.iiop variable names and code style was changed. This > wasn't done to make the previous point easier. > - Made a number of GBeans to support various elements of the server > - Started to use the existing NetworkServices idea of the EJBContainer and > WebServiceContainer. > - More things that I can not remember doing... > Still todo: > - Add interceptor support to plug in security and transactions > - Add code for inserting custom data into the object ref to store references > to statefull objects on the server side. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-614) Deployment user error should not vomit stacktraces
Deployment user error should not vomit stacktraces -- Key: GERONIMO-614 URL: http://issues.apache.org/jira/browse/GERONIMO-614 Project: Geronimo Type: Improvement Components: deployment Reporter: Jeremy Boynes The command line deployer dumps a full stacktrace for some common user error conditions (e.g. trying to deploy a RAR without a plan) which is confusing for the user. It should just print an appropriate error message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: Experimental maven plugin
Hi Jeremy,
Looks like this code needs Java 5?
java:compile:
[echo] Compiling to
/opt/geronimo/geronimo/plugins/geronimo-packaging-plugin/target/classes
[echo]
==
NOTE: Targetting JVM 1.4, classes
will not run on earlier JVMs
==
[javac] Compiling 5 source files to
/opt/geronimo/geronimo/plugins/geronimo-packaging-plugin/target/classes
/opt/geronimo/geronimo/plugins/geronimo-packaging-plugin/src/java/org/apache/geronimo/plugin/packaging/AbstractDistributor.java:103:
cannot resolve symbol
symbol : constructor IllegalArgumentException
(java.lang.String,javax.management.MalformedObjectNameException)
location: class java.lang.IllegalArgumentException
throw new IllegalArgumentException("Invalid storeName: " +
storeName, e);
^
1 error
Thanks
-Hari
On Sun, 2005-03-20 at 23:42, Jeremy Boynes wrote:
> I have just committed an experimental maven plugin that can be used to
> build Configurations using the local Maven repo as a source for
> dependencies and parent Configurations.
>
> The plugin produces a packaged configuration as its output artifact
> which can be used for subsequent deployments. There is also a goal for
> installing such an artifact in a running server.
>
> Currently only GBean configurations are supported; I plan to add support
> for other configurations (including J2EE) over the next few days.
>
> This is experimental; the normal build process is unaffected.
>
> --
> Jeremy
Re: Experimental maven plugin
Fixed.
Regards,
Alan
Hari Kodungallur wrote:
Hi Jeremy,
Looks like this code needs Java 5?
java:compile:
[echo] Compiling to /opt/geronimo/geronimo/plugins/geronimo-packaging-plugin/target/classes
[echo]
==
NOTE: Targetting JVM 1.4, classes
will not run on earlier JVMs
==
[javac] Compiling 5 source files to /opt/geronimo/geronimo/plugins/geronimo-packaging-plugin/target/classes
/opt/geronimo/geronimo/plugins/geronimo-packaging-plugin/src/java/org/apache/geronimo/plugin/packaging/AbstractDistributor.java:103: cannot resolve symbol
symbol : constructor IllegalArgumentException (java.lang.String,javax.management.MalformedObjectNameException)
location: class java.lang.IllegalArgumentException
throw new IllegalArgumentException("Invalid storeName: " + storeName, e);
^
1 error
Thanks
-Hari
On Sun, 2005-03-20 at 23:42, Jeremy Boynes wrote:
I have just committed an experimental maven plugin that can be used to
build Configurations using the local Maven repo as a source for
dependencies and parent Configurations.
The plugin produces a packaged configuration as its output artifact
which can be used for subsequent deployments. There is also a goal for
installing such an artifact in a running server.
Currently only GBean configurations are supported; I plan to add support
for other configurations (including J2EE) over the next few days.
This is experimental; the normal build process is unaffected.
--
Jeremy
Re: Experimental maven plugin
thanks
Alan D. Cabrera wrote:
Fixed.
Regards,
Alan
Hari Kodungallur wrote:
Hi Jeremy,
Looks like this code needs Java 5?
java:compile:
[echo] Compiling to
/opt/geronimo/geronimo/plugins/geronimo-packaging-plugin/target/classes
[echo] ==
NOTE: Targetting JVM 1.4, classes
will not run on earlier JVMs
==
[javac] Compiling 5 source files to
/opt/geronimo/geronimo/plugins/geronimo-packaging-plugin/target/classes
/opt/geronimo/geronimo/plugins/geronimo-packaging-plugin/src/java/org/apache/geronimo/plugin/packaging/AbstractDistributor.java:103:
cannot resolve symbol
symbol : constructor IllegalArgumentException
(java.lang.String,javax.management.MalformedObjectNameException)
location: class java.lang.IllegalArgumentException
throw new IllegalArgumentException("Invalid storeName: " +
storeName, e);
^
1 error
Thanks
-Hari
On Sun, 2005-03-20 at 23:42, Jeremy Boynes wrote:
I have just committed an experimental maven plugin that can be used
to build Configurations using the local Maven repo as a source for
dependencies and parent Configurations.
The plugin produces a packaged configuration as its output artifact
which can be used for subsequent deployments. There is also a goal
for installing such an artifact in a running server.
Currently only GBean configurations are supported; I plan to add
support for other configurations (including J2EE) over the next few
days.
This is experimental; the normal build process is unaffected.
--
Jeremy
