Nabble - codehaus - milyn

EDI components moved in SVN

2009-12-05T02:27:15Z

Hi guys... I moved all the EDI related components into a new "edi"
folder in SVN (http://jira.codehaus.org/browse/MILYN-401). You'll need
to do an update... rebuild your eclipse projects etc.

Bard... I'm looking at ECT etc... will follow up later on that other
thread :)

T.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - dev

[Bamboo] Milyn - Trunk (JDK1.5) build 365 was SUCCESSFUL (with 1028 tests). Change made by Tom Fennelly

2009-12-05T02:06:30Z

MILYN-TRUNKJDK15-365 was successful.
Code has been updated by Tom Fennelly.
1028 tests in total.

Code Changes

See full change details

Tom Fennelly
http://jira.codehaus.org/browse/MILYN-401 - Move all EDI related projects under a single folder in SVN

(1272)

JIRA Issues

See full issue details

MILYN-401 (Related)
Move all EDI related projects under a single folder in SVN

Error Summary

See full build log

                    2009-12-05 04:04:51.146::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog

                

                    2009-12-05 04:04:51.198::INFO:  jetty-6.1.1rc1

                

                    2009-12-05 04:04:51.322::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK15/smooks-examples/servlet/war/target/milyn-smooks-example-servlet-1.0.war!/ to /tmp/Jetty_0_0_0_0_19191_milyn-smooks-example-servlet-1.0.war__smooks-test__-s6meis/webapp

                

                    2009-12-05 04:04:52.287:/smooks-test:INFO:  [Milyn] Defaulting resource [SmooksConfig] load location to: /smooks-config.xml

                

                    Dec 5, 2009 4:04:52 AM org.milyn.servlet.SmooksServletFilter loadConfigStore

                

                    INFO: Smooks Config Store load complete.

                

                    Dec 5, 2009 4:04:52 AM org.milyn.servlet.SmooksServletFilter init

                

                    INFO: Smooks Servlet Filter initalised.

                

                    2009-12-05 04:04:53.354::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK15/smooks-examples/servlet/test/target/jetty6x/container/cargocpc.war!/ to /tmp/Jetty_0_0_0_0_19191_cargocpc.war__cargocpc__n0o14m/webapp

                

                    2009-12-05 04:04:54.209::INFO:  Started SelectChannelConnector @ 0.0.0.0:19191

                

                    2009-12-05 04:04:56.926:/smooks-test:INFO:  [Milyn] Defaulting resource [DeviceIdentUrl] load location to: /device-ident.xml

                

                    log4j:WARN No appenders could be found for logger (freemarker.cache).

                

                    log4j:WARN Please initialize the log4j system properly.

                

                    2009-12-05 04:06:16.905::INFO:  Shutdown hook executing

                

                    2009-12-05 04:06:16.906::INFO:  Shutdown hook complete

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

[jira] Closed: (MILYN-401) Move all EDI related projects under a single folder in SVN

2009-12-05T01:58:55Z

[ http://jira.codehaus.org/browse/MILYN-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Fennelly closed MILYN-401.
------------------------------

Resolution: Fixed

trunk: 1272

> Move all EDI related projects under a single folder in SVN
> ----------------------------------------------------------
>
> Key: MILYN-401
> URL: http://jira.codehaus.org/browse/MILYN-401
> Project: Milyn
> Issue Type: Task
> Components: EDI
> Reporter: Tom Fennelly
> Assignee: Tom Fennelly
> Fix For: Smooks v1.3
>
>

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - dev

[Bamboo] Milyn - Trunk (JDK1.6) build 241 has FAILED (1 tests failed). Change made by Tom Fennelly

2009-12-05T01:58:26Z

MILYN-TRUNKJDK16-241 failed.
Code has been updated by Tom Fennelly.
1/1028 tests failed.

Code Changes

See full change details

Tom Fennelly
http://jira.codehaus.org/browse/MILYN-401 - Move all EDI related projects under a single folder in SVN

(1272)

Tests

See full test details

Failed Tests (1)
	HsqlServerTest : Start stop (New)

JIRA Issues

See full issue details

MILYN-401 (Related)
Move all EDI related projects under a single folder in SVN

Error Summary

See full build log

                    [INFO] ------------------------------------------------------------------------

                

                    [ERROR] BUILD FAILURE

                

                    [INFO] ------------------------------------------------------------------------

                

                    [INFO] There are test failures.

                

                    Please refer to /opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK16/commons/target/surefire-reports for the individual test results.

                

                    [INFO] ------------------------------------------------------------------------

                

                    [INFO] For more information, run Maven with the -e switch

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

[jira] Created: (MILYN-401) Move all EDI related projects under a single folder in SVN

2009-12-05T01:22:55Z

Move all EDI related projects under a single folder in SVN
----------------------------------------------------------

Key: MILYN-401
URL: http://jira.codehaus.org/browse/MILYN-401
Project: Milyn
Issue Type: Task
Components: EdiSax
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Fix For: Smooks v1.3

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - dev

[jira] Created: (MILYN-400) Add maven-license-plugin to build

2009-12-05T01:05:55Z

Add maven-license-plugin to build
---------------------------------

Key: MILYN-400
URL: http://jira.codehaus.org/browse/MILYN-400
Project: Milyn
Issue Type: Task
Components: House Keeping
Reporter: Tom Fennelly
Fix For: Smooks v1.3

A number of files in the build have no project license. This plugin checks for and fixes this issue.

http://code.google.com/p/maven-license-plugin/

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - dev

Re: retrieve java binding xml configuration from the java code

2009-12-04T04:38:02Z

Hi Vincent.

You should be able to access this information by

1. Creating an ExecutionContext from the configured Smooks instance
2. Get the ContentDeliveryConfig instance from the ExecutionContext
3. Get the ResourceConfigurations for "csv-record" from the
ContentDeliveryConfig... it should be in that list.

Regards,

T.

Vincent LAUGIER wrote:

> Hello,
>
> I am trying to retrieve the binding configuration that has been
> defined in my smooks configuration file.
>
> The binding looks like the following :
>
> <jb:bean beanId="personItem" class="fr.helmet.test.entity.Person"
> createOnElement="csv-record">
> <jb:value property="firstname" data="csv-record/firstname" />
> <jb:value property="country" data="csv-record/country" />
> <jb:value property="birthDate" decoder="Date"
> data="csv-record/birthDate" >
> <jb:decodeParam name="format">yyyy-mm-dd</jb:decodeParam>
> </jb:value>
> </jb:bean>
>
>
> and I would like to be able to access the tag and attributes values
> from the java code...because I need to know the date format that has
> been set.
>
> I have tried many things through the applicationContext and
> executionContext without success.
>
> thanks for your help
>
> regards
>
> --
> *Vincent LAUGIER*
> Email : vincent.laugier@...
> Téléphone : + 33 (0)1 75 43 92 52
> Fax : + 33 (0)1 79 75 01 12 (monfax.com <http://monfax.com>)
> Objectwiz <http://objectwiz.org>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - user

Re: SV: SV: SV: SV: Edi Conversion Tool

2009-12-04T04:34:27Z

Bard.... I haven't forgotten this at all... just up to my t*ts in work.
I have started looking at it, but need to dig in more :)

T.

Tom Fennelly wrote:

> That's great Bard, thanks... I'll have a look at it asap... it's next
> on my list of Smooks tasks :)
>
> Bård Langöy wrote:
>> Hi,
>> I have checked in the ECT into the trunk now.
>>
>> I also solved Milyn-362 which was the extension of the
>> EDIParseException to also contain the current erranous MappingNode,
>> the current segment number as well as the current segment line.
>>
>> Regards,
>> Bård
>>
>> -----Ursprungligt meddelande-----
>> Från: Tom Fennelly [mailto:tom.fennelly@...] Skickat: den 10
>> november 2009 16:29
>> Till: dev@...
>> Ämne: Re: SV: SV: SV: [milyn-dev] Edi Conversion Tool
>>
>> Nice one Bard :)
>>
>> Bård Langöy wrote:
>>
>>> Okidoki Tom,
>>>
>>> I will try to get it into the trunk tonight then.
>>>
>>> Regards,
>>> Bård
>>>
>>>
>>>
>>> -----Ursprungligt meddelande-----
>>> Från: Tom Fennelly [mailto:tom.fennelly@...] Skickat: den 10
>>> november 2009 16:12
>>> Till: dev@...
>>> Ämne: Re: SV: SV: [milyn-dev] Edi Conversion Tool
>>>
>>> Hey Bard..... if it builds and doesn't break the build lets go for
>>> it and check it into trunk. We can still make changes to it from
>>> there, but I'd prefer to get this out into the wild asap in a
>>> snapshot. The more feedback we get the better. We can be playing
>>> with it and refining it ourselves too!!!
>>>
>>> Bård Langöy wrote:
>>>
>>>> Hi Tom,
>>>>
>>>> Should I check in the stuff now or do you want to look at it first ?
>>>>
>>>> Regards,
>>>> Bård
>>>>
>>>> -----Ursprungligt meddelande-----
>>>> Från: Tom Fennelly [mailto:tom.fennelly@...] Skickat: den 10
>>>> november 2009 15:50
>>>> Till: dev@...
>>>> Ämne: Re: SV: [milyn-dev] Edi Conversion Tool
>>>>
>>>> Hey Bard.
>>>>
>>>> Well first thing I plan on doing is just looking at it. I suppose
>>>> the best thing we should do for now is get what you have sorted out
>>>> and checked into trunk. Then we can look at adding the plugins and
>>>> EJC. Yeah?
>>>>
>>>> T.
>>>>
>>>>
>>>> Bård Langöy wrote:
>>>>
>>>>> Hi Tom,
>>>>>
>>>>> Yes that would be great ! When integrating the ECT with the EJC it
>>>>> would be great to add the new documentation element as javadoc in
>>>>> the generated classes. Will you do that or should I take a look at
>>>>> it ?
>>>>>
>>>>>
>>>>> Regards,
>>>>> Bård
>>>>>
>>>>>
>>>>>
>>>>> -----Ursprungligt meddelande-----
>>>>> Från: Tom Fennelly [mailto:tom.fennelly@...] Skickat: den 8
>>>>> november 2009 21:48
>>>>> Till: dev@...
>>>>> Ämne: Re: [milyn-dev] Edi Conversion Tool
>>>>>
>>>>> This stuff is awesome Bard. I will be looking at it ASAP!! I might
>>>>> also look at creating Ant and Maven plugins for this, as well as
>>>>> integrating it with EJC.
>>>>>
>>>>> Bård Langöy wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have finally checked in the first parts of the Edi Convert
>>>>>> Tool. The code does not exist in the trunk yet, but can be
>>>>>> downloaded at:
>>>>>> https://svn.codehaus.org/milyn/workspaces/bardl/bardl_edipop/ECT
>>>>>>
>>>>>> The conversion tool converts the zipped un/edifact specifications
>>>>>> located at http://www.unece.org/trade/untdid/down_index.htm into
>>>>>> Smooks configuration files (mapping-files) . I have created a
>>>>>> test-case that demonstrates the whole procedure:
>>>>>> ConfigReaderTest. test_Converting_UnEdifact_D08A().
>>>>>>
>>>>>> But in general the conversion-tool takes the following arguments:
>>>>>>
>>>>>> · InFile - the zip-file containing the un/edifact specs.
>>>>>>
>>>>>> · outDir - the directory to put the generated configuration-files.
>>>>>>
>>>>>> · message - The name of the message to parse. In the testcase
>>>>>> example I am generating the INVOIC message. It is also possible
>>>>>> to generate all messages by writing ALL.
>>>>>>
>>>>>> Today the conversion tool only handles zip-files. An improvement
>>>>>> would be to check whether it is a zip-file or an unzipped directory.
>>>>>>
>>>>>> Also, when writing the testcases I found that the segments UNH
>>>>>> and UNT are not located in the zip-file containing the
>>>>>> specification :(. I have handwritten a config-file
>>>>>> (un-edifact-interchange-definition.xml) that will be used for
>>>>>> now. But in the future it would be nice if we could find the
>>>>>> location/url of the interchange envelope specification.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Bård**
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe from this list, please visit:
>>>>>
>>>>> http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe from this list, please visit:
>>>>>
>>>>> http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>> http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>> http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>> http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>> http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - dev

retrieve java binding xml configuration from the java code

2009-12-03T12:32:41Z

Hello,

I am trying to retrieve the binding configuration that has been defined in my smooks configuration file.

The binding looks like the following :

<jb:bean beanId="personItem" class="fr.helmet.test.entity.Person" createOnElement="csv-record">
        <jb:value property="firstname" data="csv-record/firstname" />
        <jb:value property="country" data="csv-record/country" />
        <jb:value property="birthDate" decoder="Date" data="csv-record/birthDate" >
            <jb:decodeParam name="format">yyyy-mm-dd</jb:decodeParam>
        </jb:value>
    </jb:bean>

and I would like to be able to access the tag and attributes values from the java code...because I need to know the date format that has been set.

I have tried many things through the applicationContext and executionContext without success.

thanks for your help

regards

--
Vincent LAUGIER

Vincent LAUGIER
Email : vincent.laugier@...
Téléphone : + 33 (0)1 75 43 92 52
Fax : + 33 (0)1 79 75 01 12 (monfax.com)

From forum: milyn - user

[Bamboo] Milyn - Trunk (JDK1.6) build 240 was SUCCESSFUL (with 1028 tests)

2009-11-30T06:08:36Z

MILYN-TRUNKJDK16-240 was successful.
This build was manually triggered by smies.
1028 tests in total.

Code Changes

This build does not have any commits.

Error Summary

See full build log

                    2009-11-30 08:06:11.697::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog

                

                    2009-11-30 08:06:11.811::INFO:  jetty-6.1.1rc1

                

                    2009-11-30 08:06:12.101::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK16/smooks-examples/servlet/war/target/milyn-smooks-example-servlet-1.0.war!/ to /tmp/Jetty_0_0_0_0_19191_milyn-smooks-example-servlet-1.0.war__smooks-test__-s6meis/webapp

                

                    2009-11-30 08:06:14.614:/smooks-test:INFO:  [Milyn] Defaulting resource [SmooksConfig] load location to: /smooks-config.xml

                

                    Nov 30, 2009 8:06:14 AM org.milyn.servlet.SmooksServletFilter loadConfigStore

                

                    INFO: Smooks Config Store load complete.

                

                    Nov 30, 2009 8:06:14 AM org.milyn.servlet.SmooksServletFilter init

                

                    INFO: Smooks Servlet Filter initalised.

                

                    2009-11-30 08:06:16.339::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK16/smooks-examples/servlet/test/target/jetty6x/container/cargocpc.war!/ to /tmp/Jetty_0_0_0_0_19191_cargocpc.war__cargocpc__n0o14m/webapp

                

                    2009-11-30 08:06:18.163::INFO:  Started SelectChannelConnector @ 0.0.0.0:19191

                

                    2009-11-30 08:06:21.193:/smooks-test:INFO:  [Milyn] Defaulting resource [DeviceIdentUrl] load location to: /device-ident.xml

                

                    log4j:WARN No appenders could be found for logger (freemarker.cache).

                

                    log4j:WARN Please initialize the log4j system properly.

                

                    2009-11-30 08:08:22.946::INFO:  Shutdown hook executing

                

                    2009-11-30 08:08:22.946::INFO:  Shutdown hook complete

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

[Bamboo] Milyn - Trunk (JDK1.6) build 239 has FAILED (0 tests failed)

2009-11-30T03:50:50Z

MILYN-TRUNKJDK16-239 failed.
This build was manually triggered by smies.
No failed tests found, a possible compilation error.

Code Changes

This build does not have any commits.

Error Summary

See full build log

                    [INFO] ------------------------------------------------------------------------

                

                    [ERROR] BUILD FAILURE

                

                    [INFO] ------------------------------------------------------------------------

                

                    [INFO] Compilation failure

                

                    Failure executing javac, but could not parse the error:

                

                    The system is out of resources.

                

                    Consult the following stack trace for details.

                

                    java.lang.OutOfMemoryError: PermGen space

                

                            at java.lang.ClassLoader.defineClass1(Native Method)

                

                            at java.lang.ClassLoader.defineClass(ClassLoader.java:616)

                

                            at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)

                

                            at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)

                

                            at java.net.URLClassLoader.access$000(URLClassLoader.java:56)

                

                            at java.net.URLClassLoader$1.run(URLClassLoader.java:195)

                

                            at java.security.AccessController.doPrivileged(Native Method)

                

                            at java.net.URLClassLoader.findClass(URLClassLoader.java:188)

                

                            at org.codehaus.plexus.compiler.javac.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:56)

                

                            at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:340)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:279)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:270)

                

                            at com.sun.tools.javac.Main.compile(Main.java:87)

                

                            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                

                            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

                

                            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

                

                            at java.lang.reflect.Method.invoke(Method.java:597)

                

                            at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:420)

                

                            at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141)

                

                            at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493)

                

                            at org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:102)

                

                            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)

                

                            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)

                

                            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)

                

                            at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)

                

                    Failure executing javac, but could not parse the error:

                

                    The system is out of resources.

                

                    Consult the following stack trace for details.

                

                    java.lang.OutOfMemoryError: PermGen space

                

                            at java.lang.ClassLoader.defineClass1(Native Method)

                

                            at java.lang.ClassLoader.defineClass(ClassLoader.java:616)

                

                            at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)

                

                            at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)

                

                            at java.net.URLClassLoader.access$000(URLClassLoader.java:56)

                

                            at java.net.URLClassLoader$1.run(URLClassLoader.java:195)

                

                            at java.security.AccessController.doPrivileged(Native Method)

                

                            at java.net.URLClassLoader.findClass(URLClassLoader.java:188)

                

                            at org.codehaus.plexus.compiler.javac.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:56)

                

                            at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:340)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:279)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:270)

                

                            at com.sun.tools.javac.Main.compile(Main.java:87)

                

                            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                

                            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

                

                            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

                

                            at java.lang.reflect.Method.invoke(Method.java:597)

                

                            at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:420)

                

                            at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141)

                

                            at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493)

                

                            at org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:102)

                

                            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)

                

                            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)

                

                            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)

                

                            at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)

                

                    [INFO] ------------------------------------------------------------------------

                

                    [INFO] For more information, run Maven with the -e switch

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

Re: New snapshot build

2009-11-30T03:43:50Z

Thanks for the SNAPSHOT. The build is failing because of a permgen exception. I am trying to rebuild again.

Maurice

On Mon, Nov 30, 2009 at 12:20 PM, Tom Fennelly <tom.fennelly@...> wrote:

The SNAPSHOT is there now... I see Bamboo failing though? Might be the same old HSQL issue!!

Maurice Zeijen wrote:

Hey Tom,

I just fixed a bug in the javabean cartridge for the 1.3 release. I need this bug fix for a project I am working on. It would be great if you could do a snapshot release as soon as possible.

Thanks,

Maurice

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - dev

[Bamboo] Milyn - Trunk (JDK1.6) build 238 has FAILED (0 tests failed)

2009-11-30T03:40:28Z

MILYN-TRUNKJDK16-238 failed.
This build was manually triggered by smies.
No failed tests found, a possible compilation error.

Code Changes

This build does not have any commits.

Error Summary

See full build log

                    [INFO] ------------------------------------------------------------------------

                

                    [ERROR] BUILD FAILURE

                

                    [INFO] ------------------------------------------------------------------------

                

                    [INFO] Compilation failure

                

                    Failure executing javac, but could not parse the error:

                

                    The system is out of resources.

                

                    Consult the following stack trace for details.

                

                    java.lang.OutOfMemoryError: PermGen space

                

                            at java.lang.ClassLoader.defineClass1(Native Method)

                

                            at java.lang.ClassLoader.defineClass(ClassLoader.java:616)

                

                            at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)

                

                            at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)

                

                            at java.net.URLClassLoader.access$000(URLClassLoader.java:56)

                

                            at java.net.URLClassLoader$1.run(URLClassLoader.java:195)

                

                            at java.security.AccessController.doPrivileged(Native Method)

                

                            at java.net.URLClassLoader.findClass(URLClassLoader.java:188)

                

                            at org.codehaus.plexus.compiler.javac.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:56)

                

                            at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:340)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:279)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:270)

                

                            at com.sun.tools.javac.Main.compile(Main.java:87)

                

                            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                

                            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

                

                            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

                

                            at java.lang.reflect.Method.invoke(Method.java:597)

                

                            at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:420)

                

                            at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141)

                

                            at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493)

                

                            at org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:102)

                

                            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)

                

                            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)

                

                            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)

                

                            at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)

                

                    Failure executing javac, but could not parse the error:

                

                    The system is out of resources.

                

                    Consult the following stack trace for details.

                

                    java.lang.OutOfMemoryError: PermGen space

                

                            at java.lang.ClassLoader.defineClass1(Native Method)

                

                            at java.lang.ClassLoader.defineClass(ClassLoader.java:616)

                

                            at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)

                

                            at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)

                

                            at java.net.URLClassLoader.access$000(URLClassLoader.java:56)

                

                            at java.net.URLClassLoader$1.run(URLClassLoader.java:195)

                

                            at java.security.AccessController.doPrivileged(Native Method)

                

                            at java.net.URLClassLoader.findClass(URLClassLoader.java:188)

                

                            at org.codehaus.plexus.compiler.javac.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:56)

                

                            at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:340)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:279)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:270)

                

                            at com.sun.tools.javac.Main.compile(Main.java:87)

                

                            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                

                            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

                

                            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

                

                            at java.lang.reflect.Method.invoke(Method.java:597)

                

                            at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:420)

                

                            at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141)

                

                            at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493)

                

                            at org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:102)

                

                            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)

                

                            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)

                

                            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)

                

                            at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)

                

                    [INFO] ------------------------------------------------------------------------

                

                    [INFO] For more information, run Maven with the -e switch

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

Re: New snapshot build

2009-11-30T03:20:01Z

The SNAPSHOT is there now... I see Bamboo failing though? Might be the
same old HSQL issue!!

Maurice Zeijen wrote:
> Hey Tom,
>
> I just fixed a bug in the javabean cartridge for the 1.3 release. I
> need this bug fix for a project I am working on. It would be great if
> you could do a snapshot release as soon as possible.
>
> Thanks,
>
> Maurice

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - dev

[Bamboo] Milyn - Trunk (JDK1.6) build 237 has FAILED (0 tests failed). Change made by smies

2009-11-30T03:17:21Z

MILYN-TRUNKJDK16-237 failed.
Code has been updated by smies.
No failed tests found, a possible compilation error.

Code Changes

See full change details

smies
- deactivated report generation for a certain test

(1271)

Error Summary

See full build log

                    [INFO] ------------------------------------------------------------------------

                

                    [ERROR] BUILD FAILURE

                

                    [INFO] ------------------------------------------------------------------------

                

                    [INFO] Compilation failure

                

                    Failure executing javac, but could not parse the error:

                

                    The system is out of resources.

                

                    Consult the following stack trace for details.

                

                    java.lang.OutOfMemoryError: PermGen space

                

                            at java.lang.ClassLoader.defineClass1(Native Method)

                

                            at java.lang.ClassLoader.defineClass(ClassLoader.java:616)

                

                            at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)

                

                            at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)

                

                            at java.net.URLClassLoader.access$000(URLClassLoader.java:56)

                

                            at java.net.URLClassLoader$1.run(URLClassLoader.java:195)

                

                            at java.security.AccessController.doPrivileged(Native Method)

                

                            at java.net.URLClassLoader.findClass(URLClassLoader.java:188)

                

                            at org.codehaus.plexus.compiler.javac.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:56)

                

                            at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)

                

                            at com.sun.tools.javac.comp.Attr.<init>(Attr.java:84)

                

                            at com.sun.tools.javac.comp.Attr.instance(Attr.java:74)

                

                            at com.sun.tools.javac.comp.Annotate.<init>(Annotate.java:52)

                

                            at com.sun.tools.javac.comp.Annotate.instance(Annotate.java:36)

                

                            at com.sun.tools.javac.jvm.ClassReader.<init>(ClassReader.java:215)

                

                            at com.sun.tools.javac.jvm.ClassReader.instance(ClassReader.java:168)

                

                            at com.sun.tools.javac.main.JavaCompiler.<init>(JavaCompiler.java:293)

                

                            at com.sun.tools.javac.main.JavaCompiler.instance(JavaCompiler.java:72)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:340)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:279)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:270)

                

                            at com.sun.tools.javac.Main.compile(Main.java:87)

                

                            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                

                            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

                

                            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

                

                            at java.lang.reflect.Method.invoke(Method.java:597)

                

                            at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:420)

                

                            at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141)

                

                            at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493)

                

                            at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)

                

                            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

                

                    Failure executing javac, but could not parse the error:

                

                    The system is out of resources.

                

                    Consult the following stack trace for details.

                

                    java.lang.OutOfMemoryError: PermGen space

                

                            at java.lang.ClassLoader.defineClass1(Native Method)

                

                            at java.lang.ClassLoader.defineClass(ClassLoader.java:616)

                

                            at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)

                

                            at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)

                

                            at java.net.URLClassLoader.access$000(URLClassLoader.java:56)

                

                            at java.net.URLClassLoader$1.run(URLClassLoader.java:195)

                

                            at java.security.AccessController.doPrivileged(Native Method)

                

                            at java.net.URLClassLoader.findClass(URLClassLoader.java:188)

                

                            at org.codehaus.plexus.compiler.javac.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:56)

                

                            at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)

                

                            at com.sun.tools.javac.comp.Attr.<init>(Attr.java:84)

                

                            at com.sun.tools.javac.comp.Attr.instance(Attr.java:74)

                

                            at com.sun.tools.javac.comp.Annotate.<init>(Annotate.java:52)

                

                            at com.sun.tools.javac.comp.Annotate.instance(Annotate.java:36)

                

                            at com.sun.tools.javac.jvm.ClassReader.<init>(ClassReader.java:215)

                

                            at com.sun.tools.javac.jvm.ClassReader.instance(ClassReader.java:168)

                

                            at com.sun.tools.javac.main.JavaCompiler.<init>(JavaCompiler.java:293)

                

                            at com.sun.tools.javac.main.JavaCompiler.instance(JavaCompiler.java:72)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:340)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:279)

                

                            at com.sun.tools.javac.main.Main.compile(Main.java:270)

                

                            at com.sun.tools.javac.Main.compile(Main.java:87)

                

                            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                

                            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

                

                            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

                

                            at java.lang.reflect.Method.invoke(Method.java:597)

                

                            at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:420)

                

                            at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141)

                

                            at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493)

                

                            at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)

                

                            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

                

                    [INFO] ------------------------------------------------------------------------

                

                    [INFO] For more information, run Maven with the -e switch

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

[Bamboo] Milyn - Trunk (JDK1.5) build 364 was SUCCESSFUL (with 1028 tests). Change made by smies

2009-11-30T03:13:38Z

MILYN-TRUNKJDK15-364 was successful.
This build was manually triggered by smies.
1028 tests in total.

Code Changes

See full change details

smies
- deactivated report generation for a certain test

(1271)

Error Summary

See full build log

                    2009-11-30 05:09:21.519::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog

                

                    2009-11-30 05:09:21.615::INFO:  jetty-6.1.1rc1

                

                    2009-11-30 05:09:21.960::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK15/smooks-examples/servlet/war/target/milyn-smooks-example-servlet-1.0.war!/ to /tmp/Jetty_0_0_0_0_19191_milyn-smooks-example-servlet-1.0.war__smooks-test__-s6meis/webapp

                

                    2009-11-30 05:09:29.283:/smooks-test:INFO:  [Milyn] Defaulting resource [SmooksConfig] load location to: /smooks-config.xml

                

                    Nov 30, 2009 5:09:29 AM org.milyn.servlet.SmooksServletFilter loadConfigStore

                

                    INFO: Smooks Config Store load complete.

                

                    Nov 30, 2009 5:09:29 AM org.milyn.servlet.SmooksServletFilter init

                

                    INFO: Smooks Servlet Filter initalised.

                

                    2009-11-30 05:09:30.541::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK15/smooks-examples/servlet/test/target/jetty6x/container/cargocpc.war!/ to /tmp/Jetty_0_0_0_0_19191_cargocpc.war__cargocpc__n0o14m/webapp

                

                    2009-11-30 05:09:31.538::INFO:  Started SelectChannelConnector @ 0.0.0.0:19191

                

                    2009-11-30 05:09:34.641:/smooks-test:INFO:  [Milyn] Defaulting resource [DeviceIdentUrl] load location to: /device-ident.xml

                

                    log4j:WARN No appenders could be found for logger (freemarker.cache).

                

                    log4j:WARN Please initialize the log4j system properly.

                

                    2009-11-30 05:12:33.701::INFO:  Shutdown hook executing

                

                    2009-11-30 05:12:33.701::INFO:  Shutdown hook complete

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

[Bamboo] Milyn - Trunk (JDK1.6) build 236 was SUCCESSFUL (with 1028 tests). Change made by smies

2009-11-30T02:55:37Z

MILYN-TRUNKJDK16-236 was successful.
Code has been updated by smies.
1028 tests in total.

Code Changes

See full change details

smies
Fixed a bug where attribute value where not available when doing an expression binding with the _VALUE special variable.

(1270)

Error Summary

See full build log

                    2009-11-30 04:51:55.559::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog

                

                    2009-11-30 04:51:55.696::INFO:  jetty-6.1.1rc1

                

                    2009-11-30 04:52:13.348::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK16/smooks-examples/servlet/war/target/milyn-smooks-example-servlet-1.0.war!/ to /tmp/Jetty_0_0_0_0_19191_milyn-smooks-example-servlet-1.0.war__smooks-test__-s6meis/webapp

                

                    2009-11-30 04:52:17.442:/smooks-test:INFO:  [Milyn] Defaulting resource [SmooksConfig] load location to: /smooks-config.xml

                

                    Nov 30, 2009 4:52:17 AM org.milyn.servlet.SmooksServletFilter loadConfigStore

                

                    INFO: Smooks Config Store load complete.

                

                    Nov 30, 2009 4:52:17 AM org.milyn.servlet.SmooksServletFilter init

                

                    INFO: Smooks Servlet Filter initalised.

                

                    2009-11-30 04:52:19.612::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK16/smooks-examples/servlet/test/target/jetty6x/container/cargocpc.war!/ to /tmp/Jetty_0_0_0_0_19191_cargocpc.war__cargocpc__n0o14m/webapp

                

                    2009-11-30 04:52:27.247::INFO:  Started SelectChannelConnector @ 0.0.0.0:19191

                

                    2009-11-30 04:52:30.621:/smooks-test:INFO:  [Milyn] Defaulting resource [DeviceIdentUrl] load location to: /device-ident.xml

                

                    log4j:WARN No appenders could be found for logger (freemarker.cache).

                

                    log4j:WARN Please initialize the log4j system properly.

                

                    2009-11-30 04:54:52.639::INFO:  Shutdown hook executing

                

                    2009-11-30 04:54:52.639::INFO:  Shutdown hook complete

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

[Bamboo] Milyn - Trunk (JDK1.5) build 363 has FAILED (0 tests failed). Change made by smies

2009-11-30T02:53:39Z

MILYN-TRUNKJDK15-363 failed.
Code has been updated by smies.
No failed tests found, a possible compilation error.

Code Changes

See full change details

smies
Fixed a bug where attribute value where not available when doing an expression binding with the _VALUE special variable.

(1270)

Error Summary

See full build log

                    [INFO] ------------------------------------------------------------------------

                

                    [ERROR] FATAL ERROR

                

                    [INFO] ------------------------------------------------------------------------

                

                    [INFO] Failed to start the Jetty 6.x Embedded container.

                

                    Deployable [http://localhost:19191/cargocpc/index.html] failed to finish deploying within the timeout period [120000]. The Deployable state is thus unknown.

                

                    [INFO] ------------------------------------------------------------------------

                

                    [INFO] Trace

                

                    org.codehaus.cargo.container.ContainerException: Failed to start the Jetty 6.x Embedded container.

                

                            at org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:160)

                

                            at org.codehaus.cargo.maven2.ContainerStartMojo.doExecute(ContainerStartMojo.java:61)

                

                            at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:243)

                

                            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)

                

                            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)

                

                            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)

                

                            at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)

                

                            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.codehaus.cargo.container.ContainerException: Deployable [http://localhost:19191/cargocpc/index.html] failed to finish deploying within the timeout period [120000]. The Deployable state is thus unknown.

                

                            at org.codehaus.cargo.container.spi.deployer.DeployerWatchdog.watch(DeployerWatchdog.java:111)

                

                            at org.codehaus.cargo.container.spi.AbstractLocalContainer.waitForCompletion(AbstractLocalContainer.java:212)

                

                            at org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:155)

                

                            ... 20 more

                

                    org.codehaus.cargo.container.ContainerException: Deployable [http://localhost:19191/cargocpc/index.html] failed to finish deploying within the timeout period [120000]. The Deployable state is thus unknown.

                

                            at org.codehaus.cargo.container.spi.deployer.DeployerWatchdog.watch(DeployerWatchdog.java:111)

                

                            at org.codehaus.cargo.container.spi.AbstractLocalContainer.waitForCompletion(AbstractLocalContainer.java:212)

                

                            at org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:155)

                

                            at org.codehaus.cargo.maven2.ContainerStartMojo.doExecute(ContainerStartMojo.java:61)

                

                            at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:243)

                

                            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)

                

                            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)

                

                            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)

                

                            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)

                

                            at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)

                

                            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)

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

Re: New snapshot build

2009-11-30T02:50:38Z

It's building there now Maurice.

T.

Maurice Zeijen wrote:
> Hey Tom,
>
> I just fixed a bug in the javabean cartridge for the 1.3 release. I
> need this bug fix for a project I am working on. It would be great if
> you could do a snapshot release as soon as possible.
>
> Thanks,
>
> Maurice

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - dev

New snapshot build

2009-11-30T02:10:45Z

Hey Tom,

I just fixed a bug in the javabean cartridge for the 1.3 release. I need this bug fix for a project I am working on. It would be great if you could do a snapshot release as soon as possible.

Thanks,

Maurice

From forum: milyn - dev

[Bamboo] Milyn - Trunk (JDK1.5) build 362 was SUCCESSFUL (with 1028 tests)

2009-11-26T08:22:28Z

MILYN-TRUNKJDK15-362 was successful.
This build was manually triggered by smies.
1028 tests in total.

Code Changes

This build does not have any commits.

Tests

See full test details

Fixed Tests (1)
	HsqlServerTest : Start stop

Error Summary

See full build log

                    2009-11-26 10:20:44.871::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog

                

                    2009-11-26 10:20:44.953::INFO:  jetty-6.1.1rc1

                

                    2009-11-26 10:20:45.087::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK15/smooks-examples/servlet/war/target/milyn-smooks-example-servlet-1.0.war!/ to /tmp/Jetty_0_0_0_0_19191_milyn-smooks-example-servlet-1.0.war__smooks-test__-s6meis/webapp

                

                    2009-11-26 10:20:46.190:/smooks-test:INFO:  [Milyn] Defaulting resource [SmooksConfig] load location to: /smooks-config.xml

                

                    Nov 26, 2009 10:20:46 AM org.milyn.servlet.SmooksServletFilter loadConfigStore

                

                    INFO: Smooks Config Store load complete.

                

                    Nov 26, 2009 10:20:46 AM org.milyn.servlet.SmooksServletFilter init

                

                    INFO: Smooks Servlet Filter initalised.

                

                    2009-11-26 10:20:47.504::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK15/smooks-examples/servlet/test/target/jetty6x/container/cargocpc.war!/ to /tmp/Jetty_0_0_0_0_19191_cargocpc.war__cargocpc__n0o14m/webapp

                

                    2009-11-26 10:20:48.380::INFO:  Started SelectChannelConnector @ 0.0.0.0:19191

                

                    2009-11-26 10:20:51.281:/smooks-test:INFO:  [Milyn] Defaulting resource [DeviceIdentUrl] load location to: /device-ident.xml

                

                    log4j:WARN No appenders could be found for logger (freemarker.cache).

                

                    log4j:WARN Please initialize the log4j system properly.

                

                    2009-11-26 10:22:17.015::INFO:  Shutdown hook executing

                

                    2009-11-26 10:22:17.015::INFO:  Shutdown hook complete

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

[Bamboo] Milyn - Trunk (JDK1.6) build 235 was SUCCESSFUL (with 1028 tests). Change made by smies

2009-11-26T06:15:28Z

MILYN-TRUNKJDK16-235 was successful.
Code has been updated by smies.
1028 tests in total.

Code Changes

See full change details

smies
- updated the versions of mvel and commons-lang

(1269)

Error Summary

See full build log

                    2009-11-26 08:13:46.045::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog

                

                    2009-11-26 08:13:46.099::INFO:  jetty-6.1.1rc1

                

                    2009-11-26 08:13:50.418::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK16/smooks-examples/servlet/war/target/milyn-smooks-example-servlet-1.0.war!/ to /tmp/Jetty_0_0_0_0_19191_milyn-smooks-example-servlet-1.0.war__smooks-test__-s6meis/webapp

                

                    2009-11-26 08:13:51.289:/smooks-test:INFO:  [Milyn] Defaulting resource [SmooksConfig] load location to: /smooks-config.xml

                

                    Nov 26, 2009 8:13:51 AM org.milyn.servlet.SmooksServletFilter loadConfigStore

                

                    INFO: Smooks Config Store load complete.

                

                    Nov 26, 2009 8:13:51 AM org.milyn.servlet.SmooksServletFilter init

                

                    INFO: Smooks Servlet Filter initalised.

                

                    2009-11-26 08:13:52.471::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK16/smooks-examples/servlet/test/target/jetty6x/container/cargocpc.war!/ to /tmp/Jetty_0_0_0_0_19191_cargocpc.war__cargocpc__n0o14m/webapp

                

                    2009-11-26 08:13:53.504::INFO:  Started SelectChannelConnector @ 0.0.0.0:19191

                

                    2009-11-26 08:13:56.974:/smooks-test:INFO:  [Milyn] Defaulting resource [DeviceIdentUrl] load location to: /device-ident.xml

                

                    log4j:WARN No appenders could be found for logger (freemarker.cache).

                

                    log4j:WARN Please initialize the log4j system properly.

                

                    2009-11-26 08:15:14.762::INFO:  Shutdown hook executing

                

                    2009-11-26 08:15:14.762::INFO:  Shutdown hook complete

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

[Bamboo] Milyn - Trunk (JDK1.5) build 361 has FAILED (1 tests failed). Change made by smies

2009-11-26T06:08:27Z

MILYN-TRUNKJDK15-361 failed.
Code has been updated by smies.
1/1028 tests failed.

Code Changes

See full change details

smies
- updated the versions of mvel and commons-lang

(1269)

Tests

See full test details

Failed Tests (1)
	HsqlServerTest : Start stop (New)

Error Summary

See full build log

                    [INFO] ------------------------------------------------------------------------

                

                    [ERROR] BUILD FAILURE

                

                    [INFO] ------------------------------------------------------------------------

                

                    [INFO] There are test failures.

                

                    Please refer to /opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK15/commons/target/surefire-reports for the individual test results.

                

                    [INFO] ------------------------------------------------------------------------

                

                    [INFO] For more information, run Maven with the -e switch

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

[Bamboo] Milyn - Trunk (JDK1.6) build 234 was SUCCESSFUL (with 1028 tests)

2009-11-26T05:29:47Z

MILYN-TRUNKJDK16-234 was successful.
This build was manually triggered by smies.
1028 tests in total.

Code Changes

This build does not have any commits.

Error Summary

See full build log

                    2009-11-26 07:28:01.389::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog

                

                    2009-11-26 07:28:01.477::INFO:  jetty-6.1.1rc1

                

                    2009-11-26 07:28:04.060::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK16/smooks-examples/servlet/war/target/milyn-smooks-example-servlet-1.0.war!/ to /tmp/Jetty_0_0_0_0_19191_milyn-smooks-example-servlet-1.0.war__smooks-test__-s6meis/webapp

                

                    2009-11-26 07:28:04.961:/smooks-test:INFO:  [Milyn] Defaulting resource [SmooksConfig] load location to: /smooks-config.xml

                

                    Nov 26, 2009 7:28:04 AM org.milyn.servlet.SmooksServletFilter loadConfigStore

                

                    INFO: Smooks Config Store load complete.

                

                    Nov 26, 2009 7:28:04 AM org.milyn.servlet.SmooksServletFilter init

                

                    INFO: Smooks Servlet Filter initalised.

                

                    2009-11-26 07:28:06.171::INFO:  Extract jar:file:/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.3.1/xml-data/build-dir/MILYN-TRUNKJDK16/smooks-examples/servlet/test/target/jetty6x/container/cargocpc.war!/ to /tmp/Jetty_0_0_0_0_19191_cargocpc.war__cargocpc__n0o14m/webapp

                

                    2009-11-26 07:28:07.596::INFO:  Started SelectChannelConnector @ 0.0.0.0:19191

                

                    2009-11-26 07:28:10.317:/smooks-test:INFO:  [Milyn] Defaulting resource [DeviceIdentUrl] load location to: /device-ident.xml

                

                    log4j:WARN No appenders could be found for logger (freemarker.cache).

                

                    log4j:WARN Please initialize the log4j system properly.

                

                    2009-11-26 07:29:32.530::INFO:  Shutdown hook executing

                

                    2009-11-26 07:29:32.530::INFO:  Shutdown hook complete

                

Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator
Want this information in your IDE?

Actions

View Online
Add Comments
View Artifacts
Download Logs
Link to JIRA issue

From forum: milyn - dev

Re: I'm getting an error trying to read the passed in bean from within the Freemarker template

2009-11-25T23:25:33Z

Hi Billy,

Could you please create a runnable example from this problem? You can take one of the smooks examples and change it so that it represents your use case. That way I can easily debug it and see what is happening.

Also please respond on the user mail list next time. That way other Smooks developers see your mail and can help you.

So, please build me an example and send it to me. I will look into it then.

Regards,

Maurice

On Wed, Nov 25, 2009 at 8:15 PM, Billy Buzzard <Billy.Buzzard@...> wrote:

Hey Maurice,

I think you are on the right path, but something is still not right. This is what I have:

public class SmookIt {

      public static void main(String[] args) throws Exception {

            Smooks smooks = new Smooks("smooks-config.xml");

            ExecutionContext ec = smooks.createExecutionContext();

            BeanRepository beanRepository = BeanRepository.getInstance(ec);

            beanRepository.addBean("sourceFile", new SourceFile());

            File myfile = new File("result.xml");

            FileInputStream fis = new FileInputStream(myfile);

            try {

                  StringResult result = new StringResult();

                  smooks.filter(new StreamSource(fis), result, ec);

                  System.out.println(result);

            } finally {

                  smooks.close();

            }

      }

}

class SourceFile {

      private String name = "The Builder";

      public String getName() {

            return name;

      }

      public void setName(String name) {

            this.name = name;

      }



}

My smooks-config.xml looks like this:

<?xml version="1.0" encoding="UTF-8"?>

<smooks-resource-list xmlns="http://www.milyn.org/xsd/smooks-1.1.xsd" xmlns:flt="http://www.milyn.org/xsd/smooks/freemarker-1.1.xsd" xmlns:jb="http://www.milyn.org/xsd/smooks/javabean-1.1.xsd">

<params>

    <param name="stream.filter.type">SAX</param>

</params>

<jb:bindings beanId="stList" class="java.util.ArrayList" createOnElement="tset">

    <jb:wiring beanIdRef="st"/>

</jb:bindings>

<jb:bindings beanId="st" class="com.bnsflogistics.amazon.model.ST" createOnElement="st">

    <jb:value data="st01" property="st01"/>

    <jb:value data="st02" property="st02"/>

    <jb:wiring beanIdRef="cartonDetailList" property="cartonDetailList"/>

</jb:bindings>

<jb:bindings beanId="cartonDetailList" class="java.util.ArrayList" createOnElement="st">

    <jb:wiring beanIdRef="cartonDetail"/>

</jb:bindings>

<jb:bindings beanId="cartonDetail" class="com.bnsflogistics.amazon.model.CartonDetail" createOnElement="/tset/st/loop200_smd/loop240_cd3">

    <jb:value data="/tset/st/loop200_smd/loop240_cd3/cd301" property="wtQual"/>

    <jb:value data="/tset/st/loop200_smd/loop240_cd3/cd302" property="weight"/>

    <jb:wiring beanIdRef="busnInstRefNoList" property="busnInstRefNoList"/>

</jb:bindings>

<jb:bindings beanId="busnInstRefNoList" class="java.util.ArrayList" createOnElement="/tset/st/loop200_smd/loop240_cd3">

    <jb:wiring beanIdRef="busnInstRefNo"/>

</jb:bindings>

<jb:bindings beanId="busnInstRefNo" class="com.bnsflogistics.amazon.model.BusnInstRefNo" createOnElement="/tset/st/loop200_smd/loop240_cd3">

    <jb:value data="/tset/st/loop200_smd/loop240_cd3/l11/l1101" property="refId"/>

    <jb:value data="/tset/st/loop200_smd/loop240_cd3/l11/l1102" property="refIdQual"/>

</jb:bindings>

<flt:freemarker applyOnElement="/tset/st">

    <flt:template><![CDATA[<st id="${st.st02}">

            <wtQual>${cartonDetail.wtQual}</wtQual>

            <weight>${cartonDetail.weight}</weight>

            <upsTracking>${busnInstRefNo.upsTracking}</upsTracking>

            <transport>${busnInstRefNo.transport}</transport>

            <msgRef>${busnInstRefNo.msgRef}</msgRef>

            <sourceFile>aaa</sourceFile>

      </st>]]></flt:template>

</flt:freemarker>

</smooks-resource-list>

When I replace the “<sourceFile>aaa</sourceFile>” in the smooks-config file above with “<sourceFile>${sourceFile.name}</sourceFile>” I get an error. What am I doing wrong!

From forum: milyn - user

Re: When will Smooks 1.3 be released?

2009-11-25T13:28:08Z

Many thanks Maurice for your help,

Chris

Maurice Zeijen-2 wrote:

Hi Chris,

There are only a few little things to be done. I expect that we release
within a couple of weeks, but I don't promise anything. The current snapshot
codebase is very stable. So you could start using that. You can use Maven or
Ant to retrieve the Smooks 1.3 snapshot release. Take a look here:
http://www.smooks.org/mediawiki/index.php?title=Maven_%26_Ant#Getting_SNAPSHOTs

Regards,

Maurice

On Wed, Nov 25, 2009 at 5:46 PM, ccdigix <Chris.Clohosy@mandg.co.uk> wrote:

>
> Hi,
>
> I like the product, was just wondering when version 1.3 of Smooks will be
> officially released? I'm in need of some fixed length processing :-)
>
> Thanks,
>
> Chris
> --
> View this message in context:
> http://old.nabble.com/When-will-Smooks-1.3-be-released--tp26516149p26516149.html
> Sent from the milyn - user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

From forum: milyn - user

RE: RE: [SPAM] - Re: [milyn-user] How do you pass values into a smooks filter. - Email found in subject

2009-11-25T11:39:43Z

Nevermind, I figured it out. I was making this too hard. Thanks for the help Maurice.

From: Billy Buzzard [mailto:Billy.Buzzard@...]
Sent: Wednesday, November 25, 2009 11:47 AM
To: user@...
Subject: [milyn-user] RE: [SPAM] - Re: [milyn-user] How do you pass values into a smooks filter. - Email found in subject

Hey Maurice,

I think you are on the right path, but something is still not right. I did exactly what you showed me to do. I used a JavaResults object for the result object so I could see all of the beans that were processed by the filter, but an empty result was returned. I expected to see the sourceFile bean plus all of the other beans that the smooks-config.xml script identified for the filter. What did I do wrong?

From: Maurice Zeijen [mailto:smies.com@...]
Sent: Wednesday, November 25, 2009 1:37 AM
To: user@...
Subject: [SPAM] - Re: [milyn-user] How do you pass values into a smooks filter. - Email found in subject

Hey Billy,

Here is a solution, expecting you are using Smooks 1.1 or a newer version. You can use the BeanRepository to provide the filter process with beans before you call the smooks filter method. Here is an example:

// Create an exec context
executionContext = smooks.createExecutionContext();

// Retrieve the BeanRepository from the executionContext
BeanRepository beanRepository = BeanRepository.getInstance(executionContext);

// Add the file to the bean repository
beanRepository.addBean("sourceFile", sourceFile)

// Filter the input data
smooks.filterSource(executionContext, source, result);

When the file name is in the bean repository then you can use it like any bean that you created within Smooks.

I hope this was enough information.

M.

On Tue, Nov 24, 2009 at 11:49 PM, Billy Buzzard <Billy.Buzzard@...> wrote:

I have a smooks-config.xml script that reads some java beans and saved the values into a database. I want to save the filename in each database record that shows where the data for the javabeans came from. Does anyone know how to do this?

From forum: milyn - user

RE: [SPAM] - Re: [milyn-user] How do you pass values into a smooks filter. - Email found in subject

2009-11-25T09:47:26Z

Hey Maurice,

On Tue, Nov 24, 2009 at 11:49 PM, Billy Buzzard <Billy.Buzzard@...> wrote:

From forum: milyn - user

Re: When will Smooks 1.3 be released?

2009-11-25T09:00:59Z

Hi Chris,

There are only a few little things to be done. I expect that we release within a couple of weeks, but I don't promise anything. The current snapshot codebase is very stable. So you could start using that. You can use Maven or Ant to retrieve the Smooks 1.3 snapshot release. Take a look here: http://www.smooks.org/mediawiki/index.php?title=Maven_%26_Ant#Getting_SNAPSHOTs

Regards,

Maurice

On Wed, Nov 25, 2009 at 5:46 PM, ccdigix <Chris.Clohosy@...> wrote:

Hi,

I like the product, was just wondering when version 1.3 of Smooks will be
officially released? I'm in need of some fixed length processing :-)

Thanks,

Chris
--
View this message in context: http://old.nabble.com/When-will-Smooks-1.3-be-released--tp26516149p26516149.html
Sent from the milyn - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - user

When will Smooks 1.3 be released?

2009-11-25T08:46:43Z

Hi,

I like the product, was just wondering when version 1.3 of Smooks will be officially released? I'm in need of some fixed length processing :-)

Thanks,

Chris

From forum: milyn - user

Re: SV: SV: SV: SV: EJC - javadoc

2009-11-25T02:27:15Z

I was just thinking... if they all extended the same abstract base type
(JNamedType?), we could just add the docs there. No need for the JDoc
class. We might need to create a new JProperty type, which would take
the place of JNamedType for properties and would be kinda like
JNamedType, accept it has really general info about the type - name,
docs etc. In fact, "JMember" would probably be a more accurate name?

T.

Bård Langöy wrote:

> Hmm... I have no idea :)
>
> Regards,
> Bård
>
> -----Ursprungligt meddelande-----
> Från: Tom Fennelly [mailto:tom.fennelly@...]
> Skickat: den 25 november 2009 09:09
> Till: dev@...
> Ämne: Re: SV: SV: SV: [milyn-dev] EJC - javadoc
>
> I must have looked the other day, but why did we no make JClass, JMethod
> etc extend JNamedType??
>
> T.
>
>
> Bård Langöy wrote:
>
>> Hi Tom,
>>
>> Yes, this makes sense to me :). Great you've had a look at it !
>>
>> So then the JDoc class could have the properties:
>>
>> * String documentation
>> * List<ParamEntry<String, String>> parameters
>>
>> My original suggestion using a Map will not work when there are more than 1 param for a method.
>>
>>
>> So, have you had time to look at the ECT ? It would be nice to discuss some of my implementation. I think for example someone should take a look at the ftl-script I wrote for writing out the Edimap-model. The script tries to fix indentation and stuff while writing out so the script-code might not be the most clean and readable code I have written :).
>>
>> Regards,
>> Bård
>>
>> -----Ursprungligt meddelande-----
>> Från: Tom Fennelly [mailto:tom.fennelly@...]
>> Skickat: den 24 november 2009 09:40
>> Till: dev@...
>> Ämne: Re: SV: SV: [milyn-dev] EJC - javadoc
>>
>> Hey Bard.
>>
>> Had a look at it. Looks to me like your original suggestion is good
>> i.e. to create a JDoc or JJavadoc class and use it on the JClass and
>> JMethod types. I'd also put it on JNamedType. This way you can javadoc
>> at the class, property, method and method parameter levels. The
>> setter/getter methods are based on the addition of the properties
>> anyway, so the docs will be the same for the properties and the
>> getter/setter method params/returns.
>>
>> Am I making sense this time? Sorry about the confusion.
>>
>> T.
>>
>>
>> Tom and have an Fennelly wrote:
>>
>>
>>> Hey Bard.... sorry about not coming back on this. Not quite sure
>>> which classes... I'm going to have a look at your new config
>>> generation code tonight, so will hopefully have a better idea then.
>>>
>>> T.
>>>
>>> Bård Langöy wrote:
>>>
>>>
>>>> Hi Tom,
>>>>
>>>> Mmmmm... so you mean we should store the documentation in the
>>>> JNamedType ?
>>>>
>>>> Regards,
>>>> Bård
>>>>
>>>> -----Ursprungligt meddelande-----
>>>> Från: Tom Fennelly [mailto:tom.fennelly@...] Skickat: den 17
>>>> november 2009 09:07
>>>> Till: dev@...
>>>> Ämne: Re: SV: [milyn-dev] EJC - javadoc
>>>>
>>>> Hey Bard.
>>>>
>>>> No.... I was trying to say that we keep the class level docs (about
>>>> the type in general). I'm saying NOT to store getter/setter method
>>>> level specific docs, but to generate them from the docs associated
>>>> with the property (so store at the property level), associated with
>>>> those methods. Hope that makes sense :)
>>>>
>>>> T.
>>>>
>>>> Bård Langöy wrote:
>>>>
>>>>
>>>>
>>>>> Hi Tom,
>>>>>
>>>>> That sounds great to me. So we skip the javadoc at class-level then
>>>>> ? And only apply the documentation for the setter and getter methods ?
>>>>>
>>>>> And for the param attribute we autogenerate something like
>>>>>
>>>>> @param ${variableName} the ${variableName}.
>>>>>
>>>>> Maybe we can get something more out if this. I just don't know how
>>>>> much info we have about the parameter.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Bård
>>>>>
>>>>> *Från:* Tom Fennelly [mailto:tom.fennelly@...]
>>>>> *Skickat:* den 16 november 2009 15:29
>>>>> *Till:* dev@...
>>>>> *Ämne:* Re: [milyn-dev] EJC - javadoc
>>>>>
>>>>> Hey Bard.
>>>>>
>>>>> I had thought about the javadoc slightly differently in that we'd
>>>>> store the documentation on the class and then on the properties of
>>>>> the class. Then, when creating the getter and setter methods for the
>>>>> properties, we'd take the documentation from the property and...
>>>>>
>>>>> Example... property "lastName"... documentation on property "Last
>>>>> Name of Customer"... getter and setter methods....
>>>>>
>>>>> /**
>>>>> * Get Last Name of Customer.
>>>>> * @return Last Name of Customer.
>>>>> */
>>>>> ... method...
>>>>>
>>>>>
>>>>> /**
>>>>> * Set Last Name of Customer.
>>>>> * @param lastName Last Name of Customer.
>>>>> */
>>>>> ... method
>>>>>
>>>>> Done this way, I don't think we need to create special classes for
>>>>> storing the docs... just store them as a String on the appropriate
>>>>> object, no?
>>>>>
>>>>> T.
>>>>>
>>>>>
>>>>> Bård Langöy wrote:
>>>>>
>>>>> Good morning,
>>>>>
>>>>> I have been looking into the javadoc support for EJC. There are two
>>>>> places where we should introduce the documentation: at class-level
>>>>> and method-level.
>>>>>
>>>>> So maybe we should introduce a new class JJavaDoc or JDoc that
>>>>> exists in both JClass and JMethod.
>>>>>
>>>>> Class : JDoc/JJavaDoc
>>>>>
>>>>> String documentation;
>>>>>
>>>>> Map<String, String> params;
>>>>>
>>>>> I don't think we can say much useful for each param but if we create
>>>>> the javadoc then I think it should exist.
>>>>>
>>>>> Any thoughts / suggestions ?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Bård
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>> http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>> http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - dev

SV: SV: SV: SV: EJC - javadoc

2009-11-25T01:23:05Z

Hmm... I have no idea :)

Regards,
Bård

-----Ursprungligt meddelande-----
Från: Tom Fennelly [mailto:tom.fennelly@...]
Skickat: den 25 november 2009 09:09
Till: dev@...
Ämne: Re: SV: SV: SV: [milyn-dev] EJC - javadoc

I must have looked the other day, but why did we no make JClass, JMethod
etc extend JNamedType??

T.

Bård Langöy wrote:

> Hi Tom,
>
> Yes, this makes sense to me :). Great you've had a look at it !
>
> So then the JDoc class could have the properties:
>
> * String documentation
> * List<ParamEntry<String, String>> parameters
>
> My original suggestion using a Map will not work when there are more than 1 param for a method.
>
>
> So, have you had time to look at the ECT ? It would be nice to discuss some of my implementation. I think for example someone should take a look at the ftl-script I wrote for writing out the Edimap-model. The script tries to fix indentation and stuff while writing out so the script-code might not be the most clean and readable code I have written :).
>
> Regards,
> Bård
>
> -----Ursprungligt meddelande-----
> Från: Tom Fennelly [mailto:tom.fennelly@...]
> Skickat: den 24 november 2009 09:40
> Till: dev@...
> Ämne: Re: SV: SV: [milyn-dev] EJC - javadoc
>
> Hey Bard.
>
> Had a look at it. Looks to me like your original suggestion is good
> i.e. to create a JDoc or JJavadoc class and use it on the JClass and
> JMethod types. I'd also put it on JNamedType. This way you can javadoc
> at the class, property, method and method parameter levels. The
> setter/getter methods are based on the addition of the properties
> anyway, so the docs will be the same for the properties and the
> getter/setter method params/returns.
>
> Am I making sense this time? Sorry about the confusion.
>
> T.
>
>
> Tom and have an Fennelly wrote:
>
>> Hey Bard.... sorry about not coming back on this. Not quite sure
>> which classes... I'm going to have a look at your new config
>> generation code tonight, so will hopefully have a better idea then.
>>
>> T.
>>
>> Bård Langöy wrote:
>>
>>> Hi Tom,
>>>
>>> Mmmmm... so you mean we should store the documentation in the
>>> JNamedType ?
>>>
>>> Regards,
>>> Bård
>>>
>>> -----Ursprungligt meddelande-----
>>> Från: Tom Fennelly [mailto:tom.fennelly@...] Skickat: den 17
>>> november 2009 09:07
>>> Till: dev@...
>>> Ämne: Re: SV: [milyn-dev] EJC - javadoc
>>>
>>> Hey Bard.
>>>
>>> No.... I was trying to say that we keep the class level docs (about
>>> the type in general). I'm saying NOT to store getter/setter method
>>> level specific docs, but to generate them from the docs associated
>>> with the property (so store at the property level), associated with
>>> those methods. Hope that makes sense :)
>>>
>>> T.
>>>
>>> Bård Langöy wrote:
>>>
>>>
>>>> Hi Tom,
>>>>
>>>> That sounds great to me. So we skip the javadoc at class-level then
>>>> ? And only apply the documentation for the setter and getter methods ?
>>>>
>>>> And for the param attribute we autogenerate something like
>>>>
>>>> @param ${variableName} the ${variableName}.
>>>>
>>>> Maybe we can get something more out if this. I just don't know how
>>>> much info we have about the parameter.
>>>>
>>>> Regards,
>>>>
>>>> Bård
>>>>
>>>> *Från:* Tom Fennelly [mailto:tom.fennelly@...]
>>>> *Skickat:* den 16 november 2009 15:29
>>>> *Till:* dev@...
>>>> *Ämne:* Re: [milyn-dev] EJC - javadoc
>>>>
>>>> Hey Bard.
>>>>
>>>> I had thought about the javadoc slightly differently in that we'd
>>>> store the documentation on the class and then on the properties of
>>>> the class. Then, when creating the getter and setter methods for the
>>>> properties, we'd take the documentation from the property and...
>>>>
>>>> Example... property "lastName"... documentation on property "Last
>>>> Name of Customer"... getter and setter methods....
>>>>
>>>> /**
>>>> * Get Last Name of Customer.
>>>> * @return Last Name of Customer.
>>>> */
>>>> ... method...
>>>>
>>>>
>>>> /**
>>>> * Set Last Name of Customer.
>>>> * @param lastName Last Name of Customer.
>>>> */
>>>> ... method
>>>>
>>>> Done this way, I don't think we need to create special classes for
>>>> storing the docs... just store them as a String on the appropriate
>>>> object, no?
>>>>
>>>> T.
>>>>
>>>>
>>>> Bård Langöy wrote:
>>>>
>>>> Good morning,
>>>>
>>>> I have been looking into the javadoc support for EJC. There are two
>>>> places where we should introduce the documentation: at class-level
>>>> and method-level.
>>>>
>>>> So maybe we should introduce a new class JJavaDoc or JDoc that
>>>> exists in both JClass and JMethod.
>>>>
>>>> Class : JDoc/JJavaDoc
>>>>
>>>> String documentation;
>>>>
>>>> Map<String, String> params;
>>>>
>>>> I don't think we can say much useful for each param but if we create
>>>> the javadoc then I think it should exist.
>>>>
>>>> Any thoughts / suggestions ?
>>>>
>>>> Regards,
>>>>
>>>> Bård
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>> http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>> http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - dev

SV: SV: SV: SV: EJC - javadoc

2009-11-25T01:22:06Z

Hi Tom,

Yes that sounds like a smart way to do it.

Regards,
Bård

-----Ursprungligt meddelande-----
Från: Tom Fennelly [mailto:tom.fennelly@...]
Skickat: den 25 november 2009 08:59
Till: dev@...
Ämne: Re: SV: SV: SV: [milyn-dev] EJC - javadoc

Hey Bard.

I thought JDoc would just need:

* String summary
* String detail

As far as parameters on methods.... can't that be done by having JDoc a
member of JNamedType, which is used for the parameters, since the setter
parameters all come from the properties of POJO. No?

T.

Bård Langöy wrote:

From forum: milyn - dev

Re: SV: SV: SV: EJC - javadoc

2009-11-25T00:08:49Z

I must have looked the other day, but why did we no make JClass, JMethod
etc extend JNamedType??

T.

Bård Langöy wrote:

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - dev

Re: SV: SV: SV: EJC - javadoc

2009-11-24T23:59:27Z

Hey Bard.

I thought JDoc would just need:

* String summary
* String detail

As far as parameters on methods.... can't that be done by having JDoc a
member of JNamedType, which is used for the parameters, since the setter
parameters all come from the properties of POJO. No?

T.

Bård Langöy wrote:

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: milyn - dev