date:20100329


 [ 
https://issues.apache.org/jira/browse/GERONIMO-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shawn Jiang closed GERONIMO-5208.
-


Closing it.

> console is broken after upgrading dojo to 1.4.2
> ---
>
> Key: GERONIMO-5208
> URL: https://issues.apache.org/jira/browse/GERONIMO-5208
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2.1, 3.0
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
> Attachments: printscreen.png
>
>
> console is broken after upgrading dojo to 1.4.2.   Some dojo syntax is not 
> compatible with previous version.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (GERONIMODEVTOOLS-607) Missing JSTL jar in server runtime

2010-03-29 Thread Delos Dai (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Delos Dai resolved GERONIMODEVTOOLS-607.


   Resolution: Fixed
Fix Version/s: 3.0
   2.2.1

#928965 for 2.2.1 branch and #928964 for trunk

> Missing JSTL jar in server runtime 
> ---
>
> Key: GERONIMODEVTOOLS-607
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-607
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.2.0
>Reporter: Delos Dai
>Assignee: Delos Dai
> Fix For: 2.2.1, 3.0
>
>
> JSTL jar is missing in GEP 2.2 server runtime

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMODEVTOOLS-607) Missing JSTL jar in server runtime

2010-03-29 Thread Delos Dai (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Delos Dai closed GERONIMODEVTOOLS-607.
--


> Missing JSTL jar in server runtime 
> ---
>
> Key: GERONIMODEVTOOLS-607
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-607
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.2.0
>Reporter: Delos Dai
>Assignee: Delos Dai
> Fix For: 2.2.1, 3.0
>
>
> JSTL jar is missing in GEP 2.2 server runtime

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Webapp Annotation processing for 299

2010-03-29 Thread David Blevins


On Mar 29, 2010, at 7:02 PM, Shawn Jiang wrote:


I'd like to work on this.  Is there a JIRA opened for this ?


Not yet.  Feel free to create as many subtasks as you need under this  
jira:


  http://issues.apache.org/jira/browse/GERONIMO-5080

Maybe a good title for this one would be something like "Java EE  
Injection annotation scanning for 299 beans"


And basically the goal is to give Geronimo a list of 299 bean classes  
so that it can scan them for these annotations:


  @Resource
  @EJB
  @PersistenceContext
  @PersistenceUnit
  @WebServiceRef

The code to do the scanning is there in the naming builders, but the  
code to get a list of bean classes is not there.


Bare in mind this task is way bigger than it appears as we currently  
have no code to really bootstrap OpenWebBeans into Geronimo and kick  
of any of the work it needs to do to actually generate that list of  
299 beans.


There's also a requirement which we might want to just ignore  
initially as it might be way too against the Geronimo architecture.   
The trick is that new beans can be added at startup via the  
BeanManager events and Geronimo does not do *any* annotation scanning  
at startup, only at deploy which could be in a completely different  
java process.  I think we might just need to turn a blind eye to that  
detail or it might be too hard to get started as essentially it might  
mean have re-architect Geronimo at a very fundamental level.  Getting  
anything running would be a great step forward.


Anyway, get ready for a challenge :)

-David

Re: Connector/openejb progress/heads up

2010-03-29 Thread Jarek Gawor

On Mon, Mar 29, 2010 at 1:37 PM, David Jencks  wrote:
> I have most of the new j2ca connector functionality working ok, and finding 
> out whether the rest of it works requires mdbs.  So I'm going to work on 
> getting openejb running in trunk.
>
> Currently there's a bit of a fight between an osgi extender that registers 
> openejb services set up openejb-style and the same functionality set up 
> through gbeans.  Right now I'm dealing with this by disabling the gbean.  I 
> can see 3 choices here...

There shouldn't be any conflict. The EjbDaemonGBean just configures
the properties for the openejb server services. The openejb extender
tracks these server services. The EjbDaemonGBean & openejb extender
work together or at least they used to.

Initially when I worked on the openejb server services, I was thinking
of using config admin to configure the server service properties. That
way, the openejb services could be configured in the same way when
running openejb inside or outside of Geronimo.

Jarek

Re: Publish with GEP takes minutes, while deploy takes 10 seconds

2010-03-29 Thread Delos

Hi Boes,

I also found with eclipse 3.5+, the deployment seems slower than before. I'm
still investigating the root cause.

In deployment process, GEP will pass all artifacts(EAR,WAR,JAR) to WTP. As I
know, WTP will analyze these artifacts, generate many objects,
package&extract them. I've ever tried a big EAR and found most time is
consumed by WTP.  But I haven't further investigated the process in WTP.

If possible, could you provide your app for me to double check the problem?

Although we haven't found the root cause, there may be some workaround for
you
1) To speed up the deployment of JSP,  you can select "No re-deployment when
only JSP files are updated" in "Test environment" section of server
"Overview" page. You may find the page after double click server instance in
"Servers" view.
2) Put all lib you will never change as shared library in Geronimo server
3) Avoid automatic publishing. If automatic publishing is enabled, any save
action on an deployed artifact will trigger publishing. It's inconvenient
for a big artifact. I suggest you disable it and manually publish it when
all your changes have been completed. You can select "Never publish
automatically" in "Publishing" section of server "Overview" page.

Hope it helps!

2010/3/30 boes 

>
> Hi,
>
> I have an Enterprise Application (EAR) that I develop in Eclipse
> (galileo-SR1). When I publish my EAR to the started local Geronimo V2.1.4
> server, it takes more then 3 minutes to finish. I use GEP version 2.2.
> During the process 1 CPU is constantly running at 100%, so it looks like
> the
> system is very busy. The status bar shows 'Publishing to Apache Geronimo
> V2.1 at localhost (0%)' and it stays on 0% almost to the end of the
> publishing process.
>
> When I export the application as an .ear file to the file system and then
> deploy the application to the same Geronimo server using the Geronimo
> console, I found that writing the EAR to the filesystem takes 2 seconds to
> complete, and the deployment of the EAR to Geronimo takes about 8 seconds.
>
> My EAR consists of 8 web applications (WAR) and one utility project (JAR).
> Deployment to the production environment also takes less then 10 seconds.
> The application itself is extensively used and stable.
>
> Is there a logical reason why publishing takes much more time then
> deployment? Are they two different things that can't be compared?
>
> I tried to get some more info on what the publishing process is actually
> doing in those three minutes. In the server settings in Eclipse I set the
> console output to 'Debug', but I did not get any output from GEP. Is there
> an option to make GEP verbose and let it print what it is doing?
>
> I found that adding dependencies to a project slows down the publishing
> process. I started with a new EAR project with one WAR, which had only one
> html page. It takes a second to publish this EAR to Geronimo. Then I
> extended the geronimo-application.xml deployment despriptor by adding some
> dependencies to existing libraries in the Geronimo repository. This
> increases the publish time to 30 seconds. How can that be explained?
>
> Is there any more info on GEP? What is it doing when it publishes an EAR to
> Geronimo? What can I do to speed up publishing?
>
> Thanks for any help and information on this subject.
>
> Boes
>
>
> --
> View this message in context:
> http://n3.nabble.com/Publish-with-GEP-takes-minutes-while-deploy-takes-10-seconds-tp684484p684484.html
> Sent from the Development mailing list archive at Nabble.com.
>



-- 
Best Regards,

Delos

Re: Delay Geronimo 2.1.5 RC to Mar. 30

2010-03-29 Thread Rex Wang

Tomcat 6.0.26.0 has passed the vote. Unfortunately, OpenEJB 3.0.2's voting
is canceled. So still need 3 or 4 days to get a RC build.

-Rex

2010/3/29 Rex Wang 

> Dear all,
>
> We almost closed all the JIRAs that MUST be fixed for 2.1.5, except the two
> opened for upgrade Tomcat and OpenEJB. Hope the votes can be passed tomorrow
> so that we can make a RC on time.
>
> I also create a wiki page to record what changes I have made for 2.1.5
> build, please refer:
>
> http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+2.1.5+Release+Tips
> Hope this can help the guy who became the following version's release
> manager know more about the new process.
>
> -Rex
>
> 2010/3/26 Rex Wang 
>
>
>> We are still waiting the TCK results of external Tomcat 6.0.26.0 and also
>> OpenEJB voting result, so delay the release candidate build.
>>
>> --
>> Lei Wang (Rex)
>> rwonly AT apache.org
>>
>
>
>
> --
> Lei Wang (Rex)
> rwonly AT apache.org
>



-- 
Lei Wang (Rex)
rwonly AT apache.org

Re: [VOTE] Release tomcat-parent-6.0.26

2010-03-29 Thread Delos

Thanks all!

Here is the voting result
+1: Ivan, Kevan, Rick

So it has passed voting!

2010/3/30 Rick McGuire 

>  +1
>
>
> On 3/24/2010 10:44 PM, Delos wrote:
>
>
> This voting is for  tomcat-parent-6.0.26. It will be used by Geronimo
> 2.1.5.It's based on tomcat 6.0.26, built with maven. Besides, we also
> applied some patches which haven't been included in tomcat 6.0.26.
>
>
>  Based on tomcat 6.0.26 tag, we applied additional patches for
>
>
> GERONIMO-3451 -  'Restricted listeners property file not found' error
> logged during Tomcat server startup (Patch from Shawn Jiang)
>
> GERONIMO-4685 - patch for revision 790742
>
> Staging repo:
>
>  
> https://repository.apache.org/content/repositories/orgapachegeronimo-015/
>
>
>  svn tag at:
>
>  
>
> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.26.0
> /
>
>
> [ ] +1 go for it
> [ ] 0
> [ ] -1 whoa, hold on a minute
>
>
> thanks a lot!
>
> --
> Best Regards,
>
> Delos
>
>
>


-- 
Best Regards,

Delos

Re: Webapp Annotation processing for 299

2010-03-29 Thread Shawn Jiang

I'd like to work on this.  Is there a JIRA opened for this ?

On Tue, Mar 30, 2010 at 9:43 AM, David Blevins wrote:

> Bringing this thread up again as it is still a major TODO and if someone is
> looking for something to work on, it's a very good place.
>
>
> On Aug 21, 2009, at 8:16 PM, David Blevins wrote:
>
>  Great summary, thanks!
>>
>> So as I mentioned on the OpenEJB list and the reason I kicked the thread
>> over here is that the ServletContextListener approach to scanning doesn't
>> work as none of those things exist at deploy time.
>>
>> To try and move things forward I've created a basic plugin for
>> OpenWebBeans that can serve as a starting point for the integration.  This
>> will help get us out of the abstract and right down to the nuts and bolts.
>>
>> DEPLOYMENT
>>
>> Long story short, the code that scans the managed bean classes for
>> @Resource etc. goes here:
>>
>>
>> http://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/geronimo-openwebbeans-builder/src/main/java/org/apache/geronimo/openwebbeans/deployment/OpenWebBeansModuleBuilderExtension.java
>>
>> The code to do the @Resource scanning is actually in there already, it's
>> the line like this:
>>  namingBuilders.buildNaming(webApp, jettyWebApp, webModule,
>> buildingContext);
>> What needs to happen in this class is we need to get a complete list of
>> the managed bean classes so they can be scanned by the Geronimo naming
>> builder.  This class is an extension to the Geronimo deployment system, so
>> no webapp objects exist yet.  I know that the OpenWebBeans code doesn't
>> currently work like this and relies on ServetContext and other things.  We
>> will have to find a way to get that to work without the use of any servet
>> APIs.
>>
>> A bonus is that you can install any servlets or filters or listeners you
>> like into the webapp so when it boots, anything you'd like to add will be
>> there without the user having to add it.  A pretty cool advantage to being
>> part of the deployment system.  I've got some code in there that adds a
>> ServletContextListener -- I left the classname of the listener blank, you
>> just need to fill it in.
>>
>> For a great example of what the JSF deployer extension looks like, see
>> this class:
>>
>>
>> https://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/myfaces/geronimo-myfaces-builder/src/main/java/org/apache/geronimo/myfaces/deployment/MyFacesModuleBuilderExtension.java
>>
>>
>> RUNTIME
>>
>> Here's where you can add any startup and shutdown code you'd like:
>>
>>
>> http://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/OpenWebBeansGBean.java
>>
>> This will be guaranteed to run just before the webapp starts up and stop
>> just after the webapp stops.  Great place for initialization code and taking
>> care of getting any hooks into Geronimo that you might need/want for while
>> the webapp is running.
>>
>> This doesn't tackle everything on the TODO list but is a step in the right
>> direction.
>>
>> -David
>>
>> On Aug 20, 2009, at 8:01 AM, Gurkan Erdogdu wrote:
>>
>>  I want to give brief introduction about current implementation in the
>>> view of integration points
>>>
>>> Brief Summary About Current Situation
>>> -
>>> Currently we bootstrap OpenWebBeans via ServletContextListener. It
>>> supports following containers
>>>
>>> - Java Web Containers like Jetty, Tomcat etc.
>>> - Tomcat Embeddable OpenEJB Container
>>>
>>> If developer wants to use OWB functionality in his application, it has to
>>> configure its "web.xml" to include some OWB specific classes. For EJB
>>> functionality, we use embeddable Tomcat OpenEJB container. To use EJB
>>> functionality, developer must annotate their EJB classes with OWB specific
>>> "Interceptor" class.
>>>
>>> How OWB Boots Currently(From integration point of view)
>>> ---
>>> 1* Web Container calls OWB specific context listener's "application
>>> started" method
>>> 2* OWB container scans related classes from the artifacts (if
>>> META-INF/beans.xml, or WEB-INF/beans.xml exists. beans.xml is a marker for
>>> deployment)
>>> 3* If developer configures OWB to use EJB functionality, for each scanned
>>> class, it asks OpenEJB to learn whether it is an EJB class or not (Using EJB
>>> Plugin that is written accroding to the OpenEJB)
>>> 4* If it is an EJB class, it creates EJB bean and register it with the
>>> OWB container otherwise if it is a Java EE defined Managed Bean Class, it
>>> creates a "Managed Bean" and register it with the OWB container.
>>>
>>> Developer Responsibility to Use OWB
>>> 
>>> 1* Add servlet context listener to his web module's "web.xml"
>>> 2* Annotate EJB classes with OWB interceptor
>>> 3* Configure OWB container to use EJB functionality
>>> 4* Conf

[jira] Closed: (GERONIMO-5093) Create JAXB 2.2 spec jar


 [ 
https://issues.apache.org/jira/browse/GERONIMO-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shawn Jiang closed GERONIMO-5093.
-

Resolution: Fixed

there's only signature testing for jaxb,  there won't be singature problems in 
the changes.  Closing it.

> Create JAXB 2.2 spec jar
> 
>
> Key: GERONIMO-5093
> URL: https://issues.apache.org/jira/browse/GERONIMO-5093
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: javaee6, specs
>Affects Versions: 3.0
>Reporter: Rick McGuire
>Assignee: Shawn Jiang
> Fix For: 3.0
>
>
> A new version of the jaxb specs is needed for the 2.2 level. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Webapp Annotation processing for 299

2010-03-29 Thread David Blevins

Bringing this thread up again as it is still a major TODO and if
someone is looking for something to work on, it's a very good place.

On Aug 21, 2009, at 8:16 PM, David Blevins wrote:

Great summary, thanks!

So as I mentioned on the OpenEJB list and the reason I kicked the
thread over here is that the ServletContextListener approach to
scanning doesn't work as none of those things exist at deploy time.

To try and move things forward I've created a basic plugin for
OpenWebBeans that can serve as a starting point for the
integration. This will help get us out of the abstract and right
down to the nuts and bolts.

DEPLOYMENT

Long story short, the code that scans the managed bean classes for
@Resource etc. goes here:

http://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/geronimo-openwebbeans-builder/src/main/java/org/apache/geronimo/openwebbeans/deployment/OpenWebBeansModuleBuilderExtension.java

The code to do the @Resource scanning is actually in there already,
it's the line like this:
namingBuilders.buildNaming(webApp, jettyWebApp, webModule,
buildingContext);
What needs to happen in this class is we need to get a complete list
of the managed bean classes so they can be scanned by the Geronimo
naming builder. This class is an extension to the Geronimo
deployment system, so no webapp objects exist yet. I know that the
OpenWebBeans code doesn't currently work like this and relies on
ServetContext and other things. We will have to find a way to get
that to work without the use of any servet APIs.

A bonus is that you can install any servlets or filters or listeners
you like into the webapp so when it boots, anything you'd like to
add will be there without the user having to add it. A pretty cool
advantage to being part of the deployment system. I've got some
code in there that adds a ServletContextListener -- I left the
classname of the listener blank, you just need to fill it in.

For a great example of what the JSF deployer extension looks like,
see this class:

https://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/myfaces/geronimo-myfaces-builder/src/main/java/org/apache/geronimo/myfaces/deployment/MyFacesModuleBuilderExtension.java

RUNTIME

Here's where you can add any startup and shutdown code you'd like:

http://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/OpenWebBeansGBean.java

This will be guaranteed to run just before the webapp starts up and
stop just after the webapp stops. Great place for initialization
code and taking care of getting any hooks into Geronimo that you
might need/want for while the webapp is running.

This doesn't tackle everything on the TODO list but is a step in the
right direction.

-David

On Aug 20, 2009, at 8:01 AM, Gurkan Erdogdu wrote:

I want to give brief introduction about current implementation in
the view of integration points

Brief Summary About Current Situation
-
Currently we bootstrap OpenWebBeans via ServletContextListener. It
supports following containers

- Java Web Containers like Jetty, Tomcat etc.
- Tomcat Embeddable OpenEJB Container

If developer wants to use OWB functionality in his application, it
has to configure its "web.xml" to include some OWB specific
classes. For EJB functionality, we use embeddable Tomcat OpenEJB
container. To use EJB functionality, developer must annotate their
EJB classes with OWB specific "Interceptor" class.

How OWB Boots Currently(From integration point of view)
---
1* Web Container calls OWB specific context listener's "application
started" method
2* OWB container scans related classes from the artifacts (if META-
INF/beans.xml, or WEB-INF/beans.xml exists. beans.xml is a marker
for deployment)
3* If developer configures OWB to use EJB functionality, for each
scanned class, it asks OpenEJB to learn whether it is an EJB class
or not (Using EJB Plugin that is written accroding to the OpenEJB)
4* If it is an EJB class, it creates EJB bean and register it with
the OWB container otherwise if it is a Java EE defined Managed Bean
Class, it creates a "Managed Bean" and register it with the OWB
container.

Developer Responsibility to Use OWB

1* Add servlet context listener to his web module's "web.xml"
2* Annotate EJB classes with OWB interceptor
3* Configure OWB container to use EJB functionality
4* Configure some OWB specific parameters (For example : if use JMS
injections, specify ConnectionFactory JNDI name)

Current Problems
-
1* Currently we just support "WAR" module with embeddable EJB.
2* Developer requires to update WAR/EJB module metadata files to
use OWB.

3* Standalone EJB JAR,RA

Re: [VOTE] Release tomcat-parent-6.0.26

2010-03-29 Thread Rick McGuire


+1

On 3/24/2010 10:44 PM, Delos wrote:


This voting is for tomcat-parent-6.0.26. It will be used by Geronimo 
2.1.5.It 's based on tomcat 6.0.26, built with maven. 
Besides, we also applied some patches which haven't been included in 
tomcat 6.0.26.



Based on tomcat 6.0.26 tag, we applied additional patches for


GERONIMO-3451 -  'Restricted listeners property file not found' error 
logged during Tomcat server startup (Patch from Shawn Jiang)


GERONIMO-4685 - patch for revision 790742

Staging repo:


https://repository.apache.org/content/repositories/orgapachegeronimo-015/


svn tag at:


https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.26.0/


[ ] +1 go for it
[ ] 0
[ ] -1 whoa, hold on a minute


thanks a lot!

--
Best Regards,

Delos

[BUILD] trunk: Failed for Revision: 928953

Geronimo Revision: 928953 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100329/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100329/unit-test-reports
 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) 
org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT
2) 
org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT
3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots),
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  java.net.2 (http://download.java.net/maven/1/),
  jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/),
  openqa-releases (http://nexus.openqa.org/content/repositories/releases),
  smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) 
org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT
2) 
org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT
3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots

Re: 3.0 Milestone Release?

2010-03-29 Thread Ivan

A milestone release might be a good report for what we have done. I wish to
include some servlet 3.0 updates that I am working now.

2010/3/30 Kevan Miller 

> I'm curious to hear the community's thoughts about starting to pull
> together a 3.0 Milestone release. I think there's been a lot of progress on
> trunk and that it would be valuable to start pulling things together for a
> release.
>
> If anything, just planning for a release starts to identify hat parts are
> missing and what needs to be done. Also, gives users a chance to start
> focusing on what features they are going to need...
>
> Thoughts?
>
> --kevan




-- 
Ivan

[jira] Commented: (GERONIMO-5214) connector builder should export interfaces that need to be used by users of the connector


[ 
https://issues.apache.org/jira/browse/GERONIMO-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851174#action_12851174
 ] 

David Jencks commented on GERONIMO-5214:


rev 928947, seems to work maybe we can think of some way if the package is 
also imported.

> connector builder should export interfaces that need to be used by users of 
> the connector
> -
>
> Key: GERONIMO-5214
> URL: https://issues.apache.org/jira/browse/GERONIMO-5214
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: connector, osgi
>Affects Versions: 3.0
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 3.0
>
>
> The connector builder should automatically export packages that are used in 
> the connection interface, connection factory interface, activation spec, 
> message listener, and admin object interface if they are actually supplied by 
> the ra.  We can be pretty sure that clients need to use these.
> It's not entirely reliable, but we can use package admin to find the bundle 
> for each of these classes and see if it is the same as the current bundle we 
> are working on: in this case the connector definitely supplies the class.  It 
> might still be able to supply it if its wired in from elsewhere not much 
> we can do about this I think.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-5214) connector builder should export interfaces that need to be used by users of the connector

connector builder should export interfaces that need to be used by users of the 
connector
-

 Key: GERONIMO-5214
 URL: https://issues.apache.org/jira/browse/GERONIMO-5214
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: connector, osgi
Affects Versions: 3.0
Reporter: David Jencks
Assignee: David Jencks
 Fix For: 3.0


The connector builder should automatically export packages that are used in the 
connection interface, connection factory interface, activation spec, message 
listener, and admin object interface if they are actually supplied by the ra.  
We can be pretty sure that clients need to use these.

It's not entirely reliable, but we can use package admin to find the bundle for 
each of these classes and see if it is the same as the current bundle we are 
working on: in this case the connector definitely supplies the class.  It might 
still be able to supply it if its wired in from elsewhere not much we can 
do about this I think.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Publish with GEP takes minutes, while deploy takes 10 seconds

2010-03-29 Thread boes

Hi,

I have an Enterprise Application (EAR) that I develop in Eclipse
(galileo-SR1). When I publish my EAR to the started local Geronimo V2.1.4
server, it takes more then 3 minutes to finish. I use GEP version 2.2.
During the process 1 CPU is constantly running at 100%, so it looks like the
system is very busy. The status bar shows 'Publishing to Apache Geronimo
V2.1 at localhost (0%)' and it stays on 0% almost to the end of the
publishing process.

When I export the application as an .ear file to the file system and then
deploy the application to the same Geronimo server using the Geronimo
console, I found that writing the EAR to the filesystem takes 2 seconds to
complete, and the deployment of the EAR to Geronimo takes about 8 seconds.

My EAR consists of 8 web applications (WAR) and one utility project (JAR).
Deployment to the production environment also takes less then 10 seconds.
The application itself is extensively used and stable.

Is there a logical reason why publishing takes much more time then
deployment? Are they two different things that can't be compared?

I tried to get some more info on what the publishing process is actually
doing in those three minutes. In the server settings in Eclipse I set the
console output to 'Debug', but I did not get any output from GEP. Is there
an option to make GEP verbose and let it print what it is doing?

I found that adding dependencies to a project slows down the publishing
process. I started with a new EAR project with one WAR, which had only one
html page. It takes a second to publish this EAR to Geronimo. Then I
extended the geronimo-application.xml deployment despriptor by adding some
dependencies to existing libraries in the Geronimo repository. This
increases the publish time to 30 seconds. How can that be explained?

Is there any more info on GEP? What is it doing when it publishes an EAR to
Geronimo? What can I do to speed up publishing?

Thanks for any help and information on this subject.

Boes

--
View this message in context:
http://n3.nabble.com/Publish-with-GEP-takes-minutes-while-deploy-takes-10-seconds-tp684484p684484.html
Sent from the Development mailing list archive at Nabble.com.

Re: Connector/openejb progress/heads up

2010-03-29 Thread David Jencks


On Mar 29, 2010, at 2:58 PM, David Blevins wrote:

> 
> On Mar 29, 2010, at 10:37 AM, David Jencks wrote:
> 
>> I have most of the new j2ca connector functionality working ok, and finding 
>> out whether the rest of it works requires mdbs.  So I'm going to work on 
>> getting openejb running in trunk.
>> 
>> Currently there's a bit of a fight between an osgi extender that registers 
>> openejb services set up openejb-style and the same functionality set up 
>> through gbeans.  Right now I'm dealing with this by disabling the gbean.  I 
>> can see 3 choices here...
>> 
>> 
>> 1. disable all the openejb configuration functionality and just use gbeans.  
>> This is fairly awkward but what we've been doing so far.  I think it tends 
>> to obscure some openejb configuration possibilities, but maybe not too 
>> seriously.
>> 
>> 2. configure openejb using blueprint or xbean-blueprint.  Or write a new 
>> blueprint namespace handler that deals with the openejb multilevel property 
>> files.
>> 
>> 3. hook up openejb's native configuration system to osgi config admin.
>> 
>> Any thoughts?
> 
> I'm not sure I fully understand the implications of the second two options, 
> but generally I'm on board with anything that works for Geronimo and still 
> allows OpenEJB to function in other scenarios without OSGi.
> 
> Just for simplicity sake it would be nice to do things in the Geronimo way, 
> but I get the feeling we're still figuring that out in reference to OSGi.  In 
> which case, this might be a good use case for exploring that Geronimo-way 
> question.
> 
> What are we going to be doing in regards to Jetty/Tomcat/ActiveMQ 
> configuration?

jetty - at the moment, gbean configurations... not thrilled with it or native 
jetty configuration
tomcat - custom jaxb processing of server.xml
activemq - xbean-blueprint (the reason for the existence of xbean-blueprint)

david jencks

> 
> -David
>

Re: Connector/openejb progress/heads up

2010-03-29 Thread David Blevins



On Mar 29, 2010, at 10:37 AM, David Jencks wrote:

I have most of the new j2ca connector functionality working ok, and  
finding out whether the rest of it works requires mdbs.  So I'm  
going to work on getting openejb running in trunk.


Currently there's a bit of a fight between an osgi extender that  
registers openejb services set up openejb-style and the same  
functionality set up through gbeans.  Right now I'm dealing with  
this by disabling the gbean.  I can see 3 choices here...



1. disable all the openejb configuration functionality and just use  
gbeans.  This is fairly awkward but what we've been doing so far.  I  
think it tends to obscure some openejb configuration possibilities,  
but maybe not too seriously.


2. configure openejb using blueprint or xbean-blueprint.  Or write a  
new blueprint namespace handler that deals with the openejb  
multilevel property files.


3. hook up openejb's native configuration system to osgi config admin.

Any thoughts?


I'm not sure I fully understand the implications of the second two  
options, but generally I'm on board with anything that works for  
Geronimo and still allows OpenEJB to function in other scenarios  
without OSGi.


Just for simplicity sake it would be nice to do things in the Geronimo  
way, but I get the feeling we're still figuring that out in reference  
to OSGi.  In which case, this might be a good use case for exploring  
that Geronimo-way question.


What are we going to be doing in regards to Jetty/Tomcat/ActiveMQ  
configuration?


-David

Deploying Aries Blog sample & AriesTrader on Geronimo

2010-03-29 Thread Jarek Gawor

Hi all,

I recently integrated the JTA and JPA pieces from Aries in Geronimo
and exposed connection factories in OSGi service registry. With these
changes we now have all the main pieces in place to deploy unmodified
Aries Blog sample & AriesTrader on Geronimo. Here's how to do it:

1) Make sure you have the latest trunk build. I used tomcat ee 6
assembly but things should also work with the jetty assembly.

2) Deploy the attached aries-datasource connector. It will create the
data sources & database tables for both samples. To deploy the
connector do:

./bin/deploy -u system -p manager deploy
~/.m2/repository/org/tranql/tranql-connector-derby-embed-xa/1.5/tranql-connector-derby-embed-xa-1.5.rar
aries-datasource.xml

3) Build "samples" module in Aries trunk.

To deploy the Blog sample do:

./bin/deploy -u system -p manager deploy /samples/blog/blog-jpa-eba/target/org.apache.aries.samples.blog.jpa.eba-0.1-incubating-SNAPSHOT.eba

or to deploy AriesTrader do:

./bin/deploy -u system -p manager deploy /samples/ariestrader-sample/assemblies/ariestrader-all-eba/target/org.apache.aries.samples.ariestrader.all-0.1-incubating-SNAPSHOT.eba

If all goes well the Blog sample should be available under
http://localhost:8080/blog and AriesTrader under
http://localhost:8080/ariestrader.

Btw, when running the deploy command you might see some "Address
already in use" exceptions. They can be ignored.

Let me know if you have any problems,

Jarek





http://geronimo.apache.org/xml/ns/j2ee/connector-1.2";>

 http://geronimo.apache.org/xml/ns/deployment-1.2";>

  org.apache.geronimo.configs
  aries-datasource
  3.0-SNAPSHOT
  car

 




javax.sql.DataSource


jdbc/blogdb
jdbc/blogdb


blogDB
true





100
5000





jdbc/blogdbnojta
jdbc/blogdbnojta


blogDB
true



100
5000







jdbc/TradeDataSource
jdbc/TradeDataSource


tradedb
true





100
5000





jdbc/NoTxTradeDataSource
jdbc/NoTxTradeDataSource


tradedb
true



100
5000













create table holdingejb
  (purchaseprice decimal(10, 2),
   holdingid integer not null,
   quantity double not null,
   purchasedate timestamp,
   account_accountid integer,
   quote_symbol varchar(250),
   optLock integer);

alter table holdingejb
  add constraint pk_holdingejb primary key (holdingid);

create table accountprofileejb
  (address varchar(250),
   passwd varchar(250),
   userid varchar(250) not null,
   email varchar(250),
   creditcard varchar(250),
   fullname varchar(250),
   optLock integer);

alter table accountprofileejb
  add constraint pk_accountprofile2 primary key (userid);

create table quoteejb
  (low decimal(10, 2),
   open1 decimal(10, 2),
   volume double not null,
   price decimal(10, 2),
   high decimal(10, 2),
   companyname varchar(250),
   symbol varchar(250) not null,
   change1 double not null,
   optLock integer);

alter table quoteejb
  add constraint pk_quoteejb primary key (symbol);

create table keygenejb
  (keyval integer not null,
   keyname varchar(250) not null);

alter table keygenejb
  add constraint pk_keygenejb primary key (keyname);

create table accountejb
  (creationdate timestamp,
   openbalance decimal(10, 2),
   logoutcount integer not null,
   balance decimal(10, 2),
   accountid integer not null,
   lastlogin timestamp,
   logincount integer not null,
   PROFILE_USERID VARCHAR(250),
   optLock integer);

alter table accountejb
  add constraint pk_accountejb primary key (

3.0 Milestone Release?

2010-03-29 Thread Kevan Miller

I'm curious to hear the community's thoughts about starting to pull together a 
3.0 Milestone release. I think there's been a lot of progress on trunk and that 
it would be valuable to start pulling things together for a release. 

If anything, just planning for a release starts to identify hat parts are 
missing and what needs to be done. Also, gives users a chance to start focusing 
on what features they are going to need...

Thoughts?

--kevan

[BUILD] trunk: Failed for Revision: 928870

Geronimo Revision: 928870 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100329/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100329/unit-test-reports
 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) 
org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT
2) 
org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT
3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots),
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  java.net.2 (http://download.java.net/maven/1/),
  jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/),
  openqa-releases (http://nexus.openqa.org/content/repositories/releases),
  smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) 
org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT
2) 
org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT
3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots

[jira] Created: (GERONIMO-5213) Review Geronimo 3.0 commands need a thorough review

2010-03-29 Thread Kevan Miller (JIRA)

Review Geronimo 3.0 commands need a thorough review
---

 Key: GERONIMO-5213
 URL: https://issues.apache.org/jira/browse/GERONIMO-5213
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: commands
Affects Versions: 3.0
Reporter: Kevan Miller
 Fix For: 3.0


The current set of Geronimo commands (geronimo, deploy, start, stop, shutdown, 
admin, client) need to be reviewed for functionality. Mostly, they are adopting 
gshell syntax/semantics. There needs to be a thorough review that the new set 
of commands are providing all of the features/functions that users are 
currently using. 

I think having a single set of commands rather than the duplicate commands (old 
and newer gshell-based commands) is good. There should be documentation on how 
to migrate from the old environment to the new. For example, for people using 
JAVA_OPTS / GERONIMO_OPTS how do they move to the new geronimo command?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-5212) Do we need Karaf when starting Geronimo?

2010-03-29 Thread Kevan Miller (JIRA)

Do we need Karaf when starting Geronimo?


 Key: GERONIMO-5212
 URL: https://issues.apache.org/jira/browse/GERONIMO-5212
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 3.0
Reporter: Kevan Miller
 Fix For: 3.0


Starting up Karaf seems to consume a fair amount of time as a Geronimo server 
is started. Is it needed? I think we should consider slimming down the server 
startup. I'm not sure what it's buying us, at the moment...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-5211) geronimo start command is very verbose

2010-03-29 Thread Kevan Miller (JIRA)

geronimo start command is very verbose
--

 Key: GERONIMO-5211
 URL: https://issues.apache.org/jira/browse/GERONIMO-5211
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 3.0
Reporter: Kevan Miller
 Fix For: 3.0


Starting the geronimo server on trunk is currently very verbose. There are a 
lot of BlueprintContainer messages as Karaf is starting. That's followed by the 
Karaf banner. Finally, followed by the Geronimo startup which in my latest 
build includes a number of DigesterFactory log entries. 

Would be good to start cleaning these up.

Note I intend to raise a Jira about use of Karaf and Geronimo commands, in 
general...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Connector/openejb progress/heads up

2010-03-29 Thread David Jencks

I have most of the new j2ca connector functionality working ok, and finding out 
whether the rest of it works requires mdbs.  So I'm going to work on getting 
openejb running in trunk.

Currently there's a bit of a fight between an osgi extender that registers 
openejb services set up openejb-style and the same functionality set up through 
gbeans.  Right now I'm dealing with this by disabling the gbean.  I can see 3 
choices here...


1. disable all the openejb configuration functionality and just use gbeans.  
This is fairly awkward but what we've been doing so far.  I think it tends to 
obscure some openejb configuration possibilities, but maybe not too seriously.

2. configure openejb using blueprint or xbean-blueprint.  Or write a new 
blueprint namespace handler that deals with the openejb multilevel property 
files.

3. hook up openejb's native configuration system to osgi config admin.

Any thoughts?

thanks
david jencks

[jira] Created: (GERONIMO-5210) Openejb under osgi in geronimo

Openejb under osgi in geronimo
--

 Key: GERONIMO-5210
 URL: https://issues.apache.org/jira/browse/GERONIMO-5210
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: application client, OpenEJB, osgi
Affects Versions: 3.0
Reporter: David Jencks
Assignee: David Jencks
 Fix For: 3.0


Get current openejb running under osgi in current geronimo trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-5073) EJB 3.1 Enhancements


 [ 
https://issues.apache.org/jira/browse/GERONIMO-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Jencks updated GERONIMO-5073:
---

Component/s: OpenEJB

> EJB 3.1 Enhancements
> 
>
> Key: GERONIMO-5073
> URL: https://issues.apache.org/jira/browse/GERONIMO-5073
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: javaee6, OpenEJB
>Affects Versions: 3.0
>Reporter: Rick McGuire
> Fix For: 3.0
>
>
> Upgrade to the EJB 3.1 specification level (JSR 3.1.) 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-5074) EJB 3.1 Lite enhancements


 [ 
https://issues.apache.org/jira/browse/GERONIMO-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Jencks updated GERONIMO-5074:
---

Component/s: OpenEJB

> EJB 3.1 Lite enhancements
> -
>
> Key: GERONIMO-5074
> URL: https://issues.apache.org/jira/browse/GERONIMO-5074
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: javaee6, OpenEJB, Web Profile
>Affects Versions: 3.0
>Reporter: Rick McGuire
> Fix For: 3.0
>
>
> Add a plugin version for the EJB 3.1 Lite specification level that can be 
> used for the web profile assembly. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-5065) EJBs in WAR files enhancement


 [ 
https://issues.apache.org/jira/browse/GERONIMO-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Jencks updated GERONIMO-5065:
---

Component/s: web
 Tomcat
 OpenEJB
 Jetty

> EJBs in WAR files enhancement
> -
>
> Key: GERONIMO-5065
> URL: https://issues.apache.org/jira/browse/GERONIMO-5065
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: javaee6, Jetty, OpenEJB, Tomcat, web
>Affects Versions: 3.0
>Reporter: Rick McGuire
> Fix For: 3.0
>
>
> JSR 316 includes new support to allow EJBs to be package inside of WAR files. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Release tomcat-parent-6.0.26

2010-03-29 Thread Kevan Miller

+1

I checked source, signature/checksums, and build. All looked good.

--kevan

On Mar 24, 2010, at 10:44 PM, Delos wrote:

> 
> This voting is for  tomcat-parent-6.0.26. It will be used by Geronimo 
> 2.1.5.It's based on tomcat 6.0.26, built with maven. Besides, we also applied 
> some patches which haven't been included in tomcat 6.0.26.
> 
> 
> Based on tomcat 6.0.26 tag, we applied additional patches for
> 
> 
> GERONIMO-3451 -  'Restricted listeners property file not found' error logged 
> during Tomcat server startup (Patch from Shawn Jiang)
>   
> GERONIMO-4685 - patch for revision 790742
> 
> Staging repo:
> 
> https://repository.apache.org/content/repositories/orgapachegeronimo-015/
> 
> 
> svn tag at:
> 
> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.26.0/
> 
> 
> [ ] +1 go for it
> [ ] 0
> [ ] -1 whoa, hold on a minute
> 
> 
> thanks a lot!
> 
> -- 
> Best Regards,
> 
> Delos

[BUILD] trunk: Failed for Revision: 928762

Geronimo Revision: 928762 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100329/build-0900.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100329/unit-test-reports
 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) 
org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT
2) 
org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT
3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots),
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  java.net.2 (http://download.java.net/maven/1/),
  jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/),
  openqa-releases (http://nexus.openqa.org/content/repositories/releases),
  smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) 
org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT
2) 
org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT
3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots

[jira] Commented: (GERONIMO-5209) Geronimo support for tranql XA JDBC adapter for DB2 on ISeries

2010-03-29 Thread Ashish Jain (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850863#action_12850863
 ] 

Ashish Jain commented on GERONIMO-5209:
---

Tranql JIRA link http://jira.codehaus.org/browse/TQL-22.

> Geronimo support for tranql XA JDBC adapter for DB2 on ISeries
> --
>
> Key: GERONIMO-5209
> URL: https://issues.apache.org/jira/browse/GERONIMO-5209
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: connector
> Environment: geronimo tomcat assembly
>Reporter: Ashish Jain
>Assignee: Ashish Jain
> Fix For: 2.2.1, 3.0
>
>
> Geronimo should provide a way to connect to DB2 on ISeries using the JTOpen 
> drivers. For more information on JTOpen refer http://jt400.sourceforge.net/. 
> Currently the generic traql jdbc adapter can be utilized but only for non XA 
> transaction support.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-5209) Geronimo support for tranql XA JDBC adapter for DB2 on ISeries

2010-03-29 Thread Ashish Jain (JIRA)

Geronimo support for tranql XA JDBC adapter for DB2 on ISeries
--

 Key: GERONIMO-5209
 URL: https://issues.apache.org/jira/browse/GERONIMO-5209
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public (Regular issues)
  Components: connector
 Environment: geronimo tomcat assembly
Reporter: Ashish Jain
Assignee: Ashish Jain
 Fix For: 2.2.1, 3.0


Geronimo should provide a way to connect to DB2 on ISeries using the JTOpen 
drivers. For more information on JTOpen refer http://jt400.sourceforge.net/. 
Currently the generic traql jdbc adapter can be utilized but only for non XA 
transaction support.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMODEVTOOLS-607) Missing JSTL jar in server runtime

2010-03-29 Thread Delos Dai (JIRA)

Missing JSTL jar in server runtime 
---

 Key: GERONIMODEVTOOLS-607
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-607
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.2.0
Reporter: Delos Dai
Assignee: Delos Dai


JSTL jar is missing in GEP 2.2 server runtime



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Delay Geronimo 2.1.5 RC to Mar. 30

2010-03-29 Thread Rex Wang

Dear all,

We almost closed all the JIRAs that MUST be fixed for 2.1.5, except the two
opened for upgrade Tomcat and OpenEJB. Hope the votes can be passed tomorrow
so that we can make a RC on time.

I also create a wiki page to record what changes I have made for 2.1.5
build, please refer:
http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+2.1.5+Release+Tips
Hope this can help the guy who became the following version's release
manager know more about the new process.

-Rex

2010/3/26 Rex Wang 

>
> We are still waiting the TCK results of external Tomcat 6.0.26.0 and also
> OpenEJB voting result, so delay the release candidate build.
>
> --
> Lei Wang (Rex)
> rwonly AT apache.org
>



-- 
Lei Wang (Rex)
rwonly AT apache.org

Re: [VOTE] Release tomcat-parent-6.0.26

2010-03-29 Thread Rex Wang

Thanks!

Here is my +1

2010/3/29 Ivan 

> Just get the TCK result for Tomcat 6.0.26.0, all cases passed.
> +1
>
>
> 2010/3/25 Delos 
>
>> TCK for tomcat-parent-6.0.26 is ongoing.
>>
>> Ivan, could you give the result here once TCK is completed? Thanks in
>> advance!
>>
>>
>> 2010/3/25 Delos 
>>
>>
>>> This voting is for  tomcat-parent-6.0.26. It will be used by Geronimo
>>> 2.1.5.It's based on tomcat 6.0.26, built with maven. Besides, we also
>>> applied some patches which haven't been included in tomcat 6.0.26.
>>>
>>>
>>> Based on tomcat 6.0.26 tag, we applied additional patches for
>>>
>>>
>>> GERONIMO-3451 -  'Restricted listeners property file not found' error
>>> logged during Tomcat server startup (Patch from Shawn Jiang)
>>>
>>> GERONIMO-4685 - patch for revision 790742
>>>
>>> Staging repo:
>>>
>>> 
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-015/
>>>
>>>
>>> svn tag at:
>>>
>>> 
>>>
>>> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.26.0
>>> /
>>>
>>>
>>> [ ] +1 go for it
>>> [ ] 0
>>> [ ] -1 whoa, hold on a minute
>>>
>>>
>>> thanks a lot!
>>>
>>> --
>>> Best Regards,
>>>
>>> Delos
>>>
>>
>>
>>
>> --
>> Best Regards,
>>
>> Delos
>>
>
>
>
> --
> Ivan
>



-- 
Lei Wang (Rex)
rwonly AT apache.org

Re: [VOTE] Release tomcat-parent-6.0.26

2010-03-29 Thread Ivan

Just get the TCK result for Tomcat 6.0.26.0, all cases passed.
+1

2010/3/25 Delos 

> TCK for tomcat-parent-6.0.26 is ongoing.
>
> Ivan, could you give the result here once TCK is completed? Thanks in
> advance!
>
>
> 2010/3/25 Delos 
>
>
>> This voting is for  tomcat-parent-6.0.26. It will be used by Geronimo
>> 2.1.5.It's based on tomcat 6.0.26, built with maven. Besides, we also
>> applied some patches which haven't been included in tomcat 6.0.26.
>>
>>
>> Based on tomcat 6.0.26 tag, we applied additional patches for
>>
>>
>> GERONIMO-3451 -  'Restricted listeners property file not found' error
>> logged during Tomcat server startup (Patch from Shawn Jiang)
>>
>> GERONIMO-4685 - patch for revision 790742
>>
>> Staging repo:
>>
>> 
>> https://repository.apache.org/content/repositories/orgapachegeronimo-015/
>>
>>
>> svn tag at:
>>
>> 
>>
>> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.26.0
>> /
>>
>>
>> [ ] +1 go for it
>> [ ] 0
>> [ ] -1 whoa, hold on a minute
>>
>>
>> thanks a lot!
>>
>> --
>> Best Regards,
>>
>> Delos
>>
>
>
>
> --
> Best Regards,
>
> Delos
>



-- 
Ivan

[jira] Updated: (GERONIMO-5208) console is broken after upgrading dojo to 1.4.2

2010-03-29 Thread Rahul Mehta (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rahul Mehta updated GERONIMO-5208:
--

Attachment: printscreen.png

I also encountered broken console problem on trunk yesterday, attached the 
print screen.

//on the terminal, i see the following traces

[ra...@localhost bin]$ ./geronimo run
Unable to update instance pid: System property 'storage.location' is not set.
This property needs to be set to the full path of the instance.properties file.
2010-03-27 22:34:59,874 WARN  [BlueprintContainerImpl] Bundle 
org.apache.felix.karaf.shell.log is waiting for namespace handlers 
[(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0)),
 
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://felix.apache.org/karaf/xmlns/shell/v1.0.0))]
2010-03-27 22:34:59,981 WARN  [BlueprintContainerImpl] Bundle 
org.apache.felix.karaf.shell.obr is waiting for namespace handlers 
[(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://felix.apache.org/karaf/xmlns/shell/v1.0.0))]
2010-03-27 22:35:00,029 WARN  [BlueprintContainerImpl] Bundle 
org.apache.felix.karaf.jaas.modules is waiting for namespace handlers 
[(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0)),
 
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://felix.apache.org/karaf/xmlns/jaas/v1.0.0))]
2010-03-27 22:35:00,081 WARN  [BlueprintContainerImpl] Bundle 
org.apache.felix.karaf.shell.packages is waiting for namespace handlers 
[(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://felix.apache.org/karaf/xmlns/shell/v1.0.0))]
2010-03-27 22:35:00,090 WARN  [BlueprintContainerImpl] Bundle 
org.apache.felix.karaf.shell.osgi is waiting for namespace handlers 
[(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://felix.apache.org/karaf/xmlns/shell/v1.0.0))]
2010-03-27 22:35:00,099 WARN  [BlueprintContainerImpl] Bundle 
org.apache.felix.karaf.shell.commands is waiting for namespace handlers 
[(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://felix.apache.org/karaf/xmlns/shell/v1.0.0))]
2010-03-27 22:35:00,163 WARN  [BlueprintContainerImpl] Bundle 
org.apache.felix.karaf.shell.config is waiting for namespace handlers 
[(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://felix.apache.org/karaf/xmlns/shell/v1.0.0)),
 
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0)),
 
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0))]
2010-03-27 22:35:00,174 WARN  [jmx] There are no MBean servers registred, can't 
register MBeans
2010-03-27 22:35:00,202 WARN  [BlueprintContainerImpl] Bundle 
org.apache.felix.karaf.admin.core is waiting for namespace handlers 
[(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0))]
__ __   
   / //_/ __ _/ __/ 
  / ,<  / __ `/ ___/ __ `/ /_   
 / /| |/ /_/ / /  / /_/ / __/   
/_/ |_|\__,_/_/   \__,_/_/

  Apache Felix Karaf (1.5.0-SNAPSHOT)

Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or 'osgi:shutdown' to shutdown Karaf.

ka...@root> geronimo:start-server
Booting Geronimo Kernel (in Java 1.6.0_12)...
Starting Geronimo Application Server v3.0-SNAPSHOT
Booting Geronimo Kernel (in Java 1.6.0_12)...
Starting Geronimo Application Server v3.0-SNAPSHOT
[**  ]  36%  20s  Loading 
org.apache.ger...2010-03-27 22:35:49,084 WARN  [aries] Managed persistence 
context support is no longer available for use with the Aries Blueprint 
container
[]  42%  24s  Loading 
org.apache.ger...2010-03-27 22:35:53,431 WARN  [StringManager] Can't find 
resource org.apache.pluto.driver.container.LocalStrings 
sun.misc.launcher$appclassloa...@1ba34f2
[**  ]  47%  44s  Loading 
org.apache.ger...2010-03-27 22:36:12,506 WARN  [XBeanNamespaceHandler] Could 
not load class: org.apache.activemq.network.jms.JmsTopicConnector due to 
org/springframework/jndi/JndiTemplate
2010-03-27 22:36:12,657 WARN  [XBeanNamespaceHandler] Could not load class: 
org.apache.activemq.spring.SpringSslContext due to 
org/sp

Re: problems with admin console in trunk

2010-03-29 Thread Shawn Jiang

Opened a JIRA https://issues.apache.org/jira/browse/GERONIMO-5208 for this
and fixed it in trunk @rev: 928630

On Mon, Mar 29, 2010 at 1:27 PM, Shawn Jiang  wrote:

> I agree that this might be caused by recent dojo upgrade, I'll take a look
> at this.
>
>
> On Mon, Mar 29, 2010 at 12:24 PM, Jarek Gawor  wrote:
>
>> Hi,
>>
>> Is anybody seeing problems with the admin console in trunk? The
>> navigation tree seems to be screwed up and I can't select anything on
>> it. Maybe this is caused by recent dojo upgrade?
>>
>> Jarek
>>
>
>
>
> --
> Shawn
>



-- 
Shawn

[jira] Resolved: (GERONIMO-5208) console is broken after upgrading dojo to 1.4.2


 [ 
https://issues.apache.org/jira/browse/GERONIMO-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shawn Jiang resolved GERONIMO-5208.
---

Resolution: Fixed

Verified in 22 branch.  But the fix should apply to trunk as well.  

> console is broken after upgrading dojo to 1.4.2
> ---
>
> Key: GERONIMO-5208
> URL: https://issues.apache.org/jira/browse/GERONIMO-5208
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2.1, 3.0
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>
> console is broken after upgrading dojo to 1.4.2.   Some dojo syntax is not 
> compatible with previous version.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-5208) console is broken after upgrading dojo to 1.4.2

console is broken after upgrading dojo to 1.4.2
---

 Key: GERONIMO-5208
 URL: https://issues.apache.org/jira/browse/GERONIMO-5208
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.2.1, 3.0
Reporter: Shawn Jiang
Assignee: Shawn Jiang


console is broken after upgrading dojo to 1.4.2.   Some dojo syntax is not 
compatible with previous version.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[BUILD] trunk: Failed for Revision: 928615