date:20090113

Spring AOP AspectJ conflict when using Apache CXF
-

 Key: GERONIMO-4508
 URL: https://issues.apache.org/jira/browse/GERONIMO-4508
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
 Environment: Spring 2.5.6, Geronimo JEE Tomcat 2.1.3, AspectJ 1.6.2

Reporter: Bruno César Brito Sant'Anna


I'm trying to create a WebService Bean on Geronimo using Spring IoC container.

Well, I followed this tutorial 
http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html

My GERONIMO_OPTS var value is -Dorg.apache.geronimo.jaxws.provider=cxf 
-Dorg.apache.geronimo.saaj.provider=axis2  
-Dorg.apache.cxf.jaxws.checkPublishEndpointPermission=false

When server starts, when reading Spring AOC Config my server crashes...

Summary stack trace: 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'org.springframework.aop.support.DefaultBeanFactoryPointcutAdvisor': 
Instantiation of bean failed; nested exception is 
java.lang.AbstractMethodError: 
org.springframework.aop.aspectj.autoproxy.AspectJAwareAdvisorAutoProxyCreator.determineConstructor(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/reflect/Constructor;

It took me several hours to discover that cxf environment was messing around 
with Spring... 
reseting GERONIMO_OPTS and removing cxf webservice stuff from my 
applicationContext.xml made my server run again.

Looks like I cannot use CXF with AOP...

I'll attach full stack trace...

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

[jira] Updated: (GERONIMO-4508) Spring AOP AspectJ conflict when using Apache CXF


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

Bruno César Brito Sant'Anna updated GERONIMO-4508:
--

Attachment: trace.txt

full stack trace

 Spring AOP AspectJ conflict when using Apache CXF
 -

 Key: GERONIMO-4508
 URL: https://issues.apache.org/jira/browse/GERONIMO-4508
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
 Environment: Spring 2.5.6, Geronimo JEE Tomcat 2.1.3, AspectJ 1.6.2
Reporter: Bruno César Brito Sant'Anna
 Attachments: trace.txt


 I'm trying to create a WebService Bean on Geronimo using Spring IoC container.
 Well, I followed this tutorial 
 http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
 My GERONIMO_OPTS var value is -Dorg.apache.geronimo.jaxws.provider=cxf 
 -Dorg.apache.geronimo.saaj.provider=axis2  
 -Dorg.apache.cxf.jaxws.checkPublishEndpointPermission=false
 When server starts, when reading Spring AOC Config my server crashes...
 Summary stack trace: 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 
 'org.springframework.aop.support.DefaultBeanFactoryPointcutAdvisor': 
 Instantiation of bean failed; nested exception is 
 java.lang.AbstractMethodError: 
 org.springframework.aop.aspectj.autoproxy.AspectJAwareAdvisorAutoProxyCreator.determineConstructor(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/reflect/Constructor;
 It took me several hours to discover that cxf environment was messing around 
 with Spring... 
 reseting GERONIMO_OPTS and removing cxf webservice stuff from my 
 applicationContext.xml made my server run again.
 Looks like I cannot use CXF with AOP...
 I'll attach full stack trace...

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

[jira] Updated: (GERONIMO-4508) Spring AOP AspectJ conflict when using Apache CXF


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

Bruno César Brito Sant'Anna updated GERONIMO-4508:
--

Attachment: jetty_trace.txt

Attached Jetty trace.

I've tried to run on Geronimo Jee jetty server environment and a similar 
behavior occurs.

I'm almost sure that CXF JAX-WS engine conflicts with Spring 2.5.6

 Spring AOP AspectJ conflict when using Apache CXF
 -

 Key: GERONIMO-4508
 URL: https://issues.apache.org/jira/browse/GERONIMO-4508
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
 Environment: Spring 2.5.6, Geronimo JEE Tomcat 2.1.3, AspectJ 1.6.2
Reporter: Bruno César Brito Sant'Anna
 Attachments: jetty_trace.txt, trace.txt


 I'm trying to create a WebService Bean on Geronimo using Spring IoC container.
 Well, I followed this tutorial 
 http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
 My GERONIMO_OPTS var value is -Dorg.apache.geronimo.jaxws.provider=cxf 
 -Dorg.apache.geronimo.saaj.provider=axis2  
 -Dorg.apache.cxf.jaxws.checkPublishEndpointPermission=false
 When server starts, when reading Spring AOC Config my server crashes...
 Summary stack trace: 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 
 'org.springframework.aop.support.DefaultBeanFactoryPointcutAdvisor': 
 Instantiation of bean failed; nested exception is 
 java.lang.AbstractMethodError: 
 org.springframework.aop.aspectj.autoproxy.AspectJAwareAdvisorAutoProxyCreator.determineConstructor(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/reflect/Constructor;
 It took me several hours to discover that cxf environment was messing around 
 with Spring... 
 reseting GERONIMO_OPTS and removing cxf webservice stuff from my 
 applicationContext.xml made my server run again.
 Looks like I cannot use CXF with AOP...
 I'll attach full stack trace...

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

[Discussion] Add a geronimo status command

2009-01-13 Thread Jack Cai

I've seen users asking how to query server status [1], and recently I was
also asked for the same question by a colleague. So I think maybe it's good
that Geronimo provide a cross-platform means for querying server status.
After looking into the code that does server shutdown, I realize it's pretty
easy to achieve that. All I need to do is to -

1. Refactor the org.apache.geronimo.deployment.cli.StopServer class to
something more general, e.g., ServerControl. We can make it to do status
query or shutdown based on an extra parameter that's passed in, or make it a
super class and create another 2 subclasses to do status query and shutdown
respectively.

2. Add a new command to the geronimo.(sh/bat) script, e.g., status. And
based on how Step 1 is done, we can either reuse the shutdown.jar (probably
rename it to control.jar); or create a new status.jar just to do status
query, and leave the shutdown.jar to do the shutdown.

3. The code that does the real status query work will be as simply as
serverControl.getRunningKernel().isRunning().

I prefer to reuse the shutdown.jar. If you see no problem with my current
thinking, I'll go ahead to create a JIRA with a patch.

-Jack

[1]
http://www.nabble.com/status-from-shell-script-(System-V-starup)-td20472233s134.html

Re: svn commit: r733836 - /geronimo/server/trunk/pom.xml



On Jan 12, 2009, at 9:08 PM, Lin Sun wrote:


Donald, I performed a complete build (mvn clean install) last Friday
with this change.  There were only a few web services test failure but
my test server appeared to hang.  So I reran these failed web services
tests individually and they all passed.

snip
On Mon, Jan 12, 2009 at 5:25 PM, Donald Woods dwo...@apache.org  
wrote:

Lin, I'm now seeing some testsuite failures in -
enterprise-testsuite/jms-tests
enterprise-testsuite/jpa-tests
enterprise-testsuite/sec-tests
after updating to the latest trunk code  Did you perform a  
complete
build+testsuite (with a clean repo) with the latest txmanager  
code?  Or is

this related to an updated OpenEJB 3.1.1 SNAPSHOT?


With up-to-date txmanager/connector these tests pass for me. I do see  
4 webservices failures. Should these tests be passing on Mac OS?


--kevan

Re: svn commit: r733836 - /geronimo/server/trunk/pom.xml

2009-01-13 Thread Donald Woods

Looks like the new SNAPSHOTs fixed the automated builds that also failed 
yesterday.  Thanks.



-Donald


Kevan Miller wrote:


On Jan 12, 2009, at 9:08 PM, Lin Sun wrote:


Donald, I performed a complete build (mvn clean install) last Friday
with this change.  There were only a few web services test failure but
my test server appeared to hang.  So I reran these failed web services
tests individually and they all passed.

snip
On Mon, Jan 12, 2009 at 5:25 PM, Donald Woods dwo...@apache.org 
mailto:dwo...@apache.org wrote:

Lin, I'm now seeing some testsuite failures in -
enterprise-testsuite/jms-tests
enterprise-testsuite/jpa-tests
enterprise-testsuite/sec-tests
after updating to the latest trunk code  Did you perform a complete
build+testsuite (with a clean repo) with the latest txmanager code? 
 Or is

this related to an updated OpenEJB 3.1.1 SNAPSHOT?


With up-to-date txmanager/connector these tests pass for me. I do see 4 
webservices failures. Should these tests be passing on Mac OS?


--kevan

[jira] Closed: (GERONIMO-1367) Shutdown JAR should use deployer stored username/password


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

Donald Woods closed GERONIMO-1367.
--


 Shutdown JAR should use deployer stored username/password
 -

 Key: GERONIMO-1367
 URL: https://issues.apache.org/jira/browse/GERONIMO-1367
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: startup/shutdown, usability
Affects Versions: 1.0
Reporter: Aaron Mulder
Assignee: Jarek Gawor
Priority: Minor
 Fix For: 2.1.4, 2.2

 Attachments: GERONIMO-1367.patch


 It would be nice if the shutdown script used the username and password saved 
 by the deployer so you didn't need to specify them or re-enter them.

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

Re: [Discussion] Add a geronimo status command

2009-01-13 Thread Donald Woods

How do you propose to handle status while the server is starting or 
stopping?  How many states would be returned?  Would this also be 
exposed over JMX?


How would it really differ from the deployer list-modules command we 
already have?  Maybe that command needs to return better 
rc/status/message when the server is still starting/stopping or not started?



-Donald


Jack Cai wrote:
I've seen users asking how to query server status [1], and recently I 
was also asked for the same question by a colleague. So I think maybe 
it's good that Geronimo provide a cross-platform means for querying 
server status. After looking into the code that does server shutdown, I 
realize it's pretty easy to achieve that. All I need to do is to -


1. Refactor the org.apache.geronimo.deployment.cli.StopServer class to 
something more general, e.g., ServerControl. We can make it to do status 
query or shutdown based on an extra parameter that's passed in, or make 
it a super class and create another 2 subclasses to do status query and 
shutdown respectively.


2. Add a new command to the geronimo.(sh/bat) script, e.g., status. 
And based on how Step 1 is done, we can either reuse the shutdown.jar 
(probably rename it to control.jar); or create a new status.jar just to 
do status query, and leave the shutdown.jar to do the shutdown.


3. The code that does the real status query work will be as simply as 
serverControl.getRunningKernel().isRunning().


I prefer to reuse the shutdown.jar. If you see no problem with my 
current thinking, I'll go ahead to create a JIRA with a patch.


-Jack

[1] 
http://www.nabble.com/status-from-shell-script-(System-V-starup)-td20472233s134.html

[jira] Commented: (GERONIMO-4508) Spring AOP AspectJ conflict when using Apache CXF

2009-01-13 Thread Kevan Miller (JIRA)

[
https://issues.apache.org/jira/browse/GERONIMO-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663337#action_12663337
]

Kevan Miller commented on GERONIMO-4508:

Geronimo uses Spring 2.0.5, internally. Can you use that Spring version,
instead? Another option is to use Axis2, which should not have this Spring
issue.

IIUC, for some webservices functions, CXF will perform some client
configuration within the application's classloader - so CXF needs the internal
Spring version exposed to the applications classloader. Jarek or Dan might be
able to comment on the specifics... I don't recall what these specific features
are.

You can filter Spring and allow your application-provided version of Spring to
override. Something like the following should work (with some loss of
functionality):

?xml version=1.0 encoding=UTF-8?
web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-1.1;
xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.1;
xmlns:naming=http://geronimo.apache.org/xml/ns/naming-1.1;
dep:environment
dep:moduleId
dep:groupIdorg.mygroup/dep:groupId
dep:artifactIdMyApp/dep:artifactId
dep:version1.1/dep:version
dep:typecar/dep:type
/dep:moduleId
!--
Don't load spring classes or resources from parent ClassLoaders.
--
dep:hidden-classes
dep:filterorg.springframework./dep:filter
dep:filterMETA-INF/spring/dep:filter
/dep:hidden-classes
/dep:environment
/web-app

Spring AOP AspectJ conflict when using Apache CXF
-

Key: GERONIMO-4508
URL: https://issues.apache.org/jira/browse/GERONIMO-4508
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Environment: Spring 2.5.6, Geronimo JEE Tomcat 2.1.3, AspectJ 1.6.2
Reporter: Bruno César Brito Sant'Anna
Attachments: jetty_trace.txt, trace.txt

I'm trying to create a WebService Bean on Geronimo using Spring IoC container.
Well, I followed this tutorial
http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
My GERONIMO_OPTS var value is -Dorg.apache.geronimo.jaxws.provider=cxf
-Dorg.apache.geronimo.saaj.provider=axis2
-Dorg.apache.cxf.jaxws.checkPublishEndpointPermission=false
When server starts, when reading Spring AOC Config my server crashes...
Summary stack trace:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name
'org.springframework.aop.support.DefaultBeanFactoryPointcutAdvisor':
Instantiation of bean failed; nested exception is
java.lang.AbstractMethodError:
org.springframework.aop.aspectj.autoproxy.AspectJAwareAdvisorAutoProxyCreator.determineConstructor(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/reflect/Constructor;
It took me several hours to discover that cxf environment was messing around
with Spring...
reseting GERONIMO_OPTS and removing cxf webservice stuff from my
applicationContext.xml made my server run again.
Looks like I cannot use CXF with AOP...
I'll attach full stack trace...

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

Re: svn commit: r733836 - /geronimo/server/trunk/pom.xml

2009-01-13 Thread Lin Sun

Kevan, Thanks for resolving this.  I haven't thought of those
SNAPSHOTS were dated, as changes have been there for quite a few days.

Lin

On Tue, Jan 13, 2009 at 12:31 AM, Kevan Miller kevan.mil...@gmail.com wrote:

 On Jan 12, 2009, at 9:08 PM, Lin Sun wrote:

 Donald, I performed a complete build (mvn clean install) last Friday
 with this change.  There were only a few web services test failure but
 my test server appeared to hang.  So I reran these failed web services
 tests individually and they all passed.

 I think the geronimo-txmanager/geronimo-connector SNAPSHOTS were dated. I've
 deployed new SNAPS. Hoping that this fixes the problem...

 --kevan

[jira] Commented: (GERONIMODEVTOOLS-554) warning message about supported JDK version is wrong

2009-01-13 Thread Ted Kirby (JIRA)

[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663344#action_12663344
]

Ted Kirby commented on GERONIMODEVTOOLS-554:

I certainly believe the statement is accurate. The idea is it reflects the
level of java used to run the TCK and certify that Geronimo is JEE compliant.
I think 1.5.0+ covers the 1.6 case. But I agree that we may revisit this
message, and should as java levels change. I have resisted using the term
supported in this message, but perhaps that is a better term to use. We do
want to reflect server requirements. So, perhaps we change the message to
Apache Geronimo v2.2 requires a 5.0+ JDK (J2SE 1.5.0+)., and show the message
only on JDK levels less than that. Comments?

warning message about supported JDK version is wrong

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

Hi,
When I use JDK 6.0 with GEP 2.2, in the wizard New Server Runtime
Environment, a warning message is shown Apache Geronimo v2.2 is currently
certified only on a Sun JDK 5.0+ (J2SE 1.5.0+)..See attachment for more
details.
I think this message should only show when a JDK 1.4 is used. Otherwise, the
statement is not accurate.
Any comments?

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

[jira] Updated: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting


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

Gang Yin updated GERONIMO-4507:
---

Attachment: locale-priority_fix.patch

Hi, Donald,
   This patch can fix the problem discussed above. All *_en.properties files 
are removed, they are not necessary anymore. All requests with locale of en 
will load default  resource bundle.

 Admin console should honor the priority of user agent's language setting
 

 Key: GERONIMO-4507
 URL: https://issues.apache.org/jira/browse/GERONIMO-4507
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.3, 2.2
 Environment: All
Reporter: Jack Cai
Assignee: Gang Yin
Priority: Minor
 Fix For: 2.2

 Attachments: locale-priority.patch, locale-priority_fix.patch


 See discussion: 
 http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html

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

Re: G download stats

2009-01-13 Thread Bill Stoddard


Kevan Miller wrote:


On Jan 12, 2009, at 2:40 PM, Bill Stoddard wrote:

I'm sure most of you know about Vadim's Apache stats project for 
tracking download statistics for the verious Apache projects:


http://people.apache.org/~vgritsenko/stats/index.html 
http://people.apache.org/%7Evgritsenko/stats/index.html


A fun little project but exceedingly difficult (not to mention time 
consuming) for Vadim to dig into the details of each project in order 
to present project stats with finer details.


Just out of curiosity, I did some Ruby hacking to modify Vadim's 
apache log mining script to filter out Geronimo project data with 
finer resolution.  Here are the results:


http://people.apache.org/~stoddard/stats/data/ 
http://people.apache.org/%7Estoddard/stats/data/


BTW, if I understand what you are counting, then these statistics only 
represent some fraction of the actual downloads (i.e. the downloads 
from http://www.apache.org/dist/geronimo/ 
http://www.apache.org/dist/geronimo/2.1.3/geronimo-tomcat6-javaee5-2.1.3-bin.zip ) 
Downloads from the various Apache mirrors would not be counted... 
Wondering if hits to the mirroring system 
(e.g. http://www.apache.org/dyn/closer.cgi/geronimo/ ) would yield a 
more accurate statistic.


--kevan 
These stats include downloads redirected to the mirrors.   I do count 
the redirects for download artifacts by closer.cgi.   As expected, I 
have no way to determine if a redirect was successful... very possible 
some fractions of hits are duplicates (i.e., a mirror failed and the 
client came back for another mirror).


Bill

[jira] Commented: (GERONIMO-4484) Extraction, localization and display of messages generated in portlets


[ 
https://issues.apache.org/jira/browse/GERONIMO-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663350#action_12663350
 ] 

Donald Woods commented on GERONIMO-4484:


Applied common-message_fix.patch from Gang Yin to trunk (2.2-SNAPSHOT) as 
Rev734145.

 Extraction, localization and display of messages generated in portlets
 --

 Key: GERONIMO-4484
 URL: https://issues.apache.org/jira/browse/GERONIMO-4484
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2
Reporter: Gang Yin
Assignee: Donald Woods
 Fix For: 2.2

 Attachments: arrow_collapsed.gif, arrow_expanded.gif, 
 common-message-activemq.patch, common-message-base.patch, 
 common-message-core.patch, common-message-debugviews.patch, 
 common-message-monotor.patch, common-message-openejb.patch, 
 common-message-plancreator.patch, common-message-plugin.patch, 
 common-message-sysdb.patch, common-message_fix.patch, err_abbr.jpg, 
 err_detail.jpg, info.jpg, msg_error.gif, msg_info.gif, msg_warn.gif


 Currently in admin console, the messages generated from portlets are 
 hard-coded and thus cannot be localized, moreover, their manner of display in 
 the admin console differs from each other.
 I am trying to extract all the hard coded messages from the portlets to 
 resource bundle and work on a unified way to display these messages in admin 
 console. The styles of the messages are according to their types: error 
 messages, warning message or information messages ,etc.

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

[jira] Commented: (GERONIMODEVTOOLS-450) Modifications to JAXB classes for DWR in PlanCreator

2009-01-13 Thread B.J. Reed (JIRA)

[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663353#action_12663353
]

B.J. Reed commented on GERONIMODEVTOOLS-450:

I've looked at this patch and I have to put a -1 on it.

According to the comments in the code and from what I've seen, the getXXX
methods for Lists of Object are accessor method returns a reference to the
live list, not a snapshot. Therefore any modification you make to the returned
list will be present inside the JAXB object. This is why there is not a
CODEset/CODE method for the property.

This patch just adds set methods which aren't needed and could be potentially
dangerous since a set would replace any data that may already be present in a
List of objects.

I will leave the JIRA open for a while to allow for any discussion to challenge
the original thinking.

Modifications to JAXB classes for DWR in PlanCreator

Key: GERONIMODEVTOOLS-450
URL:
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-450
Project: Geronimo-Devtools
Issue Type: Improvement
Components: eclipse-plugin
Affects Versions: 2.1.2
Reporter: Shrey Banga
Assignee: Shiva Kumar H R
Fix For: 2.2.0

Attachments: GEP_JAXB_1.patch

I've attached a patch which makes some modifications to JAXB classes in GEP
in order to support their use with DWR in PlanCreator.

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

[jira] Assigned: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting


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

Donald Woods reassigned GERONIMO-4507:
--

Assignee: Donald Woods  (was: Gang Yin)

 Admin console should honor the priority of user agent's language setting
 

 Key: GERONIMO-4507
 URL: https://issues.apache.org/jira/browse/GERONIMO-4507
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.3, 2.2
 Environment: All
Reporter: Jack Cai
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.2

 Attachments: locale-priority.patch, locale-priority_fix.patch


 See discussion: 
 http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html

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

[jira] Commented: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting

2009-01-13 Thread Jack Cai (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663355#action_12663355
 ] 

Jack Cai commented on GERONIMO-4507:


I don't quite understand why only the language part of the locale is used ...

 Admin console should honor the priority of user agent's language setting
 

 Key: GERONIMO-4507
 URL: https://issues.apache.org/jira/browse/GERONIMO-4507
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.3, 2.2
 Environment: All
Reporter: Jack Cai
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.2

 Attachments: locale-priority.patch, locale-priority_fix.patch


 See discussion: 
 http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html

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

[jira] Updated: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting


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

Gang Yin updated GERONIMO-4507:
---

Attachment: (was: locale-priority_fix.patch)

 Admin console should honor the priority of user agent's language setting
 

 Key: GERONIMO-4507
 URL: https://issues.apache.org/jira/browse/GERONIMO-4507
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.3, 2.2
 Environment: All
Reporter: Jack Cai
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.2

 Attachments: locale-priority.patch


 See discussion: 
 http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html

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

[jira] Commented: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting


[ 
https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663357#action_12663357
 ] 

Gang Yin commented on GERONIMO-4507:


Updated patch on the basis of Rev734145

 Admin console should honor the priority of user agent's language setting
 

 Key: GERONIMO-4507
 URL: https://issues.apache.org/jira/browse/GERONIMO-4507
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.3, 2.2
 Environment: All
Reporter: Jack Cai
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.2

 Attachments: locale-priority.patch, locale-priority_fix.patch


 See discussion: 
 http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html

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

[jira] Updated: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting


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

Gang Yin updated GERONIMO-4507:
---

Attachment: locale-priority_fix.patch

 Admin console should honor the priority of user agent's language setting
 

 Key: GERONIMO-4507
 URL: https://issues.apache.org/jira/browse/GERONIMO-4507
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.3, 2.2
 Environment: All
Reporter: Jack Cai
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.2

 Attachments: locale-priority.patch, locale-priority_fix.patch


 See discussion: 
 http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html

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

Re: [jira] Commented: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting

2009-01-13 Thread Gang Yin

Of course we can use both language and country parts, but now we only
provide property files like *.zh.properties rather than *.zh-CN.properties,
I'm not sure if locale like zh-CN will match *.zh.properties. I will test
it, and If getLanguage() is not necessary I will remove it.

On Tue, Jan 13, 2009 at 11:15 PM, Jack Cai (JIRA) j...@apache.org wrote:


[
 https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663355#action_12663355]

 Jack Cai commented on GERONIMO-4507:
 

 I don't quite understand why only the language part of the locale is used
 ...

  Admin console should honor the priority of user agent's language setting
  
 
  Key: GERONIMO-4507
  URL: https://issues.apache.org/jira/browse/GERONIMO-4507
  Project: Geronimo
   Issue Type: Improvement
   Security Level: public(Regular issues)
   Components: console
 Affects Versions: 2.1.3, 2.2
  Environment: All
 Reporter: Jack Cai
 Assignee: Donald Woods
 Priority: Minor
  Fix For: 2.2
 
  Attachments: locale-priority.patch, locale-priority_fix.patch
 
 
  See discussion:
 http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html

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

Re: [Discussion] Add a geronimo status command

2009-01-13 Thread Jack Cai

In line below.

2009/1/13 Donald Woods dwo...@apache.org

 How do you propose to handle status while the server is starting or
 stopping?  How many states would be returned?  Would this also be exposed
 over JMX?


Currently the kernel only has two status: running or not running. Do we want
to add more status in it? But I assume it's not easy to get an accurate
starting/stopping status.



 How would it really differ from the deployer list-modules command we
 already have?  Maybe that command needs to return better rc/status/message
 when the server is still starting/stopping or not started?


The proposed command only deals with the kernel, and will provide meaningful
exit code to indicate the status so that other programs can call this script
to query server status. The list-modules command deals with the modules and
is mostly for human interaction.


-Jack





 -Donald



 Jack Cai wrote:

 I've seen users asking how to query server status [1], and recently I was
 also asked for the same question by a colleague. So I think maybe it's good
 that Geronimo provide a cross-platform means for querying server status.
 After looking into the code that does server shutdown, I realize it's pretty
 easy to achieve that. All I need to do is to -

 1. Refactor the org.apache.geronimo.deployment.cli.StopServer class to
 something more general, e.g., ServerControl. We can make it to do status
 query or shutdown based on an extra parameter that's passed in, or make it a
 super class and create another 2 subclasses to do status query and shutdown
 respectively.

 2. Add a new command to the geronimo.(sh/bat) script, e.g., status. And
 based on how Step 1 is done, we can either reuse the shutdown.jar (probably
 rename it to control.jar); or create a new status.jar just to do status
 query, and leave the shutdown.jar to do the shutdown.

 3. The code that does the real status query work will be as simply as
 serverControl.getRunningKernel().isRunning().

 I prefer to reuse the shutdown.jar. If you see no problem with my current
 thinking, I'll go ahead to create a JIRA with a patch.

 -Jack

 [1]
 http://www.nabble.com/status-from-shell-script-(System-V-starup)-td20472233s134.htmlhttp://www.nabble.com/status-from-shell-script-%28System-V-starup%29-td20472233s134.html

Re: [jira] Commented: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting

2009-01-13 Thread Jack Cai

It will. You can read the javadoc of ResourceBundle to see how it searches
the bundles for a given locale.

-Jack


2009/1/13 Gang Yin yg020...@gmail.com

 Of course we can use both language and country parts, but now we only
 provide property files like *.zh.properties rather than *.zh-CN.properties,
 I'm not sure if locale like zh-CN will match *.zh.properties. I will test
 it, and If getLanguage() is not necessary I will remove it.


 On Tue, Jan 13, 2009 at 11:15 PM, Jack Cai (JIRA) j...@apache.org wrote:


[
 https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663355#action_12663355]

 Jack Cai commented on GERONIMO-4507:
 

 I don't quite understand why only the language part of the locale is used
 ...

  Admin console should honor the priority of user agent's language setting
  
 
  Key: GERONIMO-4507
  URL:
 https://issues.apache.org/jira/browse/GERONIMO-4507
  Project: Geronimo
   Issue Type: Improvement
   Security Level: public(Regular issues)
   Components: console
 Affects Versions: 2.1.3, 2.2
  Environment: All
 Reporter: Jack Cai
 Assignee: Donald Woods
 Priority: Minor
  Fix For: 2.2
 
  Attachments: locale-priority.patch, locale-priority_fix.patch
 
 
  See discussion:
 http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html

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

Re: [jira] Commented: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting

2009-01-13 Thread Gang Yin

yes, it's redundant code, I will remove it.

On Tue, Jan 13, 2009 at 11:30 PM, Jack Cai greensi...@gmail.com wrote:

 It will. You can read the javadoc of ResourceBundle to see how it searches
 the bundles for a given locale.

 -Jack


 2009/1/13 Gang Yin yg020...@gmail.com

 Of course we can use both language and country parts, but now we only
 provide property files like *.zh.properties rather than *.zh-CN.properties,
 I'm not sure if locale like zh-CN will match *.zh.properties. I will test
 it, and If getLanguage() is not necessary I will remove it.


 On Tue, Jan 13, 2009 at 11:15 PM, Jack Cai (JIRA) j...@apache.orgwrote:


[
 https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663355#action_12663355]

 Jack Cai commented on GERONIMO-4507:
 

 I don't quite understand why only the language part of the locale is used
 ...

  Admin console should honor the priority of user agent's language
 setting
 
 
 
  Key: GERONIMO-4507
  URL:
 https://issues.apache.org/jira/browse/GERONIMO-4507
  Project: Geronimo
   Issue Type: Improvement
   Security Level: public(Regular issues)
   Components: console
 Affects Versions: 2.1.3, 2.2
  Environment: All
 Reporter: Jack Cai
 Assignee: Donald Woods
 Priority: Minor
  Fix For: 2.2
 
  Attachments: locale-priority.patch, locale-priority_fix.patch
 
 
  See discussion:
 http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html

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

[jira] Updated: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting


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

Gang Yin updated GERONIMO-4507:
---

Attachment: (was: locale-priority_fix.patch)

 Admin console should honor the priority of user agent's language setting
 

 Key: GERONIMO-4507
 URL: https://issues.apache.org/jira/browse/GERONIMO-4507
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.3, 2.2
 Environment: All
Reporter: Jack Cai
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.2

 Attachments: locale-priority.patch


 See discussion: 
 http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html

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

[jira] Updated: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting


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

Gang Yin updated GERONIMO-4507:
---

Attachment: locale-priority_fix.patch

Modified version according to Jack's comment.

 Admin console should honor the priority of user agent's language setting
 

 Key: GERONIMO-4507
 URL: https://issues.apache.org/jira/browse/GERONIMO-4507
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.3, 2.2
 Environment: All
Reporter: Jack Cai
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.2

 Attachments: locale-priority.patch, locale-priority_fix.patch


 See discussion: 
 http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html

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

[jira] Resolved: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting


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

Donald Woods resolved GERONIMO-4507.


Resolution: Fixed

Applied locale-priority_fix.patch from Gang Yin to trunk (2.2-SNAPSHOT) as 
Rev734161.

 Admin console should honor the priority of user agent's language setting
 

 Key: GERONIMO-4507
 URL: https://issues.apache.org/jira/browse/GERONIMO-4507
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.3, 2.2
 Environment: All
Reporter: Jack Cai
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.2

 Attachments: locale-priority.patch, locale-priority_fix.patch


 See discussion: 
 http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html

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

[jira] Commented: (GERONIMO-4508) Spring AOP AspectJ conflict when using Apache CXF

[
https://issues.apache.org/jira/browse/GERONIMO-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663374#action_12663374
]

Bruno César Brito Sant'Anna commented on GERONIMO-4508:
---

Using spring 2.0.5 EAR app could load properly...

Unfortunately I had some work since one of my web-app uses external
web-services and I have to use SOAPHandler, only spring 2.5.6 support
BindingProvider exposing
(http://static.springframework.org/spring/docs/2.5.x/changelog.txt)...

Well, I included just spring-web.jar spring-core.jar and spring-context.jar
from 2.5.6 release and added to EAR lib and included those libs in web-app
manifest... everything loads and works fine as soon as now...

Spring AOP AspectJ conflict when using Apache CXF
-

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

Re: G download stats

On Jan 13, 2009, at 9:50 AM, Bill Stoddard wrote:

Kevan Miller wrote:

On Jan 12, 2009, at 2:40 PM, Bill Stoddard wrote:

I'm sure most of you know about Vadim's Apache stats project for
tracking download statistics for the verious Apache projects:

http://people.apache.org/~vgritsenko/stats/index.html http://people.apache.org/%7Evgritsenko/stats/index.html

A fun little project but exceedingly difficult (not to mention
time consuming) for Vadim to dig into the details of each project
in order to present project stats with finer details.

Just out of curiosity, I did some Ruby hacking to modify Vadim's
apache log mining script to filter out Geronimo project data with
finer resolution. Here are the results:

http://people.apache.org/~stoddard/stats/data/ http://people.apache.org/%7Estoddard/stats/data/

BTW, if I understand what you are counting, then these statistics
only represent some fraction of the actual downloads (i.e. the
downloads from http://www.apache.org/dist/geronimo/ http://www.apache.org/dist/geronimo/2.1.3/geronimo-tomcat6-javaee5-2.1.3-bin.zip
) Downloads from the various Apache mirrors would not be
counted... Wondering if hits to the mirroring system (e.g. http://www.apache.org/dyn/closer.cgi/geronimo/
) would yield a more accurate statistic.

--kevan
These stats include downloads redirected to the mirrors. I do
count the redirects for download artifacts by closer.cgi. As
expected, I have no way to determine if a redirect was successful...
very possible some fractions of hits are duplicates (i.e., a mirror
failed and the client came back for another mirror).

Cool. Thanks for the info.

--kevan

[jira] Assigned: (GERONIMO-4501) Tomcat/Axis ignores jax-ws-catalog.xml while resolving wsdlLocation URLs

2009-01-13 Thread Jarek Gawor (JIRA)


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

Jarek Gawor reassigned GERONIMO-4501:
-

Assignee: Jarek Gawor

 Tomcat/Axis ignores jax-ws-catalog.xml while resolving wsdlLocation URLs
 

 Key: GERONIMO-4501
 URL: https://issues.apache.org/jira/browse/GERONIMO-4501
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
 Environment: Geronimo 2.2-SNAPSHOT, Tomcat/Axis
Reporter: Janko Heilgeist
Assignee: Jarek Gawor

 The problem description's context is identical to GERONIMO-4500 for the 
 Jetty/CXF assembly. This time the catalog is completely ignored while 
 resolving the wsdlLocation URL. The exception is:
 {noformat}
 2009-01-07 17:45:17,701 ERROR [GBeanInstanceState] Error while starting; 
 GBean is now in the FAILED state: 
 abstractName=default/geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar/1231346713744/car?EJBModule=default/geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar/1231346713744/car,J2EEApplication=null,StatelessSessionBean=HelloWorldServiceEJB,j2eeType=WSLink,name=HelloWorldServiceEJB
 java.io.FileNotFoundException: http://example.com/HelloWorld.wsdl
 at 
 sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
 at java.net.URL.openStream(URL.java:1007)
 at 
 org.apache.geronimo.axis2.AxisServiceGenerator.readWSDL(AxisServiceGenerator.java:302)
 at 
 org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java:141)
 at 
 org.apache.geronimo.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java:145)
 at 
 org.apache.geronimo.axis2.ejb.EJBWebServiceContainer.init(EJBWebServiceContainer.java:56)
 at 
 org.apache.geronimo.axis2.ejb.EJBWebServiceGBean.init(EJBWebServiceGBean.java:70)
 ...
 {noformat}
 The workaround that helped in the case of the Jetty/CXF assembly does not 
 work with Tomcat/Axis.

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

unsubscribe

2009-01-13 Thread Bilal Bhatti

svn update performance

2009-01-13 Thread Tim McConnell

Is anyone other than me experiencing extremely slow svn performance, especially 
when updating the Geronimo server trunk ?? Yesterday and today have been 
excruciatingly slow.


--
Thanks,
Tim McConnell

Re: svn update performance

2009-01-13 Thread Jason Warner

You're not alone

On Tue, Jan 13, 2009 at 3:39 PM, Tim McConnell tim.mcco...@gmail.comwrote:

 Is anyone other than me experiencing extremely slow svn performance,
 especially when updating the Geronimo server trunk ?? Yesterday and today
 have been excruciatingly slow.

 --
 Thanks,
 Tim McConnell




-- 
~Jason Warner

[jira] Commented: (GERONIMO-4508) Spring AOP AspectJ conflict when using Apache CXF

2009-01-13 Thread Gianny Damour (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663467#action_12663467
 ] 

Gianny Damour commented on GERONIMO-4508:
-

Hi Kevan,

This is a recurrent problem; now that we have a private class support whereby 
we can explicitly configure specific classes and resources as private for a 
given config, I believe we should use this mechanism to insulate CXF children 
configurations.

Thanks,
Gianny



 Spring AOP AspectJ conflict when using Apache CXF
 -

 Key: GERONIMO-4508
 URL: https://issues.apache.org/jira/browse/GERONIMO-4508
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
 Environment: Spring 2.5.6, Geronimo JEE Tomcat 2.1.3, AspectJ 1.6.2
Reporter: Bruno César Brito Sant'Anna
 Attachments: jetty_trace.txt, trace.txt


 I'm trying to create a WebService Bean on Geronimo using Spring IoC container.
 Well, I followed this tutorial 
 http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
 My GERONIMO_OPTS var value is -Dorg.apache.geronimo.jaxws.provider=cxf 
 -Dorg.apache.geronimo.saaj.provider=axis2  
 -Dorg.apache.cxf.jaxws.checkPublishEndpointPermission=false
 When server starts, when reading Spring AOC Config my server crashes...
 Summary stack trace: 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 
 'org.springframework.aop.support.DefaultBeanFactoryPointcutAdvisor': 
 Instantiation of bean failed; nested exception is 
 java.lang.AbstractMethodError: 
 org.springframework.aop.aspectj.autoproxy.AspectJAwareAdvisorAutoProxyCreator.determineConstructor(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/reflect/Constructor;
 It took me several hours to discover that cxf environment was messing around 
 with Spring... 
 reseting GERONIMO_OPTS and removing cxf webservice stuff from my 
 applicationContext.xml made my server run again.
 Looks like I cannot use CXF with AOP...
 I'll attach full stack trace...

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

Re: svn update performance

2009-01-13 Thread Trygve Hardersen

Same here, I've been unable to checkout the code to a new computer all day.

Trygve

On Tue, Jan 13, 2009 at 9:41 PM, Jason Warner jaw...@gmail.com wrote:

 You're not alone


 On Tue, Jan 13, 2009 at 3:39 PM, Tim McConnell tim.mcco...@gmail.comwrote:

 Is anyone other than me experiencing extremely slow svn performance,
 especially when updating the Geronimo server trunk ?? Yesterday and today
 have been excruciatingly slow.

 --
 Thanks,
 Tim McConnell




 --
 ~Jason Warner

Re: svn update performance



On Jan 13, 2009, at 3:39 PM, Tim McConnell wrote:

Is anyone other than me experiencing extremely slow svn performance,  
especially when updating the Geronimo server trunk ?? Yesterday and  
today have been excruciatingly slow.


Yep. It's been pretty bad. I checked with infra, earlier today. The  
svn server is overloaded. They killed an rsync job soaking up I/O.  
Seems a little better, now, but only slightly.


The EU svn server (http://svn.eu.apache.org/repos/asf/geronimo/server)  
is way better. I think you can use svn switch to move a working copy  
to the alternate svn server. Or, just checkout a new copy...


--kevan

[jira] Commented: (GERONIMO-4508) Spring AOP AspectJ conflict when using Apache CXF

2009-01-13 Thread Kevan Miller (JIRA)

[
https://issues.apache.org/jira/browse/GERONIMO-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663471#action_12663471
]

Kevan Miller commented on GERONIMO-4508:

I thought there was a requirement for Spring to be visible in the application
classloader. In general, I understand and agree with you. I could be mistaken,
but recall that we had some implicit filtering in place that would have already
prevented this problem. However, that filtering couldn't be used due to some
CXF requirements... I'd have to spend some time reviewing old emails to swap in
all the details...

Spring AOP AspectJ conflict when using Apache CXF
-

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

[jira] Commented: (GERONIMO-4508) Spring AOP AspectJ conflict when using Apache CXF

2009-01-13 Thread Kevan Miller (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663474#action_12663474
 ] 

Kevan Miller commented on GERONIMO-4508:


This is the old conversation that I remembered -- 
http://www.nabble.com/Re%3A-svn-commit%3A-r574694---in--geronimo-server-trunk%3A-configs-jetty6-deployer-src-main-plan--configs-jetty6-deployer-src-plan--configs-tomcat6-deployer-src-main-plan--configs-tomcat6-deployer-src-plan--modules-geronimo-cxf-src-main-java-org-apache-ger-td12681830.html

I guess the application classloader visibility that I was remembering was the 
behavior of the naming-builder...

 Spring AOP AspectJ conflict when using Apache CXF
 -

 Key: GERONIMO-4508
 URL: https://issues.apache.org/jira/browse/GERONIMO-4508
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
 Environment: Spring 2.5.6, Geronimo JEE Tomcat 2.1.3, AspectJ 1.6.2
Reporter: Bruno César Brito Sant'Anna
 Attachments: jetty_trace.txt, trace.txt


 I'm trying to create a WebService Bean on Geronimo using Spring IoC container.
 Well, I followed this tutorial 
 http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
 My GERONIMO_OPTS var value is -Dorg.apache.geronimo.jaxws.provider=cxf 
 -Dorg.apache.geronimo.saaj.provider=axis2  
 -Dorg.apache.cxf.jaxws.checkPublishEndpointPermission=false
 When server starts, when reading Spring AOC Config my server crashes...
 Summary stack trace: 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 
 'org.springframework.aop.support.DefaultBeanFactoryPointcutAdvisor': 
 Instantiation of bean failed; nested exception is 
 java.lang.AbstractMethodError: 
 org.springframework.aop.aspectj.autoproxy.AspectJAwareAdvisorAutoProxyCreator.determineConstructor(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/reflect/Constructor;
 It took me several hours to discover that cxf environment was messing around 
 with Spring... 
 reseting GERONIMO_OPTS and removing cxf webservice stuff from my 
 applicationContext.xml made my server run again.
 Looks like I cannot use CXF with AOP...
 I'll attach full stack trace...

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

[jira] Commented: (GERONIMODEVTOOLS-521) Sign features so the eclipse update manager recognizes them as signed

2009-01-13 Thread Ted Kirby (JIRA)

[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663479#action_12663479
]

Ted Kirby commented on GERONIMODEVTOOLS-521:

Thanks Delos. I am not sure what to make of the keystore and password. No
doubt something like this is required for signing. I'm not sure if and how we
want to go forward with this in terms of incorporating it with our build. It
does not appear to be an Apache requirement to sign the eclipse jars. I found
this eclipse link on Jar Signing:
http://wiki.eclipse.org/index.php/JAR_Signing. This discusses signing during
an automated build, including procedure for using an eclipse machine and
signature. ServiceMix seems to use maven-gpg-plugin, but I don't know if this
is for eclipse plugins, or if that matters. I can't tell if this is automated,
and, if so, where the passphrase is specified. It seems that Apache prefers
GPG for this sort of thing, altho for signing eclipse plugins, this may not be
required. Certainly if we put passwords in pom.xml files, this will not be
secure. On the other hand, we just wanted to sign jars, so this may not
matter. Still, a signature implies validation, and having the key in a
publicly available pom.xml file would seem to undermine that claim.

Delos, how does this patch work? Will it create a keystore if there is not
one? Will this work for clean and non-clean mvn builds? I appreciate your
efforts it getting this working. I have concerns and questions about keys and
signing. I also seek input from others.

Sign features so the eclipse update manager recognizes them as signed
-

Key: GERONIMODEVTOOLS-521
URL:
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521
Project: Geronimo-Devtools
Issue Type: Bug
Components: eclipse-plugin
Affects Versions: 2.0.0, 2.1.0, 2.1.1, 2.1.2, 2.1.3
Reporter: Ted Kirby
Assignee: Tim McConnell
Fix For: 2.2.0

Attachments: 521.patch, 521_updated.patch

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

Re: unsubscribe



As described here -- http://geronimo.apache.org/mailing-lists.html  
send a note to dev-unsubscr...@geronimo.apache.org


--kevan

[BUILD] trunk: Failed for Revision: 734228

2009-01-13 Thread gawor

Geronimo Revision: 734228 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090113/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090113/unit-test-reports
 
/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/pojo/POJOWebServiceContainer.java:[37,39]
 cannot find symbol
symbol  : class HTTPTransportUtils
location: package org.apache.axis2.transport.http

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/pojo/POJOWebServiceContainer.java:[38,44]
 cannot find symbol
symbol  : class RESTUtil
location: package org.apache.axis2.transport.http.util

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[67,39]
 cannot find symbol
symbol  : class HTTPTransportReceiver
location: package org.apache.axis2.transport.http

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[68,39]
 cannot find symbol
symbol  : class HTTPTransportUtils
location: package org.apache.axis2.transport.http

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[69,39]
 cannot find symbol
symbol  : class TransportHeaders
location: package org.apache.axis2.transport.http

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[70,44]
 cannot find symbol
symbol  : class RESTUtil
location: package org.apache.axis2.transport.http.util

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[411,39]
 cannot find symbol
symbol  : class TransportHeaders
location: class org.apache.geronimo.axis2.Axis2WebServiceContainer

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[436,13]
 cannot find symbol
symbol  : variable HTTPTransportUtils
location: class org.apache.geronimo.axis2.Axis2WebServiceContainer

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[437,12]
 cannot find symbol
symbol  : variable HTTPTransportUtils
location: class org.apache.geronimo.axis2.Axis2WebServiceContainer

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[444,12]
 cannot find symbol
symbol  : variable RESTUtil
location: class org.apache.geronimo.axis2.Axis2WebServiceContainer

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[462,39]
 cannot find symbol
symbol  : variable RESTUtil
location: class org.apache.geronimo.axis2.Axis2WebServiceContainer

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[468,23]
 cannot find symbol
symbol  : variable HTTPTransportReceiver
location: class org.apache.geronimo.axis2.Axis2WebServiceContainer

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/pojo/POJOWebServiceContainer.java:[134,17]
 cannot find symbol
symbol  : variable HTTPTransportUtils
location: class org.apache.geronimo.axis2.pojo.POJOWebServiceContainer

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/pojo/POJOWebServiceContainer.java:[135,16]
 cannot find symbol
symbol  : variable HTTPTransportUtils
location: class org.apache.geronimo.axis2.pojo.POJOWebServiceContainer

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/pojo/POJOWebServiceContainer.java:[142,16]
 cannot find symbol
symbol  : variable RESTUtil
location: class org.apache.geronimo.axis2.pojo.POJOWebServiceContainer

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/pojo/POJOWebServiceContainer.java:[171,24]
 cannot find symbol
symbol  : variable RESTUtil
location: class org.apache.geronimo.axis2.pojo.POJOWebServiceContainer

/home/geronimo/geronimo/trunk/plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/pojo/POJOWebServiceContainer.java:[182,23]
 cannot find symbol
symbol  : variable HTTPTransportReceiver
location: class org.apache.geronimo.axis2.pojo.POJOWebServiceContainer


[INFO] 
[INFO] Trace
org.apache.maven.BuildFailureException: Compilation failure
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579

Re: [Discussion] Add a geronimo status command

2009-01-13 Thread Ivan

No sure whether we have a special command to query the deployed
applications' status ( I know that we could get those status via JMX). If
not,  I guess that we could extend the Jack's ideas to query all the
modules' status. We could provide more information about the module more
than the list module command, such as context path for web
applications etcThanks
for any comment !

2009/1/13 Jack Cai greensi...@gmail.com

 In line below.

 2009/1/13 Donald Woods dwo...@apache.org

 How do you propose to handle status while the server is starting or
 stopping?  How many states would be returned?  Would this also be exposed
 over JMX?


 Currently the kernel only has two status: running or not running. Do we
 want to add more status in it? But I assume it's not easy to get an accurate
 starting/stopping status.



 How would it really differ from the deployer list-modules command we
 already have?  Maybe that command needs to return better rc/status/message
 when the server is still starting/stopping or not started?


 The proposed command only deals with the kernel, and will provide
 meaningful exit code to indicate the status so that other programs can call
 this script to query server status. The list-modules command deals with the
 modules and is mostly for human interaction.


 -Jack





 -Donald



 Jack Cai wrote:

 I've seen users asking how to query server status [1], and recently I was
 also asked for the same question by a colleague. So I think maybe it's good
 that Geronimo provide a cross-platform means for querying server status.
 After looking into the code that does server shutdown, I realize it's pretty
 easy to achieve that. All I need to do is to -

 1. Refactor the org.apache.geronimo.deployment.cli.StopServer class to
 something more general, e.g., ServerControl. We can make it to do status
 query or shutdown based on an extra parameter that's passed in, or make it a
 super class and create another 2 subclasses to do status query and shutdown
 respectively.

 2. Add a new command to the geronimo.(sh/bat) script, e.g., status. And
 based on how Step 1 is done, we can either reuse the shutdown.jar (probably
 rename it to control.jar); or create a new status.jar just to do status
 query, and leave the shutdown.jar to do the shutdown.

 3. The code that does the real status query work will be as simply as
 serverControl.getRunningKernel().isRunning().

 I prefer to reuse the shutdown.jar. If you see no problem with my current
 thinking, I'll go ahead to create a JIRA with a patch.

 -Jack

 [1]
 http://www.nabble.com/status-from-shell-script-(System-V-starup)-td20472233s134.htmlhttp://www.nabble.com/status-from-shell-script-%28System-V-starup%29-td20472233s134.html





-- 
Ivan

[jira] Created: (GERONIMO-4509) Two EJB server portlet issues

Two EJB server portlet issues
-

Key: GERONIMO-4509
URL: https://issues.apache.org/jira/browse/GERONIMO-4509
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: console
Affects Versions: 2.2
Environment: JDK 1.6
Ubuntu 8.04
AG 2.2 snapshot 20090110
Reporter: Forrest Xia
Assignee: Manu T George

For the new EJB server portlet, there are these problems:
1. Message prompt just restarting openejb module cause several console
exceptions and EJB server portlet disappear in admin console at next time
restart server.
Steps:
1.1 Change value of a EJB container parameter, then it prompts OpenEJB module
should be restarted for effectiveness. So I use expert mode to restart module
org.apache.geronimo.configs/openejb/2.2-SNAPSHOT/car, confirm restart, then
several exceptions are thrown out as following:
2009-01-14 09:35:45,546 ERROR [ConfigManagerPortlet] Exception
java.lang.IllegalStateException: Configuration
org.apache.geronimo.configs/axis2-ejb/2.2-SNAPSHOT/car still has children
at
org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69)
at
org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65)
...
2009-01-14 09:35:45,965 ERROR [[SystemModules]] Servlet.service() for servlet
SystemModules threw exception
java.lang.NullPointerException
at
org.apache.geronimo.console.configmanager.ConfigManagerPortlet.getConfigurationState(ConfigManagerPortlet.java:325)
at
org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:272)
...
2009-01-14 09:37:08,300 ERROR [[SystemModules]] Servlet.service() for servlet
SystemModules threw exception
java.lang.IllegalStateException: Configuration
org.apache.geronimo.configs/jaxws-ejb-deployer/2.2-SNAPSHOT/car still has
children
at
org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69)
at
org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65)
...
2009-01-14 09:37:19,125 ERROR [[SystemModules]] Servlet.service() for servlet
SystemModules threw exception
java.lang.IllegalStateException: Configuration
org.apache.geronimo.configs/openejb-deployer/2.2-SNAPSHOT/car still has children
at
org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69)
at
org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65)
...

Anyway, the openejb module finally restarted, but no children modules appear
anymore. Consequently the EJB server portlet disappears from the admin console.
No way to check if the changed parameter takes effect.

2.2 Followed by step 1, restart geronimo by no change of config.xml, still the
EJB server portlet is not there. Then check the config.xml, the portlet module
module
name=org.apache.geronimo.plugins/openejb-console-tomcat/2.2-SNAPSHOT/car/ is
load=false

Based on the symptom, I think it might be better to suggest user to restart
geronimo server as a whole, not just openejb module.

2. Another issue is the parameter value seems be changed only once. For
example, if you changed strictpooling from default true to false, then you want
to change it back without restarting server, there is no way. This behavior is
better to be improved.

--
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: 734302

2009-01-13 Thread gawor

Geronimo Revision: 734302 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090113/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090113
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 37 minutes 41 seconds
[INFO] Finished at: Tue Jan 13 21:52:32 EST 2009
[INFO] Final Memory: 640M/983M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090113/logs-2100-tomcat/test.log
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache.snapshots
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache-snapshots
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from codehaus-snapshots
[INFO] Using assembly artifact: 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:41.870
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 35 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:00:59.065) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:27.934) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:32.505) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:15.937) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:21.655) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:19.675) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:41.663) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:46.584) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:48.887) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:39.409) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:29.570) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:28.883) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:31.525) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:48.136) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:55.535) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:48.278) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.305) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:47.986) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security

[jira] Updated: (GERONIMO-4474) Pull out the text in the JSP files to resource bundle files


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

Gang Yin updated GERONIMO-4474:
---

Attachment: jsp-localization-tomcat6-connector.patch

Extract sll the  description texts from tomcat6 property file to localization 
property file and provide simplified-chinese translation.

 Pull out the text in the JSP files to resource bundle files
 ---

 Key: GERONIMO-4474
 URL: https://issues.apache.org/jira/browse/GERONIMO-4474
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2
Reporter: Ivan
Assignee: Gang Yin
Priority: Minor
 Fix For: 2.2

 Attachments: jsp-localization-activemq.patch, 
 jsp-localization-console.patch, jsp-localization-console_v2.patch, 
 jsp-localization-debugview.patch, jsp-localization-debugview_v2.patch, 
 jsp-localization-fix.patch, jsp-localization-monitoring.patch, 
 jsp-localization-monitoring_v2.patch, jsp-localization-openejb.patch, 
 jsp-localization-plancreator.patch, jsp-localization-plancreator_v2.patch, 
 jsp-localization-plugin.patch, jsp-localization-plugin_v2.patch, 
 jsp-localization-sysdb.patch, jsp-localization-tomcat6-connector.patch


 Currently in the admin console, some text are hard coded in the JSP files.
 We need to pull them out to the resource bundle files, so that we could 
 deliver multi-language versions in the future.

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

[jira] Updated: (GERONIMO-4475) Improve JMS portlet for Borker configuration

2009-01-13 Thread Ivan (JIRA)

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

Ivan updated GERONIMO-4475:
---

Attachment: G4475-activemq-portlet-update-02.patch

Update the codes according to the changes of G-4484. Thanks !

Improve JMS portlet for Borker configuration

Key: GERONIMO-4475
URL: https://issues.apache.org/jira/browse/GERONIMO-4475
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.2
Reporter: Ivan
Assignee: Donald Woods
Fix For: 2.2

Attachments: G4475-activemq-broker.patch,
G4475-activemq-portlet-update-01.patch,
G4475-activemq-portlet-update-02.patch, G4475-activemq-portlet-update.patch,
G4475-geronimo-management.patch

Currently in the administrator console, the users could not add another embed
broker. Also, they could not edit the broker through administrator console.
I list the features that I could see :
1. While creating the broker, let the use upload a configuration file.
2. While editing the broker, show a text area, so that the user could edit
the spring XML file in it. Shall we give the user a more friendly interface,
so that they do not need the edit the XML file directly. I am not sure how it
should look like.
3. Update the connector port let, so that while creating a new connector,
the user could specify the broker that it belongs to.
Please help to give some comments !

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

[jira] Created: (GERONIMO-4510) EJB server portlet layout issue

EJB server portlet layout issue
---

 Key: GERONIMO-4510
 URL: https://issues.apache.org/jira/browse/GERONIMO-4510
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.2
 Environment: JDK 1.6
Ubuntu 8.04
Firefox 3.0.3
Reporter: Forrest Xia
Assignee: Manu T George
Priority: Minor


Steps:
1. Get the plantsbywebsphere sample from wasce distribution download.
2. Follow the readme.txt to deploy it to geronimo
3. Check EJB server portlet if the layout is normal

Problem: 1. The layout is abnormal then, see the screenshot.
2. the bar to split object tree and object properties view can not be adjusted 
in Firefox 3.0.3

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

[jira] Updated: (GERONIMO-4510) EJB server portlet layout issue


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

Forrest Xia updated GERONIMO-4510:
--

Attachment: ejbserverportletlayoutissue.png

abnormal layout of EJB server portlet in Firefox 3.0.3

 EJB server portlet layout issue
 ---

 Key: GERONIMO-4510
 URL: https://issues.apache.org/jira/browse/GERONIMO-4510
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2
 Environment: JDK 1.6
 Ubuntu 8.04
 Firefox 3.0.3
Reporter: Forrest Xia
Assignee: Manu T George
Priority: Minor
 Attachments: ejbserverportletlayoutissue.png


 Steps:
 1. Get the plantsbywebsphere sample from wasce distribution download.
 2. Follow the readme.txt to deploy it to geronimo
 3. Check EJB server portlet if the layout is normal
 Problem: 1. The layout is abnormal then, see the screenshot.
 2. the bar to split object tree and object properties view can not be 
 adjusted in Firefox 3.0.3

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

[jira] Created: (GERONIMO-4511) Daytrader entity beans are not listed in the entity bean container of EJB server portlet

Daytrader entity beans are not listed in the entity bean container of EJB 
server portlet


 Key: GERONIMO-4511
 URL: https://issues.apache.org/jira/browse/GERONIMO-4511
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.2
 Environment: JDK 1.6
Ubuntu 8.04
Firefox 3.0.3
Reporter: Forrest Xia
Assignee: Manu T George


Deploy daytrader application to geronimo, and check if those entity beans are 
listed there. Found out that there are no entity beans in there.

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

[jira] Created: (GERONIMO-4512) Wrong JMS resource deployment plan causes server down

Wrong JMS resource deployment plan causes server down
-

Key: GERONIMO-4512
URL: https://issues.apache.org/jira/browse/GERONIMO-4512
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: ActiveMQ
Affects Versions: 2.2
Environment: JDK 1.6
Ubuntu 8.04
Reporter: Forrest Xia

Problems:
1. The log endlessly prints errors like this:
2009-01-14 13:38:22,241 ERROR [ActiveMQEndpointWorker] Failed to connect to
broker [tcp://localhost:61636]: Could not connect to broker URL:
tcp://localhost:61636. Reason: java.net.ConnectException: 连接被拒绝
javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61636.
Reason: java.net.ConnectException: 连接被拒绝
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
at
org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:280)
at
org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:179)
at
org.apache.activemq.ra.ActiveMQResourceAdapter.makeConnection(ActiveMQResourceAdapter.java:128)
at
org.apache.activemq.ra.ActiveMQEndpointWorker$1.run(ActiveMQEndpointWorker.java:106)
at
org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:290)
at
org.apache.geronimo.connector.work.pool.NamedRunnable.run(NamedRunnable.java:32)
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:896)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:735)
2. daytrader application cannot be stopped or restarted.
3. The default server instance cannot be stopped gracefully, unless use kill
process method.

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

[jira] Commented: (GERONIMO-4512) Wrong JMS resource deployment plan causes server down

[
https://issues.apache.org/jira/browse/GERONIMO-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663635#action_12663635
]

Forrest Xia commented on GERONIMO-4512:
---

Sorry for the chinese characters. The meaning as below.
连接被拒绝=connection was refused

Wrong JMS resource deployment plan causes server down
-

Key: GERONIMO-4512
URL: https://issues.apache.org/jira/browse/GERONIMO-4512
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: ActiveMQ
Affects Versions: 2.2
Environment: JDK 1.6
Ubuntu 8.04
Reporter: Forrest Xia

Steps:
1. Use the attached daytrader application and the wrong deployment plan to
deploy to the default geronimo server instance.
2. The admin console responses the deployment and start is OK
3. Check the geronimo.log and geronimo.out
4. Try to uninstall the daytrader application
5. Try to stop the server
Problems:
1. The log endlessly prints errors like this:
2009-01-14 13:38:22,241 ERROR [ActiveMQEndpointWorker] Failed to connect to
broker [tcp://localhost:61636]: Could not connect to broker URL:
tcp://localhost:61636. Reason: java.net.ConnectException: 连接被拒绝
javax.jms.JMSException: Could not connect to broker URL:
tcp://localhost:61636. Reason: java.net.ConnectException: 连接被拒绝
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
at
org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:280)
at
org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:179)
at
org.apache.activemq.ra.ActiveMQResourceAdapter.makeConnection(ActiveMQResourceAdapter.java:128)
at
org.apache.activemq.ra.ActiveMQEndpointWorker$1.run(ActiveMQEndpointWorker.java:106)
at
org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:290)
at
org.apache.geronimo.connector.work.pool.NamedRunnable.run(NamedRunnable.java:32)
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:896)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:735)
2. daytrader application cannot be stopped or restarted.
3. The default server instance cannot be stopped gracefully, unless use kill
process method.

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

[jira] Commented: (GERONIMO-4501) Tomcat/Axis ignores jax-ws-catalog.xml while resolving wsdlLocation URLs

2009-01-13 Thread Jarek Gawor (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663637#action_12663637
 ] 

Jarek Gawor commented on GERONIMO-4501:
---

The OASIS catalog resolution was not working with CXF in trunk. That was fixed 
in revision 734223.

I discovered one Axis2 problem (AXIS2-4209) while working on OASIS catalog 
support in Geronimo with Axis2.


 Tomcat/Axis ignores jax-ws-catalog.xml while resolving wsdlLocation URLs
 

 Key: GERONIMO-4501
 URL: https://issues.apache.org/jira/browse/GERONIMO-4501
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
 Environment: Geronimo 2.2-SNAPSHOT, Tomcat/Axis
Reporter: Janko Heilgeist
Assignee: Jarek Gawor

 The problem description's context is identical to GERONIMO-4500 for the 
 Jetty/CXF assembly. This time the catalog is completely ignored while 
 resolving the wsdlLocation URL. The exception is:
 {noformat}
 2009-01-07 17:45:17,701 ERROR [GBeanInstanceState] Error while starting; 
 GBean is now in the FAILED state: 
 abstractName=default/geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar/1231346713744/car?EJBModule=default/geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar/1231346713744/car,J2EEApplication=null,StatelessSessionBean=HelloWorldServiceEJB,j2eeType=WSLink,name=HelloWorldServiceEJB
 java.io.FileNotFoundException: http://example.com/HelloWorld.wsdl
 at 
 sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
 at java.net.URL.openStream(URL.java:1007)
 at 
 org.apache.geronimo.axis2.AxisServiceGenerator.readWSDL(AxisServiceGenerator.java:302)
 at 
 org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java:141)
 at 
 org.apache.geronimo.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java:145)
 at 
 org.apache.geronimo.axis2.ejb.EJBWebServiceContainer.init(EJBWebServiceContainer.java:56)
 at 
 org.apache.geronimo.axis2.ejb.EJBWebServiceGBean.init(EJBWebServiceGBean.java:70)
 ...
 {noformat}
 The workaround that helped in the case of the Jetty/CXF assembly does not 
 work with Tomcat/Axis.

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

[jira] Updated: (GERONIMO-4512) Wrong JMS resource deployment plan causes server down