You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(4) |
Jul
(2) |
Aug
(7) |
Sep
(9) |
Oct
(2) |
Nov
(4) |
Dec
(17) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(14) |
Feb
(3) |
Mar
(8) |
Apr
(9) |
May
(4) |
Jun
(4) |
Jul
(5) |
Aug
(6) |
Sep
(12) |
Oct
|
Nov
(8) |
Dec
(33) |
| 2009 |
Jan
(7) |
Feb
(17) |
Mar
(17) |
Apr
(1) |
May
(1) |
Jun
(4) |
Jul
(8) |
Aug
(8) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
(1) |
Feb
(3) |
Mar
(1) |
Apr
(2) |
May
(1) |
Jun
|
Jul
(16) |
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2011 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(1) |
|
From: SourceForge.net <no...@so...> - 2011-12-02 16:56:58
|
Bugs item #3435025, was opened at 2011-11-08 08:24 Message generated for change (Comment added) made by keitamiyazaki You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3435025&group_id=170911 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: epcis-repository Group: v0.5 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: GE_recordTime is not updated correctly in subscriptions Initial Comment: I noticed that after first output message sent through a subscription it stops functioning correctly with following error: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ns3:EPCISQueryDocument schemaVersion="1.0" creationDate="2011-11-08T17:03:30.703+01:00" xmlns:ns2="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader" xmlns:ns4="urn:epcglobal:epcis:xsd:1" xmlns:ns3="urn:epcglobal:epcis-query:xsd:1" xmlns:ns5="urn:epcglobal:epcis-masterdata:xsd:1"> <EPCISBody> <ns3:ImplementationException> <reason>An unexpected error occurred while executing a subscribed query</reason> <queryName>SimpleEventQuery</queryName> <subscriptionID>127</subscriptionID> </ns3:ImplementationException> </EPCISBody> </ns3:EPCISQueryDocument> Looking into logs detected that after execution GE_recordTime parameter gets updated in wrong format: DEBUG (2011-11-08 17:03:10,398) [org.fosstrak.epcis.repository.query.QuerySubscription:237] - Executing subscribed query '127' with 1 parameters: DEBUG (2011-11-08 17:03:10,398) [org.fosstrak.epcis.repository.query.QuerySubscription:240] - param name: GE_recordTime DEBUG (2011-11-08 17:03:10,398) [org.fosstrak.epcis.repository.query.QuerySubscription:245] - param value: 1320768180197 Looking at QuerySubscription.updateRecordTime I see that the param is set in milliseconds, not as GregorianCalendar: private void updateRecordTime(final QueryParams queryParams, final Calendar initialRecordTime) { // update or add GE_recordTime restriction boolean foundRecordTime = false; for (QueryParam p : this.queryParams.getParam()) { if (p.getName().equalsIgnoreCase("GE_recordTime")) { LOG.debug("Updating query parameter 'GE_recordTime' with value '" + initialRecordTime + "'."); p.setValue(initialRecordTime.getTimeInMillis()); foundRecordTime = true; break; } } if (!foundRecordTime) { LOG.debug("Adding query parameter 'GE_recordTime' with value '" + initialRecordTime + "'."); QueryParam newParam = new QueryParam(); newParam.setName("GE_recordTime"); newParam.setValue(initialRecordTime); this.queryParams.getParam().add(newParam); } // update the subscription in the db updateSubscription(initialRecordTime); } That messes the whole subscriptions implementations. ---------------------------------------------------------------------- Comment By: Keita Miyazaki (keitamiyazaki) Date: 2011-12-02 08:56 Message: I think it is because "parseAsCalendar" method may process data formatted in only "plusmnYYYY-MM-DDThh:mm:ss[.S]TZD". Please find the attached patch code. /$HOME/Documents/workspace/epcis/epcis-repository% patch -p0 -E < patch.txt Index: src/main/java/org/fosstrak/epcis/repository/query/QueryOperationsModule.java =================================================================== --- src/main/java/org/fosstrak/epcis/repository/query/QueryOperationsModule.java (リビジョン 1875) +++ src/main/java/org/fosstrak/epcis/repository/query/QueryOperationsModule.java (作業コピー) @@ -23,6 +23,7 @@ import java.net.MalformedURLException; import java.net.URL; import java.sql.SQLException; +import java.sql.Timestamp; import java.text.ParseException; import java.util.ArrayList; import java.util.Calendar; @@ -267,7 +268,7 @@ } } else if (paramName.equals("GE_eventTime") || paramName.equals("LT_eventTime") || paramName.equals("GE_recordTime") || paramName.equals("LT_recordTime")) { - Calendar cal = parseAsCalendar(paramValue, paramName); + Calendar cal = parseAsCalendar(paramValue, paramName); Operation op = Operation.valueOf(paramName.substring(0, 2)); String eventField = paramName.substring(3, paramName.length()) + "Ms"; aggrEventQuery.addEventQueryParam(eventField, op, cal.getTimeInMillis()); @@ -686,6 +687,10 @@ // CXF returns an XMLGregorianCalendar instance if the // XML type is specified cal = ((XMLGregorianCalendar) queryParamValue).toGregorianCalendar(); + } else if (queryParamValue instanceof Long){ + // try to parse the Long value as timestamp + Timestamp tm = new Timestamp(((Long)queryParamValue).longValue()); + cal = TimeParser.convert(tm); } else { // try to parse the value manually String date = null; ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3435025&group_id=170911 |
|
From: Keita M. <em...@sf...> - 2011-11-19 09:36:50
|
Dear EPCIS developer team. My name is Keita Miyazaki and I am a graduate student at Keio university in Japan. The reason why I am writing this email to you is I' like to send a patch for fixing bugs. In epcis-repository-0.5.1, I could not receive subscribe queries because of the bug occurred when epcis parses GE_recordTime. And, in SOURFEFORGE, I found the same bug. http://sourceforge.net/tracker/?func=detail&aid=3435025&group_id=170911&atid=856005 I think that this is very simple, because "parseAsCalendar" method may process data formatted in only "plusmnYYYY-MM-DDThh:mm:ss[.S]TZD". I attached the patch for fixing. /$HOME/Documents/workspace/epcis/epcis-repository% patch -p0 -E < fix_parsing_of_timestamp_in_Bugs_3435025.patch Could you please confirm the patch and reply me. I am looking forward to hearing from you. Sincerely, Keita Miyazaki -- Keita Miyazaki Keio Univ / Auto-ID Lab. Japan em...@sf... |
|
From: Keita M. <em...@sf...> - 2011-11-19 09:31:51
|
Dear EPCIS developer team. My name is Keita Miyazaki and I am a graduate student at Keio university in Japan. The reason why I am writing this email to you is I' like to send a patch for fixing bugs. In epcis-repository-0.5.1, I could not receive subscribe queries because of the bug occurred when epcis parses GE_recordTime. And, in SOURFEFORGE, I found the same bug. http://sourceforge.net/tracker/?func=detail&aid=3435025&group_id=170911&atid=856005 I think that this is very simple, because "parseAsCalendar" method may process data formatted in only "plusmnYYYY-MM-DDThh:mm:ss[.S]TZD". I attached the patch for fixing. /$HOME/Documents/workspace/epcis/epcis-repository% patch -p0 -E < fix_parsing_of_timestamp_in_Bugs_3435025.patch Could you please confirm the patch and reply me. I am looking forward to hearing from you. Sincerely, Keita Miyazaki -- Keita Miyazaki Keio Univ / Auto-ID Lab. Japan em...@sf... |
|
From: SourceForge.net <no...@so...> - 2011-11-08 16:24:22
|
Bugs item #3435025, was opened at 2011-11-08 08:24 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3435025&group_id=170911 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: epcis-repository Group: v0.5 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: GE_recordTime is not updated correctly in subscriptions Initial Comment: I noticed that after first output message sent through a subscription it stops functioning correctly with following error: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ns3:EPCISQueryDocument schemaVersion="1.0" creationDate="2011-11-08T17:03:30.703+01:00" xmlns:ns2="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader" xmlns:ns4="urn:epcglobal:epcis:xsd:1" xmlns:ns3="urn:epcglobal:epcis-query:xsd:1" xmlns:ns5="urn:epcglobal:epcis-masterdata:xsd:1"> <EPCISBody> <ns3:ImplementationException> <reason>An unexpected error occurred while executing a subscribed query</reason> <queryName>SimpleEventQuery</queryName> <subscriptionID>127</subscriptionID> </ns3:ImplementationException> </EPCISBody> </ns3:EPCISQueryDocument> Looking into logs detected that after execution GE_recordTime parameter gets updated in wrong format: DEBUG (2011-11-08 17:03:10,398) [org.fosstrak.epcis.repository.query.QuerySubscription:237] - Executing subscribed query '127' with 1 parameters: DEBUG (2011-11-08 17:03:10,398) [org.fosstrak.epcis.repository.query.QuerySubscription:240] - param name: GE_recordTime DEBUG (2011-11-08 17:03:10,398) [org.fosstrak.epcis.repository.query.QuerySubscription:245] - param value: 1320768180197 Looking at QuerySubscription.updateRecordTime I see that the param is set in milliseconds, not as GregorianCalendar: private void updateRecordTime(final QueryParams queryParams, final Calendar initialRecordTime) { // update or add GE_recordTime restriction boolean foundRecordTime = false; for (QueryParam p : this.queryParams.getParam()) { if (p.getName().equalsIgnoreCase("GE_recordTime")) { LOG.debug("Updating query parameter 'GE_recordTime' with value '" + initialRecordTime + "'."); p.setValue(initialRecordTime.getTimeInMillis()); foundRecordTime = true; break; } } if (!foundRecordTime) { LOG.debug("Adding query parameter 'GE_recordTime' with value '" + initialRecordTime + "'."); QueryParam newParam = new QueryParam(); newParam.setName("GE_recordTime"); newParam.setValue(initialRecordTime); this.queryParams.getParam().add(newParam); } // update the subscription in the db updateSubscription(initialRecordTime); } That messes the whole subscriptions implementations. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3435025&group_id=170911 |
|
From: Christian S. <syr...@ya...> - 2011-10-10 11:17:37
|
Hi there, just started looking through the epcis-repository code where to start with a first test to finally replace SQL by JPA2 for capturing. My Aim is currently to replace some capture code so that an object event is persisted with JPA2 in an distributed Hadoop-Database (HBase). I saw mysql-queries in CaptureOperationsBackendSQL (impl. CaptureOperationsBackend) and therefore replaced code in insertEvent() only concerning objectEvent. So I started remote debugging and captured an event with the fosstrak capture client...and was surprised that CaptureOperationsBackendSQL isn't referenced anywhere. Are CaptureOperationsBackendSQL and CaptureOperationsBackend obsolete? As I just saw that a capture (servlet) triggers methods in CaptureOperationsModule I would replace (for a first test) the hibernate code by JPA2 Code first in CaptureOperationsModule.handleEvent(..) including annotating the model classes in org.fosstrak.epcis.repository.model Is that the right starting point? |
|
From: SourceForge.net <no...@so...> - 2011-06-08 08:06:36
|
Feature Requests item #3313599, was opened at 2011-06-08 04:06 Message generated for change (Settings changed) made by domguinard You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856008&aid=3313599&group_id=170911 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements (example) Group: Next Release (example) Status: Open >Priority: 7 Private: No Submitted By: Dominique Guinard (domguinard) Assigned to: Dominique Guinard (domguinard) Summary: Add support for extension fields in the Webadapter Initial Comment: The EPCIS Webadpater REST API currently does not support extension fields, the support should be added in the next release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856008&aid=3313599&group_id=170911 |
|
From: SourceForge.net <no...@so...> - 2011-06-08 08:06:12
|
Feature Requests item #3313599, was opened at 2011-06-08 04:06 Message generated for change (Tracker Item Submitted) made by domguinard You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856008&aid=3313599&group_id=170911 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements (example) Group: Next Release (example) Status: Open Priority: 5 Private: No Submitted By: Dominique Guinard (domguinard) Assigned to: Dominique Guinard (domguinard) Summary: Add support for extension fields in the Webadapter Initial Comment: The EPCIS Webadpater REST API currently does not support extension fields, the support should be added in the next release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856008&aid=3313599&group_id=170911 |
|
From: SourceForge.net <no...@so...> - 2011-01-06 19:07:37
|
Bugs item #3151524, was opened at 2011-01-04 18:29 Message generated for change (Comment added) made by domguinard You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3151524&group_id=170911 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Dominique Guinard (domguinard) Assigned to: Nobody/Anonymous (nobody) Summary: Exception when using the EPCIS Webadapter capture simulator Initial Comment: Whenever trying to capture something using the capture simulator of the EPCIS Webadapter, the system raises an exception: "org.epcis.fosstrak.restadapter.ws.generated" doesnt contain ObjectFactory.class or jaxb.index Note: this error was probably introduced during the refactoring of the restadapter to the webadapter. ---------------------------------------------------------------------- >Comment By: Dominique Guinard (domguinard) Date: 2011-01-06 14:07 Message: The bug was due to a refactoring. The JAXB context was not refactored to reflect the project name. This fix will be committed to the next release, meanwhile the fixed source code available from the svn. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3151524&group_id=170911 |
|
From: SourceForge.net <no...@so...> - 2011-01-04 23:29:23
|
Bugs item #3151524, was opened at 2011-01-04 18:29 Message generated for change (Tracker Item Submitted) made by domguinard You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3151524&group_id=170911 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dominique Guinard (domguinard) Assigned to: Nobody/Anonymous (nobody) Summary: Exception when using the EPCIS Webadapter capture simulator Initial Comment: Whenever trying to capture something using the capture simulator of the EPCIS Webadapter, the system raises an exception: "org.epcis.fosstrak.restadapter.ws.generated" doesnt contain ObjectFactory.class or jaxb.index Note: this error was probably introduced during the refactoring of the restadapter to the webadapter. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3151524&group_id=170911 |
|
From: Christof R. <rod...@in...> - 2010-12-29 09:06:34
|
Dear all, We have just uploaded Fosstrak EPCIS version 0.5.0 to the website at www.fosstrak.org/epcis/download.html. The new release fixes a number of bugs and introduces some new features: * Support for capturing EPCIS Master Data. Thanks to Nikos Kefalakis for this work. * Support for REST clients. The new release comes with a "Webadapter" module. This module allows you to access the EPCIS repository via web protocols, such as REST, in addition to the existing Web Services interface. Please refer to www.fosstrak.org/epcis/docs/webadapter-guide.html for details. Many thanks to Dominique Guinard and Mathias Mueller for this extension. For a full list of changes, please see the following change reports: * www.fosstrak.org/epcis/epcis-repository/changes-report.html * www.fosstrak.org/epcis/epcis-queryclient/changes-report.html * www.fosstrak.org/epcis/epcis-captureclient/changes-report.html * www.fosstrak.org/epcis/epcis-commons/changes-report.html * www.fosstrak.org/epcis/epcis-interop-test/changes-report.html Thanks to everybody who contributed (www.fosstrak.org/epcis/team-list.html) to the new release through bug reports and patches! We very much appreciate your help. Best regards, Christof and Marco |
|
From: Steybe, M. <st...@zu...> - 2010-08-10 15:10:20
|
Hi Chris,
you are right, the EQ_fieldname query parameter should be of type "List of String" according to the spec and the Fosstrak implementation should handle it appropriately. The current implementation works well for queries with a List of String where only a single element is given but fails if several strings are provided! I think your modification looks good. I will apply the changes to the current code ...
Thanks for the hint and suggestion!
Marco
________________________________________
From: Chris Valencia [cva...@ne...]
Sent: Monday, August 09, 2010 18:16
To: acc...@li...
Subject: [accada-epcis-developer] Question about the SimpleEventQuery for extension fields
Hi,
I had question about the Predefined SimpleEventQuery extension field parameters. In the table in Section 8.2.7.1 for the entry EQ_fieldname the data type for the String option is List of String and not String. The current repository only takes a single string value. In the QueryOperationsModule.java at line 395 after attempting all of the other types the value is parsed as a string:
value = parseAsString(paramValue);
eventField = eventFieldExtBase + ".strValue";
In order to support a list of string I changed this to be:
ArrayOfString aos = parseAsArrayOfString(paramValue);
if(!aos.getString().isEmpty()) {
value = aos.getString();
eventField = "extension.strValue";
}
And since this introduces the possibility of having a null value and no exception thrown at line 400 I wrapped the query param adds with a check to ensure that value is not null.
I was wandering if this seems correct? Or did I miss read the specification and/or the code? I made these changes and then tested by sending a list of string and it has been working. The reason I am so interested is that in our system it is very beneficial to query for a list of string for the equal field extension. In the current implementation we have to query the repository several times for each field extension value we are gathering.
Thank you,
Chris Valencia
Chief Technical Officer
New Planet Technologies
Phone: 719-685-7900 ext. 161
|
|
From: Chris V. <cva...@ne...> - 2010-08-09 16:41:24
|
Hi,
I had question about the Predefined SimpleEventQuery extension field
parameters. In the table in Section 8.2.7.1 for the entry EQ_fieldname the
data type for the String option is List of String and not String. The
current repository only takes a single string value. In the
QueryOperationsModule.java at line 395 after attempting all of the other
types the value is parsed as a string:
value = parseAsString(paramValue);
eventField = eventFieldExtBase + ".strValue";
In order to support a list of string I changed this to be:
ArrayOfString aos = parseAsArrayOfString(paramValue);
if(!aos.getString().isEmpty()) {
value = aos.getString();
eventField = "extension.strValue";
}
And since this introduces the possibility of having a null value and no
exception thrown at line 400 I wrapped the query param adds with a check to
ensure that value is not null.
I was wandering if this seems correct? Or did I miss read the specification
and/or the code? I made these changes and then tested by sending a list of
string and it has been working. The reason I am so interested is that in
our system it is very beneficial to query for a list of string for the equal
field extension. In the current implementation we have to query the
repository several times for each field extension value we are gathering.
Thank you,
Chris Valencia
Chief Technical Officer
New Planet Technologies
Phone: 719-685-7900 ext. 161
|
|
From: <rab...@or...> - 2010-08-05 07:16:36
|
Hi Marco, Thanks for the response ! Yes, I am implementing an access-control mechanism so Tomcat authentication is not sufficient. But you're right, sending the user credentials along with the query is not at all a good idea, however, i did find the solution with the help of Marc-Antoine ! I use Tomcat (as described by fosstrak but with a JDBC Realm), then in the epcis-repository i get the username from the context of the webservice using the java.security.Principal class + javax.xml.ws.WebServiceContext class, and it's working smoothly ! Thanks again ---- Yours sincerely, Rabia AZIZA -----Message d'origine----- De : Steybe, Marco [mailto:st...@zu...] Envoyé : mercredi 4 août 2010 15:39 À : AZIZA Rabia RD-BIZZ-SOP; acc...@li... Objet : RE: [accada-epcis-developer] Sending username/password to theepcis-repository Hi Rabia, I'm not sure if I understand exactly what you wish to achieve. But the Fosstrak EPCIS repository does not currently support any backend access-control mechanisms. However, you can configure Tomcat to require client authentication before access to the EPCIS repository is granted. Please see the section "Securing your Repository" in the user guide: http://www.fosstrak.org/epcis/docs/user-guide.html#Securing%20your%20Repository. Apart from that, if your goal is to implement such an access-control mechanism then you should probably first authenticate a client, e.g., based on one of the existing client authentication mechanisms (HTTP BASIC or client-cert authentication) and then authorize certain actions based on the authenticated identity. Sending user credentials directly to the backend as part of an EPCIS query is probably not the right idea!? Regards, Marco ________________________________________ From: rab...@or... [rab...@or...] Sent: Tuesday, August 03, 2010 16:25 To: acc...@li... Subject: [accada-epcis-developer] Sending username/password to the epcis-repository Good day, I'm currently developing in the epcis-repository module, and i'm using the two client java interfaces (queryclient and captureclient) given by fosstrak. I want to know please : how can i send the username/password to the epcis-repository along with the query (when using the queryclient interface and without going thru Tomcat). I tried modifying the queryclient and sending the username and password as parameters in the query itself (in the QueryParams), and then ofcourse picking them up at the epcis-repository. This works fine, but i believe it makes the query not standard anymore. Is there another way? Thanks ---- Yours sincerely, Rabia AZIZA |
|
From: Steybe, M. <st...@zu...> - 2010-08-04 13:39:34
|
Hi Rabia, I'm not sure if I understand exactly what you wish to achieve. But the Fosstrak EPCIS repository does not currently support any backend access-control mechanisms. However, you can configure Tomcat to require client authentication before access to the EPCIS repository is granted. Please see the section "Securing your Repository" in the user guide: http://www.fosstrak.org/epcis/docs/user-guide.html#Securing%20your%20Repository. Apart from that, if your goal is to implement such an access-control mechanism then you should probably first authenticate a client, e.g., based on one of the existing client authentication mechanisms (HTTP BASIC or client-cert authentication) and then authorize certain actions based on the authenticated identity. Sending user credentials directly to the backend as part of an EPCIS query is probably not the right idea!? Regards, Marco ________________________________________ From: rab...@or... [rab...@or...] Sent: Tuesday, August 03, 2010 16:25 To: acc...@li... Subject: [accada-epcis-developer] Sending username/password to the epcis-repository Good day, I'm currently developing in the epcis-repository module, and i'm using the two client java interfaces (queryclient and captureclient) given by fosstrak. I want to know please : how can i send the username/password to the epcis-repository along with the query (when using the queryclient interface and without going thru Tomcat). I tried modifying the queryclient and sending the username and password as parameters in the query itself (in the QueryParams), and then ofcourse picking them up at the epcis-repository. This works fine, but i believe it makes the query not standard anymore. Is there another way? Thanks ---- Yours sincerely, Rabia AZIZA |
|
From: <rab...@or...> - 2010-08-03 14:38:38
|
Good day, I'm currently developing in the epcis-repository module, and i'm using the two client java interfaces (queryclient and captureclient) given by fosstrak. I want to know please : how can i send the username/password to the epcis-repository along with the query (when using the queryclient interface and without going thru Tomcat). I tried modifying the queryclient and sending the username and password as parameters in the query itself (in the QueryParams), and then ofcourse picking them up at the epcis-repository. This works fine, but i believe it makes the query not standard anymore. Is there another way? Thanks ---- Yours sincerely, Rabia AZIZA |
|
From: <mar...@or...> - 2010-07-28 13:30:40
|
Hi there,
I made my new tests with the *correct* latest snapshot and I have found a SQL query bug when I do the capture (caps mismatch).
This is a classical bug that won't appear on win32 systems but would appear on any Unix-based system:
Table 'epcis.voc_epcClass_attr' doesn't exist.
The right table name with the current schema should be voc_EPCClass_attr
________________________________
De : mar...@or... [mailto:mar...@or...]
Envoyé : vendredi 23 juillet 2010 10:33
À : st...@zu...; nk...@ai...; acc...@li...
Objet : [accada-epcis-developer] RE : Can't install latest snapshot with AIT's developments
Oh I found it
There is a
private WebServiceContext context;
private String userName = context.getUserPrincipal().getName();
at line 143 that does not seem to be in the latest online version. So I guess I had a tortoiseSVN problem that misled me.
I'll clean up everything and test again. I'll tell you the results.
Marc-Antoine
-------- Message d'origine--------
De: Steybe, Marco [mailto:st...@zu...]
Date: ven. 23/07/2010 09:38
À: MOUILLERON Marc-Antoine RD-BIZZ-SOP; nk...@ai...; acc...@li...
Objet : RE: Can't install latest snapshot with AIT's developments
Hi Marc-Antoine,
1) that's right the mysql connector jar needs to be placed in the tomcat's lib directory (it's explained in the user's guide "Setting up your own Repository")
2) this problem was reported as a bug some days ago: http://sourceforge.net/tracker/?func=detail&aid=3027356&group_id=170911&atid=856005 -> there are 2 solutions to it explained in the bug description and comment
3) still no clue :( The weird thing is that your stacktrace refers to "java.lang.NullPointerException at org.fosstrak.epcis.repository.query.QueryOperationsModule.<init>(QueryOperationsModule.java:143)", unfortunately there is nothing but javadoc at line 143 of QueryOperationsModule.java. Are you sure you're working with the latest source code? I will also try to run a clean install to see if I run into the same problem.
Regards,
Marco
________________________________________
From: mar...@or... [mar...@or...]
Sent: Friday, July 23, 2010 08:38
To: Steybe, Marco; nk...@ai...; acc...@li...
Subject: RE: Can't install latest snapshot with AIT's developments
Hi,
Yes I did the same first two steps. The only difference is I did not deploy from maven but directly by uploading/deploying the war on tomcat.
I tried again this morning on a blank win32 install with a new Tomcat (7.0) but I still have similar issues
1) on a blank Tomcat install, you have to add the mysql-connection jar in the /lib directory (I don't think it is written in Fosstrak's user guide). Or should it be in the epcis-repository lib dire'ctory?
2) I tried to create the database also on my Windows system (MySQL InnoDB / utf8), but the epcis_schema script makes the error : "Specified key was too long; max key length is 767 bytes" on the "create table subscription" phase
3) and anyhow, I still have the problem I initially quoted:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'queryOperationsModule' defined in ServletContext resource [/META-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:813)
Does it sound like a CXF problem? I know you updated CXF's version to 2.2, might it create that kind of issue?
Regards,
Marc-Antoine
-----Message d'origine-----
De : Steybe, Marco [mailto:st...@zu...]
Envoyé : jeudi 22 juillet 2010 18:11
À : Nikos Kefalakis; MOUILLERON Marc-Antoine RD-BIZZ-SOP; acc...@li...
Objet : RE: Can't install latest snapshot with AIT's developments
Hi Marc-Antoine,
I was able to test a full roundtrip using the new Master data capture interface. Here is what I did:
- updated my local code to the latest SVN revision (I already had a working MySQL instance and a Tomcat running)
- mvn clean install
- mvn tomcat:redeploy -> the application was successfully started without complaints
- sent a master data vocabulary XML (type readPoint, id="MyReadPoint") to the capture interface -> it was successfully stored to the EPCIS db
- captured an event with a readPoint reference to "MyReadPoint"
- queried the event -> the response included readPoint with id "MyReadPoint"
- queried master data for name "MyReadPoint" -> the response included the correct attribute/value pair
I'm also working on a win32 machine ...
So, at least from this simple test the new interface seems to work quite nicely :) Thanks Nikos!
Regarding your problem, Marc-Antoine, I'm afraid I can't help much either. Are you also working with the maven commands to build and deploy the application?
Regards,
Marco
________________________________________
From: Nikos Kefalakis [nk...@ai...]
Sent: Thursday, July 22, 2010 17:28
To: mar...@or...; acc...@li...
Cc: Steybe, Marco
Subject: RE: Can't install latest snapshot with AIT's developments
Dear Marc-Antoine,
I have just finished downloading (with tortoise SVN), building and testing the latest EPCIS repository snapshot by following the directions at the Fosstrak site ("http://www.fosstrak.org/epcis/docs/developer-guide.html#Building and Deploying the Project") run the "mvn install", "mvn compile" and "mvn package"and using the database schema that comes with this EPCIS version (at "\apache-tomcat-6.0.24\webapps\epcis-repository-0.4.3-SNAPSHOT\WEB-INF\classes") into two different window XP 32bit machines (the one was clean install so the SVN local repository wasn't previously been downloaded and only the CATALINA_HOME, the JAVA_HOME, and the Maven environmental virables set up to the system) and I didn't face any problems or errors. I don't have the ability to test it at a Linux platform but I cant really think of a reason for the error you are describing. Just make sure that when you undeploy (delete from webapps) the previous version of the epcis-repository to have the tomcat running and that it has not left any "remainder" before deploying the new version.
Best Regards,
Nikos Kefalakis
Athens Information Technology
Tel.: +30 210 668 2755
From: mar...@or... [mailto:mar...@or...]
Sent: ??????, 22 ??????? 2010 3:20 ??
To: acc...@li...
Cc: nk...@ai...; st...@zu...
Subject: Can't install latest snapshot with AIT's developments
Hello Nikos,
I downloaded the latest EPCIS repository snapshot yesterday, compiled it, and tried to install it on a Linux server with usual Tomcat/MySQL version.
The war extracts successfully but the application won't start.
I made several tries with different MySQL databases, then I finished with following the steps from the Fosstrak user manual (sample "epcis" database).
I have the following error message (attached is the full epcis-repository.log). Any idea of the reason for it?
[org.springframework.web.context.ContextLoader:215] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'queryOperationsModule' defined in ServletContext resource [/META-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:813)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:769)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:412)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383)
at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:400)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:627)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:98)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:807)
... 39 more
Caused by: java.lang.NullPointerException at org.fosstrak.epcis.repository.query.QueryOperationsModule.<init>(QueryOperationsModule.java:143)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:83)
... 41 more
INFO (2010-07-22 14:09:59,525) [org.fosstrak.epcis.repository.RepositoryContextListener:94] - Fosstrak EPCIS Repository application shut down
[cid:image001.gif@01CB29C6.1BADF5C0]
Marc-Antoine Mouilleron
Orange Labs - Business Services
905 rue Albert Einstein
06921 Sophia-Antipolis Cedex - France
tel. +33 (0)4 92 94 53 10
mob. +33 6 32 29 88 79
fax +33 (0)4 93 65 35 91
mar...@or...<mailto:mar...@or...>
[cid:image002.gif@01CB29C6.1BADF5C0]
|
|
From: Christof R. <rod...@in...> - 2010-07-24 07:16:03
|
Dear Nikos, Great, many thanks for your work! We will prepare a new release including your changes and other pending bugfixes as soon as possible. Best regards, Christof On 20.07.2010 21:24, Nikos Kefalakis wrote: > Dear all, > > I would like to announce that the latest Fosstrak EPCIS Repository > revision supports the MasterData document capture functionality. > > This new Capture functionality is not defined at the EPCIS specification > and uses the available EPCIS, standard defined, capture interface > without affecting its Event capture functionality. > > For now it is available by using the “epcis-commons” Revision 1724 and > the “epcis-repository” Revision 1725 from Fosstraks Source code SVN > repository (https://svn.fosstrak.org/repos/epcis/trunk). > > For the “epcis-commons” (Revision 1724) the "@XmlRootElement" annotation > was added at 4 epcis's objects. More spessifically the AggregationEvent, > the TransactionEvent, the QuantityEvent and the ObjectEvent (e.g. > @XmlRootElement(name = "ObjectEvent", namespace = ""). > > For the “epcis-repository” (Revision 1725) a numerous of required > changes/additions were made to support the Master Data Document capture > functionality and the way Vocabulary’s children are stored to the > database was also been changed (they were divided with the “_” sign and > now the “,” sign is used) > > So now, for example, to save to the EPCIS repository the > “Some_Test_Vocabulary_URI”, as the Vocabulary element URI, to the Read > Point Vocabulary (urn:epcglobal:epcis:vtype:ReadPoint) with the > “Some_Test_Vocabulary_Attr_Name”, as the Vocabulary Element’s Attribute > name, and the “Some_Test_Vocabulary_Attr_Value”, as the Vocabulary > Element’s Attribute value, the following, EPCISMasterDataDocument > compliant, XML should be sent to the EPCIS’s Capture I/F: > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > > <ns4:EPCISMasterDataDocument > creationDate="2010-07-20T20:22:50.718+03:00" schemaVersion="1.0" > xmlns:ns2="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader" > xmlns:ns4="urn:epcglobal:epcis-masterdata:xsd:1" > xmlns:ns3="urn:epcglobal:epcis-query:xsd:1" > xmlns:ns5="urn:epcglobal:epcis:xsd:1"> > > <EPCISBody> > > <VocabularyList> > > <Vocabulary type="urn:epcglobal:epcis:vtype:ReadPoint"> > > <VocabularyElementList> > > <VocabularyElement id="Some_Test_Vocabulary_URI"> > > <attribute id="urn:epcglobal:epcis:mda:Some_Test_Vocabulary_Attr_Name" > > value="Some_Test_Vocabulary_Attr_Value"/> > > </VocabularyElement> > > </VocabularyElementList> > > </Vocabulary> > > </VocabularyList> > > </EPCISBody> > > </ns4:EPCISMasterDataDocument> > > Now if we would like to delete it we should sent the following: > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > > <ns4:EPCISMasterDataDocument > creationDate="2010-07-20T20:27:01.781+03:00" schemaVersion="1.0" > xmlns:ns2="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader" > xmlns:ns4="urn:epcglobal:epcis-masterdata:xsd:1" > xmlns:ns3="urn:epcglobal:epcis-query:xsd:1" > xmlns:ns5="urn:epcglobal:epcis:xsd:1"> > > <EPCISBody> > > <VocabularyList> > > <Vocabulary type="urn:epcglobal:epcis:vtype:ReadPoint"> > > <VocabularyElementList> > > <VocabularyElement id="Some_Test_Vocabulary_URI" mode="3"/> > > </VocabularyElementList> > > </Vocabulary> > > </VocabularyList> > > </EPCISBody> > > </ns4:EPCISMasterDataDocument> > > Many more xml MasterData capturing “commands” are supported from the > EPCIS’s Master Data capture I/F which are, for your convenience, created > from the Master Data capture client and the following methods: > > - alterVocElem (String vocabularyType, String oldVocabularyElementURI, > String newVocabularyElementURI) > > Which is used to alter a vocabulary's Element URI. > > - insertVocElem (String vocabularyType, String vocabularyElementURI) > > Which is used to insert a vocabulary's Element. > > - massInsertVocElem (String vocabularyType, ArrayList<String> > vocabularyElementURIs) > > Which is used to insert many vocabulary's Elements. > > - deleteVocElem (String vocabularyType, String vocabularyElementURI) > > Which is used to delete a vocabulary's Element (When using single delete > only the element with its attributes will be deleted). > > - massDeleteVocElem (String vocabularyType, ArrayList<String> > vocabularyElementURIs) > > Which is used to delete many vocabulary's Elements (When using mass > delete only the listed elements with their attributes will be deleted). > > - deleteWithDescendantsVocElem (String vocabularyType, String > vocabularyElementURI) > > Which is used to delete a vocabulary's Element with its direct or > indirect descendants (The element with its attributes and with all of > its children elements and its children's attributes will be deleted). > > - massDeleteWithDescendantsVocElem (String vocabularyType, > ArrayList<String> vocabularyElementURIs) > > Which is used to delete many vocabulary's with their Elements and with > their direct or indirect descendants. The elements with its attributes > and with all of its children elements and its children's attributes will > be deleted. > > - insertOrAlterVocElemAttr (String vocabularyType, String > vocabularyElementURI, String vocabularyAttributeName, String > vocabularyAttributeValue) > > Which is used to insert or Update a vocabulary Element’s Attribute. If > the Vocabulary is not inserted yet it will be inserted. The > vocabularyElementURI, vocabularyAttributeName pair should be unique so > if it already exists it will be changed to the vocabularyAttribute > entered or simply rewrite it. > > - massInsertOrAlterVocElemAttr (String vocabularyType, String > vocabularyElementURI, HashMap<String, String> vocabularyAttributes) > > Which is used to mass Insert or Update a vocabulary Element’s > Attributes. If the Vocabulary is not inserted yet it will be inserted. > The vocabularyElementURI, vocabularyAttributeName pair (the > vocabularyAttributeName is the key of the vocabularyAttributes HashMap) > should be unique so if it already exists it will be changed to the > vocabularyAttributeValue (which is the value of the vocabularyAttributes > HashMap) entered or simply rewrite it. > > - deleteVocElemAttr (String vocabularyType, String vocabularyElementURI, > String vocabularyAttributeName) > > Which is used to delete a vocabulary Element’s Attribute. > > - massDeleteVocElemAttr (String vocabularyType, String > vocabularyElementURI, ArrayList<String> vocabularyAttributeNames) > > Which is used to delete many vocabulary Element’s Attributes. > > The latest MasterDataCaptureClient.java class can be found here: > http://websvn.ow2.org/filedetails.php?repname=aspire&path=%2Ftrunk%2Ftools%2FaspireRfidMasterDataCaptureClient%2Fsrc%2Fmain%2Fjava%2Forg%2Fow2%2Faspirerfid%2Fmasterdata%2Fcapture%2FMasterDataCaptureClient.java > <http://websvn.ow2.org/filedetails.php?repname=aspire&path=%2Ftrunk%2Ftools%2FaspireRfidMasterDataCaptureClient%2Fsrc%2Fmain%2Fjava%2Forg%2Fow2%2Faspirerfid%2Fmasterdata%2Fcapture%2FMasterDataCaptureClient.java> > > > And a demo Master Data capture application (source code) can be > downloaded from here: > svn://svn.forge.objectweb.org/svnroot/aspire/trunk/tools/aspireRfidMasterDataCaptureClient > > And its executable from here: > http://forge.ow2.org/project/download.php?group_id=324&file_id=15375 > <http://forge.ow2.org/project/download.php?group_id=324&file_id=15375> > > Moreover the Fosstrak EPCIS MasterData can now be edited with the use of > AspireRFID Master Data Editor plug-in > (http://wiki.aspire.ow2.org/xwiki/bin/view/Main.Documentation.AspireIDE/MasterDataEditor) > > Please feel free to test the MasterData capture I/F and report for any > existing bugs. Also due to the number of changes that has been done to > the EPCIS’s Capture I/F also check if everything is working normally at > the Event capture I/F also (the test from my side didn’t showed anything > wrong). > > One probable bug, that was noticed from the previous EPCIS revision > (without the MasterData capture changes been applied), is that for > accessing the EPCIS’s repository Query interface it requires to add the > “query/query” after the EPCIS’s address (e.g. for the current version > the following URL should be use > (http://localhost:8080/epcis-repository-0.4.3-SNAPSHOT/query/query). Is > that normal? > > Best Regards, > > Nikos Kefalakis > > AspireRFID Solution architect and lead developer > > AIT (http://www.ait.gr/) > > AspireRFID (http://wiki.aspire.ow2.org/) > > FAX: +30 210 668 2703 > > Tel.: +30 210 668 2755 > |
|
From: <mar...@or...> - 2010-07-23 08:36:39
|
Oh I found it
There is a
private WebServiceContext context;
private String userName = context.getUserPrincipal().getName();
at line 143 that does not seem to be in the latest online version. So I guess I had a tortoiseSVN problem that misled me.
I'll clean up everything and test again. I'll tell you the results.
Marc-Antoine
-------- Message d'origine--------
De: Steybe, Marco [mailto:st...@zu...]
Date: ven. 23/07/2010 09:38
À: MOUILLERON Marc-Antoine RD-BIZZ-SOP; nk...@ai...; acc...@li...
Objet : RE: Can't install latest snapshot with AIT's developments
Hi Marc-Antoine,
1) that's right the mysql connector jar needs to be placed in the tomcat's lib directory (it's explained in the user's guide "Setting up your own Repository")
2) this problem was reported as a bug some days ago: http://sourceforge.net/tracker/?func=detail&aid=3027356&group_id=170911&atid=856005 -> there are 2 solutions to it explained in the bug description and comment
3) still no clue :( The weird thing is that your stacktrace refers to "java.lang.NullPointerException at org.fosstrak.epcis.repository.query.QueryOperationsModule.<init>(QueryOperationsModule.java:143)", unfortunately there is nothing but javadoc at line 143 of QueryOperationsModule.java. Are you sure you're working with the latest source code? I will also try to run a clean install to see if I run into the same problem.
Regards,
Marco
________________________________________
From: mar...@or... [mar...@or...]
Sent: Friday, July 23, 2010 08:38
To: Steybe, Marco; nk...@ai...; acc...@li...
Subject: RE: Can't install latest snapshot with AIT's developments
Hi,
Yes I did the same first two steps. The only difference is I did not deploy from maven but directly by uploading/deploying the war on tomcat.
I tried again this morning on a blank win32 install with a new Tomcat (7.0) but I still have similar issues
1) on a blank Tomcat install, you have to add the mysql-connection jar in the /lib directory (I don't think it is written in Fosstrak's user guide). Or should it be in the epcis-repository lib dire'ctory?
2) I tried to create the database also on my Windows system (MySQL InnoDB / utf8), but the epcis_schema script makes the error : "Specified key was too long; max key length is 767 bytes" on the "create table subscription" phase
3) and anyhow, I still have the problem I initially quoted:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'queryOperationsModule' defined in ServletContext resource [/META-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:813)
Does it sound like a CXF problem? I know you updated CXF's version to 2.2, might it create that kind of issue?
Regards,
Marc-Antoine
-----Message d'origine-----
De : Steybe, Marco [mailto:st...@zu...]
Envoyé : jeudi 22 juillet 2010 18:11
À : Nikos Kefalakis; MOUILLERON Marc-Antoine RD-BIZZ-SOP; acc...@li...
Objet : RE: Can't install latest snapshot with AIT's developments
Hi Marc-Antoine,
I was able to test a full roundtrip using the new Master data capture interface. Here is what I did:
- updated my local code to the latest SVN revision (I already had a working MySQL instance and a Tomcat running)
- mvn clean install
- mvn tomcat:redeploy -> the application was successfully started without complaints
- sent a master data vocabulary XML (type readPoint, id="MyReadPoint") to the capture interface -> it was successfully stored to the EPCIS db
- captured an event with a readPoint reference to "MyReadPoint"
- queried the event -> the response included readPoint with id "MyReadPoint"
- queried master data for name "MyReadPoint" -> the response included the correct attribute/value pair
I'm also working on a win32 machine ...
So, at least from this simple test the new interface seems to work quite nicely :) Thanks Nikos!
Regarding your problem, Marc-Antoine, I'm afraid I can't help much either. Are you also working with the maven commands to build and deploy the application?
Regards,
Marco
________________________________________
From: Nikos Kefalakis [nk...@ai...]
Sent: Thursday, July 22, 2010 17:28
To: mar...@or...; acc...@li...
Cc: Steybe, Marco
Subject: RE: Can't install latest snapshot with AIT's developments
Dear Marc-Antoine,
I have just finished downloading (with tortoise SVN), building and testing the latest EPCIS repository snapshot by following the directions at the Fosstrak site ("http://www.fosstrak.org/epcis/docs/developer-guide.html#Building and Deploying the Project") run the "mvn install", "mvn compile" and "mvn package"and using the database schema that comes with this EPCIS version (at "\apache-tomcat-6.0.24\webapps\epcis-repository-0.4.3-SNAPSHOT\WEB-INF\classes") into two different window XP 32bit machines (the one was clean install so the SVN local repository wasn't previously been downloaded and only the CATALINA_HOME, the JAVA_HOME, and the Maven environmental virables set up to the system) and I didn't face any problems or errors. I don't have the ability to test it at a Linux platform but I cant really think of a reason for the error you are describing. Just make sure that when you undeploy (delete from webapps) the previous version of the epcis-repository to have the tomcat running and that it has not left any "remainder" before deploying the new version.
Best Regards,
Nikos Kefalakis
Athens Information Technology
Tel.: +30 210 668 2755
From: mar...@or... [mailto:mar...@or...]
Sent: ??????, 22 ??????? 2010 3:20 ??
To: acc...@li...
Cc: nk...@ai...; st...@zu...
Subject: Can't install latest snapshot with AIT's developments
Hello Nikos,
I downloaded the latest EPCIS repository snapshot yesterday, compiled it, and tried to install it on a Linux server with usual Tomcat/MySQL version.
The war extracts successfully but the application won't start.
I made several tries with different MySQL databases, then I finished with following the steps from the Fosstrak user manual (sample "epcis" database).
I have the following error message (attached is the full epcis-repository.log). Any idea of the reason for it?
[org.springframework.web.context.ContextLoader:215] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'queryOperationsModule' defined in ServletContext resource [/META-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:813)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:769)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:412)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383)
at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:400)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:627)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:98)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:807)
... 39 more
Caused by: java.lang.NullPointerException at org.fosstrak.epcis.repository.query.QueryOperationsModule.<init>(QueryOperationsModule.java:143)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:83)
... 41 more
INFO (2010-07-22 14:09:59,525) [org.fosstrak.epcis.repository.RepositoryContextListener:94] - Fosstrak EPCIS Repository application shut down
[cid:image001.gif@01CB29C6.1BADF5C0]
Marc-Antoine Mouilleron
Orange Labs - Business Services
905 rue Albert Einstein
06921 Sophia-Antipolis Cedex - France
tel. +33 (0)4 92 94 53 10
mob. +33 6 32 29 88 79
fax +33 (0)4 93 65 35 91
mar...@or...<mailto:mar...@or...>
[cid:image002.gif@01CB29C6.1BADF5C0]
|
|
From: Steybe, M. <st...@zu...> - 2010-07-23 07:38:29
|
Hi Marc-Antoine, 1) that's right the mysql connector jar needs to be placed in the tomcat's lib directory (it's explained in the user's guide "Setting up your own Repository") 2) this problem was reported as a bug some days ago: http://sourceforge.net/tracker/?func=detail&aid=3027356&group_id=170911&atid=856005 -> there are 2 solutions to it explained in the bug description and comment 3) still no clue :( The weird thing is that your stacktrace refers to "java.lang.NullPointerException at org.fosstrak.epcis.repository.query.QueryOperationsModule.<init>(QueryOperationsModule.java:143)", unfortunately there is nothing but javadoc at line 143 of QueryOperationsModule.java. Are you sure you're working with the latest source code? I will also try to run a clean install to see if I run into the same problem. Regards, Marco ________________________________________ From: mar...@or... [mar...@or...] Sent: Friday, July 23, 2010 08:38 To: Steybe, Marco; nk...@ai...; acc...@li... Subject: RE: Can't install latest snapshot with AIT's developments Hi, Yes I did the same first two steps. The only difference is I did not deploy from maven but directly by uploading/deploying the war on tomcat. I tried again this morning on a blank win32 install with a new Tomcat (7.0) but I still have similar issues 1) on a blank Tomcat install, you have to add the mysql-connection jar in the /lib directory (I don't think it is written in Fosstrak's user guide). Or should it be in the epcis-repository lib dire'ctory? 2) I tried to create the database also on my Windows system (MySQL InnoDB / utf8), but the epcis_schema script makes the error : "Specified key was too long; max key length is 767 bytes" on the "create table subscription" phase 3) and anyhow, I still have the problem I initially quoted: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'queryOperationsModule' defined in ServletContext resource [/META-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:813) Does it sound like a CXF problem? I know you updated CXF's version to 2.2, might it create that kind of issue? Regards, Marc-Antoine -----Message d'origine----- De : Steybe, Marco [mailto:st...@zu...] Envoyé : jeudi 22 juillet 2010 18:11 À : Nikos Kefalakis; MOUILLERON Marc-Antoine RD-BIZZ-SOP; acc...@li... Objet : RE: Can't install latest snapshot with AIT's developments Hi Marc-Antoine, I was able to test a full roundtrip using the new Master data capture interface. Here is what I did: - updated my local code to the latest SVN revision (I already had a working MySQL instance and a Tomcat running) - mvn clean install - mvn tomcat:redeploy -> the application was successfully started without complaints - sent a master data vocabulary XML (type readPoint, id="MyReadPoint") to the capture interface -> it was successfully stored to the EPCIS db - captured an event with a readPoint reference to "MyReadPoint" - queried the event -> the response included readPoint with id "MyReadPoint" - queried master data for name "MyReadPoint" -> the response included the correct attribute/value pair I'm also working on a win32 machine ... So, at least from this simple test the new interface seems to work quite nicely :) Thanks Nikos! Regarding your problem, Marc-Antoine, I'm afraid I can't help much either. Are you also working with the maven commands to build and deploy the application? Regards, Marco ________________________________________ From: Nikos Kefalakis [nk...@ai...] Sent: Thursday, July 22, 2010 17:28 To: mar...@or...; acc...@li... Cc: Steybe, Marco Subject: RE: Can't install latest snapshot with AIT's developments Dear Marc-Antoine, I have just finished downloading (with tortoise SVN), building and testing the latest EPCIS repository snapshot by following the directions at the Fosstrak site (“http://www.fosstrak.org/epcis/docs/developer-guide.html#Building and Deploying the Project”) run the “mvn install”, “mvn compile” and “mvn package”and using the database schema that comes with this EPCIS version (at “\apache-tomcat-6.0.24\webapps\epcis-repository-0.4.3-SNAPSHOT\WEB-INF\classes”) into two different window XP 32bit machines (the one was clean install so the SVN local repository wasn’t previously been downloaded and only the CATALINA_HOME, the JAVA_HOME, and the Maven environmental virables set up to the system) and I didn’t face any problems or errors. I don’t have the ability to test it at a Linux platform but I cant really think of a reason for the error you are describing. Just make sure that when you undeploy (delete from webapps) the previous version of the epcis-repository to have the tomcat running and that it has not left any “remainder” before deploying the new version. Best Regards, Nikos Kefalakis Athens Information Technology Tel.: +30 210 668 2755 From: mar...@or... [mailto:mar...@or...] Sent: Πέμπτη, 22 Ιουλίου 2010 3:20 μμ To: acc...@li... Cc: nk...@ai...; st...@zu... Subject: Can't install latest snapshot with AIT's developments Hello Nikos, I downloaded the latest EPCIS repository snapshot yesterday, compiled it, and tried to install it on a Linux server with usual Tomcat/MySQL version. The war extracts successfully but the application won't start. I made several tries with different MySQL databases, then I finished with following the steps from the Fosstrak user manual (sample "epcis" database). I have the following error message (attached is the full epcis-repository.log). Any idea of the reason for it? [org.springframework.web.context.ContextLoader:215] - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'queryOperationsModule' defined in ServletContext resource [/META-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:813) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:769) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:412) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:400) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369) at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:627) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) 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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:98) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:807) ... 39 more Caused by: java.lang.NullPointerException at org.fosstrak.epcis.repository.query.QueryOperationsModule.<init>(QueryOperationsModule.java:143) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:83) ... 41 more INFO (2010-07-22 14:09:59,525) [org.fosstrak.epcis.repository.RepositoryContextListener:94] - Fosstrak EPCIS Repository application shut down [cid:image001.gif@01CB29C6.1BADF5C0] Marc-Antoine Mouilleron Orange Labs - Business Services 905 rue Albert Einstein 06921 Sophia-Antipolis Cedex - France tel. +33 (0)4 92 94 53 10 mob. +33 6 32 29 88 79 fax +33 (0)4 93 65 35 91 mar...@or...<mailto:mar...@or...> [cid:image002.gif@01CB29C6.1BADF5C0] |
|
From: <mar...@or...> - 2010-07-23 06:40:59
|
Hi, Yes I did the same first two steps. The only difference is I did not deploy from maven but directly by uploading/deploying the war on tomcat. I tried again this morning on a blank win32 install with a new Tomcat (7.0) but I still have similar issues 1) on a blank Tomcat install, you have to add the mysql-connection jar in the /lib directory (I don't think it is written in Fosstrak's user guide). Or should it be in the epcis-repository lib dire'ctory? 2) I tried to create the database also on my Windows system (MySQL InnoDB / utf8), but the epcis_schema script makes the error : "Specified key was too long; max key length is 767 bytes" on the "create table subscription" phase 3) and anyhow, I still have the problem I initially quoted: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'queryOperationsModule' defined in ServletContext resource [/META-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:813) Does it sound like a CXF problem? I know you updated CXF's version to 2.2, might it create that kind of issue? Regards, Marc-Antoine -----Message d'origine----- De : Steybe, Marco [mailto:st...@zu...] Envoyé : jeudi 22 juillet 2010 18:11 À : Nikos Kefalakis; MOUILLERON Marc-Antoine RD-BIZZ-SOP; acc...@li... Objet : RE: Can't install latest snapshot with AIT's developments Hi Marc-Antoine, I was able to test a full roundtrip using the new Master data capture interface. Here is what I did: - updated my local code to the latest SVN revision (I already had a working MySQL instance and a Tomcat running) - mvn clean install - mvn tomcat:redeploy -> the application was successfully started without complaints - sent a master data vocabulary XML (type readPoint, id="MyReadPoint") to the capture interface -> it was successfully stored to the EPCIS db - captured an event with a readPoint reference to "MyReadPoint" - queried the event -> the response included readPoint with id "MyReadPoint" - queried master data for name "MyReadPoint" -> the response included the correct attribute/value pair I'm also working on a win32 machine ... So, at least from this simple test the new interface seems to work quite nicely :) Thanks Nikos! Regarding your problem, Marc-Antoine, I'm afraid I can't help much either. Are you also working with the maven commands to build and deploy the application? Regards, Marco ________________________________________ From: Nikos Kefalakis [nk...@ai...] Sent: Thursday, July 22, 2010 17:28 To: mar...@or...; acc...@li... Cc: Steybe, Marco Subject: RE: Can't install latest snapshot with AIT's developments Dear Marc-Antoine, I have just finished downloading (with tortoise SVN), building and testing the latest EPCIS repository snapshot by following the directions at the Fosstrak site (“http://www.fosstrak.org/epcis/docs/developer-guide.html#Building and Deploying the Project”) run the “mvn install”, “mvn compile” and “mvn package”and using the database schema that comes with this EPCIS version (at “\apache-tomcat-6.0.24\webapps\epcis-repository-0.4.3-SNAPSHOT\WEB-INF\classes”) into two different window XP 32bit machines (the one was clean install so the SVN local repository wasn’t previously been downloaded and only the CATALINA_HOME, the JAVA_HOME, and the Maven environmental virables set up to the system) and I didn’t face any problems or errors. I don’t have the ability to test it at a Linux platform but I cant really think of a reason for the error you are describing. Just make sure that when you undeploy (delete from webapps) the previous version of the epcis-repository to have the tomcat running and that it has not left any “remainder” before deploying the new version. Best Regards, Nikos Kefalakis Athens Information Technology Tel.: +30 210 668 2755 From: mar...@or... [mailto:mar...@or...] Sent: Πέμπτη, 22 Ιουλίου 2010 3:20 μμ To: acc...@li... Cc: nk...@ai...; st...@zu... Subject: Can't install latest snapshot with AIT's developments Hello Nikos, I downloaded the latest EPCIS repository snapshot yesterday, compiled it, and tried to install it on a Linux server with usual Tomcat/MySQL version. The war extracts successfully but the application won't start. I made several tries with different MySQL databases, then I finished with following the steps from the Fosstrak user manual (sample "epcis" database). I have the following error message (attached is the full epcis-repository.log). Any idea of the reason for it? [org.springframework.web.context.ContextLoader:215] - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'queryOperationsModule' defined in ServletContext resource [/META-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:813) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:769) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:412) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:400) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369) at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:627) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) 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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:98) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:807) ... 39 more Caused by: java.lang.NullPointerException at org.fosstrak.epcis.repository.query.QueryOperationsModule.<init>(QueryOperationsModule.java:143) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:83) ... 41 more INFO (2010-07-22 14:09:59,525) [org.fosstrak.epcis.repository.RepositoryContextListener:94] - Fosstrak EPCIS Repository application shut down [cid:image001.gif@01CB29C6.1BADF5C0] Marc-Antoine Mouilleron Orange Labs - Business Services 905 rue Albert Einstein 06921 Sophia-Antipolis Cedex - France tel. +33 (0)4 92 94 53 10 mob. +33 6 32 29 88 79 fax +33 (0)4 93 65 35 91 mar...@or...<mailto:mar...@or...> [cid:image002.gif@01CB29C6.1BADF5C0] |
|
From: Steybe, M. <st...@zu...> - 2010-07-22 16:10:59
|
Hi Marc-Antoine, I was able to test a full roundtrip using the new Master data capture interface. Here is what I did: - updated my local code to the latest SVN revision (I already had a working MySQL instance and a Tomcat running) - mvn clean install - mvn tomcat:redeploy -> the application was successfully started without complaints - sent a master data vocabulary XML (type readPoint, id="MyReadPoint") to the capture interface -> it was successfully stored to the EPCIS db - captured an event with a readPoint reference to "MyReadPoint" - queried the event -> the response included readPoint with id "MyReadPoint" - queried master data for name "MyReadPoint" -> the response included the correct attribute/value pair I'm also working on a win32 machine ... So, at least from this simple test the new interface seems to work quite nicely :) Thanks Nikos! Regarding your problem, Marc-Antoine, I'm afraid I can't help much either. Are you also working with the maven commands to build and deploy the application? Regards, Marco ________________________________________ From: Nikos Kefalakis [nk...@ai...] Sent: Thursday, July 22, 2010 17:28 To: mar...@or...; acc...@li... Cc: Steybe, Marco Subject: RE: Can't install latest snapshot with AIT's developments Dear Marc-Antoine, I have just finished downloading (with tortoise SVN), building and testing the latest EPCIS repository snapshot by following the directions at the Fosstrak site (“http://www.fosstrak.org/epcis/docs/developer-guide.html#Building and Deploying the Project”) run the “mvn install”, “mvn compile” and “mvn package”and using the database schema that comes with this EPCIS version (at “\apache-tomcat-6.0.24\webapps\epcis-repository-0.4.3-SNAPSHOT\WEB-INF\classes”) into two different window XP 32bit machines (the one was clean install so the SVN local repository wasn’t previously been downloaded and only the CATALINA_HOME, the JAVA_HOME, and the Maven environmental virables set up to the system) and I didn’t face any problems or errors. I don’t have the ability to test it at a Linux platform but I cant really think of a reason for the error you are describing. Just make sure that when you undeploy (delete from webapps) the previous version of the epcis-repository to have the tomcat running and that it has not left any “remainder” before deploying the new version. Best Regards, Nikos Kefalakis Athens Information Technology Tel.: +30 210 668 2755 From: mar...@or... [mailto:mar...@or...] Sent: Πέμπτη, 22 Ιουλίου 2010 3:20 μμ To: acc...@li... Cc: nk...@ai...; st...@zu... Subject: Can't install latest snapshot with AIT's developments Hello Nikos, I downloaded the latest EPCIS repository snapshot yesterday, compiled it, and tried to install it on a Linux server with usual Tomcat/MySQL version. The war extracts successfully but the application won't start. I made several tries with different MySQL databases, then I finished with following the steps from the Fosstrak user manual (sample "epcis" database). I have the following error message (attached is the full epcis-repository.log). Any idea of the reason for it? [org.springframework.web.context.ContextLoader:215] - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'queryOperationsModule' defined in ServletContext resource [/META-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:813) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:769) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:412) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:400) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369) at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:627) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) 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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.fosstrak.epcis.repository.query.QueryOperationsModule]: Constructor threw exception; nested exception is java.lang.NullPointerException at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:98) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:807) ... 39 more Caused by: java.lang.NullPointerException at org.fosstrak.epcis.repository.query.QueryOperationsModule.<init>(QueryOperationsModule.java:143) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:83) ... 41 more INFO (2010-07-22 14:09:59,525) [org.fosstrak.epcis.repository.RepositoryContextListener:94] - Fosstrak EPCIS Repository application shut down [cid:image001.gif@01CB29C6.1BADF5C0] Marc-Antoine Mouilleron Orange Labs - Business Services 905 rue Albert Einstein 06921 Sophia-Antipolis Cedex - France tel. +33 (0)4 92 94 53 10 mob. +33 6 32 29 88 79 fax +33 (0)4 93 65 35 91 mar...@or...<mailto:mar...@or...> [cid:image002.gif@01CB29C6.1BADF5C0] |
|
From: Nikos K. <nk...@ai...> - 2010-07-20 19:21:12
|
Dear all, I would like to announce that the latest Fosstrak EPCIS Repository revision supports the MasterData document capture functionality. This new Capture functionality is not defined at the EPCIS specification and uses the available EPCIS, standard defined, capture interface without affecting its Event capture functionality. For now it is available by using the "epcis-commons" Revision 1724 and the "epcis-repository" Revision 1725 from Fosstraks Source code SVN repository (https://svn.fosstrak.org/repos/epcis/trunk). For the "epcis-commons" (Revision 1724) the "@XmlRootElement" annotation was added at 4 epcis's objects. More spessifically the AggregationEvent, the TransactionEvent, the QuantityEvent and the ObjectEvent (e.g. @XmlRootElement(name = "ObjectEvent", namespace = ""). For the "epcis-repository" (Revision 1725) a numerous of required changes/additions were made to support the Master Data Document capture functionality and the way Vocabulary's children are stored to the database was also been changed (they were divided with the "_" sign and now the "," sign is used) So now, for example, to save to the EPCIS repository the "Some_Test_Vocabulary_URI", as the Vocabulary element URI, to the Read Point Vocabulary (urn:epcglobal:epcis:vtype:ReadPoint) with the "Some_Test_Vocabulary_Attr_Name", as the Vocabulary Element's Attribute name, and the "Some_Test_Vocabulary_Attr_Value", as the Vocabulary Element's Attribute value, the following, EPCISMasterDataDocument compliant, XML should be sent to the EPCIS's Capture I/F: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ns4:EPCISMasterDataDocument creationDate="2010-07-20T20:22:50.718+03:00" schemaVersion="1.0" xmlns:ns2="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHe ader" xmlns:ns4="urn:epcglobal:epcis-masterdata:xsd:1" xmlns:ns3="urn:epcglobal:epcis-query:xsd:1" xmlns:ns5="urn:epcglobal:epcis:xsd:1"> <EPCISBody> <VocabularyList> <Vocabulary type="urn:epcglobal:epcis:vtype:ReadPoint"> <VocabularyElementList> <VocabularyElement id="Some_Test_Vocabulary_URI"> <attribute id="urn:epcglobal:epcis:mda:Some_Test_Vocabulary_Attr_Name" value="Some_Test_Vocabulary_Attr_Value"/> </VocabularyElement> </VocabularyElementList> </Vocabulary> </VocabularyList> </EPCISBody> </ns4:EPCISMasterDataDocument> Now if we would like to delete it we should sent the following: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ns4:EPCISMasterDataDocument creationDate="2010-07-20T20:27:01.781+03:00" schemaVersion="1.0" xmlns:ns2="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHe ader" xmlns:ns4="urn:epcglobal:epcis-masterdata:xsd:1" xmlns:ns3="urn:epcglobal:epcis-query:xsd:1" xmlns:ns5="urn:epcglobal:epcis:xsd:1"> <EPCISBody> <VocabularyList> <Vocabulary type="urn:epcglobal:epcis:vtype:ReadPoint"> <VocabularyElementList> <VocabularyElement id="Some_Test_Vocabulary_URI" mode="3"/> </VocabularyElementList> </Vocabulary> </VocabularyList> </EPCISBody> </ns4:EPCISMasterDataDocument> Many more xml MasterData capturing "commands" are supported from the EPCIS's Master Data capture I/F which are, for your convenience, created from the Master Data capture client and the following methods: - alterVocElem (String vocabularyType, String oldVocabularyElementURI, String newVocabularyElementURI) Which is used to alter a vocabulary's Element URI. - insertVocElem (String vocabularyType, String vocabularyElementURI) Which is used to insert a vocabulary's Element. - massInsertVocElem (String vocabularyType, ArrayList<String> vocabularyElementURIs) Which is used to insert many vocabulary's Elements. - deleteVocElem (String vocabularyType, String vocabularyElementURI) Which is used to delete a vocabulary's Element (When using single delete only the element with its attributes will be deleted). - massDeleteVocElem (String vocabularyType, ArrayList<String> vocabularyElementURIs) Which is used to delete many vocabulary's Elements (When using mass delete only the listed elements with their attributes will be deleted). - deleteWithDescendantsVocElem (String vocabularyType, String vocabularyElementURI) Which is used to delete a vocabulary's Element with its direct or indirect descendants (The element with its attributes and with all of its children elements and its children's attributes will be deleted). - massDeleteWithDescendantsVocElem (String vocabularyType, ArrayList<String> vocabularyElementURIs) Which is used to delete many vocabulary's with their Elements and with their direct or indirect descendants. The elements with its attributes and with all of its children elements and its children's attributes will be deleted. - insertOrAlterVocElemAttr (String vocabularyType, String vocabularyElementURI, String vocabularyAttributeName, String vocabularyAttributeValue) Which is used to insert or Update a vocabulary Element's Attribute. If the Vocabulary is not inserted yet it will be inserted. The vocabularyElementURI, vocabularyAttributeName pair should be unique so if it already exists it will be changed to the vocabularyAttribute entered or simply rewrite it. - massInsertOrAlterVocElemAttr (String vocabularyType, String vocabularyElementURI, HashMap<String, String> vocabularyAttributes) Which is used to mass Insert or Update a vocabulary Element's Attributes. If the Vocabulary is not inserted yet it will be inserted. The vocabularyElementURI, vocabularyAttributeName pair (the vocabularyAttributeName is the key of the vocabularyAttributes HashMap) should be unique so if it already exists it will be changed to the vocabularyAttributeValue (which is the value of the vocabularyAttributes HashMap) entered or simply rewrite it. - deleteVocElemAttr (String vocabularyType, String vocabularyElementURI, String vocabularyAttributeName) Which is used to delete a vocabulary Element's Attribute. - massDeleteVocElemAttr (String vocabularyType, String vocabularyElementURI, ArrayList<String> vocabularyAttributeNames) Which is used to delete many vocabulary Element's Attributes. The latest MasterDataCaptureClient.java class can be found here: http://websvn.ow2.org/filedetails.php?repname=aspire <http://websvn.ow2.org/filedetails.php?repname=aspire&path=%2Ftrunk%2Ftools% 2FaspireRfidMasterDataCaptureClient%2Fsrc%2Fmain%2Fjava%2Forg%2Fow2%2Faspire rfid%2Fmasterdata%2Fcapture%2FMasterDataCaptureClient.java> &path=%2Ftrunk%2Ftools%2FaspireRfidMasterDataCaptureClient%2Fsrc%2Fmain%2Fja va%2Forg%2Fow2%2Faspirerfid%2Fmasterdata%2Fcapture%2FMasterDataCaptureClient .java And a demo Master Data capture application (source code) can be downloaded from here: svn://svn.forge.objectweb.org/svnroot/aspire/trunk/tools/aspireRfidMasterDat aCaptureClient And its executable from here: http://forge.ow2.org/project/download.php?group_id=324 <http://forge.ow2.org/project/download.php?group_id=324&file_id=15375> &file_id=15375 Moreover the Fosstrak EPCIS MasterData can now be edited with the use of AspireRFID Master Data Editor plug-in (http://wiki.aspire.ow2.org/xwiki/bin/view/Main.Documentation.AspireIDE/Mast erDataEditor) Please feel free to test the MasterData capture I/F and report for any existing bugs. Also due to the number of changes that has been done to the EPCIS's Capture I/F also check if everything is working normally at the Event capture I/F also (the test from my side didn't showed anything wrong). One probable bug, that was noticed from the previous EPCIS revision (without the MasterData capture changes been applied), is that for accessing the EPCIS's repository Query interface it requires to add the "query/query" after the EPCIS's address (e.g. for the current version the following URL should be use (http://localhost:8080/epcis-repository-0.4.3-SNAPSHOT/query/query). Is that normal? Best Regards, Nikos Kefalakis AspireRFID Solution architect and lead developer AIT (http://www.ait.gr/) AspireRFID (http://wiki.aspire.ow2.org/) FAX: +30 210 668 2703 Tel.: +30 210 668 2755 |
|
From: SourceForge.net <no...@so...> - 2010-07-12 08:03:29
|
Bugs item #3027356, was opened at 2010-07-09 14:15 Message generated for change (Comment added) made by maxcimo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3027356&group_id=170911 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: epcis-repository >Group: v0.4 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Markus Mahlberg (mmahlberg) Assigned to: Nobody/Anonymous (nobody) Summary: Documentation: CREATE DATABSE needs to be expanded Initial Comment: In the Installation instructions the "CREATE DATABASE epcis" instruction should be changed to "CREATE DATABASE epcis DEFAULT CHARSET latin1" since the a primary Key varchar(767) using UTF-8 would exceed the maximum supported length and there are quite some MySQL packages around which use UTF-8 by default. ---------------------------------------------------------------------- >Comment By: Marco Steybe (maxcimo) Date: 2010-07-12 10:03 Message: Thanks for the hint! Ok, I see that in MySQL primary keys are limited to 1000 bytes. Since MySQL requires 3 bytes per char for the default UTF-8 encoding, a primary key can be max VARCHAR(333) which conflicts with the VARCHAR(767) that we have for the "subscription" table. I think we should not change the default encoding of the db, instead re-think the primary key statement for the "subscription" table. The key for this table is exactly what a client provides as the subscriptionID string when talking to the EPCISQueryControlInterface. The spec does not limit the length of this string and just says it's an "arbitrary string". >From my point of view 255 bytes (85 chars) is enough for an id string, thus, we could change the table declaration like this: CREATE TABLE subscription ( subscriptionid varchar(255) NOT NULL PRIMARY KEY, ...); Any other thoughts? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3027356&group_id=170911 |
|
From: SourceForge.net <no...@so...> - 2010-07-09 12:15:11
|
Bugs item #3027356, was opened at 2010-07-09 14:15 Message generated for change (Tracker Item Submitted) made by mmahlberg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3027356&group_id=170911 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Markus Mahlberg (mmahlberg) Assigned to: Nobody/Anonymous (nobody) Summary: Documentation: CREATE DATABSE needs to be expanded Initial Comment: In the Installation instructions the "CREATE DATABASE epcis" instruction should be changed to "CREATE DATABASE epcis DEFAULT CHARSET latin1" since the a primary Key varchar(767) using UTF-8 would exceed the maximum supported length and there are quite some MySQL packages around which use UTF-8 by default. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3027356&group_id=170911 |
|
From: SourceForge.net <no...@so...> - 2010-07-05 12:39:33
|
Bugs item #3025434, was opened at 2010-07-05 14:39 Message generated for change (Tracker Item Submitted) made by don-calzone You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3025434&group_id=170911 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Don-Calzone (don-calzone) Assigned to: Nobody/Anonymous (nobody) Summary: NonUniqueResultException when send parallel requests Initial Comment: Using an EPCIS 0.4.2 with a MySQL backend the following exception is thrown in the capture module when an event is processed: ERROR (2010-07-05 13:49:08,084) [org.fosstrak.epcis.repository.capture.CaptureOperationsModule:315] - EPCIS Capture Interface request failed: org.hibernate.NonUniqueResultException: query did not return a unique result: 2 org.hibernate.NonUniqueResultException: query did not return a unique result: 2 at org.hibernate.impl.AbstractQueryImpl.uniqueElement(AbstractQueryImpl.java:820) at org.hibernate.impl.CriteriaImpl.uniqueResult(CriteriaImpl.java:305) at org.fosstrak.epcis.repository.capture.CaptureOperationsModule.getOrInsertVocabularyElement(CaptureOperationsModule.java:692) at org.fosstrak.epcis.repository.capture.CaptureOperationsModule.handleBizTransactions(CaptureOperationsModule.java:640) at org.fosstrak.epcis.repository.capture.CaptureOperationsModule.handleEvent(CaptureOperationsModule.java:434) at org.fosstrak.epcis.repository.capture.CaptureOperationsModule.handleDocument(CaptureOperationsModule.java:351) at org.fosstrak.epcis.repository.capture.CaptureOperationsModule.doCapture(CaptureOperationsModule.java:296) at org.fosstrak.epcis.repository.capture.CaptureOperationsServlet.doPost(CaptureOperationsServlet.java:261) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:619) The point is that when two events are processed parallel which have either the same read point, biz step, biz location, biz trans, biz trans type or disposition the vocabulary is created twice. This results in this exception for other events. The JMeter testplan to reproduce this bug, the used data, and the epcis log file with one thread and multiple threads are supplied as attachments. Best regards from the EPIC chair at the HPI ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=856005&aid=3025434&group_id=170911 |