Re: Error formatting macro: snippet

2007-07-10 Thread Gert Vanthienen

Daniel,

Thank you for clarifying this.  Some of our pages have the entire url 
specified in the snippet macro, that's why it doesn't work.  Now we know 
how to solve it...


Gert

Daniel Kulp wrote:
I just checked the confluence snippet macro config and it looks ok.   It 
has a mapping of:


prefix: servicemix/ 
to url: http://svn.apache.org/repos/asf/incubator/servicemix/   


Thus, on your page, it should just be:

{snippet:id=expression|lang=xml|
url=servicemix/trunk/common/servicemix-components/src/test/resources/org/apache/servicemix/components/net/ftp.xml}


Dan

On Tuesday 10 July 2007 10:25, Gert Vanthienen wrote:
  

L.S.,


Some of our documentation pages use Confluence's snippet macro to
include code sample (e.g.
http://incubator.apache.org/servicemix/ftp.html).  Currently, this
macro doesn't seem to work any more:
Error formatting macro: snippet:
java.lang.IllegalArgumentException: Invalid url: must begin with a
configured prefix.

We're not alone, apparently the Struts team has the same problem (e.g.
http://struts.apache.org/2.0.5/docs/conversion-validator.html).  A
quick search on the web seems to indicate that this is some kind of
confguration problem with the snippet macro.  Who can administer the
Confluence instance that hosts our website to resolve this issue?


Gert



  


[jira] Created: (SM-997) Basic example fails to build: InvalidProjectModelException

2007-07-10 Thread Evan Deaubl (JIRA)
Basic example fails to build: InvalidProjectModelException
--

 Key: SM-997
 URL: https://issues.apache.org/activemq/browse/SM-997
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-assembly
Affects Versions: 3.1.1
 Environment: Servicemix 3.1.1-incubating, Windows XP, Java 1.5.0_12, 
Maven 2.0.6
Reporter: Evan Deaubl


When I attempt to run either mvn install, or mvn jbi:embeddedServicemix on the 
project in examples/basic, I receive the following error.  I have completely 
removed my Maven repository and had it redownload everything from scratch, and 
still received this error.  I manually checked the file it had downloaded, and 
the XML file was indeed invalid, and downloading the file directly from the 
source 
(http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom)
 using Firefox yields an XML Parsing Error.

[INFO] Scanning for projects...
Downloading: 
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/samples/3.1.1-incubating/samples-3.1.1-incubating.pom
2K downloaded
Downloading: 
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
69K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 
'507906935d130cfa9b44696270f62e006367533d'; remote = 
'a79a1012430e34db6e471c444f0dd77c28be9d0e' - RETRYING
Downloading: 
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
69K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 
'507906935d130cfa9b44696270f62e006367533d'; remote = 
'a79a1012430e34db6e471c444f0dd77c28be9d0e' - IGNORING
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] Error building POM (may not be this project's POM).


Project ID: org.apache.servicemix:samples:pom:null

Reason: Cannot find parent: org.apache.servicemix:servicemix for project: 
org.apache.servicemix:samples:pom:null


[INFO] 
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent: 
org.apache.servicemix:servicemix for project: 
org.apache.servicemix:samples:pom:null
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache.servicemix:servicemix for project: 
org.apache.servicemix:samples:pom:null
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1264)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1281)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:749)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:479)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:537)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364)
... 11 more
Caused by: org.apache.maven.project.InvalidProjectModelException: Parse error 
reading POM. Reason: end tag name /exclusion must match start tag name 
dependency from line 819 (position: TEXT seen ...dependency\n 
/exclusion... @820:18)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1423)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1380)
at 

RE: checkstyle on the se-archectype

2007-07-10 Thread rabi.mishra

While trying to build from the source from the trunk.. Meven 2 JBI Plugin 
failed fo me ith check style errors..
 
GraphArtifactCollector.java:58:37: More than 7 parameters
JbiComponentDescriptorWriter.java:37:15: More than 7 parameters
 
Do you have the same errors?
 
Regards, 
Rabi Mishra 
http://rabisblog.blogspot.com/



From: [EMAIL PROTECTED] on behalf of Brian O'Neill
Sent: Tue 7/10/2007 11:52 PM
To: servicemix-dev@geronimo.apache.org
Subject: checkstyle on the se-archectype



Following the se tutorial:
http://incubator.apache.org/servicemix/hello-world-se.html

The code produced from the mvn archetype failed the checkstyle check
(with errors).

Has anyone else experienced this?

(I also had to go in and update the version in the pom.xml, so it
would pull a current release of sm)

-brian

--
Brian ONeill
Source Equity (http://www.sourceequity.com http://www.sourceequity.com/ )
jBIZint (http://www.jbizint.org http://www.jbizint.org/ )
Technical Architect, Gestalt LLC (http://www.gestalt-llc.com 
http://www.gestalt-llc.com/ )
mobile:215.588.6024





The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.
 
www.wipro.com

Re: checkstyle on the se-archectype

2007-07-10 Thread Brian O'Neill

Unfortunately those are different errors, because I'm getting them in
the code generated by the maven archetype.

After fixing the checkstyle errors, I had to fix a couple PMD errors.

Now, I'm on to making the test pass, which is generating:
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'jbi' defined in class path resource
[spring.xml]: Invocation of init method failed; nested exception is
java.lang.NoSuchMethodError:
org.springframework.jmx.support.ConnectorServerFactoryBean.setObjectName(Ljava/lang/String;)V


I'm guessing this is a spring version problem. Trying to track it down now.

-brian

On 7/10/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:


While trying to build from the source from the trunk.. Meven 2 JBI Plugin 
failed fo me ith check style errors..

GraphArtifactCollector.java:58:37: More than 7 parameters
JbiComponentDescriptorWriter.java:37:15: More than 7 parameters

Do you have the same errors?

Regards,
Rabi Mishra
http://rabisblog.blogspot.com/



From: [EMAIL PROTECTED] on behalf of Brian O'Neill
Sent: Tue 7/10/2007 11:52 PM
To: servicemix-dev@geronimo.apache.org
Subject: checkstyle on the se-archectype



Following the se tutorial:
http://incubator.apache.org/servicemix/hello-world-se.html

The code produced from the mvn archetype failed the checkstyle check
(with errors).

Has anyone else experienced this?

(I also had to go in and update the version in the pom.xml, so it
would pull a current release of sm)

-brian

--
Brian ONeill
Source Equity (http://www.sourceequity.com http://www.sourceequity.com/ )
jBIZint (http://www.jbizint.org http://www.jbizint.org/ )
Technical Architect, Gestalt LLC (http://www.gestalt-llc.com 
http://www.gestalt-llc.com/ )
mobile:215.588.6024





The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.

www.wipro.com



--
Brian ONeill
Source Equity (http://www.sourceequity.com)
jBIZint (http://www.jbizint.org)
Technical Architect, Gestalt LLC (http://www.gestalt-llc.com)
mobile:215.588.6024


[jira] Created: (SM-998) In-Out Exchanges in a JMS queue cannot be successfully processed after a crash/shutdown

2007-07-10 Thread Sam Gerstein (JIRA)
In-Out Exchanges in a JMS queue cannot be successfully processed after a 
crash/shutdown
---

 Key: SM-998
 URL: https://issues.apache.org/activemq/browse/SM-998
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-jms
Affects Versions: 3.1.2
 Environment: any
Reporter: Sam Gerstein
 Fix For: 3.1.2
 Attachments: servicemix-jms_patch.txt

Because a temporary queue is used for the reply-to destination and the Exchange 
is stored in an in-memory Map, In-Out message exchanges in a JMS queue cannot 
be returned to their sender after a crash or shutdown of ServiceMix.

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



Re: [jira] Created: (SM-998) In-Out Exchanges in a JMS queue cannot be successfully processed after a crash/shutdown

2007-07-10 Thread samg

I meant to add a comment here-
I've only fixed StandardProviderProcessor, MultiplexingProviderProcessor,
and StandardConsumerProcessor.  MultiplexingConsumerProcessor is a bit more
complicated and I unfortunately don't have time for it right now.
I tested with mySQL and the jdbcStore, which worked fine except that the
size of the id column that the Store created was too small for the exchange
ID.. I suppose it should just be bigger by default, and I haven't fixed that
yet.
-Sam


JIRA [EMAIL PROTECTED] wrote:
 
 In-Out Exchanges in a JMS queue cannot be successfully processed after a
 crash/shutdown
 ---
 
  Key: SM-998
  URL: https://issues.apache.org/activemq/browse/SM-998
  Project: ServiceMix
   Issue Type: Bug
   Components: servicemix-jms
 Affects Versions: 3.1.2
  Environment: any
 Reporter: Sam Gerstein
  Fix For: 3.1.2
  Attachments: servicemix-jms_patch.txt
 
 Because a temporary queue is used for the reply-to destination and the
 Exchange is stored in an in-memory Map, In-Out message exchanges in a JMS
 queue cannot be returned to their sender after a crash or shutdown of
 ServiceMix.
 
 -- 
 This message is automatically generated by JIRA.
 -
 You can reply to this email to add a comment to the issue online.
 
 
 

-- 
View this message in context: 
http://www.nabble.com/-jira--Created%3A-%28SM-998%29-In-Out-Exchanges-in-a-JMS-queue-cannot-be-successfully-processed-after-a-crash-shutdown-tf4058643s12049.html#a11530104
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.



[jira] Created: (SM-999) InOut to InOnly pattern Endpoint for eip-su

2007-07-10 Thread Netflexity (JIRA)
InOut to InOnly pattern Endpoint for eip-su
---

 Key: SM-999
 URL: https://issues.apache.org/activemq/browse/SM-999
 Project: ServiceMix
  Issue Type: Improvement
  Components: servicemix-eip
Reporter: Netflexity


Please add the following pattern to be able to use components that support only 
InOnly MEPs for InOut components. Attached file illustrates the idea.

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