Re: Can not deploy daytrader in geronimo m2
David,
I've filed a jira :GERONIMO-2970
There was another error when deploying daytrader and I
resolved it by replacing jaxb-impl-2.0.3.jar and
jaxb-api-2.0.jar with jaxb-impl-2.1.1.jar and
jaxb-api-2.1.jar, so should we update these two jars?
Error: Unable to distribute
daytrader-ear-2.0-SNAPSHOT.ear:
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException:
51 counts
of IllegalAnnotationExceptions
Property "id" has an XmlID annotation but its type
is not String.
this problem is related to the following
location:
at protected java.lang.String
org.apache.openejb.jee.EjbJar.id
at org.apache.openejb.jee.EjbJar
Thanks
Frank
On 2007-03-14 20:34:41, David Jencks
<[EMAIL PROTECTED]> wrote:
>I assume you are working with geronimo trunk from
svn?
>
>Can you please file a jira? I recently changed
where appclient
>files go and that caused this problem.
>
>What daytrader is doing here is a bit odd (including
client side jars
>in the server using manifest classpath) and I'd like
to think a bit
>about what the best solution is. It might be to
change daytrader and
>it might be to put the client jar in two places.
>
>thanks
>david jencks
>
>On Mar 14, 2007, at 5:56 AM, FranK G wrote:
>
>> Hi,
>> I did a little debug to the class not found problem
>> when deploy daytrader.
>> The MANIFEST.MF of web.war includes the following
>> line:
>> Class-Path: dt-ejb.jar streamer.jar
wsappclient.jar
>> which means the classloader will includes the above
>> three jar files. I notice these jars are added to
the
>> classpath in
>> org.apache.geronimo.deployment.DeploymentContext.
The
>> following method implements this function:
>>
>> public void addManifestClassPath(JarFile
>> moduleFile, URI moduleBaseUri) throws
>> DeploymentException {
>> ..
>> for (StringTokenizer tokenizer = new
>> StringTokenizer(manifestClassPath, " ");
>> tokenizer.hasMoreTokens();) {
>> ..
>> try {
>> URI targetUri =
>> moduleBaseUri.resolve(pathUri);
>> if
(targetUri.getPath().endsWith("/"))
>> throw new
>> IllegalStateException("target path must not end
with a
>> '/' character: " + targetUri);
>>
>> configuration.addToClassPath(targetUri.toString());
>> } catch (IOException e) {
>> throw new DeploymentException(e);
>> }
>> }
>> }
>> Let's take wsappclient.jar for example, its
targetUri
>> is "../wsappclient.jar", but wsappclient.jar is not
>> copied to the parent directory of the web module.
So
>> class Trade can not be found.
>> I also notice the structure of the
>> %geronimo_home%\repository in geronimo v2.0 is
>> different from v1.1, I don't know why.
>>
>> Thanks
>> Frank
>>
>> On 2007-03-14 11:16:05, FranK G
<[EMAIL PROTECTED]>
>> wrote:
>>> Charis, thank you for your reply.
>>> I got the same error when using SUN jdk.
>>> C:\>deploy --user system --password manager deploy
>>>
F:\daytrader\modules\ear\target\daytrader-ear-2.0-SNAPSHOT.ear
>>> F:\daytrader\plans\daytrader-2.0-M2-jpa-plan.xml
>>> Using JRE_HOME:C:\Program
>>> Files\Java\jdk1.5.0_06\jre
>>>Error: Unable to distribute
>>> daytrader-ear-2.0-SNAPSHOT.ear: Could
>>>not load service class
>>>
>>>
org.apache.geronimo.samples.daytrader.client.ws.Trade
>>>
>>>
>>>
org.apache.geronimo.samples.daytrader.client.ws.Trade
>>> in
>>>classloader
>>>
>>>
org.apache.geronimo.daytrader/daytrader_web.war/2.0-SNAPSHOT/car
>>>
>>> Thanks
>>> Frank
>>>
>>> On 2007-03-13 21:13:37, Christopher Blythe
>>> <[EMAIL PROTECTED]> wrote:
Frank...
Try using the daytrader-2.0-M2-jpa-plan.xml as
the
>>> deployment plan. If that
doesn't help, it might be worth trying the SUN
JDK.
Chris
On 3/13/07, FranK G <[EMAIL PROTECTED]> wrote:
>
> I checked out the source codes of daytrader from
>
>>>
https://svn.apache.org/repos/asf/geronimo/daytrader/trunk
> and built it successful. But I encountered the
> following error when I deployed it:
> C:\>deploy --user system --password manager
deploy
>
>>>
F:\daytrader\modules\ear\target\daytrader-ear-2.0-SNAPSHOT.ear
>
>>>
F:\daytrader\plans\daytrader-geronimo-derby-plan.xml
> Using JRE_HOME:C:\Program
>>> Files\IBM\Java50\jre
> Error: Unable to distribute
> daytrader-ear-2.0-SNAPSHOT.ear:
>
>
>>>
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException:
> 51 counts
> of IllegalAnnotationExceptions
>
> Property "id" has an XmlID annotation but
its
>>> type
> is not String.
>
> this problem is related to the following
> location:
>
> at protected java.lang.String
> org.apache.openejb.jee.EjbJar.id
>
> at org.apache.openejb.jee.EjbJar
>
> Property "id" has an XmlID annotation but
its
>>> type
> is not String.
>
>
[jira] Assigned: (GERONIMO-2972) Bind JavaMail Session to Global JNDI
[ https://issues.apache.org/jira/browse/GERONIMO-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher M. Cardona reassigned GERONIMO-2972: Assignee: Christopher M. Cardona > Bind JavaMail Session to Global JNDI > > > Key: GERONIMO-2972 > URL: https://issues.apache.org/jira/browse/GERONIMO-2972 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: mail >Affects Versions: 2.0 >Reporter: Christopher M. Cardona > Assigned To: Christopher M. Cardona > > Auto bind JavaMail Session objects to Global JNDI. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2973) Bind JDBC DataSource to Global JNDI
Bind JDBC DataSource to Global JNDI Key: GERONIMO-2973 URL: https://issues.apache.org/jira/browse/GERONIMO-2973 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Affects Versions: 2.0 Reporter: Christopher M. Cardona Auto bind JDBC DataSource objects to Global JNDI. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2961) Axis2: fix java.lang.ArrayIndexOutOfBoundsException when deploying the jaxws calculator example
[
https://issues.apache.org/jira/browse/GERONIMO-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481060
]
Lasantha Ranaweera commented on GERONIMO-2961:
--
I checked this patch and it looks correct to me. There are lot more to upgrade
in the AxisServiceGenerator and I am currently working on it :).
Thanks,
Lasantha
> Axis2: fix java.lang.ArrayIndexOutOfBoundsException when deploying the jaxws
> calculator example
> ---
>
> Key: GERONIMO-2961
> URL: https://issues.apache.org/jira/browse/GERONIMO-2961
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: webservices
>Affects Versions: Wish List
> Environment: winxp + sun 1.5 sdk
>Reporter: Lin Sun
> Fix For: 2.0
>
> Attachments: G2961.patch
>
>
> Getting the following example when deploying the calculator example for axis2
> (G2952). This is because the parameter is integer, thus
> strParamType.split(" ") length is 1.
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
> at
> org.apache.geronimo.axis2.AxisServiceGenerator.fillDocOperationInfo(A
> xisServiceGenerator.java:226)
> at
> org.apache.geronimo.axis2.AxisServiceGenerator.fillOperationInformati
> on(AxisServiceGenerator.java:169)
> at
> org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(Axi
> sServiceGenerator.java:145)
> at
> org.apache.geronimo.axis2.Axis2WebServiceContainer.(Axis2WebSer
> viceContainer.java:101)
> ... 38 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2972) Bind JavaMail Session to Global JNDI
Bind JavaMail Session to Global JNDI Key: GERONIMO-2972 URL: https://issues.apache.org/jira/browse/GERONIMO-2972 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Components: mail Affects Versions: 2.0 Reporter: Christopher M. Cardona Auto bind JavaMail Session objects to Global JNDI. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2971) Auto bind resources to Global JNDI
Auto bind resources to Global JNDI -- Key: GERONIMO-2971 URL: https://issues.apache.org/jira/browse/GERONIMO-2971 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Affects Versions: 2.0 Reporter: Christopher M. Cardona We need a way to auto bind resources like JDBC DataSource, JavaMail Session, EJB, etc. to Global JNDI namespace. This will allow the lookup of the said resources without declaring resource references in the deployment plans. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
JPA Testsuite Error in Console
Hi, I just tried to run the JPA testsuite after starting the server using "java -javaagent:bin/jpa.jar -jar bin/server.jar " command and noticed the following error in the console. It doesn't fail the test suite anyway. Is it relating to some other known bug or not? Insight would be greatly appriciated. Thanks, Lasantha 3666 WARN [RMI TCP Connection(10)-127.0.1.1] openjpa.Enhance - An exception was thrown while attempting to perform class file transformation on "org/apache/geronimo/gbean/GBeanLifecycle$$FastClassByCGLIB$$e6d2946a": <0|false|0.9.6-incubating> org.apache.openjpa.util.GeneralException: org.apache.geronimo.gbean.GBeanLifecycle$$FastClassByCGLIB$$e6d2946a in classloader org.apache.geronimo.testsuite/jpa-ear/2.0-SNAPSHOT/ear at org.apache.openjpa.enhance.PCClassFileTransformer.needsEnhance(PCClassFileTransformer.java:179) at org.apache.openjpa.enhance.PCClassFileTransformer.transform(PCClassFileTransformer.java:117) at org.apache.openjpa.persistence.PersistenceProviderImpl$ClassTransformerImpl.transform(PersistenceProviderImpl.java:140) at org.apache.geronimo.persistence.TransformerWrapper.transform(TransformerWrapper.java:43) at org.apache.geronimo.transformer.TransformerCollection.transform(TransformerCollection.java:36) at sun.instrument.TransformerManager.transform(TransformerManager.java:122) at sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:155) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at net.sf.cglib.core.ReflectUtils.defineClass(ReflectUtils.java:384) at net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:219) at net.sf.cglib.reflect.FastClass$Generator.create(FastClass.java:64) at net.sf.cglib.proxy.MethodProxy.helper(MethodProxy.java:81) at net.sf.cglib.proxy.MethodProxy.create(MethodProxy.java:46) at org.apache.geronimo.management.EJB$$EnhancerByCGLIB$$292b5294.CGLIB$STATICHOOK101() at org.apache.geronimo.management.EJB$$EnhancerByCGLIB$$292b5294.() 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:585) at net.sf.cglib.proxy.MethodProxy.find(MethodProxy.java:127) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.getSuperIndex(ProxyMethodInterceptor.java:271) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.createRawGBeanInvokers(ProxyMethodInterceptor.java:140) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.createGBeanInvokers(ProxyMethodInterceptor.java:103) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.(ProxyMethodInterceptor.java:70) at org.apache.geronimo.kernel.basic.BasicProxyManager.getMethodInterceptor(BasicProxyManager.java:232) at org.apache.geronimo.kernel.basic.BasicProxyManager$ManagedProxyFactory.createProxy(BasicProxyManager.java:209) at org.apache.geronimo.kernel.basic.BasicProxyManager.createProxy(BasicProxyManager.java:103) at org.apache.geronimo.gbean.runtime.ProxyCollection.addTarget(ProxyCollection.java:90) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.targetAdded(GBeanCollectionReference.java:96) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.addTarget(GBeanCollectionReference.java:180) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference$1.running(GBeanCollectionReference.java:110) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:529) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120) at org.apache.geronimo
[jira] Created: (GERONIMO-2970) Can not deploy daytrader in geronimo m2
Can not deploy daytrader in geronimo m2 --- Key: GERONIMO-2970 URL: https://issues.apache.org/jira/browse/GERONIMO-2970 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 2.0-M3 Reporter: Frank G Fix For: 2.0-M3 I checked out the source codes of daytrader from https://svn.apache.org/repos/asf/geronimo/daytrader/trunk and built it successful. But I encountered the following error when I deployed it: Error: Unable to distribute daytrader-ear-2.0-SNAPSHOT.ear: Could not load service class org.apache.geronimo.samples.daytrader.client.ws.Trade org.apache.geronimo.samples.daytrader.client.ws.Trade in classloader geronimo/daytrader-derby-tomcat_web.war/1.1.1/car I posted this on the dev maillist and David Jencks's comments are below: I assume you are working with geronimo trunk from svn? Can you please file a jira? I recently changed where appclient files go and that caused this problem. What daytrader is doing here is a bit odd (including client side jars in the server using manifest classpath) and I'd like to think a bit about what the best solution is. It might be to change daytrader and it might be to put the client jar in two places. thanks david jencks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Axis2 JAXWS Integration Patch waiting for review
Hi Dims, Can you please review GERONIMO-2952 patch ? I have bit more to submit relating to this area. Thanks, Lasantha
[jira] Commented: (GERONIMO-2962) More Improved Web GUI to 'Add new HTTPS listener'
[ https://issues.apache.org/jira/browse/GERONIMO-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481046 ] Lasantha Ranaweera commented on GERONIMO-2962: -- Thanks for reviewing the patch. I will submit a new patch as my time permits. Thanks Again, Lasantha > More Improved Web GUI to 'Add new HTTPS listener' > - > > Key: GERONIMO-2962 > URL: https://issues.apache.org/jira/browse/GERONIMO-2962 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.0-M3 >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2962.patch > > > As discussed with dev list this will improve the Web GUI for the Add new > HTTPS listener for Tomcat. It will remove some of the unnecessary information > from Tomcat GUI (eg. keystore type) and create more consistency between Jetty > and Tomcat consoles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2153) Global JNDI
[ https://issues.apache.org/jira/browse/GERONIMO-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2153. -- Resolution: Fixed Fix Version/s: 2.0-beta1 1.2 Dain's implementaiton has been in 1.2 and 2.0 for a long time. auto-binding needs a different jira. > Global JNDI > --- > > Key: GERONIMO-2153 > URL: https://issues.apache.org/jira/browse/GERONIMO-2153 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: naming >Affects Versions: 1.2 >Reporter: Krishnakumar B > Assigned To: David Jencks > Fix For: 1.2, 2.0-beta1 > > Attachments: ConnectorJNDIBindingGBean.java, > GeronimoGlobalContext.java, jndi-project.zip > > > Implementing Global JNDI for server > Requirements > * Non -persistent > * Read/Write > * Bindings to JNDI/COS-NAMING/JAXR > * Can bind RA,EJB,GBEAN,Any object -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2416) ProxyMethodInterceptor should work with classes that have start,stop methods
[
https://issues.apache.org/jira/browse/GERONIMO-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-2416.
--
Resolution: Won't Fix
As dain said, you can't proxy a final method. If you have a final method
wrapping and delegating to the implementation object is probably the best bet.
That's what I did with the jetty classes anyway.
> ProxyMethodInterceptor should work with classes that have start,stop methods
>
>
> Key: GERONIMO-2416
> URL: https://issues.apache.org/jira/browse/GERONIMO-2416
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: kernel
>Affects Versions: 1.2
>Reporter: David Jencks
> Assigned To: David Jencks
>Priority: Critical
> Fix For: 2.0
>
>
> jetty6 components usually have lifecycle methods start,stop, and possibly
> others. If we write a gbean extending these objects ProxyMethodInterceptor
> blows up with an ArrayIndexOutOfBoundsException (-1). I don't understand why
> this happens, and there might be a different cause, but the gbeans that have
> this problem all extend jetty objects with start methods.
> A really bad workaround that lets the server start is this patch:
> Index:
> modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/basic/ProxyMethodInterceptor.java
> ===
> ---
> modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/basic/ProxyMethodInterceptor.java
> (revision 447903)
> +++
> modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/basic/ProxyMethodInterceptor.java
> (working copy)
> @@ -110,14 +110,29 @@
> invokers[getSuperIndex(proxyType, proxyType.getMethod("equals",
> new Class[]{Object.class}))] = new EqualsInvoke(kernel);
> invokers[getSuperIndex(proxyType,
> proxyType.getMethod("hashCode", null))] = new HashCodeInvoke();
> invokers[getSuperIndex(proxyType,
> proxyType.getMethod("toString", null))] = new
> ToStringInvoke(proxyType.getName());
> -if(GeronimoManagedBean.class.isAssignableFrom(proxyType)) {
> -invokers[getSuperIndex(proxyType,
> proxyType.getMethod("getState", null))] = new GetStateInvoke(kernel);
> -invokers[getSuperIndex(proxyType,
> proxyType.getMethod("getStateInstance", null))] = new
> GetStateInstanceInvoke(kernel);
> -invokers[getSuperIndex(proxyType,
> proxyType.getMethod("start", null))] = new StartInvoke(kernel);
> -invokers[getSuperIndex(proxyType,
> proxyType.getMethod("startRecursive", null))] = new
> StartRecursiveInvoke(kernel);
> -invokers[getSuperIndex(proxyType,
> proxyType.getMethod("stop", null))] = new StopInvoke(kernel);
> -invokers[getSuperIndex(proxyType,
> proxyType.getMethod("getStartTime", null))] = new GetStartTimeInvoke(kernel);
> -invokers[getSuperIndex(proxyType,
> proxyType.getMethod("getObjectName", null))] = new
> GetObjectNameInvoke(kernel);
> +if (GeronimoManagedBean.class.isAssignableFrom(proxyType)) {
> +int superIndex;
> +if ((superIndex = getSuperIndex(proxyType,
> proxyType.getMethod("getState", null))) > -1) {
> +invokers[superIndex] = new GetStateInvoke(kernel);
> +}
> +if ((superIndex = getSuperIndex(proxyType,
> proxyType.getMethod("getStateInstance", null))) > -1) {
> +invokers[superIndex] = new
> GetStateInstanceInvoke(kernel);
> +}
> +if ((superIndex = getSuperIndex(proxyType,
> proxyType.getMethod("start", null))) > -1) {
> +invokers[superIndex] = new StartInvoke(kernel);
> +}
> +if ((superIndex = getSuperIndex(proxyType,
> proxyType.getMethod("startRecursive", null))) > -1) {
> +invokers[superIndex] = new StartRecursiveInvoke(kernel);
> +}
> +if ((superIndex = getSuperIndex(proxyType,
> proxyType.getMethod("stop", null))) > -1) {
> +invokers[superIndex] = new StopInvoke(kernel);
> +}
> +if ((superIndex = getSuperIndex(proxyType,
> proxyType.getMethod("getStartTime", null))) > -1) {
> +invokers[superIndex] = new GetStartTimeInvoke(kernel);
> +}
> +if ((superIndex = getSuperIndex(proxyType,
> proxyType.getMethod("getObjectName", null))) > -1) {
> +invokers[superIndex] = new GetObjectNameInvoke(kernel);
> +}
> }
> } catch (Exception e) {
> // this can not happen...
[jira] Closed: (GERONIMO-2657) Persistence-* builders need improvements
[ https://issues.apache.org/jira/browse/GERONIMO-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2657. -- Resolution: Fixed Fix Version/s: (was: 2.0) 2.0-beta1 Injection is done as part of other jira issues. > Persistence-* builders need improvements > > > Key: GERONIMO-2657 > URL: https://issues.apache.org/jira/browse/GERONIMO-2657 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence >Affects Versions: 2.0 >Reporter: David Jencks > Assigned To: David Jencks > Fix For: 2.0-beta1 > > > The entity-manager-factory-ref stuff needs to be renamed to > persistence-unit-ref in xml and code to follow the spec dd usage. > The builders need to look for spec dd entries as well as our proprietary > entries. > We need to do something about the injection instructions in the spec entries. > This might be taken care of in a more generic way. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[STATUS] (geronimo) Wed Mar 14 23:46:05 2007
APACHE GERONIMO STATUS: -*-text-*- Last modified at [$Date: 2007-02-22 13:03:58 -0500 (Thu, 22 Feb 2007) $] The current version of this file can be found at: * http://svn.apache.org/repos/asf/geronimo/server/trunk/STATUS Upcoming Releases: Geronimo 1.2 -- geronimo/server/trunk/ Release Manager: Dain Sundstrom and Alan Cabrera Estimated Date: Q4 2006 RELEASE SHOWSTOPPERS: The release is stalled waiting for final releases from dependent projects. Specifically, we need releases from: Yoko 1.0 - Contains many fixes to CORBA interoperability ActiveMQ 4.1.1 - We need a release which contains AMQ-1165 and AMQ-1088 OpenEJB 2.3 - Once Yoko is released, OpenEJB 2.3 can be release RELEASE HISTORY: 2006-12-16 Geronimo 1.2-beta 2006-09-18 Geronimo 1.1.1 2006-06-26 Geronimo 1.1 2006-01-05 Geronimo 1.0 2005-10-04 Geronimo 1.0 milestone 5 2005-08-10 Geronimo 1.0 milestone 4 2004-11-11 Geronimo 1.0 milestone 3 2004-09-09 Geronimo 1.0 milestone 2 2004-04-29 Geronimo 1.0 milestone 1 If you're a contributor looking for something to do: * Review the documentation and suggest improvements * Review the bug list and suggest fixes or report reproducibility * Report bugs yourself
[jira] Closed: (GERONIMO-2749) AbstractWebModuleBuilder needs to support HTTP extension methods per jacc 1.1
[ https://issues.apache.org/jira/browse/GERONIMO-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2749. -- Resolution: Fixed I fixed this at some point, not sure exactly when. > AbstractWebModuleBuilder needs to support HTTP extension methods per jacc 1.1 > - > > Key: GERONIMO-2749 > URL: https://issues.apache.org/jira/browse/GERONIMO-2749 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: security, web >Affects Versions: 2.0-M2 >Reporter: David Jencks > Assigned To: David Jencks > Fix For: 2.0-M2 > > > The code to turn web security constraints into jacc permissions needs to > understand http extension methods per jacc 1.1. Basically the meaning of "" > is reversed and we need to track exclusion lists. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2668) axis deployer still assumes it's the only one
[ https://issues.apache.org/jira/browse/GERONIMO-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2668. -- Resolution: Fixed Fix Version/s: (was: 2.0) 2.0-beta1 not sure why I didn't close this already. > axis deployer still assumes it's the only one > - > > Key: GERONIMO-2668 > URL: https://issues.apache.org/jira/browse/GERONIMO-2668 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment, webservices >Affects Versions: 2.0 >Reporter: David Jencks > Assigned To: David Jencks > Fix For: 2.0-beta1 > > > axis-builder still assumes it's the only web service deployer. It needs to > not throw exceptions if theres a javaee webservices.xml and avoid throwing > npes if there's nothing for it to configure. I think it also needs to look > in javaee webservices.xml for jaxrpc style webservices. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2763) JACC URLPatternSpec does not accept *do:login.do as it should
[ https://issues.apache.org/jira/browse/GERONIMO-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2763. -- Resolution: Fixed not sure why I didn't already close this. > JACC URLPatternSpec does not accept *do:login.do as it should > - > > Key: GERONIMO-2763 > URL: https://issues.apache.org/jira/browse/GERONIMO-2763 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: security, specs >Affects Versions: 1.1.1, 2.0-M1 >Reporter: David Jencks > Assigned To: David Jencks > Fix For: 2.0-M2 > > > This problem was originally reported by Dmitry Colebach in GERONIMO-1585. > I've copied his description here: > I'd like to add some related thoughts to this: > I have the following in my web.xml: > > > Struts pages > *.do > GET > POST > > > * > > > > > Login page > /login.do > GET > > > So the outcome I want is that in general struts pages require > authentication, but the login page doesn't require authentication > (obviously). This has been working fine on WL but when I try to > deploy on Geronimo I get this: > Caused by: java.lang.IllegalArgumentException: Only exact and > path-prefix qualifiers in the URLPatternSpec are allowed when first > URLPattern is an extension pattern > at javax.security.jacc.URLPatternSpec.(URLPatternSpec.java:82) > at > javax.security.jacc.WebResourcePermission.(WebResourcePermission.java:54) > at > org.apache.geronimo.web.deployment.AbstractWebModuleBuilder.buildSpecSecurityConfig(AbstractWebModuleBuilder.java:357) > Debugging through the code, AbstractWebModuleBuilder is merging all > the patterns including ones that don't require authentication and so > is trying to create a WebResourcePermission instance with the string > "*.do:/login.do". > The servlet spec section "12.8.1 Combining constraints" says: > "A security constraint that does not contain an authorization > constraint shall combine with authorization constraints that name or > imply roles to allow unauthenticated access." > I realise this isn't exactly what this bug is about, but it should be > addressed at the same time. > [ Show » ] > Dmitri Colebatch [21/Sep/06 05:43 PM] I'd like to add some related thoughts > to this: I have the following in my web.xml: > Struts pages > *.do GET > POST > * > Login > page /login.do > GET > So the outcome I want is that in general struts pages > require authentication, but the login page doesn't require authentication > (obviously). This has been working fine on WL but when I try to deploy on > Geronimo I get this: Caused by: java.lang.IllegalArgumentException: Only > exact and path-prefix qualifiers in the URLPatternSpec are allowed when first > URLPattern is an extension pattern at > javax.security.jacc.URLPatternSpec.(URLPatternSpec.java:82) at > javax.security.jacc.WebResourcePermission.(WebResourcePermission.java:54) > at > org.apache.geronimo.web.deployment.AbstractWebModuleBuilder.buildSpecSecurityConfig(AbstractWebModuleBuilder.java:357) > Debugging through the code, AbstractWebModuleBuilder is merging all the > patterns including ones that don't require authentication and so is trying to > create a WebResourcePermission instance with the string "*.do:/login.do". The > servlet spec section "12.8.1 Combining constraints" says: "A security > constraint that does not contain an authorization constraint shall combine > with authorization constraints that name or imply roles to allow > unauthenticated access." I realise this isn't exactly what this bug is about, > but it should be addressed at the same time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2827) Java EE 5 application client support
[ https://issues.apache.org/jira/browse/GERONIMO-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2827. -- Resolution: Fixed Fix Version/s: 2.0-beta1 I'm not aware of anything left to do here. > Java EE 5 application client support > > > Key: GERONIMO-2827 > URL: https://issues.apache.org/jira/browse/GERONIMO-2827 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: application client >Affects Versions: 2.0 >Reporter: Jacek Laskowski > Assigned To: David Jencks > Fix For: 2.0-beta1 > > > Provide javaee5 application client support, mainly no DD available and > annotations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-2919) use axis2 saaj 1.3 spec jar
[ https://issues.apache.org/jira/browse/GERONIMO-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned GERONIMO-2919: -- Assignee: Jarek Gawor (was: David Jencks) I think jarek said he'd work on this. > use axis2 saaj 1.3 spec jar > --- > > Key: GERONIMO-2919 > URL: https://issues.apache.org/jira/browse/GERONIMO-2919 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0-M3 >Reporter: David Jencks > Assigned To: Jarek Gawor > Fix For: 2.0-beta1 > > Attachments: GERONIMO-2919.patch > > > we're using the saaj 1.1 or 1.2 jar from axis1. We need saaj 1.3 support, > lets use the axis2 spec jar for this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Slow booting 2.0 + jetty
On Mar 14, 2007, at 11:12 PM, Jason Dillon wrote: So... based on commit logs... I'm guessing this is fixed now? I sure hope so david jencks --jason On Mar 14, 2007, at 5:50 PM, David Jencks wrote: I'll fix it tonight thanks david jencks On Mar 14, 2007, at 7:32 PM, Jason Dillon wrote: Any idea on how to get this fixed? This is causing problems with automated testing since the server does not appear to be started after waiting for 2 minutes... which kills testsuite builds. --jason
Re: Geronimo website update
Very nice Hernan On Mar 14, 2007, at 1:37 PM, Hernan Cunico wrote: Hi All, there is a new direct link to Geronimo forums from the "Community" menu on the website. Check it out http://geronimo.apache.org/ discussion-forums.html The links we had before were not too visible. Also updated the L&F in Nabble to make look a bit more consistent with the website. Cheers! Hernan
Re: [Fwd: What do people think about graduation ?]
On 3/14/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
Let's continue this discussion on dev list
-- Forwarded message --
From: Guillaume Nodet <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Wed, 14 Mar 2007 08:08:37 +0100
Subject: What do people think about graduation ?
It may be time to consider it.
The community is growing and diverse ...
I don't see any issues left.
We've had all of the requirements fulfilled for some time now:
http://incubator.apache.org/projects/servicemix.html
I think it's high time we call for a vote.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61Ehttp://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
Re: Slow booting 2.0 + jetty
So... based on commit logs... I'm guessing this is fixed now? --jason On Mar 14, 2007, at 5:50 PM, David Jencks wrote: I'll fix it tonight thanks david jencks On Mar 14, 2007, at 7:32 PM, Jason Dillon wrote: Any idea on how to get this fixed? This is causing problems with automated testing since the server does not appear to be started after waiting for 2 minutes... which kills testsuite builds. --jason
maven-maven-plugin vs. maven-invoker-plugin
This is mostly aimed at Prasad... But I think we should start using the maven-invoker-plugin to run the bits under testsuite/* As I recall the only reason I created maven-maven-plugin was to set the list of profiles the child executed under. Unfortunately its not terribly easy to add this to the maven-invoker-plugin, since the API which that plugin uses (the core maven-invoker bits) does not expose control over the profiles to be used. BUT... should be easy enough to simply set a property and use activation to flip them on. I've recently decided I like the maven-invoker-plugin much more, since it produces by default little output for child builds and clearly states which ones fail. One of the things I don't like about our testsuite/* is that if you run it from the top-level you get a *ton* of output and its hard to tell which pass and which don't. * * * I'm not going to change anything right now... but I think we should consider dropping maven-maven-plugin and just using maven-invoker- plugin. What do you think? --jason
[jira] Commented: (GERONIMO-2958) MyFaces annotation support
[ https://issues.apache.org/jira/browse/GERONIMO-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481006 ] David Jencks commented on GERONIMO-2958: implemented and hooked up to jetty in rev 518452. Seems to work -- at least we are creating all the jsf managed beans fine. Uses the interface for bean lifecycle we negotiated with the MyFaces team, and many thanks to them for their cooperation! This also cleans up construction of Modules and removes an unused and apparently unneeded method from ModuleBuilderExtension. Still need to integrate with tomcat. > MyFaces annotation support > -- > > Key: GERONIMO-2958 > URL: https://issues.apache.org/jira/browse/GERONIMO-2958 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Tim McConnell > Assigned To: Tim McConnell > Attachments: GERONIMO-2958-1.patch, GERONIMO-2958-2.patch, > GERONIMO-2958-3.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
I'm going to break "automatic" tomcat jsf support for a couple of days
I have the jetty-myfaces integration working with the object lifecycle contract we negotiated with the myfaces team, and I've straightened out the classloaders so that myfaces is included only if you in fact are using jsf. I'm about to commit this work, but it will break the tomcat jsf integration a bit for a couple of days. The reason is that the current integration relies on myfaces being in the same classloader as tomcat, which is obviously not compatible with the idea of adding myfaces to the app classloader only if its needed. You should be able to make a jsf app work by pretending it's not a jsf 1.2 app, i.e. including the myfaces ServletContextListener in your web.xml explicitly. We don't really have any good tests but dependency injection into jsf managed beans should be working in jetty now (after my commit). I'm going to look into dependency injection in tomcat next, and then hook up myfaces similarly, so this "outage" should be pretty short. thanks david jencks
[jira] Resolved: (GERONIMO-2693) Application classloader contains a massive number of duplicate classpath entries
[
https://issues.apache.org/jira/browse/GERONIMO-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks resolved GERONIMO-2693.
Resolution: Fixed
Fix Version/s: 2.0-beta1
I think this is fixed in trunk in rev 518426. I'd rather there was a test,
especially for the non-normailized urls Mike was seeing. This issue was making
jetty start at less than a snails pace due to its search for tlds, and fixing
it considerably speeds up jetty's startup.
> Application classloader contains a massive number of duplicate classpath
> entries
>
>
> Key: GERONIMO-2693
> URL: https://issues.apache.org/jira/browse/GERONIMO-2693
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: kernel
>Affects Versions: 1.1.1
> Environment: WAS CE 1.1.0.1
>Reporter: Mike Perham
> Assigned To: David Jencks
> Fix For: 2.0-beta1
>
> Attachments: cpath.txt, GERONIMO-2693.patch
>
>
> I have an EAR with an MDB jar and two WARs. The EAR contains a large number
> of jars within a lib directory. The wars and ejb-jar all contain MANIFEST.MF
> Class-Path entries which reference those jars within lib/.
> When I print out my WAR classpath, I get output attached. The duplications
> don't really matter all that much except for the duplications due to
> non-canonicalized paths:
> jar:file:/D:/perforce/depot/external/wasce/1.1.0.1/repository/com/ibm/websphere/fabric-tools-ear/6.0/fabric-tools-ear-6.0.car/lib/fabric-gov-api-1.4.0.jar!/META-INF
> jar:file:/D:/perforce/depot/external/wasce/1.1.0.1/repository/com/ibm/websphere/fabric-tools-ear/6.0/fabric-tools-ear-6.0.car/fabric-tools-web.war/../lib/fabric-gov-api-1.4.0.jar!/META-INF
> If I do a getResources("foo") and that gov-api jar has a foo resource, the
> system will think there are two foo resources when in fact there is only one,
> due to different URLs for the same resource. As a result, for instance, this
> causes Apache Hivemind to blow up with an error due to it thinking a
> component jar is doubly defined in the classpath.
> I'm unclear why Geronimo is adding all the lib jars to my classpath without
> my asking. It seems like the various J2EE modules should be able to control
> their own classpath wrt jars in the ear.
> This is a blocker preventing us from using our application on WAS CE.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Slow booting 2.0 + jetty
I'll fix it tonight thanks david jencks On Mar 14, 2007, at 7:32 PM, Jason Dillon wrote: Any idea on how to get this fixed? This is causing problems with automated testing since the server does not appear to be started after waiting for 2 minutes... which kills testsuite builds. --jason
Slow booting 2.0 + jetty
Any idea on how to get this fixed? This is causing problems with automated testing since the server does not appear to be started after waiting for 2 minutes... which kills testsuite builds. --jason
Re: SAAJ integration idea
On Mar 14, 2007, at 10:40 AM, Jarek Gawor wrote: > Another idea I've had was to create a new context classloader (when > set() is called) instead of the thread local solution. That new > context classloader would first load a specific jar file for the SAAJ > implementation (the jar file would just contain SAAJ configuration > files) and delegate everything else to the existing context > classloader. That way, since the right configuration files would > appear first in the classloader, it would force the right SAAJ > implementation to be used (the SAAJ factory classes first check the > context classloader for the configuration files). I don't see how this could work as the resource data would likely be cached by Java code, so when you attempt switch to another SAAJ implementation the Java code won't notice the CL switch. Hmm... you mean that information would be cached somewhere else besides the classloader? Sure. Resource files are just byte arrays, and some code will read them in and interpret them. Normally, this type of code caches the results since disks are so slow. Maybe we are talking about different things. -dain
[jira] Updated: (SM-877) Bottleneck in SoapReader.readSoapUsingDom()
[ https://issues.apache.org/activemq/browse/SM-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-877: --- Fix Version/s: 3.2 > Bottleneck in SoapReader.readSoapUsingDom() > --- > > Key: SM-877 > URL: https://issues.apache.org/activemq/browse/SM-877 > Project: ServiceMix > Issue Type: Improvement >Affects Versions: 3.1 > Environment: ServiceMix 3.1 >Reporter: Alex Boisvert > Assigned To: Alex Boisvert >Priority: Minor > Fix For: 3.1.1, 3.2 > > Attachments: SoapReader.patch.txt > > > This stacktrace illustrates a bottleneck in SoapReader.readSoapUsingDom() due > to creating its own DocumentBuilders: > "btpool0-14" prio=1 tid=0x7dc857d0 nid=0x4f28 waiting for monitor entry > [0x79f35000..0x79f35e60] > at > org.apache.xbean.classloader.NamedClassLoader.isDestroyed(NamedClassLoader.java:76) > - waiting to lock <0x915cb918> (a > org.apache.xbean.classloader.JarFileClassLoader) > at > org.apache.xbean.classloader.MultiParentClassLoader.getResource(MultiParentClassLoader.java:238) > at > org.apache.xbean.classloader.MultiParentClassLoader.getResource(MultiParentClassLoader.java:258) > at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:1159) > at javax.xml.parsers.SecuritySupport$4.run(SecuritySupport.java:72) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.xml.parsers.SecuritySupport.getResourceAsStream(SecuritySupport.java:65) > at > javax.xml.parsers.FactoryFinder.findJarServiceProvider(FactoryFinder.java:213) > at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:185) > at > javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:98) > at > org.apache.servicemix.soap.marshalers.SoapReader.readSoapUsingDom(SoapReader.java:93) > at > org.apache.servicemix.soap.marshalers.SoapReader.read(SoapReader.java:80) > at > org.apache.servicemix.soap.marshalers.SoapReader.read(SoapReader.java:73) > at > org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:164) > at > org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141) > at org.mortbay.jetty.Server.handle(Server.java:269) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430) > at > org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:701) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:698) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:199) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:339) > at > org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270) > at > org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475) > Attaching patch to use DOMUtil.getDocumentBuilder() instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-877) Bottleneck in SoapReader.readSoapUsingDom()
[ https://issues.apache.org/activemq/browse/SM-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned SM-877: -- Assignee: Alex Boisvert > Bottleneck in SoapReader.readSoapUsingDom() > --- > > Key: SM-877 > URL: https://issues.apache.org/activemq/browse/SM-877 > Project: ServiceMix > Issue Type: Improvement >Affects Versions: 3.1 > Environment: ServiceMix 3.1 >Reporter: Alex Boisvert > Assigned To: Alex Boisvert >Priority: Minor > Fix For: 3.1.1, 3.2 > > Attachments: SoapReader.patch.txt > > > This stacktrace illustrates a bottleneck in SoapReader.readSoapUsingDom() due > to creating its own DocumentBuilders: > "btpool0-14" prio=1 tid=0x7dc857d0 nid=0x4f28 waiting for monitor entry > [0x79f35000..0x79f35e60] > at > org.apache.xbean.classloader.NamedClassLoader.isDestroyed(NamedClassLoader.java:76) > - waiting to lock <0x915cb918> (a > org.apache.xbean.classloader.JarFileClassLoader) > at > org.apache.xbean.classloader.MultiParentClassLoader.getResource(MultiParentClassLoader.java:238) > at > org.apache.xbean.classloader.MultiParentClassLoader.getResource(MultiParentClassLoader.java:258) > at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:1159) > at javax.xml.parsers.SecuritySupport$4.run(SecuritySupport.java:72) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.xml.parsers.SecuritySupport.getResourceAsStream(SecuritySupport.java:65) > at > javax.xml.parsers.FactoryFinder.findJarServiceProvider(FactoryFinder.java:213) > at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:185) > at > javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:98) > at > org.apache.servicemix.soap.marshalers.SoapReader.readSoapUsingDom(SoapReader.java:93) > at > org.apache.servicemix.soap.marshalers.SoapReader.read(SoapReader.java:80) > at > org.apache.servicemix.soap.marshalers.SoapReader.read(SoapReader.java:73) > at > org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:164) > at > org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141) > at org.mortbay.jetty.Server.handle(Server.java:269) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430) > at > org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:701) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:698) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:199) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:339) > at > org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270) > at > org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475) > Attaching patch to use DOMUtil.getDocumentBuilder() instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2964) Cannot specify the Tomcat work directory for a web application
[ https://issues.apache.org/jira/browse/GERONIMO-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Nanner updated GERONIMO-2964: -- Attachment: tomcat-config-workdir.patch Here's an additional patch for the config XSD. > Cannot specify the Tomcat work directory for a web application > -- > > Key: GERONIMO-2964 > URL: https://issues.apache.org/jira/browse/GERONIMO-2964 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 1.2 >Reporter: Aman Nanner >Priority: Minor > Fix For: 1.2 > > Attachments: tomcat-config-workdir.patch, tomcat-workdir.patch > > > In Tomcat, a work directory can be specified for a web application in a > WEB-INF/context.xml file. The GeronimoStandardContext does not permit the > user to specify a work directory, and so the work directory defaults to > var/catalina/work/. > I've submitted a patch file that modifies the geronimo-tomcat-1.2 schema to > permit the user to optionally specify a work directory. This work directory > is then propagated into the TomcatContext. I've tested this and it seems to > work well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2960) test for MyFaces 1.2 in Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480878 ] Paul McMahan commented on GERONIMO-2960: the spec says that JSF applications are required to reference FacesServlet in their web.xml, so neither it nor the *.jsf mapping should be removed from the sample > test for MyFaces 1.2 in Geronimo > > > Key: GERONIMO-2960 > URL: https://issues.apache.org/jira/browse/GERONIMO-2960 > Project: Geronimo > Issue Type: Test > Security Level: public(Regular issues) >Affects Versions: 2.0-beta1 >Reporter: Paul McMahan > Assigned To: Paul McMahan > Fix For: 2.0-beta1 > > > Add a new test for MyFaces 1.2 running natively in Geronimo -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[Fwd: What do people think about graduation ?]
Let's continue this discussion on dev list --- Begin Message --- It may be time to consider it. The community is growing and diverse ... I don't see any issues left. Cheers, Guillaume Nodet --- End Message ---
Re: eip filter extension
Btw, I think i will add an MBean interface for the new jms consumer endpoints, so that we can change the number of concurrent consumers on a queue. So i you come with something interesting ... On 3/14/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: Well, i think it will be difficult without accessing ServiceMix internals. Or maybe tweaking with the mbean names factory available on the component context ? I don't recall what it gives ... On 3/14/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: > > Guillaume Nodet wrote: > > Yeah, sounds good. > > Make sure you use the facilities available on > > the ComponentContext to create the mbean names ... > Do you have special vision there? What I thought is to have it under the > > Type=Endpoint,SubType=Internal or External. But it seems not so easy. > > If the mbean name for this interface could be related > > to the endpoint name, that would make it easier to find. > > > > > On 3/13/07, Thomas TERMIN < [EMAIL PROTECTED]> wrote: > >> > >> Guillaume Nodet wrote: > >> > I mean, did you already implement the JMX part ? > >> > Which interface are you exposing to JMX ? > >> > Anyway, you should raise a JIRA ... > >> I didn't implemtet it up to now. But what I want to do is expose an > >> SwitchPredicateMBean interface where you can change some properties. > >> What do you think. This could also be done for the XpathPredicate and > so > >> on. I have implemented the SwitchPredicate and doing tests at the > moment. > >> > >> > > >> > On 3/13/07, Thomas TERMIN < [EMAIL PROTECTED]> wrote: > >> >> > >> >> Yes of course should also be changeable via JMX. > >> >> > >> >> Guillaume Nodet wrote: > >> >> > Well, it sounds good. > >> >> > What about the JMX stuff ? > >> >> > > >> >> > On 3/13/07, Thomas TERMIN < [EMAIL PROTECTED]> > wrote: > >> >> >> > >> >> >> Guillaume Nodet wrote: > >> >> >> > On 3/12/07, Thomas TERMIN < [EMAIL PROTECTED] > > wrote: > >> >> >> >> > >> >> >> >> > >> >> >> >> Peter my colleague asked if you need a switch-filter as an > EIP > >> >> >> >> > component. It does nothing more then check a property for > >> message > >> >> >> flow. > >> >> >> >> > If this property is true it sends the message to the > >> destination > >> >> and > >> >> >> if > >> >> >> >> > it is false the exchange will be discarde. This is > helpfull if > >> >> you > >> >> >> have > >> >> >> >> > different installations where some services are installed > or > >> not > >> >> >> >> > installed in servicemix. What he want to do is that you > can > >> >> >> enable or > >> >> >> >> > disbale the flow via JMX as well as an property in a > property > >> >> >> file at > >> >> >> >> > runtime. (Hope the explanation was understandable) > >> >> >> >> > >> >> >> >> > >> >> >> >> Sounds good, but I wonder wha's the difference with the > >> >> >> >> > >> >> >> > >> >> > >> > http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter > >> > >> >> > >> >> >> > >> >> >> >> > >> >> >> >> . > >> >> >> >> We only need to implement a new predicate based on > properties, > >> >> which > >> >> >> >> could > >> >> >> >> be > >> >> >> >> reused by the router for example. I'm not sure if this is > what > >> you > >> >> >> meant > >> >> >> >> or not > >> >> >> >> (maybe you were talking about a system property ?) > >> >> >> >> As for the JMX stuff, it's a very good idea. > >> >> >> >> > >> >> >> >> > >> >> >> >> I'm still not sure if you were talking about a property on > the > >> JBI > >> >> >> > exchange > >> >> >> > or a system property. There's no predicate on message > properties > >> it > >> >> >> > could be implemented easily (and should anyway). As I said, > JMX > >> >> >> controlled > >> >> >> > routers or filters would be very useful for manually > re-routing > >> >> flows, > >> >> >> etc > >> >> >> This filter is intended just as a on/off filter. > >> >> >> > >> >> >> > >> >> >> >> >> >> propertyResource="file:conf/feature.properties" > propertyName="on"/> > >> >> >> > >> >> >> > >> >> >> So as you can see above there is a spring resourece defined and > a > >> >> >> property name. This property name will be read from the > resource > >> and > >> > >> >> can > >> >> >> have the value true(on) or false(off). The property could also > >> be an > >> >> >> exchange property. The configuration would be: > >> >> >> > >> >> >> > >> >> >> >> propertyName="on"/> > >> >> >> > >> >> >> > >> >> >> > >> >> >> We implemented this just as a SwitchPredicate which just > returns > >> true > >> >> or > >> >> >> false depending on the property. > >> >> >> > >> >> >> > >> >> >> > >> >> > > >> >> > > >> >> > >> >> > >> >> -- > >> >> Thomas Termin > >> >> ___ > >> >> blue elephant systems GmbH > >> >> Wollgrasweg 49 > >> >> D-70599 Stuttgart > >> >> > >> >> Tel: (+49) 0711 - 45 10 17 676 > >> >> Fax: (+49) 0711 - 45 10 17 573 > >> >> WWW: http://www.blue-elephant-systems.com > >> >> Email : [EMAIL PROTECTED] > >> >> > >> >> blue e
Re: eip filter extension
Well, i think it will be difficult without accessing ServiceMix internals. Or maybe tweaking with the mbean names factory available on the component context ? I don't recall what it gives ... On 3/14/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: Guillaume Nodet wrote: > Yeah, sounds good. > Make sure you use the facilities available on > the ComponentContext to create the mbean names ... Do you have special vision there? What I thought is to have it under the Type=Endpoint,SubType=Internal or External. But it seems not so easy. > If the mbean name for this interface could be related > to the endpoint name, that would make it easier to find. > > On 3/13/07, Thomas TERMIN < [EMAIL PROTECTED]> wrote: >> >> Guillaume Nodet wrote: >> > I mean, did you already implement the JMX part ? >> > Which interface are you exposing to JMX ? >> > Anyway, you should raise a JIRA ... >> I didn't implemtet it up to now. But what I want to do is expose an >> SwitchPredicateMBean interface where you can change some properties. >> What do you think. This could also be done for the XpathPredicate and so >> on. I have implemented the SwitchPredicate and doing tests at the moment. >> >> > >> > On 3/13/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >> >> >> Yes of course should also be changeable via JMX. >> >> >> >> Guillaume Nodet wrote: >> >> > Well, it sounds good. >> >> > What about the JMX stuff ? >> >> > >> >> > On 3/13/07, Thomas TERMIN < [EMAIL PROTECTED]> wrote: >> >> >> >> >> >> Guillaume Nodet wrote: >> >> >> > On 3/12/07, Thomas TERMIN <[EMAIL PROTECTED] > wrote: >> >> >> >> >> >> >> >> >> >> >> >> Peter my colleague asked if you need a switch-filter as an EIP >> >> >> >> > component. It does nothing more then check a property for >> message >> >> >> flow. >> >> >> >> > If this property is true it sends the message to the >> destination >> >> and >> >> >> if >> >> >> >> > it is false the exchange will be discarde. This is helpfull if >> >> you >> >> >> have >> >> >> >> > different installations where some services are installed or >> not >> >> >> >> > installed in servicemix. What he want to do is that you can >> >> >> enable or >> >> >> >> > disbale the flow via JMX as well as an property in a property >> >> >> file at >> >> >> >> > runtime. (Hope the explanation was understandable) >> >> >> >> >> >> >> >> >> >> >> >> Sounds good, but I wonder wha's the difference with the >> >> >> >> >> >> >> >> >> >> http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter >> >> >> >> >> >> >> >> >> >> >> >> >> >> . >> >> >> >> We only need to implement a new predicate based on properties, >> >> which >> >> >> >> could >> >> >> >> be >> >> >> >> reused by the router for example. I'm not sure if this is what >> you >> >> >> meant >> >> >> >> or not >> >> >> >> (maybe you were talking about a system property ?) >> >> >> >> As for the JMX stuff, it's a very good idea. >> >> >> >> >> >> >> >> >> >> >> >> I'm still not sure if you were talking about a property on the >> JBI >> >> >> > exchange >> >> >> > or a system property. There's no predicate on message properties >> it >> >> >> > could be implemented easily (and should anyway). As I said, JMX >> >> >> controlled >> >> >> > routers or filters would be very useful for manually re-routing >> >> flows, >> >> >> etc >> >> >> This filter is intended just as a on/off filter. >> >> >> >> >> >> >> >> >> > >> >> propertyResource="file:conf/feature.properties" propertyName="on"/> >> >> >> >> >> >> >> >> >> So as you can see above there is a spring resourece defined and a >> >> >> property name. This property name will be read from the resource >> and >> >> >> can >> >> >> have the value true(on) or false(off). The property could also >> be an >> >> >> exchange property. The configuration would be: >> >> >> >> >> >> >> >> >> > propertyName="on"/> >> >> >> >> >> >> >> >> >> >> >> >> We implemented this just as a SwitchPredicate which just returns >> true >> >> or >> >> >> false depending on the property. >> >> >> >> >> >> >> >> >> >> >> > >> >> > >> >> >> >> >> >> -- >> >> Thomas Termin >> >> ___ >> >> blue elephant systems GmbH >> >> Wollgrasweg 49 >> >> D-70599 Stuttgart >> >> >> >> Tel: (+49) 0711 - 45 10 17 676 >> >> Fax: (+49) 0711 - 45 10 17 573 >> >> WWW: http://www.blue-elephant-systems.com >> >> Email : [EMAIL PROTECTED] >> >> >> >> blue elephant systems GmbH >> >> Firmensitz : Wollgrasweg 49, D-70599 Stuttgart >> >> Registergericht : Amtsgericht Stuttgart, HRB 24106 >> >> Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle >> >> >> >> >> > >> > >> >> >> -- >> Thomas Termin >> ___ >> blue elephant systems GmbH >> Wollgrasweg 49 >> D-70599 Stuttgart >> >> Tel: (+49) 0711 - 45 10 17 676 >> Fax: (+49) 0711 - 45 10 17 573 >> WWW: http://www.blue-elephant-systems.com >> Email : [EMAIL PROTECTED] >> >> blue elephant systems GmbH >> Fi
Re: Geronimo website update
Very nice ... I really like the G-theme in Nabble! Joe Hernan Cunico wrote: Hi All, there is a new direct link to Geronimo forums from the "Community" menu on the website. Check it out http://geronimo.apache.org/discussion-forums.html The links we had before were not too visible. Also updated the L&F in Nabble to make look a bit more consistent with the website. Cheers! Hernan
Re: Geronimo website update
Nice work Hernan! --jason On Mar 14, 2007, at 10:37 AM, Hernan Cunico wrote: Hi All, there is a new direct link to Geronimo forums from the "Community" menu on the website. Check it out http://geronimo.apache.org/ discussion-forums.html The links we had before were not too visible. Also updated the L&F in Nabble to make look a bit more consistent with the website. Cheers! Hernan
Re: Geronimo website update
Hernan this looks great! Nabble is an excellent resource and its cool to have the Geronimo L&F applied to it. Best wishes, Paul On 3/14/07, Hernan Cunico <[EMAIL PROTECTED]> wrote: Hi All, there is a new direct link to Geronimo forums from the "Community" menu on the website. Check it out http://geronimo.apache.org/discussion-forums.html The links we had before were not too visible. Also updated the L&F in Nabble to make look a bit more consistent with the website. Cheers! Hernan
Re: [RESULT] VOTE J2G Conversion tool acceptance
Thanks Dims. Now that the paperwork has been ack'd here's the final patch for the IP clearance form. Once that's in place I'll notify [EMAIL PROTECTED] that we're ready to move forward with checking the code into SVN. Best wishes, Paul Index: site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml === --- site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml (revision 518229) +++ site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml (working copy) @@ -94,7 +94,7 @@ - Not yet done + March-13-2007 Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the On 3/13/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: Paul, I've checked in the xml, generated the html and svn up'ed the incubator site. Should show up on line in a few hours. thanks, dims On 3/7/07, Paul McMahan <[EMAIL PROTECTED]> wrote: > fyi I pinged [EMAIL PROTECTED] for help on patching the IP clearnance > form and resolving the last remaining item on the form. > > Best wishes, > Paul > > On 3/5/07, Paul McMahan <[EMAIL PROTECTED]> wrote: > > Thanks for the feedback Kevan. > > > > Below is a patch for the ip-clearance form that marks three of the > > remaining four items as completed. The last remaining item on the > > form is: > > "Check and make sure that the papers that transfer rights to the ASF > > been received. It is only necessary to transfer rights for the > > package, the core code, and any new code produced by the project." > > > > Can someone help complete this item or provide guidance on how to > > verify the transferal paperwork? > > > > Best wishes, > > Paul > > > > > > Index: site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml > > === > > --- site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml > > (revision 514856) > > +++ site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml (working copy) > > @@ -102,7 +102,7 @@ > > > > > > > > - Not Yet Done. > > + March-5-2007 > > > > Check and > > make sure that the files that have been donated have been > > updated to reflect the new ASF copyright. > > @@ -135,7 +135,7 @@ > > > > > > > > - Not Yet Done. > > + March-5-2007 > > > > Check and > > make sure that for all items included with the distribution > > that is not under the Apache license, we have the right to combine > > @@ -143,7 +143,7 @@ > > > > > > > > - Not Yet Done. > > + March-5-2007 > > > > Check and > > make sure that all items depended upon by the project is > > covered by one or more of the following approved licenses: Apache, > > > -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
Looking for a ServiceMix developer for File/Ftp transfer
I'm looking for a developer that can configure ServiceMix 3.1 to manage some file transfers. I need to automatize the transfer of binary files from a Windows server file system to a remote Ftp server and vivecersa. When a predermined file appears on a folder I'll transfer it to a folder of the Ftp server. If the folder is new it have to create it. Viceversa, when a predermined file appears on a folder of the Ftp server I'll transfer it to a folder of the local Windows server. If the folder is new it have to create it. Optionally, I have to delete the file from the source folder, or archive it in another folder. I'm looking for a developer that is able to produce the necessary configuration files to use the Ftp and File component of ServiceMix 3.1. Ivano Carrara -- View this message in context: http://www.nabble.com/Looking-for-a-ServiceMix-developer-for-File-Ftp-transfer-tf3403709s12049.html#a9479552 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: SAAJ integration idea
If a webservice can call another webservice locally (using the same thread), you will need to keep the original thread local value and reset it on the way out. Yes, of course. Do all the SAAJ implementations implement the same spec API version? If not you will not be able to switch implementations like this. Axis2 and CXF yes. Yesterday I got Axis1 updated so that it also implements SAAJ 1.3 API. The new methods in Axis1 will just throw OperationUnsupportedException or similar but at least they are there. > Just to clarify, the user is not expected to do the SAAJUniverse > set/unset bit. Only the web service container implementations or > service-ref builders would do that (i.e. the idea is to make it > transparent to the user as much as possible). > > Also, if a call is made within some SAAJ universe but then it is > handled by some thread pool later on, things might break. So this > solution is definitely not foolproof but hopefully good enough. It should work as long as you reset the thread local in a finally block as you have above. Right, ok. > Another idea I've had was to create a new context classloader (when > set() is called) instead of the thread local solution. That new > context classloader would first load a specific jar file for the SAAJ > implementation (the jar file would just contain SAAJ configuration > files) and delegate everything else to the existing context > classloader. That way, since the right configuration files would > appear first in the classloader, it would force the right SAAJ > implementation to be used (the SAAJ factory classes first check the > context classloader for the configuration files). I don't see how this could work as the resource data would likely be cached by Java code, so when you attempt switch to another SAAJ implementation the Java code won't notice the CL switch. Hmm... you mean that information would be cached somewhere else besides the classloader? Thanks, Jarek
Geronimo website update
Hi All, there is a new direct link to Geronimo forums from the "Community" menu on the website. Check it out http://geronimo.apache.org/discussion-forums.html The links we had before were not too visible. Also updated the L&F in Nabble to make look a bit more consistent with the website. Cheers! Hernan
Re: svn commit: r518224 - /geronimo/server/branches/1.2/pom.xml
Do incubating jars not make it into central (and on to mirrors)? --jason On Mar 14, 2007, at 10:23 AM, [EMAIL PROTECTED] wrote: Author: rickmcguire Date: Wed Mar 14 10:23:02 2007 New Revision: 518224 URL: http://svn.apache.org/viewvc?view=rev&rev=518224 Log: GERONIMO-2967 Update the yoko dependencies to the M2 release level. Modified: geronimo/server/branches/1.2/pom.xml Modified: geronimo/server/branches/1.2/pom.xml URL: http://svn.apache.org/viewvc/geronimo/server/branches/1.2/ pom.xml?view=diff&rev=518224&r1=518223&r2=518224 == --- geronimo/server/branches/1.2/pom.xml (original) +++ geronimo/server/branches/1.2/pom.xml Wed Mar 14 10:23:02 2007 @@ -477,25 +477,25 @@ org.apache.yoko yoko-core -1.0-incubating-M2-SNAPSHOT +1.0-incubating-M2 org.apache.yoko yoko-spec-corba -1.0-incubating-M2-SNAPSHOT +1.0-incubating-M2 org.apache.yoko yoko-rmi-spec -1.0-incubating-M2-SNAPSHOT +1.0-incubating-M2 org.apache.yoko yoko-rmi-impl -1.0-incubating-M2-SNAPSHOT +1.0-incubating-M2 @@ -1268,6 +1268,21 @@ false + + + + +apache-incubator +Apache Incubator Repository +http://people.apache.org/repo/m2-incubating- repository +default + +true +daily +ignore + + +true
[jira] Created: (GERONIMO-2969) Transaction recovery broken for MDBs
Transaction recovery broken for MDBs Key: GERONIMO-2969 URL: https://issues.apache.org/jira/browse/GERONIMO-2969 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: connector, OpenEJB Reporter: Dain Sundstrom Transaction recovery for MDBs is not currently working because the OpenEJB MdbContainer does not register the XAResources from an ActivationSpec with the Geronimo transaction manager. This means that Geronimo has no resource name to write in to the transaction recovery log. I commented out the code in the HowlLog that enforces a registered name to the MDB container will function, but the recover process will not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: MDBs working in 2.0
On Mar 14, 2007, at 5:46 AM, Kevan Miller wrote: On Mar 14, 2007, at 3:53 AM, Dain Sundstrom wrote: I believe that I have MDBs working in 2.0 (and the tck). In general they should work about as well as Stateless beans do, but haven't received as much testing. That's great. Nice stuff. I also believe I have broken transaction recovery for the time being. K. Did you create a Jira so that we can keep track of this? Don't want it to be forgotten... Some information on how it's broken would be helpful. GERONIMO-2969 -dain
[jira] Updated: (GERONIMO-2968) Hide Bogus Tomcat 5.5 error message when running on Java SE 5
[ https://issues.apache.org/jira/browse/GERONIMO-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-2968: --- Affects Version/s: 1.2 Fix Version/s: 1.2 Assignee: (was: Donald Woods) Unassigning myself so a committer can apply it. > Hide Bogus Tomcat 5.5 error message when running on Java SE 5 > - > > Key: GERONIMO-2968 > URL: https://issues.apache.org/jira/browse/GERONIMO-2968 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Logging >Affects Versions: 1.1.1, 1.1.2, 1.2 > Environment: Java SE 5 >Reporter: Donald Woods >Priority: Minor > Fix For: 1.1.2, 1.2 > > Attachments: G2968-1.1.1.patch > > > Tomcat 5.5.x will generate the following exception when DEBUG logging is > enabled in the geronimo.log file when run on a Java SE 5 JVM, since Tomcat > 5.5.x was compiled using the Sun 1.4.2 SDK and the JSSE15 classes were not > generated (and the message can be ignored) - > 13:09:15,156 DEBUG [JSSEImplementation] Error getting factory: > org.apache.tomcat.util.net.jsse.JSSE15Factory > java.lang.ClassNotFoundException: > org.apache.tomcat.util.net.jsse.JSSE15Factory > at java.lang.Class.forNameImpl(Native Method) > at java.lang.Class.forName(Class.java:127) > at > org.apache.tomcat.util.net.jsse.JSSEImplementation.(JSSEImplementation.java:53) > at > org.apache.tomcat.util.net.SSLImplementation.getInstance(SSLImplementation.java:70) > at > org.apache.tomcat.util.net.SSLImplementation.getInstance(SSLImplementation.java:47) > at > org.apache.tomcat.util.net.SSLImplementation.getInstance(SSLImplementation.java:63) > at > org.apache.coyote.http11.Http11BaseProtocol.checkSocketFactory(Http11BaseProtocol.java:732) > at > org.apache.coyote.http11.Http11BaseProtocol.init(Http11BaseProtocol.java:123) > at > org.apache.catalina.connector.Connector.initialize(Connector.java:1016) > at > org.apache.catalina.core.StandardService.addConnector(StandardService.java:260) > at org.apache.catalina.startup.Embedded.addConnector(Embedded.java:326) > at > org.apache.geronimo.tomcat.TomcatContainer.addConnector(TomcatContainer.java:341) > at > org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817) > at > org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) > at > org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) > at > org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$1a3cefb5.addConnector() > at > org.apache.geronimo.tomcat.ConnectorGBean.doStart(ConnectorGBean.java:129) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146) > at > org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBean
[jira] Updated: (GERONIMO-2968) Hide Bogus Tomcat 5.5 error message when running on Java SE 5
[ https://issues.apache.org/jira/browse/GERONIMO-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-2968: --- Attachment: G2968-1.1.1.patch Patch adds the following to server-log4j.properties for the J2EE and Minimal Tomcat assemblies - log4j.category.org.apache.tomcat.util.net.jsse.JSSEImplementation=WARN Also adds the following to reduce Tomcat logging - log4j.category.org.apache.catalina.loader.WebappClassLoader=WARN log4j.category.org.apache.tomcat.util.net.SSLImplementation=WARN Syncs up the minimal assemblies file with the missing entry of - log4j.category.org.apache.catalina.core.StandardContext=WARN > Hide Bogus Tomcat 5.5 error message when running on Java SE 5 > - > > Key: GERONIMO-2968 > URL: https://issues.apache.org/jira/browse/GERONIMO-2968 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Logging >Affects Versions: 1.1.1, 1.1.2, 1.2 > Environment: Java SE 5 >Reporter: Donald Woods > Assigned To: Donald Woods >Priority: Minor > Fix For: 1.1.2, 1.2 > > Attachments: G2968-1.1.1.patch > > > Tomcat 5.5.x will generate the following exception when DEBUG logging is > enabled in the geronimo.log file when run on a Java SE 5 JVM, since Tomcat > 5.5.x was compiled using the Sun 1.4.2 SDK and the JSSE15 classes were not > generated (and the message can be ignored) - > 13:09:15,156 DEBUG [JSSEImplementation] Error getting factory: > org.apache.tomcat.util.net.jsse.JSSE15Factory > java.lang.ClassNotFoundException: > org.apache.tomcat.util.net.jsse.JSSE15Factory > at java.lang.Class.forNameImpl(Native Method) > at java.lang.Class.forName(Class.java:127) > at > org.apache.tomcat.util.net.jsse.JSSEImplementation.(JSSEImplementation.java:53) > at > org.apache.tomcat.util.net.SSLImplementation.getInstance(SSLImplementation.java:70) > at > org.apache.tomcat.util.net.SSLImplementation.getInstance(SSLImplementation.java:47) > at > org.apache.tomcat.util.net.SSLImplementation.getInstance(SSLImplementation.java:63) > at > org.apache.coyote.http11.Http11BaseProtocol.checkSocketFactory(Http11BaseProtocol.java:732) > at > org.apache.coyote.http11.Http11BaseProtocol.init(Http11BaseProtocol.java:123) > at > org.apache.catalina.connector.Connector.initialize(Connector.java:1016) > at > org.apache.catalina.core.StandardService.addConnector(StandardService.java:260) > at org.apache.catalina.startup.Embedded.addConnector(Embedded.java:326) > at > org.apache.geronimo.tomcat.TomcatContainer.addConnector(TomcatContainer.java:341) > at > org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817) > at > org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) > at > org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) > at > org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$1a3cefb5.addConnector() > at > org.apache.geronimo.tomcat.ConnectorGBean.doStart(ConnectorGBean.java:129) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146) > at > org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart
[jira] Closed: (GERONIMO-2967) Update the yoko dependencies to the M2 release level.
[ https://issues.apache.org/jira/browse/GERONIMO-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed GERONIMO-2967. -- Resolution: Fixed Committed revision 518212. -- openejb2 Committed revision 518224. -- Geronimo > Update the yoko dependencies to the M2 release level. > - > > Key: GERONIMO-2967 > URL: https://issues.apache.org/jira/browse/GERONIMO-2967 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: CORBA >Affects Versions: 1.2 >Reporter: Rick McGuire > Assigned To: Rick McGuire > Fix For: 1.2 > > > The Yoko 1.0-incubating-M2 release has just been put out. It's time to > update the openejb/Geronimo dependencies for the 1.2 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Code donation] J2G Conversion tool
The IBM and Covalent grants for the J2G Migration toolset (as described here and in https://issues.apache.org/jira/browse/ GERONIMO-2743) have been rec'd and filed.
Re: SAAJ integration idea
On Mar 14, 2007, at 8:15 AM, Jarek Gawor wrote:
I'm working on the SAAJ integration in Geronimo. I have the following
idea on how to integrate it and I would applicate any comments,
suggestions, better solutions, etc.
We have three different SAAJ implementations to work with: Axis1,
Axis2, and Sun. And we can't really just use one as Axis1/Axis2 expect
their own implementations. Also, please keep in mind that within the
same module we can have both JAX-RPC and JAX-WS web services.
Now, in G code in certain places we know exactly what sort of SAAJ
implementation should be used. For example, if I'm invoking a Axis2
service, it should be using Axis2 SAAJ implementation. Or if I'm
calling a JAX-RPC service (using service-ref) Axis1 SAAJ
implementation should be used, and so on. So the idea is this:
First, in such places that we know what implementation should be used,
set the SAAJ implementation preference explicitly. For example:
SAAJUniverse universe = new SAAJUniverse(SAAJUniverse.Axis1);
universe.set();
try {
// invoke the web service
} finally {
universe.unset();
}
The .set() method would set some thread local variable with the SAAJ
implementation preference.
If a webservice can call another webservice locally (using the same
thread), you will need to keep the original thread local value and
reset it on the way out.
Second, we would provide our own implementations of the different SAAJ
Factory classes. These factory classes would just check that thread
local preference variable and return the appropriate factory instance.
Or if no preference is set, default to Sun's implementation.
Do all the SAAJ implementations implement the same spec API version?
If not you will not be able to switch implementations like this.
Just to clarify, the user is not expected to do the SAAJUniverse
set/unset bit. Only the web service container implementations or
service-ref builders would do that (i.e. the idea is to make it
transparent to the user as much as possible).
Also, if a call is made within some SAAJ universe but then it is
handled by some thread pool later on, things might break. So this
solution is definitely not foolproof but hopefully good enough.
It should work as long as you reset the thread local in a finally
block as you have above.
Another idea I've had was to create a new context classloader (when
set() is called) instead of the thread local solution. That new
context classloader would first load a specific jar file for the SAAJ
implementation (the jar file would just contain SAAJ configuration
files) and delegate everything else to the existing context
classloader. That way, since the right configuration files would
appear first in the classloader, it would force the right SAAJ
implementation to be used (the SAAJ factory classes first check the
context classloader for the configuration files).
I don't see how this could work as the resource data would likely be
cached by Java code, so when you attempt switch to another SAAJ
implementation the Java code won't notice the CL switch.
Thoughts?
I was worried that we would have to force all WS stacks to a common
SAAJ implementation, but this may just work.
-dain
[jira] Created: (GERONIMO-2968) Hide Bogus Tomcat 5.5 error message when running on Java SE 5
Hide Bogus Tomcat 5.5 error message when running on Java SE 5 - Key: GERONIMO-2968 URL: https://issues.apache.org/jira/browse/GERONIMO-2968 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Logging Affects Versions: 1.1.1, 1.1.2 Environment: Java SE 5 Reporter: Donald Woods Assigned To: Donald Woods Priority: Minor Fix For: 1.1.2 Tomcat 5.5.x will generate the following exception when DEBUG logging is enabled in the geronimo.log file when run on a Java SE 5 JVM, since Tomcat 5.5.x was compiled using the Sun 1.4.2 SDK and the JSSE15 classes were not generated (and the message can be ignored) - 13:09:15,156 DEBUG [JSSEImplementation] Error getting factory: org.apache.tomcat.util.net.jsse.JSSE15Factory java.lang.ClassNotFoundException: org.apache.tomcat.util.net.jsse.JSSE15Factory at java.lang.Class.forNameImpl(Native Method) at java.lang.Class.forName(Class.java:127) at org.apache.tomcat.util.net.jsse.JSSEImplementation.(JSSEImplementation.java:53) at org.apache.tomcat.util.net.SSLImplementation.getInstance(SSLImplementation.java:70) at org.apache.tomcat.util.net.SSLImplementation.getInstance(SSLImplementation.java:47) at org.apache.tomcat.util.net.SSLImplementation.getInstance(SSLImplementation.java:63) at org.apache.coyote.http11.Http11BaseProtocol.checkSocketFactory(Http11BaseProtocol.java:732) at org.apache.coyote.http11.Http11BaseProtocol.init(Http11BaseProtocol.java:123) at org.apache.catalina.connector.Connector.initialize(Connector.java:1016) at org.apache.catalina.core.StandardService.addConnector(StandardService.java:260) at org.apache.catalina.startup.Embedded.addConnector(Embedded.java:326) at org.apache.geronimo.tomcat.TomcatContainer.addConnector(TomcatContainer.java:341) at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke() at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$1a3cefb5.addConnector() at org.apache.geronimo.tomcat.ConnectorGBean.doStart(ConnectorGBean.java:129) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.
[jira] Commented: (GERONIMO-2964) Cannot specify the Tomcat work directory for a web application
[ https://issues.apache.org/jira/browse/GERONIMO-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480838 ] Jeff Genender commented on GERONIMO-2964: - The config XSDs need updating as well. > Cannot specify the Tomcat work directory for a web application > -- > > Key: GERONIMO-2964 > URL: https://issues.apache.org/jira/browse/GERONIMO-2964 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 1.2 >Reporter: Aman Nanner >Priority: Minor > Fix For: 1.2 > > Attachments: tomcat-workdir.patch > > > In Tomcat, a work directory can be specified for a web application in a > WEB-INF/context.xml file. The GeronimoStandardContext does not permit the > user to specify a work directory, and so the work directory defaults to > var/catalina/work/. > I've submitted a patch file that modifies the geronimo-tomcat-1.2 schema to > permit the user to optionally specify a work directory. This work directory > is then propagated into the TomcatContext. I've tested this and it seems to > work well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: eip filter extension
Guillaume Nodet wrote: > Yeah, sounds good. > Make sure you use the facilities available on > the ComponentContext to create the mbean names ... Do you have special vision there? What I thought is to have it under the Type=Endpoint,SubType=Internal or External. But it seems not so easy. > If the mbean name for this interface could be related > to the endpoint name, that would make it easier to find. > > On 3/13/07, Thomas TERMIN < [EMAIL PROTECTED]> wrote: >> >> Guillaume Nodet wrote: >> > I mean, did you already implement the JMX part ? >> > Which interface are you exposing to JMX ? >> > Anyway, you should raise a JIRA ... >> I didn't implemtet it up to now. But what I want to do is expose an >> SwitchPredicateMBean interface where you can change some properties. >> What do you think. This could also be done for the XpathPredicate and so >> on. I have implemented the SwitchPredicate and doing tests at the moment. >> >> > >> > On 3/13/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >> >> >> Yes of course should also be changeable via JMX. >> >> >> >> Guillaume Nodet wrote: >> >> > Well, it sounds good. >> >> > What about the JMX stuff ? >> >> > >> >> > On 3/13/07, Thomas TERMIN < [EMAIL PROTECTED]> wrote: >> >> >> >> >> >> Guillaume Nodet wrote: >> >> >> > On 3/12/07, Thomas TERMIN <[EMAIL PROTECTED] > wrote: >> >> >> >> >> >> >> >> >> >> >> >> Peter my colleague asked if you need a switch-filter as an EIP >> >> >> >> > component. It does nothing more then check a property for >> message >> >> >> flow. >> >> >> >> > If this property is true it sends the message to the >> destination >> >> and >> >> >> if >> >> >> >> > it is false the exchange will be discarde. This is helpfull if >> >> you >> >> >> have >> >> >> >> > different installations where some services are installed or >> not >> >> >> >> > installed in servicemix. What he want to do is that you can >> >> >> enable or >> >> >> >> > disbale the flow via JMX as well as an property in a property >> >> >> file at >> >> >> >> > runtime. (Hope the explanation was understandable) >> >> >> >> >> >> >> >> >> >> >> >> Sounds good, but I wonder wha's the difference with the >> >> >> >> >> >> >> >> >> >> http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter >> >> >> >> >> >> >> >> >> >> >> >> >> >> . >> >> >> >> We only need to implement a new predicate based on properties, >> >> which >> >> >> >> could >> >> >> >> be >> >> >> >> reused by the router for example. I'm not sure if this is what >> you >> >> >> meant >> >> >> >> or not >> >> >> >> (maybe you were talking about a system property ?) >> >> >> >> As for the JMX stuff, it's a very good idea. >> >> >> >> >> >> >> >> >> >> >> >> I'm still not sure if you were talking about a property on the >> JBI >> >> >> > exchange >> >> >> > or a system property. There's no predicate on message properties >> it >> >> >> > could be implemented easily (and should anyway). As I said, JMX >> >> >> controlled >> >> >> > routers or filters would be very useful for manually re-routing >> >> flows, >> >> >> etc >> >> >> This filter is intended just as a on/off filter. >> >> >> >> >> >> >> >> >> > >> >> propertyResource="file:conf/feature.properties" propertyName="on"/> >> >> >> >> >> >> >> >> >> So as you can see above there is a spring resourece defined and a >> >> >> property name. This property name will be read from the resource >> and >> >> >> can >> >> >> have the value true(on) or false(off). The property could also >> be an >> >> >> exchange property. The configuration would be: >> >> >> >> >> >> >> >> >> > propertyName="on"/> >> >> >> >> >> >> >> >> >> >> >> >> We implemented this just as a SwitchPredicate which just returns >> true >> >> or >> >> >> false depending on the property. >> >> >> >> >> >> >> >> >> >> >> > >> >> > >> >> >> >> >> >> -- >> >> Thomas Termin >> >> ___ >> >> blue elephant systems GmbH >> >> Wollgrasweg 49 >> >> D-70599 Stuttgart >> >> >> >> Tel: (+49) 0711 - 45 10 17 676 >> >> Fax: (+49) 0711 - 45 10 17 573 >> >> WWW: http://www.blue-elephant-systems.com >> >> Email : [EMAIL PROTECTED] >> >> >> >> blue elephant systems GmbH >> >> Firmensitz : Wollgrasweg 49, D-70599 Stuttgart >> >> Registergericht : Amtsgericht Stuttgart, HRB 24106 >> >> Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle >> >> >> >> >> > >> > >> >> >> -- >> Thomas Termin >> ___ >> blue elephant systems GmbH >> Wollgrasweg 49 >> D-70599 Stuttgart >> >> Tel: (+49) 0711 - 45 10 17 676 >> Fax: (+49) 0711 - 45 10 17 573 >> WWW: http://www.blue-elephant-systems.com >> Email : [EMAIL PROTECTED] >> >> blue elephant systems GmbH >> Firmensitz : Wollgrasweg 49, D-70599 Stuttgart >> Registergericht : Amtsgericht Stuttgart, HRB 24106 >> Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle >> >> > > -- Thomas Termin ___ blue elep
[jira] Commented: (GERONIMO-2964) Cannot specify the Tomcat work directory for a web application
[ https://issues.apache.org/jira/browse/GERONIMO-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480830 ] Paul McMahan commented on GERONIMO-2964: OK I understand that for your requirements that the current functionality does not suffice. A visual inspection of the patch looks good. The 1.2 release is in the final stretch of testing and preparation right now, so I think we should wait until a maintenance branch is created where we can add this enhancement. It could go into the 2.0 release at that time as well. > Cannot specify the Tomcat work directory for a web application > -- > > Key: GERONIMO-2964 > URL: https://issues.apache.org/jira/browse/GERONIMO-2964 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 1.2 >Reporter: Aman Nanner >Priority: Minor > Fix For: 1.2 > > Attachments: tomcat-workdir.patch > > > In Tomcat, a work directory can be specified for a web application in a > WEB-INF/context.xml file. The GeronimoStandardContext does not permit the > user to specify a work directory, and so the work directory defaults to > var/catalina/work/. > I've submitted a patch file that modifies the geronimo-tomcat-1.2 schema to > permit the user to optionally specify a work directory. This work directory > is then propagated into the TomcatContext. I've tested this and it seems to > work well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2967) Update the yoko dependencies to the M2 release level.
Update the yoko dependencies to the M2 release level. - Key: GERONIMO-2967 URL: https://issues.apache.org/jira/browse/GERONIMO-2967 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: CORBA Affects Versions: 1.2 Reporter: Rick McGuire Assigned To: Rick McGuire Fix For: 1.2 The Yoko 1.0-incubating-M2 release has just been put out. It's time to update the openejb/Geronimo dependencies for the 1.2 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2678) Exception parsing a XML with Digester
[ https://issues.apache.org/jira/browse/GERONIMO-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480824 ] Alwin Joseph commented on GERONIMO-2678: Hi I also faced ClassNotFoundException problem for my class when used with digester and WAS CE 1.1 . Enabling inverse class loading will resolve this problem > Exception parsing a XML with Digester > - > > Key: GERONIMO-2678 > URL: https://issues.apache.org/jira/browse/GERONIMO-2678 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 1.1.1 > Environment: Windows XP SP2, Geronimo 1.1.1 with Tomcat >Reporter: Sergio Montesa > > My web application, deploy in geronimo, parse with Digester the following XML: > > > >name="ing__yy" > schema="ingres" > connection-driver="ca.edbc.jdbc.EdbcDriver" > url="jdbc:edbc://host:1919/bdd;CURSOR=READONLY" > username="user" > password="passwd" > jndi="" > /> > > and generate this exception: > java.lang.ClassNotFoundException: com.unizar.sql.DataSource in classloader > geronimo/tomcat/1.1.1/car > > org.apache.commons.digester.Digester.createSAXException(Digester.java:2792) > > org.apache.commons.digester.Digester.createSAXException(Digester.java:2818) > org.apache.commons.digester.Digester.startElement(Digester.java:1289) > org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) > > org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown > Source) > > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown > Source) > > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > org.apache.commons.digester.Digester.parse(Digester.java:1591) > com.unizar.sql.DataSourceCollection.parse(Unknown Source) > com.unizar.sql.DataSourceCollection.parse(Unknown Source) > org.apache.jsp.benchXml_jsp._jspService(org.apache.jsp.benchXml_jsp:136) > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) > javax.servlet.http.HttpServlet.service(HttpServlet.java:688) > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > javax.servlet.http.HttpServlet.service(HttpServlet.java:688) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2964) Cannot specify the Tomcat work directory for a web application
[ https://issues.apache.org/jira/browse/GERONIMO-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480823 ] Aman Nanner commented on GERONIMO-2964: --- Thanks for your comment. I actually want to set the workdir for JSPs on a per-web-application basis, which is why I provided the solution above. > Cannot specify the Tomcat work directory for a web application > -- > > Key: GERONIMO-2964 > URL: https://issues.apache.org/jira/browse/GERONIMO-2964 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 1.2 >Reporter: Aman Nanner >Priority: Minor > Fix For: 1.2 > > Attachments: tomcat-workdir.patch > > > In Tomcat, a work directory can be specified for a web application in a > WEB-INF/context.xml file. The GeronimoStandardContext does not permit the > user to specify a work directory, and so the work directory defaults to > var/catalina/work/. > I've submitted a patch file that modifies the geronimo-tomcat-1.2 schema to > permit the user to optionally specify a work directory. This work directory > is then propagated into the TomcatContext. I've tested this and it seems to > work well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: G 2.0 + Jetty taking forever to start...
A little experimentation with Matt's cooperation indicates a big culprit is fixed by the patch to GERONIMO-2693. If this is annoying people a lot I could apply the current version, otherwise I'd like to see if I can fix the remaining duplicates. (and maybe even write a test). thanks david jencks On Mar 14, 2007, at 10:24 AM, Hernan Cunico wrote: Just in case it may help, these are the startup times for Tomcat on a Windows XP (three runs in sequence) 1.- 46 2.- 31 3.- 26 did other 3 more runs and the time was just about the same as the third one These are the startup times for Jetty (on the same Windows XP box) Booting Geronimo Kernel (in Java 1.5.0_06)... Module 1/26 org.apache.geronimo.configs/rmi-naming/2.0-SNAPSHOT/ car started in .312s Module 2/26 org.apache.geronimo.configs/j2ee-server/2.0-SNAPSHOT/ carstarted in .188s Module 3/26 org.apache.geronimo.configs/transaction-jta11/2.0- SNAPSHOT/car started in .359s Module 4/26 org.apache.geronimo.configs/j2ee-security/2.0-SNAPSHOT/ car started in .469s Module 5/26 org.apache.geronimo.configs/openejb/2.0-SNAPSHOT/ carstarted in 5.907s Module 6/26 org.apache.geronimo.configs/system-database/2.0- SNAPSHOT/carstarted in .000s Module 7/26 org.apache.geronimo.configs/activemq-broker/2.0- SNAPSHOT/carstarted in 2.812s Module 8/26 org.apache.geronimo.configs/activemq/2.0-SNAPSHOT/ car started in .750s Module 9/26 org.apache.geronimo.configs/jetty6/2.0-SNAPSHOT/ car started in 1.062s Module 10/26 org.apache.geronimo.configs/geronimo-gbean-deployer/ 2.0-SNAPSHOT/carstarted in .282s Module 11/26 org.apache.geronimo.configs/j2ee-deployer/2.0-SNAPSHOT/ car started in .328s Module 12/26 org.apache.geronimo.configs/connector-deployer/2.0- SNAPSHOT/car started in .172s Module 13/26 org.apache.geronimo.configs/persistence-jpa10-deployer/ 2.0-SNAPSHOT/car started in .109s Module 14/26 org.apache.geronimo.configs/openejb-deployer/2.0- SNAPSHOT/car started in .218s Module 15/26 org.apache.geronimo.configs/client-deployer/2.0- SNAPSHOT/carstarted in .094s Module 16/26 org.apache.geronimo.configs/cxf-deployer/2.0-SNAPSHOT/ car started in .235s Module 17/26 org.apache.geronimo.configs/axis-deployer/2.0-SNAPSHOT/ car started in .703s Module 18/26 org.apache.geronimo.configs/javamail/2.0-SNAPSHOT/ car started in .063s Module 19/26 org.apache.geronimo.configs/sharedlib/2.0-SNAPSHOT/ car started in .000s Module 20/26 org.apache.geronimo.configs/jetty6-deployer/2.0- SNAPSHOT/carstarted in .265s Module 21/26 org.apache.geronimo.configs/welcome-jetty/2.0-SNAPSHOT/ car started in 27.516s Module 22/26 org.apache.geronimo.configs/dojo-jetty6/2.0-SNAPSHOT/ carstarted in 23.969s Module 23/26 org.apache.geronimo.configs/webconsole-jetty6/2.0- SNAPSHOT/car 10:13:35,546 WARN [WebXmlParser] Ignored element 'dispatcher' as child of 'filter-mapping'. started in 3:50.297s Module 24/26 org.apache.geronimo.configs/remote-deploy-jetty/2.0- SNAPSHOT/carstarted in 23.875s Module 25/26 org.apache.geronimo.configs/hot-deployer/2.0-SNAPSHOT/ car started in .469s Module 26/26 org.apache.geronimo.configs/jsr88-rar-configurer/2.0- SNAPSHOT/car started in .110s Startup completed in 324 seconds It seems to take nearly double the time on Windows boxes. I tried these on rev #518074 Cheers! Hernan Jason Dillon wrote: FYI... The Tomcat flavor boots up *much* quicker... in ~20 seconds. --jason On Mar 13, 2007, at 12:59 AM, Jason Dillon wrote: Anyone notice that it takes a long, long... long time for the server to start now? I've not yet tried Tomcat, but the Jetty flavor appears to take *very* long time to boot up: Odd that the "started in" message appears before the rest of the startup output too... :-( [INFO] [geronimo:start] [INFO] Using assembly configuration: jetty [INFO] snapshot org.apache.geronimo.assemblies:geronimo-jetty6- jee5:2.0-SNAPSHOT: checking for updates from apache-snapshots [INFO] snapshot org.apache.geronimo.assemblies:geronimo-jetty6- jee5:2.0-SNAPSHOT: checking for updates from axis2-m2-repo [INFO] snapshot org.apache.geronimo.assemblies:geronimo-jetty6- jee5:2.0-SNAPSHOT: checking for updates from codehaus-snapshots [INFO] snapshot org.apache.geronimo.assemblies:geronimo-jetty6- jee5:2.0-SNAPSHOT: checking for updates from apache.snapshots [INFO] Using assembly artifact: org.apache.geronimo.assemblies:geronimo-jetty6-jee5:zip:bin:2.0- SNAPSHOT [INFO] Using geronimoHome: /Users/jason/ws/geronimo/server/target/ geronimo-jetty6-jee5-2.0-SNAPSHOT [INFO] Uninstalling: /Users/jason/ws/geronimo/server/target/ geronimo-jetty6-jee5-2.0-SNAPSHOT [INFO
[jira] Updated: (GERONIMO-2966) [Code donation] Web2 Plugins
[ https://issues.apache.org/jira/browse/GERONIMO-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Faelnar updated GERONIMO-2966: -- Attachment: IBM-Web20Plugins-CCLA.pdf > [Code donation] Web2 Plugins > > > Key: GERONIMO-2966 > URL: https://issues.apache.org/jira/browse/GERONIMO-2966 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Affects Versions: 1.1.x > Environment: MS Windows XP SP2 (although Java based should work on > any OS supporting Java) >Reporter: Jeffrey Faelnar >Priority: Minor > Fix For: 1.1.x > > Attachments: IBM-Web20Plugins-CCLA.pdf, web2-plugins-0.1.1.zip > > > IBM has developed a set of Web2.0 plugins for Apache Geronimo. The first > two, the DOJO plug-in and the JSON-RPC-Java plug-in, will supply Geronimo > with client and server side support of AJAX technology. Developers will > create Web applications where the client side is implemented with the help of > a DOJO library and makes JSON-RPC calls to the server side business logic > exposed as a coarse-grained façade JavaBean. To add DOJO library support > developers need to make their applications dependent on the DOJO plug-in and > similarly to handle JSON-RPC calls using JSON-RPC-Java library developers > need to make the applications dependent on the JSON-RPC plug-in. > The remaining Feeds plug-in will allow developers to easily create RSS 1.0, > RSS 2.0 and ATOM 1.0 syndication feeds. The plug-in will be used in one of > two ways. Developers will implement feeds so that they are accessed through > the Feeds plug-in acting as an already deployed Web module. In addition, > developers can implement feeds as separately deployed Web applications that > use some functionality of the Feeds plug-in. > Attached are the plugins and IBM's CCLA. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2966) [Code donation] Web2 Plugins
[ https://issues.apache.org/jira/browse/GERONIMO-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Faelnar updated GERONIMO-2966: -- Attachment: web2-plugins-0.1.1.zip > [Code donation] Web2 Plugins > > > Key: GERONIMO-2966 > URL: https://issues.apache.org/jira/browse/GERONIMO-2966 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Affects Versions: 1.1.x > Environment: MS Windows XP SP2 (although Java based should work on > any OS supporting Java) >Reporter: Jeffrey Faelnar >Priority: Minor > Fix For: 1.1.x > > Attachments: web2-plugins-0.1.1.zip > > > IBM has developed a set of Web2.0 plugins for Apache Geronimo. The first > two, the DOJO plug-in and the JSON-RPC-Java plug-in, will supply Geronimo > with client and server side support of AJAX technology. Developers will > create Web applications where the client side is implemented with the help of > a DOJO library and makes JSON-RPC calls to the server side business logic > exposed as a coarse-grained façade JavaBean. To add DOJO library support > developers need to make their applications dependent on the DOJO plug-in and > similarly to handle JSON-RPC calls using JSON-RPC-Java library developers > need to make the applications dependent on the JSON-RPC plug-in. > The remaining Feeds plug-in will allow developers to easily create RSS 1.0, > RSS 2.0 and ATOM 1.0 syndication feeds. The plug-in will be used in one of > two ways. Developers will implement feeds so that they are accessed through > the Feeds plug-in acting as an already deployed Web module. In addition, > developers can implement feeds as separately deployed Web applications that > use some functionality of the Feeds plug-in. > Attached are the plugins and IBM's CCLA. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2966) [Code donation] Web2 Plugins
[Code donation] Web2 Plugins Key: GERONIMO-2966 URL: https://issues.apache.org/jira/browse/GERONIMO-2966 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Affects Versions: 1.1.x Environment: MS Windows XP SP2 (although Java based should work on any OS supporting Java) Reporter: Jeffrey Faelnar Priority: Minor Fix For: 1.1.x IBM has developed a set of Web2.0 plugins for Apache Geronimo. The first two, the DOJO plug-in and the JSON-RPC-Java plug-in, will supply Geronimo with client and server side support of AJAX technology. Developers will create Web applications where the client side is implemented with the help of a DOJO library and makes JSON-RPC calls to the server side business logic exposed as a coarse-grained façade JavaBean. To add DOJO library support developers need to make their applications dependent on the DOJO plug-in and similarly to handle JSON-RPC calls using JSON-RPC-Java library developers need to make the applications dependent on the JSON-RPC plug-in. The remaining Feeds plug-in will allow developers to easily create RSS 1.0, RSS 2.0 and ATOM 1.0 syndication feeds. The plug-in will be used in one of two ways. Developers will implement feeds so that they are accessed through the Feeds plug-in acting as an already deployed Web module. In addition, developers can implement feeds as separately deployed Web applications that use some functionality of the Feeds plug-in. Attached are the plugins and IBM's CCLA. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2964) Cannot specify the Tomcat work directory for a web application
[
https://issues.apache.org/jira/browse/GERONIMO-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480820
]
Paul McMahan commented on GERONIMO-2964:
Are you interested in setting the workdir for JSPs or for the web application
in general? If for JSPs then you can specify the work dir for the JSP servlet
by setting the following param in var/catalina/conf/web.xml
{{monospaced}}
[...]
jsp
org.apache.jasper.servlet.JspServlet
scratchdir
mypath
[...]
{{monospaced}}
This solution is of course not as generic as what your patch provides because
it's only useful for JSPs. I just wanted to point out that its already
available in case that could help meet your specific requirements.
> Cannot specify the Tomcat work directory for a web application
> --
>
> Key: GERONIMO-2964
> URL: https://issues.apache.org/jira/browse/GERONIMO-2964
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Tomcat
>Affects Versions: 1.2
>Reporter: Aman Nanner
>Priority: Minor
> Fix For: 1.2
>
> Attachments: tomcat-workdir.patch
>
>
> In Tomcat, a work directory can be specified for a web application in a
> WEB-INF/context.xml file. The GeronimoStandardContext does not permit the
> user to specify a work directory, and so the work directory defaults to
> var/catalina/work/.
> I've submitted a patch file that modifies the geronimo-tomcat-1.2 schema to
> permit the user to optionally specify a work directory. This work directory
> is then propagated into the TomcatContext. I've tested this and it seems to
> work well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: In Raleigh next week
Yes. I'm also in the same area and will be available. See you next week! Jarek On 3/14/07, Lin Sun <[EMAIL PROTECTED]> wrote: Hey Dims, Yes I am in Raleigh and will be avail early next week.:) I look forward to meeting you! Lin Davanum Srinivas wrote: > Hey Lin, > Found a typo. Sorry. Will let you know when it actually makes it to > the m2 repo. > > On a related note, You and Matt are in Raleigh right? I will be there > early next week. Monday/Tues to be precise. Would you have some time > to hack on code? Is Jarek in RTP as well? > > If we have a few more folks, maybe we could have a mini-hackathon. > Though i am really sorry about the short notice. Anyone else around? > or can make it there? > > thanks, > dims > > On 3/13/07, Lin Sun <[EMAIL PROTECTED]> wrote: >> Hi Dims, >> >> No, still don't see the provider file after i clean up my axis2 files in >>c:\.m2 and build the geronimo-axis2 module. Was the provider file >> there before you copy to the m2 snapshot repo? >> >> P.S. I could only get axis2-jaxws module to build with test turned off. >> >> Lin >> >> Davanum Srinivas wrote: >> > Lin, >> > >> > Please check now when you get a chance. >> > >> > thanks, >> > dims >
[jira] Commented: (SM-882) Allow text/binary output
[
https://issues.apache.org/activemq/browse/SM-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38823
]
Hervé Bourzeix commented on SM-882:
---
Bonjour Guillaume,
Je ne me sens pas encore à l'aise mais j'aimerais beaucoup en effet participer!
Dans ta solution tu parles d'attachement, j'avoue que j'ai encore un peu du mal
à comprendre la nature exact des messages NMR.
Pour moi, un msg NMR est une structure qui contient des propriétés ainsi qu'un
corps XML.
Je n'ai pas encore compris comme déclarer et utiliser des propriétés et je ne
savais pas que l'on pouvait attacher des éléments (xml je suppose ou autre ) à
la manière d'un email (je suppose tjs bcp).
Je veux bien que tu m'expliques la solution, comment faire comprendre à XSLT que
le résultat doit être accroché au msg en sorti et comment faire comprendre à au
file-bc qu'il faut qu'il utilise un attachement plutôt que le corps?
Si tu veux que l'on en parle de vive voix mon numero est le +33499132708 ou je
peux t'appeler... une petite discussion vaut mieux qu'une centaine d'email :)
Hervé
https://issues.apache.org/activemq/browse/SM-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38820
org.apache.servicemix.expression.JAXPXPathExpression.evaluate(JAXPXPathExpression.java:114)
org.apache.servicemix.components.util.DefaultFileMarshaler.getOutputName(DefaultFileMarshaler.java:65)
org.apache.servicemix.file.FileSenderEndpoint.processInOnly(FileSenderEndpoint.java:68)
org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMSourceFromStream(SourceTransformer.java:224)
org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMSource(SourceTransformer.java:135)
org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMNode(SourceTransformer.java:289)
org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMNode(SourceTransformer.java:306)
org.apache.servicemix.expression.JAXPXPathExpression.getXMLNode(JAXPXPathExpression.java:179)
org.apache.servicemix.expression.JAXPXPathExpression.evaluate(JAXPXPathExpression.java:94)
> Allow text/binary output
>
>
> Key: SM-882
> URL: https://issues.apache.org/activemq/browse/SM-882
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-saxon
>Affects Versions: 3.1
> Environment: servicemix 3.1 , java 1.5
>Reporter: Hervé Bourzeix
>
> When outputting something else than XML , I got the following exception:
> ERROR - FileComponent - Error processing exchange InOnly[
> id: ID:MON-HBOURZEIX-1214-1173859213020-3:33
> status: Active
> role: provider
> service: {http://www.genesys.com/jbi}pervasive
> endpoint: writeParam
> in: Unable to display: org.xml.sax.SAXParseException: Content is not
> allowed in prolog.
> ]
> javax.jbi.messaging.MessagingException: org.xml.sax.SAXParseException:
> Content is not allowed in prolog.
> at
> org.apache.servicemix.expression.JAXPXPathExpression.evaluate(JAXPXPathExpression.java:114)
> at
> org.apache.servicemix.components.util.DefaultFileMarshaler.getOutputName(DefaultFileMarshaler.java:65)
> at
> org.apache.servicemix.file.FileSenderEndpoint.processInOnly(FileSenderEndpoint.java:68)
> at
> org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$W
SAAJ integration idea
I'm working on the SAAJ integration in Geronimo. I have the following
idea on how to integrate it and I would applicate any comments,
suggestions, better solutions, etc.
We have three different SAAJ implementations to work with: Axis1,
Axis2, and Sun. And we can't really just use one as Axis1/Axis2 expect
their own implementations. Also, please keep in mind that within the
same module we can have both JAX-RPC and JAX-WS web services.
Now, in G code in certain places we know exactly what sort of SAAJ
implementation should be used. For example, if I'm invoking a Axis2
service, it should be using Axis2 SAAJ implementation. Or if I'm
calling a JAX-RPC service (using service-ref) Axis1 SAAJ
implementation should be used, and so on. So the idea is this:
First, in such places that we know what implementation should be used,
set the SAAJ implementation preference explicitly. For example:
SAAJUniverse universe = new SAAJUniverse(SAAJUniverse.Axis1);
universe.set();
try {
// invoke the web service
} finally {
universe.unset();
}
The .set() method would set some thread local variable with the SAAJ
implementation preference.
Second, we would provide our own implementations of the different SAAJ
Factory classes. These factory classes would just check that thread
local preference variable and return the appropriate factory instance.
Or if no preference is set, default to Sun's implementation.
Just to clarify, the user is not expected to do the SAAJUniverse
set/unset bit. Only the web service container implementations or
service-ref builders would do that (i.e. the idea is to make it
transparent to the user as much as possible).
Also, if a call is made within some SAAJ universe but then it is
handled by some thread pool later on, things might break. So this
solution is definitely not foolproof but hopefully good enough.
Another idea I've had was to create a new context classloader (when
set() is called) instead of the thread local solution. That new
context classloader would first load a specific jar file for the SAAJ
implementation (the jar file would just contain SAAJ configuration
files) and delegate everything else to the existing context
classloader. That way, since the right configuration files would
appear first in the classloader, it would force the right SAAJ
implementation to be used (the SAAJ factory classes first check the
context classloader for the configuration files).
Thoughts?
Thanks,
Jarek
[jira] Updated: (GERONIMO-2964) Cannot specify the Tomcat work directory for a web application
[ https://issues.apache.org/jira/browse/GERONIMO-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Nanner updated GERONIMO-2964: -- Attachment: tomcat-workdir.patch Here is the patch that addresses this improvement. If there's still time left, it would be cool if this made it into Geronimo 1.2. I understand if it does not though, since it involves a schema modification. > Cannot specify the Tomcat work directory for a web application > -- > > Key: GERONIMO-2964 > URL: https://issues.apache.org/jira/browse/GERONIMO-2964 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 1.2 >Reporter: Aman Nanner >Priority: Minor > Fix For: 1.2 > > Attachments: tomcat-workdir.patch > > > In Tomcat, a work directory can be specified for a web application in a > WEB-INF/context.xml file. The GeronimoStandardContext does not permit the > user to specify a work directory, and so the work directory defaults to > var/catalina/work/. > I've submitted a patch file that modifies the geronimo-tomcat-1.2 schema to > permit the user to optionally specify a work directory. This work directory > is then propagated into the TomcatContext. I've tested this and it seems to > work well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2965) TLDs can contain listener declarations that need to hook into injection framework.
TLDs can contain listener declarations that need to hook into injection framework. -- Key: GERONIMO-2965 URL: https://issues.apache.org/jira/browse/GERONIMO-2965 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Jetty Affects Versions: 2.0-M3 Reporter: David Jencks Assigned To: David Jencks Fix For: 2.0-beta1 It turns out that tld files can also contain listener specifications and these listeners need to be scanned for annotations and injections. I think this is specific to jsp stuff so I'm inclined to make a jsp module builder extension to handle this like the myfaces one. I don't think we've gotten far enough with tomcat to know if there's a similar problem there. A MBE ought to work for both if necessary. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2964) Cannot specify the Tomcat work directory for a web application
Cannot specify the Tomcat work directory for a web application -- Key: GERONIMO-2964 URL: https://issues.apache.org/jira/browse/GERONIMO-2964 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Tomcat Affects Versions: 1.2 Reporter: Aman Nanner Priority: Minor Fix For: 1.2 Attachments: tomcat-workdir.patch In Tomcat, a work directory can be specified for a web application in a WEB-INF/context.xml file. The GeronimoStandardContext does not permit the user to specify a work directory, and so the work directory defaults to var/catalina/work/. I've submitted a patch file that modifies the geronimo-tomcat-1.2 schema to permit the user to optionally specify a work directory. This work directory is then propagated into the TomcatContext. I've tested this and it seems to work well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
test - ignore
-sachin
Re: Working on DayTrader
On Mar 14, 2007, at 10:14 AM, Christopher Blythe wrote: Matt... As I mentioned last week, I started working on a full EJB3 mode for Daytrader 2.0 on Glassfish. I was able to get this up and running under load late yesterday afternoon. So far, I have not seen any exceptions; however, I have not had a chance to verify how much data I may be stomping due to the optimistic nature of EJB3/JPA. In addition to the full workload, I also have a full set of EJB3 session and entity primitives. I will try to have a patch (and/or these changes integrated) within the next day or so. Excellent, I'd be curious as I spect everyone else would about differences you might see between Glassfish and Geronimo in terms of application behaviour. I'll focus on the EJB 2.1 stuff which I believe is currently broken. Also, if you could commit your primitive stuff that would be awesome. thanks
Re: G 2.0 + Jetty taking forever to start...
Just in case it may help, these are the startup times for Tomcat on a Windows XP (three runs in sequence) 1.- 46 2.- 31 3.- 26 did other 3 more runs and the time was just about the same as the third one These are the startup times for Jetty (on the same Windows XP box) Booting Geronimo Kernel (in Java 1.5.0_06)... Module 1/26 org.apache.geronimo.configs/rmi-naming/2.0-SNAPSHOT/car started in .312s Module 2/26 org.apache.geronimo.configs/j2ee-server/2.0-SNAPSHOT/car started in .188s Module 3/26 org.apache.geronimo.configs/transaction-jta11/2.0-SNAPSHOT/car started in .359s Module 4/26 org.apache.geronimo.configs/j2ee-security/2.0-SNAPSHOT/car started in .469s Module 5/26 org.apache.geronimo.configs/openejb/2.0-SNAPSHOT/car started in 5.907s Module 6/26 org.apache.geronimo.configs/system-database/2.0-SNAPSHOT/car started in .000s Module 7/26 org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car started in 2.812s Module 8/26 org.apache.geronimo.configs/activemq/2.0-SNAPSHOT/car started in .750s Module 9/26 org.apache.geronimo.configs/jetty6/2.0-SNAPSHOT/car started in 1.062s Module 10/26 org.apache.geronimo.configs/geronimo-gbean-deployer/2.0-SNAPSHOT/carstarted in .282s Module 11/26 org.apache.geronimo.configs/j2ee-deployer/2.0-SNAPSHOT/car started in .328s Module 12/26 org.apache.geronimo.configs/connector-deployer/2.0-SNAPSHOT/car started in .172s Module 13/26 org.apache.geronimo.configs/persistence-jpa10-deployer/2.0-SNAPSHOT/car started in .109s Module 14/26 org.apache.geronimo.configs/openejb-deployer/2.0-SNAPSHOT/car started in .218s Module 15/26 org.apache.geronimo.configs/client-deployer/2.0-SNAPSHOT/car started in .094s Module 16/26 org.apache.geronimo.configs/cxf-deployer/2.0-SNAPSHOT/car started in .235s Module 17/26 org.apache.geronimo.configs/axis-deployer/2.0-SNAPSHOT/car started in .703s Module 18/26 org.apache.geronimo.configs/javamail/2.0-SNAPSHOT/car started in .063s Module 19/26 org.apache.geronimo.configs/sharedlib/2.0-SNAPSHOT/car started in .000s Module 20/26 org.apache.geronimo.configs/jetty6-deployer/2.0-SNAPSHOT/car started in .265s Module 21/26 org.apache.geronimo.configs/welcome-jetty/2.0-SNAPSHOT/car started in 27.516s Module 22/26 org.apache.geronimo.configs/dojo-jetty6/2.0-SNAPSHOT/car started in 23.969s Module 23/26 org.apache.geronimo.configs/webconsole-jetty6/2.0-SNAPSHOT/car 10:13:35,546 WARN [WebXmlParser] Ignored element 'dispatcher' as child of 'filter-mapping'. started in 3:50.297s Module 24/26 org.apache.geronimo.configs/remote-deploy-jetty/2.0-SNAPSHOT/car started in 23.875s Module 25/26 org.apache.geronimo.configs/hot-deployer/2.0-SNAPSHOT/car started in .469s Module 26/26 org.apache.geronimo.configs/jsr88-rar-configurer/2.0-SNAPSHOT/car started in .110s Startup completed in 324 seconds It seems to take nearly double the time on Windows boxes. I tried these on rev #518074 Cheers! Hernan Jason Dillon wrote: FYI... The Tomcat flavor boots up *much* quicker... in ~20 seconds. --jason On Mar 13, 2007, at 12:59 AM, Jason Dillon wrote: Anyone notice that it takes a long, long... long time for the server to start now? I've not yet tried Tomcat, but the Jetty flavor appears to take *very* long time to boot up: Odd that the "started in" message appears before the rest of the startup output too... :-( [INFO] [geronimo:start] [INFO] Using assembly configuration: jetty [INFO] snapshot org.apache.geronimo.assemblies:geronimo-jetty6-jee5:2.0-SNAPSHOT: checking for updates from apache-snapshots [INFO] snapshot org.apache.geronimo.assemblies:geronimo-jetty6-jee5:2.0-SNAPSHOT: checking for updates from axis2-m2-repo [INFO] snapshot org.apache.geronimo.assemblies:geronimo-jetty6-jee5:2.0-SNAPSHOT: checking for updates from codehaus-snapshots [INFO] snapshot org.apache.geronimo.assemblies:geronimo-jetty6-jee5:2.0-SNAPSHOT: checking for updates from apache.snapshots [INFO] Using assembly artifact: org.apache.geronimo.assemblies:geronimo-jetty6-jee5:zip:bin:2.0-SNAPSHOT [INFO] Using geronimoHome: /Users/jason/ws/geronimo/server/target/geronimo-jetty6-jee5-2.0-SNAPSHOT [INFO] Uninstalling: /Users/jason/ws/geronimo/server/target/geronimo-jetty6-jee5-2.0-SNAPSHOT [INFO] Installing assembly... [INFO] Expanding: /Users/jason/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty6-jee5/2.0-SNAPSHOT/geronimo-jetty6-jee5-2.0-SNAPSHOT-bin.zip into /Users/jason/ws/geronimo/server/target [INFO] Starting Geronimo server... log4j:WARN No appenders could be found for logger (org.apache.geronimo.mavenplugins.geronimo.ServerProxy). log4j:WARN Please initialize
Re: geronimo start scripts
The scripts seem to work now, thx! Cheers! Hernan Jason Dillon wrote: Oh, its probably the jpa.jar muck I added... have not tested it... I _may_ have fixed it just now... can you please try? --jason On Mar 13, 2007, at 12:25 PM, Hernan Cunico wrote: Hi All, I don't remember seeing any discussion on the startup scripts not working in trunk. I can't start the server with any of the provided scripts for windows, that is geronimo.bat and startup.bat Both complain with "The system cannot find the batch label specified - set" is there anyone else seeing this problem? Cheers! Hernan
Re: Working on DayTrader
Matt... As I mentioned last week, I started working on a full EJB3 mode for Daytrader 2.0 on Glassfish. I was able to get this up and running under load late yesterday afternoon. So far, I have not seen any exceptions; however, I have not had a chance to verify how much data I may be stomping due to the optimistic nature of EJB3/JPA. In addition to the full workload, I also have a full set of EJB3 session and entity primitives. I will try to have a patch (and/or these changes integrated) within the next day or so. Chris On 3/14/07, David Jencks <[EMAIL PROTECTED]> wrote: someone just reported a problem with some required classes being in one of the app client jars and no longer being accessible to the server. I caused this recently :-) by making the app client deployer copy the files into the app client's configuration rather than the ear configuration. This makes the app client config independent of the ear config so it should be possible to deploy it without the ear config present. I'm not quite sure what the best solution isnor am I sure that having an app client as a manifest dependency of a server side component is spec compliant. I think we could either: (1) if the app client is specified as a manifest cp entry, copy it into the ear config but just as a jar, so there would be 2 copies, one in the ear and one in the app client (2) in this case make the app client config a parent of the ear config At the moment (1) sounds more reliable to me. thanks david jencks On Mar 14, 2007, at 9:42 AM, Matt Hogstrom wrote: > I'll be working on DT today. My goals are to first get the monster > deployed on trunk (and working or JIRA's opened identifying > issues). I'm also going to next look at primitives for EJB 3.0 and > see where we lack and what needs to be added. > > I suspect we would like to keep the AppClients that use WS and for > data integrity verification. Most people don't find them that > useful (only a few postings about what they are). If anyone has an > opinion one way or the other chime in. > > I know chris has done some cleanup so maybe all this is already > done :) > > -- "I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden
Re: In Raleigh next week
Hey Dims, Yes I am in Raleigh and will be avail early next week.:) I look forward to meeting you! Lin Davanum Srinivas wrote: Hey Lin, Found a typo. Sorry. Will let you know when it actually makes it to the m2 repo. On a related note, You and Matt are in Raleigh right? I will be there early next week. Monday/Tues to be precise. Would you have some time to hack on code? Is Jarek in RTP as well? If we have a few more folks, maybe we could have a mini-hackathon. Though i am really sorry about the short notice. Anyone else around? or can make it there? thanks, dims On 3/13/07, Lin Sun <[EMAIL PROTECTED]> wrote: Hi Dims, No, still don't see the provider file after i clean up my axis2 files in c:\.m2 and build the geronimo-axis2 module. Was the provider file there before you copy to the m2 snapshot repo? P.S. I could only get axis2-jaxws module to build with test turned off. Lin Davanum Srinivas wrote: > Lin, > > Please check now when you get a chance. > > thanks, > dims
Re: In Raleigh next week
I would love to be there.. You probably don't want me to hack ws related code :) Thanks Anita --- Matt Hogstrom <[EMAIL PROTECTED]> wrote: > that's excellent. Let me see what I can drum up for a place to do > this. Anita, are you up for a few days next week ? > > > On Mar 14, 2007, at 9:34 AM, Davanum Srinivas wrote: > > > Hey Lin, > > Found a typo. Sorry. Will let you know when it actually makes it to > > the m2 repo. > > > > On a related note, You and Matt are in Raleigh right? I will be > there > > early next week. Monday/Tues to be precise. Would you have some > time > > to hack on code? Is Jarek in RTP as well? > > > > If we have a few more folks, maybe we could have a mini-hackathon. > > Though i am really sorry about the short notice. Anyone else > around? > > or can make it there? > > > > thanks, > > dims > > > > On 3/13/07, Lin Sun <[EMAIL PROTECTED]> wrote: > >> Hi Dims, > >> > >> No, still don't see the provider file after i clean up my axis2 > >> files in > >>c:\.m2 and build the geronimo-axis2 module. Was the provider > > >> file > >> there before you copy to the m2 snapshot repo? > >> > >> P.S. I could only get axis2-jaxws module to build with test turned > > >> off. > >> > >> Lin > >> > >> Davanum Srinivas wrote: > >> > Lin, > >> > > >> > Please check now when you get a chance. > >> > > >> > thanks, > >> > dims > > > > It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/
Re: Working on DayTrader
someone just reported a problem with some required classes being in one of the app client jars and no longer being accessible to the server. I caused this recently :-) by making the app client deployer copy the files into the app client's configuration rather than the ear configuration. This makes the app client config independent of the ear config so it should be possible to deploy it without the ear config present. I'm not quite sure what the best solution isnor am I sure that having an app client as a manifest dependency of a server side component is spec compliant. I think we could either: (1) if the app client is specified as a manifest cp entry, copy it into the ear config but just as a jar, so there would be 2 copies, one in the ear and one in the app client (2) in this case make the app client config a parent of the ear config At the moment (1) sounds more reliable to me. thanks david jencks On Mar 14, 2007, at 9:42 AM, Matt Hogstrom wrote: I'll be working on DT today. My goals are to first get the monster deployed on trunk (and working or JIRA's opened identifying issues). I'm also going to next look at primitives for EJB 3.0 and see where we lack and what needs to be added. I suspect we would like to keep the AppClients that use WS and for data integrity verification. Most people don't find them that useful (only a few postings about what they are). If anyone has an opinion one way or the other chime in. I know chris has done some cleanup so maybe all this is already done :)
Re: In Raleigh next week
that's excellent. Let me see what I can drum up for a place to do this. Anita, are you up for a few days next week ? On Mar 14, 2007, at 9:34 AM, Davanum Srinivas wrote: Hey Lin, Found a typo. Sorry. Will let you know when it actually makes it to the m2 repo. On a related note, You and Matt are in Raleigh right? I will be there early next week. Monday/Tues to be precise. Would you have some time to hack on code? Is Jarek in RTP as well? If we have a few more folks, maybe we could have a mini-hackathon. Though i am really sorry about the short notice. Anyone else around? or can make it there? thanks, dims On 3/13/07, Lin Sun <[EMAIL PROTECTED]> wrote: Hi Dims, No, still don't see the provider file after i clean up my axis2 files in c:\.m2 and build the geronimo-axis2 module. Was the provider file there before you copy to the m2 snapshot repo? P.S. I could only get axis2-jaxws module to build with test turned off. Lin Davanum Srinivas wrote: > Lin, > > Please check now when you get a chance. > > thanks, > dims
Working on DayTrader
I'll be working on DT today. My goals are to first get the monster deployed on trunk (and working or JIRA's opened identifying issues). I'm also going to next look at primitives for EJB 3.0 and see where we lack and what needs to be added. I suspect we would like to keep the AppClients that use WS and for data integrity verification. Most people don't find them that useful (only a few postings about what they are). If anyone has an opinion one way or the other chime in. I know chris has done some cleanup so maybe all this is already done :)
In Raleigh next week
Hey Lin, Found a typo. Sorry. Will let you know when it actually makes it to the m2 repo. On a related note, You and Matt are in Raleigh right? I will be there early next week. Monday/Tues to be precise. Would you have some time to hack on code? Is Jarek in RTP as well? If we have a few more folks, maybe we could have a mini-hackathon. Though i am really sorry about the short notice. Anyone else around? or can make it there? thanks, dims On 3/13/07, Lin Sun <[EMAIL PROTECTED]> wrote: Hi Dims, No, still don't see the provider file after i clean up my axis2 files in c:\.m2 and build the geronimo-axis2 module. Was the provider file there before you copy to the m2 snapshot repo? P.S. I could only get axis2-jaxws module to build with test turned off. Lin Davanum Srinivas wrote: > Lin, > > Please check now when you get a chance. > > thanks, > dims
Re: Deployment Plan for j2ee connector
Cool! thanks for the contribution ;-) it will be great to have this doc updated
for 1.2 and 2.0 too
I hope you don't mind, I did some minor cosmetic touch-ups to make it look more
consistent with the rest of the doc (mainly changed {noformat} with {code:xml})
Also remember to use the HTML version for the reference links, like
http://cwiki.apache.org/GMOxDOC11/geronimo-raxml.html
Take a look at "Tips for writing and formatting documentation"
http://cwiki.apache.org/geronimo/tips-for-writing-and-formatting-documentation.html
let me know if we should add more tips there ;-)
Cheers!
Hernan
Kanchana Welagedara wrote:
Hi All
Finally geronimo-ra.xml has been confluenced for G1.1.I will continue
the job to bring it for G v1.2 and G v2 with in few days.
http://cwiki.apache.org/confluence/display/GMOxDOC11/geronimo-ra.xml
My special thanks to Karthiga who made this article more clear by
formatting and drawing pictures.
Thanks and Regards.
Kanchana
Easier configuration when embedding servicemix
FYI, i have committed some changes to servicemix-core (and the needed ones in xbean-spring), so that when one use a lightweight configuration, you can only declare endpoints and components will be automatically created / discovered. This leads to a much cleaner syntax: http://incubator.apache.org/servicemix/embedding.html#Embedding-Easierconfiguration -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
[jira] Commented: (GERONIMO-2962) More Improved Web GUI to 'Add new HTTPS listener'
[ https://issues.apache.org/jira/browse/GERONIMO-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480758 ] David Jencks commented on GERONIMO-2962: I don't know that it would fit in this jira issue but I think the ideal solution for password stuff is to have the tomcat connector refer to a keystore gbean similarly to how the jetty connector works. > More Improved Web GUI to 'Add new HTTPS listener' > - > > Key: GERONIMO-2962 > URL: https://issues.apache.org/jira/browse/GERONIMO-2962 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.0-M3 >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2962.patch > > > As discussed with dev list this will improve the Web GUI for the Add new > HTTPS listener for Tomcat. It will remove some of the unnecessary information > from Tomcat GUI (eg. keystore type) and create more consistency between Jetty > and Tomcat consoles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: RE : servicemix.properties
Guillaume Nodet wrote:
> This property is used to configure the
> org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean
> so I gess this class could be improved to trim the url before
> using it.
> Thomas, you can fix it, once your account is activated.
Ok. That's what I mean. ;-)
>
> On 3/14/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hello,
>>
>> Spring framework reads this file to provide all
>> properties into servicemix.xml file
>> please see @servicemix.xml:
>> > class="
>> org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>> > value="classpath:servicemix.properties" />
>>
>>
>> You can use all properties from servicemix.properties
>> in your servicemix.xml file. For example
>> ${activemq.url} property.
>>
>> i hope it is could help you.
>>
>> Cordialement,
>>
>>
>> --- Thomas TERMIN <[EMAIL PROTECTED]> a
>> écrit :
>>
>> > Which class is reading the servicemix.properties
>> > file? If you have some
>> > spaces after a property the jmx.url is then also
>> > with spaces and that
>> > doesn't work.
>> >
>> >
>>
>>
>>
>>
>>
>>
>>
>>
>> ___
>>
>> Découvrez une nouvelle façon d'obtenir des réponses à toutes vos
>> questions
>> !
>> Profitez des connaissances, des opinions et des expériences des
>> internautes sur Yahoo! Questions/Réponses
>> http://fr.answers.yahoo.com
>>
>
>
>
--
Thomas Termin
___
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart
Tel: (+49) 0711 - 45 10 17 676
Fax: (+49) 0711 - 45 10 17 573
WWW: http://www.blue-elephant-systems.com
Email : [EMAIL PROTECTED]
blue elephant systems GmbH
Firmensitz : Wollgrasweg 49, D-70599 Stuttgart
Registergericht : Amtsgericht Stuttgart, HRB 24106
Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: Deployment Plan for j2ee connector
Still a bit more editing to go :D Thanks Karthiga On 3/14/07, Kanchana Welagedara <[EMAIL PROTECTED]> wrote: Hi All Finally geronimo-ra.xml has been confluenced for G1.1.I will continue the job to bring it for G v1.2 and G v2 with in few days. http://cwiki.apache.org/confluence/display/GMOxDOC11/geronimo-ra.xml My special thanks to Karthiga who made this article more clear by formatting and drawing pictures. Thanks and Regards. Kanchana
Re: MDBs working in 2.0
Dain Sundstrom wrote: I believe that I have MDBs working in 2.0 (and the tck). In general they should work about as well as Stateless beans do, but haven't received as much testing. Super! I also believe I have broken transaction recovery for the time being. -dain
[jira] Commented: (SM-882) Allow text/binary output
[
https://issues.apache.org/activemq/browse/SM-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38820
]
Guillaume Nodet commented on SM-882:
Do you want to try creating a patch for this ?
I can help you if you need some informations.
> Allow text/binary output
>
>
> Key: SM-882
> URL: https://issues.apache.org/activemq/browse/SM-882
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-saxon
>Affects Versions: 3.1
> Environment: servicemix 3.1 , java 1.5
>Reporter: Hervé Bourzeix
>
> When outputting something else than XML , I got the following exception:
> ERROR - FileComponent - Error processing exchange InOnly[
> id: ID:MON-HBOURZEIX-1214-1173859213020-3:33
> status: Active
> role: provider
> service: {http://www.genesys.com/jbi}pervasive
> endpoint: writeParam
> in: Unable to display: org.xml.sax.SAXParseException: Content is not
> allowed in prolog.
> ]
> javax.jbi.messaging.MessagingException: org.xml.sax.SAXParseException:
> Content is not allowed in prolog.
> at
> org.apache.servicemix.expression.JAXPXPathExpression.evaluate(JAXPXPathExpression.java:114)
> at
> org.apache.servicemix.components.util.DefaultFileMarshaler.getOutputName(DefaultFileMarshaler.java:65)
> at
> org.apache.servicemix.file.FileSenderEndpoint.processInOnly(FileSenderEndpoint.java:68)
> at
> org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
> at
> org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMSourceFromStream(SourceTransformer.java:224)
> at
> org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMSource(SourceTransformer.java:135)
> at
> org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMNode(SourceTransformer.java:289)
> at
> org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMNode(SourceTransformer.java:306)
> at
> org.apache.servicemix.expression.JAXPXPathExpression.getXMLNode(JAXPXPathExpression.java:179)
> at
> org.apache.servicemix.expression.JAXPXPathExpression.evaluate(JAXPXPathExpression.java:94)
> ... 13 more
> [Fatal Error] :2:4: Content is not allowed in prolog.
> [Fatal Error] :2:4: Content is not allowed in prolog.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: RE : servicemix.properties
This property is used to configure the
org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean
so I gess this class could be improved to trim the url before
using it.
Thomas, you can fix it, once your account is activated.
On 3/14/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hello,
Spring framework reads this file to provide all
properties into servicemix.xml file
please see @servicemix.xml:
You can use all properties from servicemix.properties
in your servicemix.xml file. For example
${activemq.url} property.
i hope it is could help you.
Cordialement,
--- Thomas TERMIN <[EMAIL PROTECTED]> a
écrit :
> Which class is reading the servicemix.properties
> file? If you have some
> spaces after a property the jmx.url is then also
> with spaces and that
> doesn't work.
>
>
___
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
!
Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com
--
Cheers,
Guillaume Nodet
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
External to External!
Hi everybody, I have some questions to the following scenario: Client1 --> BC1 --> NMR --> SE ---> NRM --> BC2 --> other Clients So Client1 sends a message to the ESB, BC1 receives and transmits it to the NMR, NMR transmits it to the SE, SE does some Business Logik, so that there is something changed lets say in a database. So now all other related clients need to be informed about this changes. So the SE sends a message about the succesfull changes to the NRM, the NRM sends this message to BC2 and the BC2 informs all the related clients. So this a scenario what I'm just thinking about. So is this scenario actually possible? What does a Client (other Clients) need to receive a Message from the ESB? And how is it possible just to inform Client2, Client3 and not Client4? greets Goldi -- View this message in context: http://www.nabble.com/External-to-External%21-tf3401934s12049.html#a9473716 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: MDBs working in 2.0
On Mar 14, 2007, at 3:53 AM, Dain Sundstrom wrote: I believe that I have MDBs working in 2.0 (and the tck). In general they should work about as well as Stateless beans do, but haven't received as much testing. That's great. Nice stuff. I also believe I have broken transaction recovery for the time being. K. Did you create a Jira so that we can keep track of this? Don't want it to be forgotten... Some information on how it's broken would be helpful. --kevan
Re: Can not deploy daytrader in geronimo m2
I assume you are working with geronimo trunk from svn?
Can you please file a jira? I recently changed where appclient
files go and that caused this problem.
What daytrader is doing here is a bit odd (including client side jars
in the server using manifest classpath) and I'd like to think a bit
about what the best solution is. It might be to change daytrader and
it might be to put the client jar in two places.
thanks
david jencks
On Mar 14, 2007, at 5:56 AM, FranK G wrote:
Hi,
I did a little debug to the class not found problem
when deploy daytrader.
The MANIFEST.MF of web.war includes the following
line:
Class-Path: dt-ejb.jar streamer.jar wsappclient.jar
which means the classloader will includes the above
three jar files. I notice these jars are added to the
classpath in
org.apache.geronimo.deployment.DeploymentContext. The
following method implements this function:
public void addManifestClassPath(JarFile
moduleFile, URI moduleBaseUri) throws
DeploymentException {
..
for (StringTokenizer tokenizer = new
StringTokenizer(manifestClassPath, " ");
tokenizer.hasMoreTokens();) {
..
try {
URI targetUri =
moduleBaseUri.resolve(pathUri);
if (targetUri.getPath().endsWith("/"))
throw new
IllegalStateException("target path must not end with a
'/' character: " + targetUri);
configuration.addToClassPath(targetUri.toString());
} catch (IOException e) {
throw new DeploymentException(e);
}
}
}
Let's take wsappclient.jar for example, its targetUri
is "../wsappclient.jar", but wsappclient.jar is not
copied to the parent directory of the web module. So
class Trade can not be found.
I also notice the structure of the
%geronimo_home%\repository in geronimo v2.0 is
different from v1.1, I don't know why.
Thanks
Frank
On 2007-03-14 11:16:05, FranK G <[EMAIL PROTECTED]>
wrote:
Charis, thank you for your reply.
I got the same error when using SUN jdk.
C:\>deploy --user system --password manager deploy
F:\daytrader\modules\ear\target\daytrader-ear-2.0-SNAPSHOT.ear
F:\daytrader\plans\daytrader-2.0-M2-jpa-plan.xml
Using JRE_HOME:C:\Program
Files\Java\jdk1.5.0_06\jre
Error: Unable to distribute
daytrader-ear-2.0-SNAPSHOT.ear: Could
not load service class
org.apache.geronimo.samples.daytrader.client.ws.Trade
org.apache.geronimo.samples.daytrader.client.ws.Trade
in
classloader
org.apache.geronimo.daytrader/daytrader_web.war/2.0-SNAPSHOT/car
Thanks
Frank
On 2007-03-13 21:13:37, Christopher Blythe
<[EMAIL PROTECTED]> wrote:
Frank...
Try using the daytrader-2.0-M2-jpa-plan.xml as the
deployment plan. If that
doesn't help, it might be worth trying the SUN JDK.
Chris
On 3/13/07, FranK G <[EMAIL PROTECTED]> wrote:
I checked out the source codes of daytrader from
https://svn.apache.org/repos/asf/geronimo/daytrader/trunk
and built it successful. But I encountered the
following error when I deployed it:
C:\>deploy --user system --password manager deploy
F:\daytrader\modules\ear\target\daytrader-ear-2.0-SNAPSHOT.ear
F:\daytrader\plans\daytrader-geronimo-derby-plan.xml
Using JRE_HOME:C:\Program
Files\IBM\Java50\jre
Error: Unable to distribute
daytrader-ear-2.0-SNAPSHOT.ear:
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException:
51 counts
of IllegalAnnotationExceptions
Property "id" has an XmlID annotation but its
type
is not String.
this problem is related to the following
location:
at protected java.lang.String
org.apache.openejb.jee.EjbJar.id
at org.apache.openejb.jee.EjbJar
Property "id" has an XmlID annotation but its
type
is not String.
this problem is related to the following
location:
at protected java.lang.String
org.apache.openejb.jee.Text.id
at org.apache.openejb.jee.Text
at public
org.apache.openejb.jee.Text[]
org.apache.openejb.jee.EjbJar.getDescriptions()
at org.apache.openejb.jee.EjbJar
...
51 counts of IllegalAnnotationExceptions
I think this is a problem of JAXB, so I replaced
jaxb-impl-2.0.3.jar and jaxb-api-2.0.jar with
jaxb-impl-2.1.1.jar and jaxb-api-2.1.jar, then I
got
another error:
Using JRE_HOME:C:\Program
Files\IBM\Java50\jre
Error: Unable to distribute
daytrader-ear-2.0-SNAPSHOT.ear: Could
not load service class
org.apache.geronimo.samples.daytrader.client.ws.Trade
org.apache.geronimo.samples.daytrader.client.ws.Trade
in
classloader
geronimo/daytrader-derby-tomcat_web.war/1.1.1/car
Can anyone help me?
Frank
_
___
Expecting? Get great news right away with email
Auto-Check.
Try the Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html
--
"I say never be complete, I say stop
test - ignore
-sachin
RE: How is the yoko 1.0-m2 release coming?
I think we got our 3 votes... We should be able to release now... Rick, do you want to call the result? - Balaji -Original Message- From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason Dillon Sent: Wednesday, March 14, 2007 12:45 AM To: yoko-dev@incubator.apache.org Cc: dev@geronimo.apache.org Subject: How is the yoko 1.0-m2 release coming? Will this puppy be out soonish? Any ETA? --jason
RE : servicemix.properties
Hello,
Spring framework reads this file to provide all
properties into servicemix.xml file
please see @servicemix.xml:
You can use all properties from servicemix.properties
in your servicemix.xml file. For example
${activemq.url} property.
i hope it is could help you.
Cordialement,
--- Thomas TERMIN <[EMAIL PROTECTED]> a
écrit :
> Which class is reading the servicemix.properties
> file? If you have some
> spaces after a property the jmx.url is then also
> with spaces and that
> doesn't work.
>
>
___
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur
Yahoo! Questions/Réponses
http://fr.answers.yahoo.com
[jira] Created: (SM-882) Allow text/binary output
Allow text/binary output
Key: SM-882
URL: https://issues.apache.org/activemq/browse/SM-882
Project: ServiceMix
Issue Type: Improvement
Components: servicemix-saxon
Affects Versions: 3.1
Environment: servicemix 3.1 , java 1.5
Reporter: Hervé Bourzeix
When outputting something else than XML , I got the following exception:
ERROR - FileComponent - Error processing exchange InOnly[
id: ID:MON-HBOURZEIX-1214-1173859213020-3:33
status: Active
role: provider
service: {http://www.genesys.com/jbi}pervasive
endpoint: writeParam
in: Unable to display: org.xml.sax.SAXParseException: Content is not allowed
in prolog.
]
javax.jbi.messaging.MessagingException: org.xml.sax.SAXParseException: Content
is not allowed in prolog.
at
org.apache.servicemix.expression.JAXPXPathExpression.evaluate(JAXPXPathExpression.java:114)
at
org.apache.servicemix.components.util.DefaultFileMarshaler.getOutputName(DefaultFileMarshaler.java:65)
at
org.apache.servicemix.file.FileSenderEndpoint.processInOnly(FileSenderEndpoint.java:68)
at
org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at
org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMSourceFromStream(SourceTransformer.java:224)
at
org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMSource(SourceTransformer.java:135)
at
org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMNode(SourceTransformer.java:289)
at
org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMNode(SourceTransformer.java:306)
at
org.apache.servicemix.expression.JAXPXPathExpression.getXMLNode(JAXPXPathExpression.java:179)
at
org.apache.servicemix.expression.JAXPXPathExpression.evaluate(JAXPXPathExpression.java:94)
... 13 more
[Fatal Error] :2:4: Content is not allowed in prolog.
[Fatal Error] :2:4: Content is not allowed in prolog.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
servicemix.properties
Which class is reading the servicemix.properties file? If you have some spaces after a property the jmx.url is then also with spaces and that doesn't work.
Re: Can not deploy daytrader in geronimo m2
Hi,
I did a little debug to the class not found problem
when deploy daytrader.
The MANIFEST.MF of web.war includes the following
line:
Class-Path: dt-ejb.jar streamer.jar wsappclient.jar
which means the classloader will includes the above
three jar files. I notice these jars are added to the
classpath in
org.apache.geronimo.deployment.DeploymentContext. The
following method implements this function:
public void addManifestClassPath(JarFile
moduleFile, URI moduleBaseUri) throws
DeploymentException {
..
for (StringTokenizer tokenizer = new
StringTokenizer(manifestClassPath, " ");
tokenizer.hasMoreTokens();) {
..
try {
URI targetUri =
moduleBaseUri.resolve(pathUri);
if (targetUri.getPath().endsWith("/"))
throw new
IllegalStateException("target path must not end with a
'/' character: " + targetUri);
configuration.addToClassPath(targetUri.toString());
} catch (IOException e) {
throw new DeploymentException(e);
}
}
}
Let's take wsappclient.jar for example, its targetUri
is "../wsappclient.jar", but wsappclient.jar is not
copied to the parent directory of the web module. So
class Trade can not be found.
I also notice the structure of the
%geronimo_home%\repository in geronimo v2.0 is
different from v1.1, I don't know why.
Thanks
Frank
On 2007-03-14 11:16:05, FranK G <[EMAIL PROTECTED]>
wrote:
>Charis, thank you for your reply.
>I got the same error when using SUN jdk.
>C:\>deploy --user system --password manager deploy
>F:\daytrader\modules\ear\target\daytrader-ear-2.0-SNAPSHOT.ear
>F:\daytrader\plans\daytrader-2.0-M2-jpa-plan.xml
>Using JRE_HOME:C:\Program
>Files\Java\jdk1.5.0_06\jre
>Error: Unable to distribute
>daytrader-ear-2.0-SNAPSHOT.ear: Could
>not load service class
>
>org.apache.geronimo.samples.daytrader.client.ws.Trade
>
>
>org.apache.geronimo.samples.daytrader.client.ws.Trade
>in
>classloader
>
>org.apache.geronimo.daytrader/daytrader_web.war/2.0-SNAPSHOT/car
>
>Thanks
>Frank
>
>On 2007-03-13 21:13:37, Christopher Blythe
><[EMAIL PROTECTED]> wrote:
>>Frank...
>>
>>Try using the daytrader-2.0-M2-jpa-plan.xml as the
>deployment plan. If that
>>doesn't help, it might be worth trying the SUN JDK.
>>
>>Chris
>>
>>On 3/13/07, FranK G <[EMAIL PROTECTED]> wrote:
>>>
>>> I checked out the source codes of daytrader from
>>>
>https://svn.apache.org/repos/asf/geronimo/daytrader/trunk
>>> and built it successful. But I encountered the
>>> following error when I deployed it:
>>> C:\>deploy --user system --password manager deploy
>>>
>F:\daytrader\modules\ear\target\daytrader-ear-2.0-SNAPSHOT.ear
>>>
>F:\daytrader\plans\daytrader-geronimo-derby-plan.xml
>>> Using JRE_HOME:C:\Program
>Files\IBM\Java50\jre
>>> Error: Unable to distribute
>>> daytrader-ear-2.0-SNAPSHOT.ear:
>>>
>>>
>com.sun.xml.bind.v2.runtime.IllegalAnnotationsException:
>>> 51 counts
>>> of IllegalAnnotationExceptions
>>>
>>> Property "id" has an XmlID annotation but its
>type
>>> is not String.
>>>
>>> this problem is related to the following
>>> location:
>>>
>>> at protected java.lang.String
>>> org.apache.openejb.jee.EjbJar.id
>>>
>>> at org.apache.openejb.jee.EjbJar
>>>
>>> Property "id" has an XmlID annotation but its
>type
>>> is not String.
>>>
>>> this problem is related to the following
>>> location:
>>>
>>> at protected java.lang.String
>>> org.apache.openejb.jee.Text.id
>>>
>>> at org.apache.openejb.jee.Text
>>>
>>> at public
>>> org.apache.openejb.jee.Text[]
>>>
org.apache.openejb.jee.EjbJar.getDescriptions()
>>>
>>> at org.apache.openejb.jee.EjbJar
>>> ...
>>> 51 counts of IllegalAnnotationExceptions
>>>
>>> I think this is a problem of JAXB, so I replaced
>>> jaxb-impl-2.0.3.jar and jaxb-api-2.0.jar with
>>> jaxb-impl-2.1.1.jar and jaxb-api-2.1.jar, then I
>got
>>> another error:
>>> Using JRE_HOME:C:\Program
>Files\IBM\Java50\jre
>>> Error: Unable to distribute
>>> daytrader-ear-2.0-SNAPSHOT.ear: Could
>>> not load service class
>>>
>>>
>org.apache.geronimo.samples.daytrader.client.ws.Trade
>>>
>>>
>>>
>org.apache.geronimo.samples.daytrader.client.ws.Trade
>>> in
>>> classloader
>>> geronimo/daytrader-derby-tomcat_web.war/1.1.1/car
>>>
>>> Can anyone help me?
>>>
>>> Frank
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>
>>> Expecting? Get great news right away with email
>Auto-Check.
>>> Try the Yahoo! Mail Beta.
>>>
>http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html
>>>
>>
>>
>>
>>--
>>"I say never be complete, I say stop being perfect,
I
>say let... lets
>>evolve, let the chips fall where they may." - Tyler
>Durden
>>
>
>
>
>
>
>
>_
Re: How is the yoko 1.0-m2 release coming?
Jason Dillon wrote: Will this puppy be out soonish? We're waiting on the incubator vote to release. With any luck, it will release today. Rick Any ETA? --jason
Deployment Plan for j2ee connector
Hi All Finally geronimo-ra.xml has been confluenced for G1.1.I will continue the job to bring it for G v1.2 and G v2 with in few days. http://cwiki.apache.org/confluence/display/GMOxDOC11/geronimo-ra.xml My special thanks to Karthiga who made this article more clear by formatting and drawing pictures. Thanks and Regards. Kanchana
